On Saturday 8 February 2025 10:24:06 Greenwich Mean Time n952162 wrote: > Hello, > > Can anyone give me a tip or two here? > > Usually, when I encounter this, I temporarily de-emerge the package > causing the problem, and it's always worked so far. But I'm having > trouble identifying the package/s to remove or whether that's even possible: > > (I cut out stuff at the beginning to reduce the size of this post. If > anybody would like to seem it, I can post it all) > > ... > > Total: 14 packages (10 upgrades, 1 new, 3 in new slots), Size of > downloads: 2145496 KiB > > * Error: circular dependencies: > > (dev-lang/rust-1.81.0-r100:1.81.0/1.81.0::gentoo, ebuild scheduled for > merge) depends on > (dev-lang/rust-1.81.0-r100:1.81.0/1.81.0::gentoo, ebuild scheduled for > merge) (buildtime) Since you are not compiling from source, you could temporarily emerge rust- bin, especially as the rust source version is currently up to 1.83.0-r1. This will save time from emerging intermediate rust versions. You can return to compiling rust from source later on. > * Note that circular dependencies can often be avoided by temporarily > * disabling USE flags that trigger optional dependencies. > > !!! Multiple package instances within a single package slot have been pulled > !!! into the dependency graph, resulting in a slot conflict: > > dev-libs/openssl:0 You seem to have a reverse dependency on old and unsafe openssl version(s) due to your postgresql installations. I'd make a backup of the postgresql files, upgrade postgresql, migrate data over to the new postgresql version, test all is good, finally unmerge the old postgresql version(s). This should allow you to emerge the later/latest openssl release. > dev-libs/libffi:0 > > (dev-libs/libffi-3.4.6-r2:0/8::gentoo, ebuild scheduled for merge) > USE="-debug -exec-static-trampoline -pax-kernel -static-libs -test" > ABI_X86="(64) -32 (-x32)" pulled in by > >=dev-libs/libffi-3.4.4-r1:= required by > (dev-python/cffi-1.17.1:0/1.17.1::gentoo, ebuild scheduled for merge) > USE="-debug -doc -test" ABI_X86="(64)" PYTHON_TARGETS="python3_12 > -python3_10 -python3_11 -python3_13" > ^^ ^^^^^^^^ > > (dev-libs/libffi-3.3-r2:0/7::gentoo, installed) USE="userland_GNU > -debug -pax_kernel -static-libs -test" ABI_X86="(64) -32 (-x32)" pulled > in by > dev-libs/libffi:0/7= required by > (dev-lang/python-3.7.13:3.7/3.7m::gentoo, installed) USE="gdbm ncurses > readline sqlite ssl userland_GNU xml -bluetooth -build -examples > -hardened -test -tk -verify-sig -wininst" ABI_X86="(64)" > ^^^^^ > dev-libs/libffi:0/7= required by > (dev-lang/python-3.6.15:3.6/3.6m::gentoo, installed) USE="gdbm ncurses > readline sqlite ssl userland_GNU xml -bluetooth -build -examples > -hardened -test -tk -verify-sig -wininst" ABI_X86="(64)" > ^^^^^ > > > !!! The slot conflict(s) shown above involve package(s) which may need to > !!! be rebuilt in order to solve the conflict(s). However, the following > !!! package(s) cannot be rebuilt for the reason(s) shown: > > (dev-lang/python-3.6.15:3.6/3.6m::gentoo, installed): ebuild is > masked or unavailable > (dev-db/postgresql-11.14-r1:11/11::gentoo, installed): ebuild is > masked or unavailable > (dev-lang/python-3.7.13:3.7/3.7m::gentoo, installed): ebuild is > masked or unavailable > (dev-db/postgresql-10.19-r1:10/10::gentoo, installed): ebuild is > masked or unavailable Can you 'emerge -1aDv python' first, before you proceed with the rest? > The following packages are causing rebuilds: > > (dev-lang/perl-5.40.0-r1:0/5.40::gentoo, ebuild scheduled for merge) > causes rebuilds for: perl-cleaner --reallyall > !!! The following updates are masked by LICENSE changes: > - sys-kernel/linux-firmware-20250109-r1::gentoo (masked by: || ( ) > linux-fw-redistributable license(s)) > A copy of the 'linux-fw-redistributable' license is located at > '/var/db/repos/gentoo/licenses/linux-fw-redistributable'. add to /etc/portagepackage/license: sys-kernel/linux-firmware linux-fw-redistributable Hopefully the above will help you get on the way to a full @world update.