public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] problems emerging world
Date: Sun, 09 Feb 2025 12:20:45 +0000	[thread overview]
Message-ID: <1995509.PYKUYFuaPT@rogueboard> (raw)
In-Reply-To: <9625eeb9-5ac9-4e2e-9363-35c4540e9851@web.de>

[-- Attachment #1: Type: text/plain, Size: 4154 bytes --]

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.

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2025-02-09 12:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-08 10:24 [gentoo-user] problems emerging world n952162
2025-02-09 12:20 ` Michael [this message]
2025-02-16 20:10   ` Wol

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1995509.PYKUYFuaPT@rogueboard \
    --to=confabulate@kintzios.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox