Il 22/08/24 20:36, Eli Schwartz ha scritto:
On 8/22/24 11:38 AM, ralfconn wrote:
Il 22/08/24 06:50, Eli Schwartz ha scritto:
emerging portage itself, will require gnupg as a dependency, and in
turn that means app-crypt/pinentry If pinentry is built with
USE=keyring, it requires app-crypt/libsecret, which in turn has a
PDEPEND for virtual/secret-service, so that you can actually have
something implementing a keyring. There are exactly two current
implementations of a secret-service API provider: - gnome-keyring -
keepassxc And that is how keepassxc comes to be a "dependency" of the
@system set. Due to optional USE flags. :)
That makes sense, thanks (wow, it is complicated!)but there must be
something else because here:
- pinentry does not USE keyring:
# eix -I pinentry [I] app-crypt/pinentry Available versions: 1.2.1-r7
(~)1.2.1-r8 (~)1.3.0-r3 (~)1.3.1 {X caps efl emacs gtk keyring ncurses
qt5 qt6 verify-sig wayland} Installed versions: 1.3.1(16:25:28
07/06/24)(X gtk ncurses qt5 -caps -efl -emacs -keyring -qt6 -verify-sig
-wayland)
Dunno then. You can try emerge -cpv keepassxc app-crypt/libsecret
virtual/secret-service and trace the reported blockers yourself if
you're really curious. :D
Looks like it _is_ portage:
app-admin/keepassxc-2.7.9 pulled in by:
virtual/secret-service-0 requires app-admin/keepassxc
virtual/secret-service-0 pulled in by:
app-crypt/libsecret-0.21.1 requires =virtual/secret-service-0,
virtual/secret-service
app-crypt/libsecret-0.21.1 pulled in by:
app-crypt/gcr-3.41.1-r2 requires >=app-crypt/libsecret-0.20
app-crypt/gcr-4.2.1 requires >=app-crypt/libsecret-0.20
app-crypt/gcr-4.2.1 pulled in by:
app-crypt/pinentry-1.3.1 requires app-crypt/gcr:4[gtk]
app-crypt/pinentry-1.3.1 pulled in by:
app-crypt/gnupg-2.4.5-r2 requires app-crypt/pinentry
app-crypt/gnupg-2.4.5-r2 pulled in by:
app-crypt/gcr-3.41.1-r2 requires app-crypt/gnupg
app-crypt/gcr-4.2.1 requires app-crypt/gnupg
app-crypt/gpgme-1.23.2 requires >=app-crypt/gnupg-2
app-portage/gemato-20.6 requires >=app-crypt/gnupg-2.2.20-r1[ssl]
app-portage/getuto-1.13 requires app-crypt/gnupg
dev-vcs/git-2.46.0 requires app-crypt/gnupg
sys-apps/portage-3.0.65-r1 requires >=app-crypt/gnupg-2.2.4-r2[ssl(-)]
There it is, portage requires gnupg, which requires pinentry, blah blah
up to keepassxc. So exactly as you explained in your first reply except
that it happens even without USE=keyring.
BTW looks like a circular dependency there: gcr->pinentry->gnupg->gcr
- portage is not in @system:
Ah, but virtual/package-manager *is* in @system, and depends on your
choice of portage or pkgcore but in practice always portage...
Right!
raffaele
