250727 Michael wrote:

A hard Block "B" indicates a conflict
between what packages/versions you have installed or specified
and what portage seeks to install/update.
This requires manual intervention by the user to be resolved,
typically be editing any user additions in /etc/portage/.
A soft block "b" is resolvable by portage alone.
Either way, portage will install what you've told it you want on your system and generally will do so quite reliably.

Currently, 'shadow' has an 'U'pdate. Here's what I get when I try :

root:516 ~> emerge -pv shadow
These are the packages that would be merged, in order:
Calculating dependencies... done!
Dependency resolution took 3.78 s (backtrack: 0/20).

[ebuild U ] sys-apps/shadow-4.14.8:0/4::gentoo [4.13-r4:0/4::gentoo] USE="acl -audit (-bcrypt%) -cracklib nls pam (-selinux) -skey (split-usr) su* (-systemd) -verify-sig xattr" 1765 KiB
[blocks B ] sys-apps/util-linux[su(-)] ("sys-apps/util-linux[su(-)]" is soft blocking sys-apps/shadow-4.14.8)
[blocks B ] >=sys-apps/shadow-4.7-r2[su] (">=sys-apps/shadow-4.7-r2[su]" is soft blocking sys-apps/util-linux-2.41.1)

Total: 1 package (1 upgrade), Size of downloads: 1765 KiB
Conflict: 2 blocks (2 unsatisfied)

* Error: The above package list contains packages which cannot be
* installed at the same time on the same system.

(sys-apps/util-linux-2.41.1-2:0/0::gentoo, installed) pulled in by
sys-apps/util-linux:= required by (dev-lang/python-3.13.5:3.13/3.13::gentoo, installed) USE="-bluetooth -build -debug ensurepip -examples gdbm (-jit) -libedit ncurses -pgo readline sqlite ssl -test tk -valgrind -verify-sig" ABI_X86="(64)" LLVM_SLOT="
18"
>=sys-apps/util-linux-2.30 required by (sys-libs/libblockdev-3.3.1:0/3::gentoo, installed) USE="cryptsetup -device-mapper -escrow -gtk-doc -introspection -lvm nvme -python -smart -test tools" ABI_X86="(64)" PYTHON_SINGLE_TARGET="-python3_11 -python3_
12 python3_13"
sys-apps/util-linux required by (sys-block/parted-3.6:0/0::gentoo, installed) USE="debug -device-mapper nls readline -verify-sig" ABI_X86="(64)"
sys-apps/util-linux required by (sys-boot/syslinux-6.04_pre1-r5:0/0::gentoo, installed) USE="bios -secureboot uefi" ABI_X86="-32 (64)"
>=sys-apps/util-linux-2.30 required by (sys-fs/udisks-2.10.1-r3:2/2::gentoo, installed) USE="acl daemon -debug elogind introspection -lvm nls (-selinux) (-systemd)" ABI_X86="(64)"
>=sys-apps/util-linux-2.31-r1 required by (sys-fs/cryptsetup-2.7.5:0/12::gentoo, installed) USE="argon2 -fips -gcrypt -kernel -nettle nls openssl -pwquality -ssh -static -static-libs -test udev -urandom" ABI_X86="(64)"
>=sys-apps/util-linux-2.24.1-r3[abi_x86_64(-)] required by (x11-libs/libSM-1.2.4-1:0/0::gentoo, installed) USE="-doc userland_GNU uuid" ABI_X86="-32 (64) (-x32)"
sys-apps/util-linux:0/0= required by (dev-lang/python-3.12.11:3.12/3.12::gentoo, installed) USE="-bluetooth -build -debug ensurepip -examples gdbm -libedit ncurses -pgo readline sqlite ssl -test tk -valgrind -verify-sig" ABI_X86="(64)"
sys-apps/util-linux[caps] required by (app-portage/pfl-3.5.3:0/0::gentoo, installed) USE="network-cron" ABI_X86="(64)" PYTHON_TARGETS="-python3_11 -python3_12 python3_13"
sys-apps/util-linux required by (app-text/build-docbook-catalog-2.4-1:0/0::gentoo, installed) USE="" ABI_X86="(64)"
sys-apps/util-linux required by (kde-frameworks/solid-6.13.0:6/6.13::gentoo, installed) USE="-debug -doc -ios -test" ABI_X86="(64)"
sys-apps/util-linux required by (app-text/xmlto-0.0.28-r10-2:0/0::gentoo, installed) USE="-latex text userland_GNU" ABI_X86="(64)"
sys-apps/util-linux:0/0= required by (dev-lang/python-3.13.5:3.13/3.13::gentoo, installed) USE="-bluetooth -build -debug ensurepip -examples gdbm (-jit) -libedit ncurses -pgo readline sqlite ssl -test tk -valgrind -verify-sig" ABI_X86="(64)" LLVM_
SLOT="18"
sys-apps/util-linux required by (sys-auth/elogind-255.17:0/0::gentoo, installed) USE="acl -audit -cgroup-hybrid -debug -doc pam (policykit) (-selinux) -test" ABI_X86="(64)"
sys-apps/util-linux required by (sys-apps/gptfdisk-1.0.9-r3:0/0::gentoo, installed) USE="ncurses -static" ABI_X86="(64)"
sys-apps/util-linux required by (sys-apps/portage-3.0.68:0/0::gentoo, installed) USE="-apidoc -build -doc -gentoo-dev (ipc) native-extensions rsync-verify (-selinux) -test xattr" ABI_X86="(64)" PYTHON_TARGETS="(-pypy3_11) -python3_11 -python3_12
python3_13"
>=sys-apps/util-linux-2.23[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_s390_32(-)?,abi_s390_64(-)?] (>=sys-apps/util-linux-2.23[abi_x86_64(-)]) required by (dev-libs/glib-2.82.5:2/2::gentoo,
installed) USE="dbus -debug -doc elf introspection (mime) (-selinux) -static-libs -sysprof -systemtap -test -utils xattr" ABI_X86="-32 (64) (-x32)"
>=sys-apps/util-linux-2.30:0=[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_s390_32(-)?,abi_s390_64(-)?] (>=sys-apps/util-linux-2.30:0=[abi_x86_64(-)]) required by (sys-apps/systemd-utils-255.18:
0/0::gentoo, installed) USE="acl -boot -kernel-install kmod -secureboot (-selinux) (split-usr) -sysusers -test tmpfiles udev -ukify" ABI_X86="-32 (64) (-x32)" PYTHON_SINGLE_TARGET="-python3_11 python3_12 -python3_13"
sys-apps/util-linux required by @system
sys-apps/util-linux:= required by (dev-lang/python-3.12.11:3.12/3.12::gentoo, installed) USE="-bluetooth -build -debug ensurepip -examples gdbm -libedit ncurses -pgo readline sqlite ssl -test tk -valgrind -verify-sig" ABI_X86="(64)"
sys-apps/util-linux[abi_x86_64(-)] required by (net-misc/networkmanager-1.48.10-r1:0/0::gentoo, installed) USE="-audit -bluetooth concheck -connection-sharing -debug -dhclient dhcpcd elogind gnutls gtk-doc introspection -iptables -iwd -libedit
modemmanager -nftables -nss -ofono -ovs (policykit) ppp -psl -resolvconf (-selinux) -syslog (-systemd) -teamd -test tools -vala wext wifi" ABI_X86="-32 (64) (-x32)"
>=sys-apps/util-linux-2.33.2 required by (sys-block/gparted-1.6.0-r2:0/0::gentoo, installed) USE="kde (policykit) -test wayland" ABI_X86="(64)"
sys-apps/util-linux[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_s390_32(-)?,abi_s390_64(-)?] (sys-apps/util-linux[abi_x86_64(-)]) required by (media-libs/fontconfig-2.16.2-r1:1.0/1.0::gentoo,
installed) USE="-doc nls -test" ABI_X86="-32 (64) (-x32)"
sys-apps/util-linux required by (sys-fs/e2fsprogs-1.47.2-r10-1:0/0::gentoo, installed) USE="-archive -cron -fuse nls -static-libs -test tools" ABI_X86="-32 (64) (-x32)"
>=sys-apps/util-linux-2.30:0/0=[abi_x86_64(-)] required by (sys-apps/systemd-utils-255.18:0/0::gentoo, installed) USE="acl -boot -kernel-install kmod -secureboot (-selinux) (split-usr) -sysusers -test tmpfiles udev -ukify" ABI_X86="-32 (64) (-x32)"
PYTHON_SINGLE_TARGET="-python3_11 python3_12 -python3_13"
>=sys-apps/util-linux-2.19 required by (dev-libs/rasqal-0.9.33-r1:0/0::gentoo, installed) USE="crypt -gmp mhash pcre -static-libs -test xml" ABI_X86="(64)"

(sys-apps/shadow-4.14.8:0/4::gentoo, ebuild scheduled for merge) pulled in by
sys-apps/shadow required by (net-misc/openssh-10.0_p1:0/0::gentoo, installed) USE="-audit (-debug) -kerberos -ldns -libedit -livecd pam pie -security-key (-selinux) ssl -static -test -verify-sig (-xmss)" ABI_X86="(64)"
shadow
sys-apps/shadow required by @system

For more information about Blocked Packages, please refer to the following section of the Gentoo Linux x86 Handbook (architecture is irrelevant): https://wiki.gentoo.org/wiki/Handbook:X86/Working/Portage#Blocked_packages

-- end of Emerge output --

I looked at the Handbook entry cited, but it doesn't help.
No wonder, when you check the end :
"This page was last edited on 13 December 2014, at 19:42" !!

Can anyone explain what I'm supposed to make of the output above ?
How can I successfully update 'shadow', a vital system pkg ?

In case anyone doesn't know, I've been relying on Gentoo since 2003.
Most of the time, it does a very good job, but it needs some improvements.

Today, I encountered a demand for a USE flag '!gnutls' -- NB the '!' :
what does that mean ? 'USE="gnutls"' makes no difference
& there's no explanation of '!' via 'man emerge'.

An exclamation mark "!" before an item denotes a negation.
You'd normally see this when emerge informs you
it cannot emerge a package with the USE flags you have currently specified.

Thanks, 'USE="-gnutls" emerge curl' appears to work.

However, where in Gentoo docs are we told that '!' = '-' ?

--
========================,,============================================
SUPPORT ___________//___, Philip Webb
ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto
TRANSIT `-O----------O---' purslowatcadotinterdotnet

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

On 2025-07-29, Philip Webb wrote:

250727 Michael wrote:

A hard Block "B" indicates a conflict
between what packages/versions you have installed or specified
and what portage seeks to install/update.
This requires manual intervention by the user to be resolved,
typically be editing any user additions in /etc/portage/.
A soft block "b" is resolvable by portage alone.
Either way, portage will install what you've told it you want on your system >> and generally will do so quite reliably.

Currently, 'shadow' has an 'U'pdate. Here's what I get when I try :

root:516 ~> emerge -pv shadow
These are the packages that would be merged, in order:
Calculating dependencies... done!
Dependency resolution took 3.78 s (backtrack: 0/20).

[ebuild U ] sys-apps/shadow-4.14.8:0/4::gentoo [4.13-r4:0/4::gentoo] USE="acl -audit (-bcrypt%) -cracklib nls pam (-selinux) -skey (split-usr) su* (-systemd) -verify-sig xattr" 1765 KiB
[blocks B ] sys-apps/util-linux[su(-)] ("sys-apps/util-linux[su(-)]" is soft blocking sys-apps/shadow-4.14.8)
[blocks B ] >=sys-apps/shadow-4.7-r2[su] (">=sys-apps/shadow-4.7-r2[su]" is soft blocking sys-apps/util-linux-2.41.1)

From these lines, it's somewhat clear that the problem is that only one
of these two packages can have the "su" USE flag set.

This because IIRC both can provide the "su" utility.

If you did not change any USE flags, I guess a quick first step after
this would be to try to update util-linux as well, just in case that's
all it takes.

In case it was you who manually enabled the "su" flag for shadow, you
need to ensure that util-linux has it disabled. And then update both at
the same time (or is that not sufficient to handle this block?).

[...]

Total: 1 package (1 upgrade), Size of downloads: 1765 KiB
Conflict: 2 blocks (2 unsatisfied)

[...]

-- end of Emerge output --

I looked at the Handbook entry cited, but it doesn't help.
No wonder, when you check the end :
"This page was last edited on 13 December 2014, at 19:42" !!

That, by itself, is not an indication that it is not suitable.

Can anyone explain what I'm supposed to make of the output above ?
How can I successfully update 'shadow', a vital system pkg ?

Well, the -pv output by itself, the list of packages and the block, in
this case appears to be sufficient?

In case anyone doesn't know, I've been relying on Gentoo since 2003.
Most of the time, it does a very good job, but it needs some improvements.

Today, I encountered a demand for a USE flag '!gnutls' -- NB the '!' :
what does that mean ? 'USE="gnutls"' makes no difference
& there's no explanation of '!' via 'man emerge'.

An exclamation mark "!" before an item denotes a negation.
You'd normally see this when emerge informs you
it cannot emerge a package with the USE flags you have currently specified.

Thanks, 'USE="-gnutls" emerge curl' appears to work.

However, where in Gentoo docs are we told that '!' = '-' ?

I'd guess in the online manual page for the ebuild syntax.

man 5 ebuild

Or, on the Web, possibly in the devmanual or the Package Manager
Specification? (Which are also available for install.)

(Maybe there are better sources to use as a reference, which I've
forgotten about.)

--
Nuno Silva

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

On Tuesday, 29 July 2025 11:18:06 British Summer Time Philip Webb wrote:

250727 Michael wrote:

A hard Block "B" indicates a conflict
between what packages/versions you have installed or specified
and what portage seeks to install/update.
This requires manual intervention by the user to be resolved,
typically be editing any user additions in /etc/portage/.
A soft block "b" is resolvable by portage alone.
Either way, portage will install what you've told it you want on your system and generally will do so quite reliably.

Currently, 'shadow' has an 'U'pdate. Here's what I get when I try :

root:516 ~> emerge -pv shadow
These are the packages that would be merged, in order:
Calculating dependencies... done!
Dependency resolution took 3.78 s (backtrack: 0/20).

[ebuild U ] sys-apps/shadow-4.14.8:0/4::gentoo [4.13-r4:0/4::gentoo] USE="acl -audit (-bcrypt%) -cracklib nls pam (-selinux) -skey (split-usr)
su* (-systemd) -verify-sig xattr" 1765 KiB [blocks B ] sys-apps/util-linux[su(-)] ("sys-apps/util-linux[su(-)]" is soft blocking sys-apps/shadow-4.14.8) [blocks B ] >=sys-apps/shadow-4.7-r2[su] (">=sys-apps/shadow-4.7-r2[su]" is soft blocking
sys-apps/util-linux-2.41.1)

Total: 1 package (1 upgrade), Size of downloads: 1765 KiB
Conflict: 2 blocks (2 unsatisfied)

[snip ...]

It appears USE="su" for sys-apps/shadow is causing a clash.

~ $ grep su -r /etc/portage

should show where you have set it up to cause this problem.

An exclamation mark "!" before an item denotes a negation.
You'd normally see this when emerge informs you
it cannot emerge a package with the USE flags you have currently
specified.

Thanks, 'USE="-gnutls" emerge curl' appears to work.

However, where in Gentoo docs are we told that '!' = '-' ?

The "!" will appear in emerge output within some conditional logic statement, typically hinting at what may be causing a clash and requiring manual intervention. A loose hypothetical example: if you have installed X but !Y, then you must select Z.
-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmiIpcwACgkQseqq9sKV ZxmBphAA45wwFpi8L6+mLiANwSJ3dzUAyypbtta90Wdjt+kOvo1yFXIxINf9w2Ml Es5fZ/vEiYzkT/xmEJ7k0sCDp1WZsj8ulmhtEAR3tH7acUFNuJAABDdHalCwSw8j gNLLPAMd9f62v3oknFyV/dDfqHv3hUFgMfUkuhTBlgLG69Bha5HgKlBNiSM71B1E IcT8CXvCc0AAQfo/HKE6WCYuhbtqsdD7LaD8sk8XpOBXsLXEMwqUazt4CsdFNd1m Vpt9JEIisKn9EzSN8HT8v1edQAzdcVPYSLlXOemYU7JRdLdpCuDesbgPuh/5g/Es ftMtQ8+558gaThfrgC4sbnn1UYiq8DLW6V67aXb777+PkaadtxKWh8zbD3mhDIBD jvBZGE9yKleEV6/KKtOt4D6M31NmL0VrWmNqAukcYN85Rj2443MJulqrTglfYAQp f972y6Gko8kmXVtGpedMHJXFZU5TdzTdZYHH2LqR4XSCApzFEby/jzZE/OMvXkvp WetyaJvYaELgo0k6y+anOFYziGTj63cWBEOXNHMHp/70RQyiYu+WQu9anOAwFL/n 46GREtWlTyBNWw/FDQNDr8g9pk62nF7/mVyPfGS+xL/yRZup87u+ysFPs3JP8LFs q94WzK3341KNmMNyLc4IpOGPQfzji9JhDLGVQN5WETrRJr42NyY=
=h+fn
-----END PGP SIGNATURE-----

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

On martedì 29 luglio 2025 12:18:06 Ora legale dell’Europa centrale Philip Webb
wrote:

250727 Michael wrote:

A hard Block "B" indicates a conflict
between what packages/versions you have installed or specified
and what portage seeks to install/update.
This requires manual intervention by the user to be resolved,
typically be editing any user additions in /etc/portage/.
A soft block "b" is resolvable by portage alone.
Either way, portage will install what you've told it you want on your system and generally will do so quite reliably.

Currently, 'shadow' has an 'U'pdate. Here's what I get when I try :

root:516 ~> emerge -pv shadow
These are the packages that would be merged, in order:
Calculating dependencies... done!
Dependency resolution took 3.78 s (backtrack: 0/20).

[ebuild U ] sys-apps/shadow-4.14.8:0/4::gentoo [4.13-r4:0/4::gentoo] USE="acl -audit (-bcrypt%) -cracklib nls pam (-selinux) -skey (split-usr)
su* (-systemd) -verify-sig xattr" 1765 KiB [blocks B ] sys-apps/util-linux[su(-)] ("sys-apps/util-linux[su(-)]" is soft blocking sys-apps/shadow-4.14.8) [blocks B ] >=sys-apps/shadow-4.7-r2[su] (">=sys-apps/shadow-4.7-r2[su]" is soft blocking
sys-apps/util-linux-2.41.1)

Total: 1 package (1 upgrade), Size of downloads: 1765 KiB
Conflict: 2 blocks (2 unsatisfied)

* Error: The above package list contains packages which cannot be
* installed at the same time on the same system.

(sys-apps/util-linux-2.41.1-2:0/0::gentoo, installed) pulled in by
sys-apps/util-linux:= required by (dev-lang/python-3.13.5:3.13/3.13::gentoo, installed) USE="-bluetooth
-build -debug ensurepip -examples gdbm (-jit) -libedit ncurses -pgo
readline sqlite ssl -test tk -valgrind -verify-sig" ABI_X86="(64)" LLVM_SLOT="18"
>=sys-apps/util-linux-2.30 required by
>(sys-libs/libblockdev-3.3.1:0/3::gentoo, installed) USE="cryptsetup
>-device-mapper -escrow -gtk-doc -introspection -lvm nvme -python
>-smart -test tools" ABI_X86="(64)" PYTHON_SINGLE_TARGET="-python3_11
>-python3_12 python3_13"
sys-apps/util-linux required by (sys-block/parted-3.6:0/0::gentoo, installed) USE="debug -device-mapper nls readline -verify-sig"
ABI_X86="(64)" sys-apps/util-linux required by (sys-boot/syslinux-6.04_pre1-r5:0/0::gentoo, installed) USE="bios
-secureboot uefi" ABI_X86="-32 (64)"
>=sys-apps/util-linux-2.30 required by
>(sys-fs/udisks-2.10.1-r3:2/2::gentoo, installed) USE="acl daemon
>-debug elogind introspection -lvm nls (-selinux) (-systemd)"
>ABI_X86="(64)" =sys-apps/util-linux-2.31-r1 required by
>(sys-fs/cryptsetup-2.7.5:0/12::gentoo, installed) USE="argon2 -fips
>-gcrypt -kernel -nettle nls openssl -pwquality -ssh -static
>-static-libs -test udev -urandom" ABI_X86="(64)"
>=sys-apps/util-linux-2.24.1-r3[abi_x86_64(-)] required by
>(x11-libs/libSM-1.2.4-1:0/0::gentoo, installed) USE="-doc userland_GNU
>uuid" ABI_X86="-32 (64) (-x32)"
sys-apps/util-linux:0/0= required by (dev-lang/python-3.12.11:3.12/3.12::gentoo, installed) USE="-bluetooth
-build -debug ensurepip -examples gdbm -libedit ncurses -pgo readline
sqlite ssl -test tk -valgrind -verify-sig" ABI_X86="(64)" sys-apps/util-linux[caps] required by (app-portage/pfl-3.5.3:0/0::gentoo, installed) USE="network-cron" ABI_X86="(64)" PYTHON_TARGETS="-python3_11 -python3_12 python3_13" sys-apps/util-linux required by (app-text/build-docbook-catalog-2.4-1:0/0::gentoo, installed) USE="" ABI_X86="(64)" sys-apps/util-linux required by (kde-frameworks/solid-6.13.0:6/6.13::gentoo, installed) USE="-debug -doc
-ios -test" ABI_X86="(64)" sys-apps/util-linux required by (app-text/xmlto-0.0.28-r10-2:0/0::gentoo, installed) USE="-latex text userland_GNU" ABI_X86="(64)" sys-apps/util-linux:0/0= required by (dev-lang/python-3.13.5:3.13/3.13::gentoo, installed) USE="-bluetooth
-build -debug ensurepip -examples gdbm (-jit) -libedit ncurses -pgo
readline sqlite ssl -test tk -valgrind -verify-sig" ABI_X86="(64)" LLVM_SLOT="18" sys-apps/util-linux required by (sys-auth/elogind-255.17:0/0::gentoo, installed) USE="acl -audit -cgroup-hybrid -debug -doc pam (policykit) (-selinux) -test" ABI_X86="(64)" sys-apps/util-linux required by (sys-apps/gptfdisk-1.0.9-r3:0/0::gentoo, installed) USE="ncurses -static" ABI_X86="(64)" sys-apps/util-linux
required by (sys-apps/portage-3.0.68:0/0::gentoo, installed) USE="-apidoc -build -doc -gentoo-dev (ipc) native-extensions rsync-verify (-selinux)
-test xattr" ABI_X86="(64)" PYTHON_TARGETS="(-pypy3_11) -python3_11 -python3_12 python3_13"
>=sys-apps/util-linux-2.23[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?
>,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_s390_32(-)?,abi
>_s390_64(-)?] (>=sys-apps/util-linux-2.23[abi_x86_64(-)]) required by
>(dev-libs/glib-2.82.5:2/2::gentoo, installed) USE="dbus -debug -doc
>elf introspection (mime) (-selinux) -static-libs -sysprof -systemtap
>-test -utils xattr" ABI_X86="-32 (64) (-x32)"
>=sys-apps/util-linux-2.30:0=[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32
>(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_s390_32(-)?
>,abi_s390_64(-)?] (>=sys-apps/util-linux-2.30:0=[abi_x86_64(-)])
>required by (sys-apps/systemd-utils-255.18:0/0::gentoo, installed)
>USE="acl -boot -kernel-install kmod -secureboot (-selinux) (split-usr)
>-sysusers -test tmpfiles udev -ukify" ABI_X86="-32 (64) (-x32)"
>PYTHON_SINGLE_TARGET="-python3_11 python3_12 -python3_13"
sys-apps/util-linux required by @system
sys-apps/util-linux:= required by (dev-lang/python-3.12.11:3.12/3.12::gentoo, installed) USE="-bluetooth
-build -debug ensurepip -examples gdbm -libedit ncurses -pgo readline
sqlite ssl -test tk -valgrind -verify-sig" ABI_X86="(64)" sys-apps/util-linux[abi_x86_64(-)] required by (net-misc/networkmanager-1.48.10-r1:0/0::gentoo, installed) USE="-audit -bluetooth concheck -connection-sharing -debug -dhclient dhcpcd elogind gnutls gtk-doc introspection -iptables -iwd -libedit modemmanager -nftables -nss -ofono -ovs (policykit) ppp -psl -resolvconf (-selinux) -syslog (-systemd) -teamd -test tools -vala wext wifi" ABI_X86="-32 (64) (-x32)"
>=sys-apps/util-linux-2.33.2 required by
>(sys-block/gparted-1.6.0-r2:0/0::gentoo, installed) USE="kde
>(policykit) -test wayland" ABI_X86="(64)"

sys-apps/util-linux[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_ n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_s390_32(-)?,abi_s390_64(-)?] (sys-apps/util-linux[abi_x86_64(-)]) required by (media-libs/fontconfig-2.16.2-r1:1.0/1.0::gentoo, installed) USE="-doc nls -test" ABI_X86="-32 (64) (-x32)" sys-apps/util-linux required by (sys-fs/e2fsprogs-1.47.2-r10-1:0/0::gentoo, installed) USE="-archive -cron -fuse nls -static-libs -test tools" ABI_X86="-32 (64) (-x32)"
>=sys-apps/util-linux-2.30:0/0=[abi_x86_64(-)] required by
>(sys-apps/systemd-utils-255.18:0/0::gentoo, installed) USE="acl -boot
>-kernel-install kmod -secureboot (-selinux) (split-usr) -sysusers
>-test tmpfiles udev -ukify" ABI_X86="-32 (64) (-x32)"
>PYTHON_SINGLE_TARGET="-python3_11 python3_12 -python3_13"
>=sys-apps/util-linux-2.19 required by
>(dev-libs/rasqal-0.9.33-r1:0/0::gentoo, installed) USE="crypt -gmp
>mhash pcre -static-libs -test xml" ABI_X86="(64)"
(sys-apps/shadow-4.14.8:0/4::gentoo, ebuild scheduled for merge) pulled in by sys-apps/shadow required by (net-misc/openssh-10.0_p1:0/0::gentoo, installed) USE="-audit (-debug) -kerberos -ldns -libedit -livecd pam pie -security-key (-selinux) ssl -static -test -verify-sig (-xmss)" ABI_X86="(64)" shadow
sys-apps/shadow required by @system

For more information about Blocked Packages, please refer to the following section of the Gentoo Linux x86 Handbook (architecture is irrelevant): https://wiki.gentoo.org/wiki/Handbook:X86/Working/Portage#Blocked_packages

-- end of Emerge output --

I looked at the Handbook entry cited, but it doesn't help.
No wonder, when you check the end :
"This page was last edited on 13 December 2014, at 19:42" !!

Can anyone explain what I'm supposed to make of the output above ?
How can I successfully update 'shadow', a vital system pkg ?

In case anyone doesn't know, I've been relying on Gentoo since 2003.
Most of the time, it does a very good job, but it needs some improvements.

If I'm not mistaken, your problem comes from the fact you're emerging shadow with the su USE flag while having util-linux installed with the same USE flag. Since that flag enables building the "su" program, it be set for both packages.
I think what you should disable the "su" flag for either shadow or util-linux. On my system, I have it on for util-linux and not for shadow.

I hope this helps

Stefano

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

250729 Nuno Silva wrote:

On 2025-07-29, Philip Webb wrote:

Currently, 'shadow' has an 'U'pdate. Here's what I get when I try :

root:516 ~> emerge -pv shadow
These are the packages that would be merged, in order:
Calculating dependencies... done!
Dependency resolution took 3.78 s (backtrack: 0/20).

[ebuild U ] sys-apps/shadow-4.14.8:0/4::gentoo [4.13-r4:0/4::gentoo] USE="acl -audit (-bcrypt%) -cracklib nls pam (-selinux) -skey (split-usr) su* (-systemd) -verify-sig xattr" 1765 KiB
[blocks B ] sys-apps/util-linux[su(-)] ("sys-apps/util-linux[su(-)]" is soft blocking sys-apps/shadow-4.14.8)
[blocks B ] >=sys-apps/shadow-4.7-r2[su] (">=sys-apps/shadow-4.7-r2[su]" is soft blocking sys-apps/util-linux-2.41.1)

From these lines, it's somewhat clear that the problem is
that only one of these two packages can have the "su" USE flag set.
This because both can provide the "su" utility.
If you did not change any USE flags, I guess a quick first step after this would be to try to update util-linux as well,
just in case that's all it takes.
In case it was you who manually enabled the "su" flag for shadow,
you need to ensure that util-linux has it disabled
& then update both at the same time.

Yes, that's the explanation for the problem.
It comes back that I encountered it before some years ago
& chose to enable 'su' for 'util-linux'.
I've now added lines in 'package.use' to set the flag appropriately
& have successfully updated both pkgs.

However, I continue to believe that Portage could do a better job
in reporting the nature of the problem.

I looked at the Handbook entry cited, but it doesn't help.
No wonder, when you check the end :
"This page was last edited on 13 December 2014, at 19:42" !!

That, by itself, is not an indication that it is not suitable.

No, but 11 yrs is a very long time in the world of software
& one would expect some improvements in the interim.

However, where in Gentoo docs are we told that '!' = '-' ?

I'd guess in the online manual page for the ebuild syntax : 'man 5 ebuild'.

Yes, it's there on the 1st page, but I wasn't aware of that man file.
When reporting a flag requirement, Portage should say '-x', not '!x'.

Thanks for your careful explanation & to the others who advised similarly.

--
========================,,============================================
SUPPORT ___________//___, Philip Webb
ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto
TRANSIT `-O----------O---' purslowatcadotinterdotnet

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

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

On 7/30/25 4:50 AM, Philip Webb wrote:

Yes, that's the explanation for the problem.
It comes back that I encountered it before some years ago
& chose to enable 'su' for 'util-linux'.
I've now added lines in 'package.use' to set the flag appropriately
& have successfully updated both pkgs.

However, I continue to believe that Portage could do a better job
in reporting the nature of the problem.

I agree! :) I believe this is a known issue, which I reported at https://bugs.gentoo.org/916462


Portage's error message wording isn't always the best, it would be very
nice if it could be improved.


--
Eli Schwartz

--------------7Mc6K600fVgFpFxBnWWqEtMb--

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

wnsEABYIACMWIQTnFNnmK0TPZHnXm3qEp9ErcA0vVwUCaIo4aQUDAAAAAAAKCRCEp9ErcA0vVy1n APsFsLNdjuzqrlG9OWp0pJinfOlOPVbd2y502fngap1FfwEA1XxecuRMTVpzV5QWawsaNQNSR8je md6+JzIiAk6BdQ4=
=+3ki
-----END PGP SIGNATURE-----

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

On Wednesday, 30 July 2025 09:50:31 British Summer Time Philip Webb wrote:

250729 Nuno Silva wrote:

On 2025-07-29, Philip Webb wrote:

Currently, 'shadow' has an 'U'pdate. Here's what I get when I try :
root:516 ~> emerge -pv shadow
These are the packages that would be merged, in order:
Calculating dependencies... done!
Dependency resolution took 3.78 s (backtrack: 0/20).

[ebuild U ] sys-apps/shadow-4.14.8:0/4::gentoo
[4.13-r4:0/4::gentoo] USE="acl -audit (-bcrypt%) -cracklib nls pam
(-selinux) -skey (split-usr) su* (-systemd) -verify-sig xattr" 1765

The suffix "*" to your USE flag "su" above indicates a change of this flag
from a previous emerged state with it being disabled. This is the default here:
============================
~ $ equery u sys-apps/shadow
[ Legend : U - final flag setting for installation]
[ : I - package is installed with flag ]
[ Colors : set, unset ]
* Found these USE flags for sys-apps/shadow-4.14.8:
U I
+ + acl : Add support for Access Control Lists
- - audit : Enable support for Linux audit subsystem using sys-process/ audit
- - cracklib : Support for cracklib strong password checking
+ + nls : Add Native Language Support (using gettext - GNU locale utilities)
+ + pam : Add support for PAM (Pluggable Authentication Modules) - DANGEROUS to arbitrarily flip
- - skey : Enable S/Key (Single use password) authentication support
- - su : build the su program
- - systemd : Enable use of systemd-specific libraries and features like socket activation or session tracking
- - verify-sig : Verify upstream signatures on distfiles
+ + xattr : Add support for extended attributes (filesystem-stored metadata)
================

KiB [blocks B ] sys-apps/util-linux[su(-)]
("sys-apps/util-linux[su(-)]" is soft blocking sys-apps/shadow-4.14.8) >> [blocks B ] >=sys-apps/shadow-4.7-r2[su]
(">=sys-apps/shadow-4.7-r2[su]" is soft blocking
sys-apps/util-linux-2.41.1)>

The above output explains the clash caused by the USE flag "su" being enabled on both packages.

From these lines, it's somewhat clear that the problem is
that only one of these two packages can have the "su" USE flag set.
This because both can provide the "su" utility.
If you did not change any USE flags, I guess a quick first step after this would be to try to update util-linux as well,
just in case that's all it takes.
In case it was you who manually enabled the "su" flag for shadow,
you need to ensure that util-linux has it disabled
& then update both at the same time.

Yes, that's the explanation for the problem.
It comes back that I encountered it before some years ago
& chose to enable 'su' for 'util-linux'.
I've now added lines in 'package.use' to set the flag appropriately
& have successfully updated both pkgs.

You /should/ find the problem goes away if you let portage decide on this occasion, by removing manual edits about the "su" USE flag on both of these packages in /etc/portage/package.use/.

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

iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmiKFocACgkQseqq9sKV ZxkQ5BAAj4oLrNsenNcGOt+/7//W5obqohubTybcufz76wp2WD0ma8tWeufwtdJl Jr+tnER9iCCLw7UKGY2pd+0lv3Mx/ep2uCjybQwEadwB+X0G+WJBX/eoaWiBeDTR 5THLV/D9lj3/JkiwSif1B+/P1QsB7l5A6GgwN3OFeAx0xH0R2OUSvYus0Qt09utc PDgf/MF9Q656O+7TJNWVoyzSTlQH/2Kxmb6+9JEyGg9fC/vvamLUCQq+zAPMKuNw USCEFsYhOdYKhbrIAPwYwd5ukrt+mzRnegBi7ZMdP9ccB/uRtL5TpvKS21jFKYZO iO0dslDitDWnSb/tBkV9ksd52gffWmIwwzEdIJJsUaFdXYbnO9lj6JRS0CHXCpPf z20Tx8H/xxcZgHmvZs50v9iSkp2+PytfPMwwUsBFzPFs7NxzWIAGoGN8iFvQzz3m 8i0CmEmonCB4ePsUmzS8VDU/qCeOFsIzqjtTRyYYOP5TSWwRwienccVHw+sFa36J Gaj/i6QX5gl6sfcU2vdSjhLzmXy5lYZ03Xi5AfLvm670AjAM3mKLdFODRys2k4cH rfqwE6UXcBZ6+vPMeUDIy22XsnxoKgFxhoCeDsoJ4EFrYR1NFFieQX89TLbacjaW +OZvrko0uIpMJe4dTrGpg7T4AbTezO53F9lNbiCZCLvZO4oAFDI=
=Bv3p
-----END PGP SIGNATURE-----

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

On Thursday, 31 July 2025 12:28:54 British Summer Time Philip Webb wrote:

250730 Eli Schwartz wrote:

On 7/30/25 4:50 AM, Philip Webb wrote:

Yes, that's the explanation for the problem.
It comes back that I encountered it before some years ago
& chose to enable 'su' for 'util-linux'.
I've now added lines in 'package.use' to set the flag appropriately
& have successfully updated both pkgs.
However, I continue to believe that Portage could do a better job
in reporting the nature of the problem.

I agree! :) I believe this is a known issue,
which I reported at https://bugs.gentoo.org/916462
Portage's error message wording isn't always the best,
it would be very nice if it could be improved.

Finally, some support for common sense !

The difficulty with the output of emerge is it requires interpreting various symbols, which the user have to familiarise themselves with, but also provides little additional explanation as to the underlying causes. Yes, it may be obvious there is clash caused by some USE flag, but why might that be? An upstream change? A prior user edit now incompatible with some build-time dependency? Some hard-coded dependency you now have to live with, if you want to update a package? Additional information to this effect would save time fishing around in ebuilds and upstream bug reports, trying to invent workarounds and creating noise in BGO.


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

iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmiLYykACgkQseqq9sKV ZxlgWw//dhwmMPC/WDs21/1wDhM4LpENoMuwsIi2m6fZQ5ySKvvBSeahoGQ6Dmik NVAE2bim0fsaLrLtxcaSRKvTVSEN0luzxPoaWPFLVZBLwyKEpK+hL7yqgx3tzV2K EJCbppqQxo/zHnGHwCHTLExDrxRVwISn9+qObPzkpNtk9mPlfxz73Pk5psjkOldA wqRTSkVXc5a+v5JFseU3vasmbgYDTZkFzeKls/Jo9mQv74EsUPbih/XukizPCqn1 EFg06LUQhYr+p5MCcwfHlE4oPsErteYxDcuvJ3Us+D7J3qKqw0LMZr92qMAlDWwo aog1yK1huUyPcItk2ewFp+4DwX+o9imZhTOj4Bz0HEGE/kLUkMAzY7fJKGARN/cV tCLo90G+hZB2BFn2PBj9yJn5IfPfXYaGDlkb2ybg7Oo5rIxBjxqYGTugsEXPpVtw 1xu16YbBMgSTXvIysCFiCnpkoQEoRwVP0hRD2TEWZzQBic9/+8j2OmItSbxeYgq4 fSZ0R70rzy6H78p/us9Llb2rLsOC7WpNT0CbGxz1Flw4cWzKPuXgc1ek36tLNP19 aLZvLqrddN1o6DGXsp+eESXsMj7mROYLP6UriHQjvbNabbX+3d8jMpsOlKIwEfa8 pI+wjyg+kYHqnQ+hgQ7Ta3AphX/7Od5phS39Tp6VWajJfZDPvk4=
=99CJ
-----END PGP SIGNATURE-----

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

250730 Eli Schwartz wrote:

On 7/30/25 4:50 AM, Philip Webb wrote:

Yes, that's the explanation for the problem.
It comes back that I encountered it before some years ago
& chose to enable 'su' for 'util-linux'.
I've now added lines in 'package.use' to set the flag appropriately
& have successfully updated both pkgs.
However, I continue to believe that Portage could do a better job
in reporting the nature of the problem.

I agree! :) I believe this is a known issue,
which I reported at https://bugs.gentoo.org/916462
Portage's error message wording isn't always the best,
it would be very nice if it could be improved.

Finally, some support for common sense !

--
========================,,============================================
SUPPORT ___________//___, Philip Webb
ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto
TRANSIT `-O----------O---' purslowatcadotinterdotnet

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