eject has RDEPEND="|| ( >=sys-apps/util-linux-2.22 sys-block/eject-bsd )" and 2.3.20 interprets the RDEPEND wrong since I'm getting emerge: there are no ebuilds to satisfy "sys-block/eject". as an error.
This has nothing to do with the virtual, someone forgot to remove the blocker for sys-block/eject from sys-apps/util-linux
Well, sys-block/eject doesn't exist. I believe it used to, but it's now part of util-linux, I would need to go verify that. But I reported this because sys-apps/portage-2.3.19-r1 works. 2.3.20 tries to pull in a non-existing package, 2.3.19-r1 does not.
I believe this rename is wrong, unless sys-block/eject is coming back, but that's been provided by util-linux since 2012 (it was removed in 2016.) Also, where is portage getting "sys-block/eject" from, that's not mentioned in virtual/eject-0. The only mention of "sys-block/eject" is the blocker in util-linux.
(In reply to Michael Cook from comment #3) > I believe this rename is wrong, unless sys-block/eject is coming back, but > that's been provided by util-linux since 2012 (it was removed in 2016.) > Also, where is portage getting "sys-block/eject" from, that's not mentioned > in virtual/eject-0. The only mention of "sys-block/eject" is the blocker in > util-linux. https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=cd3a0b27cd6e363978b1e27b5f8f8eae199715f5
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=20fc0e05f59fe9ee3da2cdf7aa3dcb33295cd362 commit 20fc0e05f59fe9ee3da2cdf7aa3dcb33295cd362 Author: Lars Wendler <polynomial-c@gentoo.org> AuthorDate: 2018-01-21 19:31:55 +0000 Commit: Lars Wendler <polynomial-c@gentoo.org> CommitDate: 2018-01-21 19:32:10 +0000 sys-apps/util-linux: Removed sys-block/eject blocker. The package is long gone from the tree. Closes: https://bugs.gentoo.org/645284 Package-Manager: Portage-2.3.20, Repoman-2.3.6 sys-apps/util-linux/util-linux-2.30.2.ebuild | 3 +-- sys-apps/util-linux/util-linux-2.31-r1.ebuild | 3 +-- sys-apps/util-linux/util-linux-2.31.1.ebuild | 1 - sys-apps/util-linux/util-linux-9999.ebuild | 3 +-- 4 files changed, 3 insertions(+), 7 deletions(-)
This is not fixed. Well the issue this was transformed into was fixed, but not the issue I reported. Doing emerge -uDN @world still giving me: emerge: there are no ebuilds to satisfy "sys-block/eject". (dependency required by "virtual/eject-0::gentoo" [installed]) (dependency required by "sys-fs/udisks-1.0.5-r1::gentoo" [installed]) (dependency required by "media-tv/kodi-9999::gentoo" [installed]) (dependency required by "@selected" [set]) (dependency required by "@world" [argument]) In order to satisfy virtual/eject portage is deciding to pull in sys-block/eject. This package is NOT referenced by virtual/eject, the stale blockers in sys-apps/util-linux are no longer present on my system and porage 2.3.20 is still magically finding sys-block/eject.
Can someone fix the title of this bug? I think my original name was good enough, but I guess not since devs completely misunderstood what I was reporting. Also, can someone re-assign to portage devs? This is a portage bug. Unless it's something specific to my set up, but I do not believe so.
This may be a dynamic-deps thing. Please try running "emerge --oneshot virtual/eject" to see if that resolves the issue.
*** This bug has been marked as a duplicate of bug 558458 ***
(In reply to Larry the Git Cow from comment #5) > commit 20fc0e05f59fe9ee3da2cdf7aa3dcb33295cd362 > Author: Lars Wendler <polynomial-c@gentoo.org> > AuthorDate: 2018-01-21 19:31:55 +0000 > Commit: Lars Wendler <polynomial-c@gentoo.org> > CommitDate: 2018-01-21 19:32:10 +0000 > > sys-apps/util-linux: Removed sys-block/eject blocker. > > The package is long gone from the tree. > > Closes: https://bugs.gentoo.org/645284 > Package-Manager: Portage-2.3.20, Repoman-2.3.6 > > sys-apps/util-linux/util-linux-2.30.2.ebuild | 3 +-- > sys-apps/util-linux/util-linux-2.31-r1.ebuild | 3 +-- > sys-apps/util-linux/util-linux-2.31.1.ebuild | 1 - > sys-apps/util-linux/util-linux-9999.ebuild | 3 +-- > 4 files changed, 3 insertions(+), 7 deletions(-) Dropping those blockers means that if anyone who hasn't updated in the last 15+ months still has sys-block/eject installed then they may experience a file collision when updating to latest util-linux.
(In reply to Michael Cook from comment #6) > This is not fixed. Well the issue this was transformed into was fixed, but > not the issue I reported. Doing emerge -uDN @world still giving me: > > emerge: there are no ebuilds to satisfy "sys-block/eject". > (dependency required by "virtual/eject-0::gentoo" [installed]) > (dependency required by "sys-fs/udisks-1.0.5-r1::gentoo" [installed]) > (dependency required by "media-tv/kodi-9999::gentoo" [installed]) > (dependency required by "@selected" [set]) > (dependency required by "@world" [argument]) > > In order to satisfy virtual/eject portage is deciding to pull in > sys-block/eject. This package is NOT referenced by virtual/eject, the stale > blockers in sys-apps/util-linux are no longer present on my system and > porage 2.3.20 is still magically finding sys-block/eject. Please attach the content of /var/db/pkg/virtual/eject-0/RDEPEND. You notice the problem with sys-apps/portage-2.3.20 because it defaults to --dynamic-deps=n. It's also possible to use the emerge --dynamic-deps=y or --changed-deps=y options as a workaround for this sort of issue.
(In reply to Zac Medico from comment #11) > (In reply to Michael Cook from comment #6) > > This is not fixed. Well the issue this was transformed into was fixed, but > > not the issue I reported. Doing emerge -uDN @world still giving me: > > > > emerge: there are no ebuilds to satisfy "sys-block/eject". > > (dependency required by "virtual/eject-0::gentoo" [installed]) > > (dependency required by "sys-fs/udisks-1.0.5-r1::gentoo" [installed]) > > (dependency required by "media-tv/kodi-9999::gentoo" [installed]) > > (dependency required by "@selected" [set]) > > (dependency required by "@world" [argument]) > > > > In order to satisfy virtual/eject portage is deciding to pull in > > sys-block/eject. This package is NOT referenced by virtual/eject, the stale > > blockers in sys-apps/util-linux are no longer present on my system and > > porage 2.3.20 is still magically finding sys-block/eject. > > Please attach the content of /var/db/pkg/virtual/eject-0/RDEPEND. > > You notice the problem with sys-apps/portage-2.3.20 because it defaults to > --dynamic-deps=n. > > It's also possible to use the emerge --dynamic-deps=y or --changed-deps=y > options as a workaround for this sort of issue. yep, that was the issue "|| ( sys-block/eject sys-block/eject-bsd )" I believe floppym's revbump should fix that, I will let you know if it doesn't.
(In reply to Michael Cook from comment #12) > (In reply to Zac Medico from comment #11) > > (In reply to Michael Cook from comment #6) > > > This is not fixed. Well the issue this was transformed into was fixed, but > > > not the issue I reported. Doing emerge -uDN @world still giving me: > > > > > > emerge: there are no ebuilds to satisfy "sys-block/eject". > > > (dependency required by "virtual/eject-0::gentoo" [installed]) > > > (dependency required by "sys-fs/udisks-1.0.5-r1::gentoo" [installed]) > > > (dependency required by "media-tv/kodi-9999::gentoo" [installed]) > > > (dependency required by "@selected" [set]) > > > (dependency required by "@world" [argument]) > > > > > > In order to satisfy virtual/eject portage is deciding to pull in > > > sys-block/eject. This package is NOT referenced by virtual/eject, the stale > > > blockers in sys-apps/util-linux are no longer present on my system and > > > porage 2.3.20 is still magically finding sys-block/eject. > > > > Please attach the content of /var/db/pkg/virtual/eject-0/RDEPEND. > > > > You notice the problem with sys-apps/portage-2.3.20 because it defaults to > > --dynamic-deps=n. > > > > It's also possible to use the emerge --dynamic-deps=y or --changed-deps=y > > options as a workaround for this sort of issue. > > yep, that was the issue "|| ( sys-block/eject sys-block/eject-bsd )" I > believe floppym's revbump should fix that, I will let you know if it doesn't. So if we run into more of these issues, should be be opening more revbump requests?
(In reply to Michael Cook from comment #13) > So if we run into more of these issues, should be be opening more revbump > requests? Yes, please do.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e4821e616033d658c494780b1ec66bdace912071 commit e4821e616033d658c494780b1ec66bdace912071 Author: Zac Medico <zmedico@gentoo.org> AuthorDate: 2018-01-22 02:27:14 +0000 Commit: Zac Medico <zmedico@gentoo.org> CommitDate: 2018-01-22 02:28:16 +0000 virtual/dev-manager: revbump to 0-r1 for dep changes Since sys-apps/portage-2.3.20 defaults to --dynamic-deps=n, this revbump is needed in order to correct the dependencies of installed instances of virtual/dev-manager. See: https://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/virtual/dev-manager/dev-manager-0.ebuild?view=log Bug: https://bugs.gentoo.org/645284 Package-Manager: Portage-2.3.20, Repoman-2.3.6 virtual/dev-manager/{dev-manager-0.ebuild => dev-manager-0-r1.ebuild} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)}
*** This bug has been marked as a duplicate of bug 645310 ***
