Summary: | circular dependency with gnome-base/gnome-keyring app-crypt/pinentry app-crypt/gcr and app-crypt/gnupg | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Oleh <moonlapse81> |
Component: | Current packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | crypto+disabled, jstein |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=560322 https://bugs.gentoo.org/show_bug.cgi?id=570512 |
||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Oleh
2016-07-26 11:24:46 UTC
(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 |