Hello,

On my system:
emerge -p @world | wc -l
198
emerge -ep @world | wc -l
1151
emerge -p @system | wc -l
56
emerge -ep @system | wc -l
502

The last one does not look right, in particular the list of packages
contains some from @world (e.g. keepassxc). I am running a local mixed
profile local:23.0-no-multilib-hardened-desktop which I thought could be
the culprit, but merely switching to default/linux/amd64/23.0 (without recompiling) does not change much the numbers. The same happens on
another box where the difference between -e @world and -e @system is
even more ridiculous (~750 vs ~500). Again there I use a mixed local
profile, something like local:23.0-hardened-desktop.

Could the mixed profile be the reason? What numbers do others have?

thanks,

raffaele

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------UQM01hAZoUJ66w6XXCQACNta
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 8/22/24 12:40 AM, ralfconn wrote:

Hello,

On my system:
emerge -p @world | wc -l
198
emerge -ep @world | wc -l
1151
emerge -p @system | wc -l
56
emerge -ep @system | wc -l
502

The last one does not look right, in particular the list of packages
contains some from @world (e.g. keepassxc). I am running a local mixed profile local:23.0-no-multilib-hardened-desktop which I thought could be
the culprit, but merely switching to default/linux/amd64/23.0 (without recompiling) does not change much the numbers. The same happens on
another box where the difference between -e @world and -e @system is
even more ridiculous (~750 vs ~500). Again there I use a mixed local
profile, something like local:23.0-hardened-desktop.

Could the mixed profile be the reason? What numbers do others have?

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. :)


--
Eli Schwartz


--------------UQM01hAZoUJ66w6XXCQACNta--

-----BEGIN PGP SIGNATURE-----

wnsEABYIACMWIQTnFNnmK0TPZHnXm3qEp9ErcA0vVwUCZsbDpQUDAAAAAAAKCRCEp9ErcA0vV8OH AP9K6fdpWLXrGydNCzP+MRgXElMm402mOxiIe6o8HnlvVQEAwWZfbGRtBfYYc5Y5dSuIoF5TVglD sXg4AWfFiKO3Kwk=
=uafr
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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)
- portage is not in @system:
# emerge -pv @system These are the packages that would be merged, in
order: Calculating dependencies... done! Dependency resolution took 1.90
s (backtrack: 0/20). [ebuild R ] sys-devel/gnuconfig-20240101::gentoo 76
KiB [ebuild R ] sys-apps/baselayout-2.15::gentoo USE="-build
(-split-usr)" 30 KiB [ebuild R ] sec-keys/openpgp-keys-gentoo-release-20240703::gentoo USE="-test" 19 KiB [ebuild R ] sys-apps/which-2.21::gentoo 146 KiB [ebuild R ] app-arch/xz-utils-5.6.2-r1::gentoo USE="extra-filters nls -doc -pgo -static-libs -verify-sig" 2301 KiB [ebuild R ]
virtual/os-headers-0-r2::gentoo 0 KiB [ebuild R ] app-shells/bash-5.2_p32::gentoo USE="net nls (readline) -afs -bashlogger -examples -mem-scramble -pgo -plugins -verify-sig" 10926 KiB [ebuild R ] sys-apps/gawk-5.3.0-r1::gentoo USE="nls readline -mpfr -pma -verify-sig"
3356 KiB [ebuild R ] sys-apps/less-661::gentoo USE="pcre -test" 634 KiB
[ebuild R ] virtual/man-0-r4::gentoo 0 KiB [ebuild R ] sys-apps/findutils-4.10.0::gentoo USE="nls (-selinux) -static -test -verify-sig" 2189 KiB [ebuild R ] sys-devel/patch-2.7.6-r5::gentoo
USE="xattr -static -test -verify-sig" 766 KiB [ebuild R ] sys-apps/diffutils-3.10::gentoo USE="nls -verify-sig" 1587 KiB [ebuild R
] sys-apps/elfix-0.9.5-r1::gentoo USE="xtpax -ptpax -test" 393 KiB
[ebuild R ] sys-process/psmisc-23.7::gentoo USE="X nls -apparmor
(-selinux) -test" 423 KiB [ebuild R ] virtual/editor-0-r7::gentoo 0 KiB
[ebuild R ] virtual/libc-1-r1::gentoo 0 KiB [ebuild R ] virtual/package-manager-1::gentoo 0 KiB [ebuild R ] virtual/service-manager-1-r2::gentoo 0 KiB [ebuild R ] sys-apps/coreutils-9.5::gentoo USE="acl nls openssl (xattr) -caps -gmp -hostname -kill -multicall (-selinux) (-split-usr) -static -test
-vanilla -verify-sig" 5873 KiB [ebuild R ] sys-apps/sed-4.9-r1::gentoo
USE="acl nls (-selinux) -static -verify-sig" 1365 KiB [ebuild R ] sys-apps/util-linux-2.40.2::gentoo USE="audit cramfs hardlink logger
ncurses nls pam readline su suid udev (unicode) -build -caps -cryptsetup -fdformat -kill -magic -python (-rtas) (-selinux) -slang -static-libs
-systemd -test -tty-helpers -uuidd -verify-sig"
PYTHON_TARGETS="python3_12 -python3_10 -python3_11" 8648 KiB [ebuild R ] app-alternatives/awk-4::gentoo USE="gawk -busybox -mawk -nawk
(-split-usr)" 0 KiB [ebuild R ] app-alternatives/sh-0::gentoo USE="bash -busybox -dash -ksh -lksh -mksh" 0 KiB [ebuild R ] dev-build/make-4.4.1-r1::gentoo USE="nls -doc -guile -static -test
-verify-sig" 1276 KiB [ebuild R ] net-misc/iputils-20240117::gentoo
USE="arping filecaps nls -caps -clockdiff -doc -idn -test -tracepath"
436 KiB [ebuild R ] net-misc/rsync-3.3.0-r1::gentoo USE="acl iconv ssl
xattr -examples -lz4 -rrsync -stunnel -system-zlib -verify-sig -xxhash
-zstd" PYTHON_SINGLE_TARGET="python3_12 -python3_10 -python3_11" 1127
KiB [ebuild R ] net-misc/wget-1.24.5::gentoo USE="nls pcre (ssl) zlib -cookie-check -debug -gnutls -idn -ipv6 -libproxy -metalink -ntlm
-static -test -uuid -verify-sig" 2487 KiB [ebuild R ] sys-apps/grep-3.11-r1::gentoo USE="egrep-fgrep nls pcre -static
-verify-sig" 1664 KiB [ebuild R ] sys-apps/iproute2-6.10.0::gentoo USE="iptables -atm -berkdb -bpf -caps -elf -minimal -nfs (-selinux)" 900
KiB [ebuild R ] sys-apps/kmod-33::gentoo USE="lzma (tools) zlib zstd
-debug -doc -pkcs7 -static-libs" 503 KiB [ebuild R ] sys-apps/man-pages-6.06::gentoo USE="-verify-sig" L10N="it -cs -da -de
-el -es -fi -fr -hu -id -ja -mk -nb -nl -pl -pt-BR -ro -ru -sr -sv -uk
-vi -zh-CN" 2121 KiB [ebuild R ] sys-apps/net-tools-2.10::gentoo
USE="arp hostname nls -ipv6 -nis -plipconfig (-selinux) -slattach
-static" 225 KiB [ebuild R ] sys-apps/shadow-4.14.8:0/4::gentoo USE="acl
audit nls pam xattr -cracklib (-selinux) -skey (-split-usr) -su -systemd -verify-sig" 1765 KiB [ebuild R ] sys-devel/binutils-2.43:2.43::gentoo USE="(cet) hardened nls plugins zstd -debuginfod -doc (-gold) -gprofng -multitarget -pgo -static-libs -test -vanilla" 27527 KiB [ebuild R ] sys-devel/gcc-14.2.1_p20240817:14::gentoo USE="cet (cxx) (default-stack-clash-protection) (default-znow) fortran hardened nls
openmp (pie) sanitize (ssp) zstd -ada (-custom-cflags) -d -debug -doc (-fixed-point) -go -graphite (-ieee-long-double) -jit (-libssp) -lto
-modula2 (-multilib) -objc -objc++ -objc-gc (-pch) -pgo -rust -systemtap
-test -valgrind -vanilla -vtv" 85977 KiB [ebuild R ] sys-process/procps-4.0.4-r1:0/0-ng::gentoo USE="elogind kill ncurses nls (unicode) -modern-top (-selinux) -static-libs -systemd -test" 1369 KiB
[ebuild R ] virtual/dev-manager-0-r2::gentoo 0 KiB [ebuild R ] virtual/pager-0-r1::gentoo 0 KiB [ebuild R ] virtual/ssh-0-r2::gentoo USE="-minimal" 0 KiB [ebuild R ] sys-fs/e2fsprogs-1.47.1::gentoo
USE="nls tools -archive -cron -fuse -static-libs -test" 7102 KiB [ebuild
R ] app-arch/bzip2-1.0.8-r5:0/1::gentoo USE="-static -static-libs
-verify-sig" 792 KiB [ebuild R ] app-alternatives/bzip2-1::gentoo USE="reference -lbzip2 -pbzip2 (-split-usr)" 0 KiB [ebuild R ] sys-apps/file-5.45-r4::gentoo USE="bzip2 seccomp zlib -lzip -lzma
-python -static-libs -verify-sig -zstd" PYTHON_TARGETS="python3_12
-python3_10 -python3_11" 1218 KiB [ebuild R ] app-admin/eselect-1.4.27-r1::gentoo USE="-doc -emacs -vim-syntax" 181
KiB [ebuild R ] app-arch/gzip-1.13-r1::gentoo USE="pic -static
-verify-sig" 819 KiB [ebuild R ] app-alternatives/gzip-1::gentoo
USE="reference -pigz (-split-usr)" 0 KiB [ebuild R ]
sys-apps/kbd-2.6.4::gentoo USE="nls pam (-selinux) -test" 1470 KiB
[ebuild R ] app-arch/tar-1.35::gentoo USE="acl nls (xattr) -minimal
(-selinux) -verify-sig" 2263 KiB [ebuild R ]
app-alternatives/tar-0::gentoo USE="gnu -libarchive (-split-usr)" 0 KiB

What am I missing?

raffaele

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------s169B7SILwFbZeL4E6xJGbrD
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

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

- 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...



--
Eli Schwartz


--------------s169B7SILwFbZeL4E6xJGbrD--

-----BEGIN PGP SIGNATURE-----

wnsEABYIACMWIQTnFNnmK0TPZHnXm3qEp9ErcA0vVwUCZseFKgUDAAAAAAAKCRCEp9ErcA0vV7DU AP9UpVjPbCnXVkDEVI0+4JfD8I1QLL0vgXVDw/VA4D9bXwD+PZlcS988EEx1/kfeyaZru1v3cK4b MQwPezmF5NuvHAc=
=0YmE
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------kuKFHD9b30F74FH9q2rkCUg3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 8/22/24 11:16 PM, ralfconn wrote:

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

Ah yes, USE=gtk (adding gcr in as a dep) is an alternative to
USE=keyring for this purpose.

By the way it's not a circular dependency because gcr uses PDEPEND to
indicate that it is acceptable to merge gnupg after gcr itself, as long
as they both end up merged.


--
Eli Schwartz


--------------kuKFHD9b30F74FH9q2rkCUg3--

-----BEGIN PGP SIGNATURE-----

wnsEABYIACMWIQTnFNnmK0TPZHnXm3qEp9ErcA0vVwUCZsgKXQUDAAAAAAAKCRCEp9ErcA0vVyIX AQCf8JLAaWYEj7HWTh1b4GhW2QfAf+3G/0TcCqqamgxO6gEA4fG1VJdHJP3B2d7TtmUrXjxRIer7 TWpixKpvxVJ7Cwc=
=F6vF
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)