As in summary. pinentry ebuild has wrong RDEPEND gnome-keyring? conditional dep. Reproducible: Always Steps to Reproduce: 1. make sure no gnome-keyring, pinentry, gnupg and gcr installed. 2. emerge -pvt gnome-keyring pinentry app-crypt/gnupg gcr 3. notice circ dep as in Actual results 4. in pintenty ebuild move RDEPEND on gnome-keyring to PDEPEND. this allows to break circ dep. Actual Results: [nomerge ] gnome-base/gnome-keyring-3.16.0-r1::gentoo USE="caps filecaps pam ssh-agent -debug (-selinux) {-test}" [ebuild N ] app-crypt/pinentry-0.9.7::gentoo USE="gnome-keyring gtk ncurses -caps -emacs -qt4 -qt5 -static" 0 KiB [ebuild N ] app-crypt/gcr-3.16.0:0/1::gentoo USE="gtk introspection vala -debug {-test}" 0 KiB [ebuild N ] app-crypt/gnupg-2.0.30::gentoo USE="bzip2 mta nls readline -doc -ldap (-selinux) -smartcard -static -tools -usb" 0 KiB [nomerge ] dev-vcs/git-2.9.0::gentoo USE="blksha1 curl gnome-keyring gpg gtk iconv nls pcre perl python threads webdav -cgi -cvs -doc -emacs -highlight -libressl -mediawiki -mediawiki-experimental (-ppcsha1) -subversion {-test} -tk -xinetd" LINGUAS="-bg -ca -de -fr -is -it -ko -pt_PT -ru -sv -vi -zh_CN" PYTHON_TARGETS="python2_7" [ebuild N ] gnome-base/libgnome-keyring-3.12.0::gentoo USE="introspection -debug {-test} -vala" 0 KiB [ebuild N ] gnome-base/gnome-keyring-3.16.0-r1::gentoo USE="caps filecaps pam ssh-agent -debug (-selinux) {-test}" 0 KiB Total: 6 packages (6 new), Size of downloads: 0 KiB * Error: circular dependencies: (app-crypt/gcr-3.16.0:0/1::gentoo, ebuild scheduled for merge) depends on (app-crypt/gnupg-2.0.30:0/0::gentoo, ebuild scheduled for merge) (buildtime) (app-crypt/pinentry-0.9.7:0/0::gentoo, ebuild scheduled for merge) (buildtime) (app-crypt/gcr-3.16.0:0/1::gentoo, ebuild scheduled for merge) (runtime)
(In reply to Oleg from comment #0) > As in summary. pinentry ebuild has wrong RDEPEND gnome-keyring? conditional > dep. No, I still haven't gotten a clear answer as to why gcr require gnupg c.f bug 570512 comment 7. Until I do I consider this a gcr bug hence assigning it to gnome
gcr is not requiring gnupg for some time :/
(In reply to Pacho Ramos from comment #2) > gcr is not requiring gnupg for some time :/ Then I'm missing something here... Of potential relevance might be http://lists.gnupg.org/pipermail/gnupg-devel/2016-August/031529.html that could reduce the subset of requirements. But I'm not sure if it helps us as we don't split the package anyways. Another alternative is of course just removing gnome3 support from pinentry and sticking to the normal input methods (gtk in this case) instead of a keyring style thing.
Well, the versions in the bug report are older... this should be checked in testing
(In reply to Pacho Ramos from comment #4) > Well, the versions in the bug report are older... this should be checked in > testing Ah. In that case it sounds like this can be closed if the respective versions are in stable
they are being stabilized in bug 587010
