[SOLVED] Emerging from a clean slate, stil have conflicts.

Message

pygoscelis · Post by **pygoscelis** » Tue Mar 24, 2026 8:34 pm

This is related to this question https://forums.gentoo.org/viewtopic-t-1177162.html but is a separate one.

I have removed all of my package.use and package.accept_keyword, and trying to rebuild everything from a clean slate. Somehow I'm still getting a few slot conflicts

Code: Select all

emerge -pg --emptytree --backtrack=0 @world
..........
!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:

media-libs/flac:0

  (media-libs/flac-1.5.0-9:0/11-14::gentoo, binary scheduled for merge) USE="cxx ogg -debug -static-libs" ABI_X86="(64) -32 (-x32)" CPU_FLAGS_X86="avx avx2" pulled in by
    >=media-libs/flac-1.2.1:0/11-14=[abi_x86_64(-)] required by (media-libs/audiofile-0.3.6-r6-14:0/1::gentoo, binary scheduled for merge) USE="flac" ABI_X86="(64) -32 (-x32)"
                           ^^^^^^^^^                                                                                                                                                                                                                                                           
    (and 2 more with the same problem)

  (media-libs/flac-1.4.3-5:0/10-12::gentoo, binary scheduled for merge) USE="cxx ogg -debug -static-libs" ABI_X86="(64) -32 (-x32)" CPU_FLAGS_X86="avx avx2" pulled in by
    >=media-libs/flac-1.2.1-r5:0/10-12=[abi_x86_64(-)] required by (media-libs/sdl-sound-1.0.3_p20220525-1:0/0::gentoo, binary scheduled for merge) USE="flac mp3 vorbis -mikmod -modplug -speex -static-libs" ABI_X86="(64) -32 (-x32)"
                              ^^^^^^^^^                                                                                                                                                                                                                                                                                                                                                                                                                                   

dev-libs/libxml2:2

  (dev-libs/libxml2-2.15.1:2/16::gentoo, ebuild scheduled for merge) USE="icu python readline -doc -static-libs -test" ABI_X86="(64) -32 (-x32)" PYTHON_TARGETS="python3_13 python3_14 -python3_11 -python3_12" pulled in by
    dev-libs/libxml2[python(-),python_targets_python3_14(-)] required by (app-doc/gimp-help-3.0.2:2/2::gentoo, ebuild scheduled for merge) USE="nls" ABI_X86="(64)"
                                                                                                                                                                                                                          
    dev-libs/libxml2:2/16= required by (app-text/libodfgen-0.1.8-r1-6:0/0::gentoo, binary scheduled for merge) USE="-doc -test" ABI_X86="(64)"
                    ^^^^^^                                                                                                                                                                                                                 
    >=dev-libs/libxml2-2.15.1:2/16=[abi_x86_64(-)] required by (dev-libs/libxslt-1.1.45-9:0/0::gentoo, binary scheduled for merge) USE="crypt -debug -debugger -examples -python -static-libs" ABI_X86="(64) -32 (-x32)" PYTHON_TARGETS="python3_13 -python3_11 -python3_12 -python3_14"
    ^^                 ^^^^^^^^^^^^                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      
    (and 30 more with the same problems)

  (dev-libs/libxml2-2.13.9:2/2::gentoo, ebuild scheduled for merge) USE="icu readline -examples -lzma -python -static-libs -test" ABI_X86="(64) -32 (-x32)" PYTHON_TARGETS="python3_13 -python3_11 -python3_12 -python3_14" pulled in by
    dev-libs/libxml2:2/2= required by (dev-util/ctags-6.2.0-r1-1:0/0::gentoo, binary scheduled for merge) USE="pcre seccomp xml -json -test -yaml" ABI_X86="(64)"
                    ^^^^^                                                                                                                                                                                                                                                                                                                 

dev-libs/icu:0

  (dev-libs/icu-78.2-8:0/78::gentoo, binary scheduled for merge) USE="-debug -doc -examples -static-libs -test -verify-sig" ABI_X86="(64) -32 (-x32)" pulled in by
    dev-libs/icu:0/78= required by (media-libs/libzmf-0.0.2-r1-11:0/0::gentoo, binary scheduled for merge) USE="-debug -doc -test -tools" ABI_X86="(64)"
                ^^^^^^                                                                                                                                                                                                                                                                     
    (and 16 more with the same problem)

  (dev-libs/icu-77.1-1:0/77::gentoo, binary scheduled for merge) USE="-debug -doc -examples -static-libs -test -verify-sig" ABI_X86="(64) -32 (-x32)" pulled in by
    >=dev-libs/icu-4.4:0/77= required by (dev-tex/bibtexu-3.72_p20240311-1:0/0::gentoo, binary scheduled for merge) USE="-doc -source" ABI_X86="(64)"
                      ^^^^^^

Is it normal to have such conflicts? How can they be solved?

Edit: just removed some conflicting packages

Post by **sam_** » Tue Mar 24, 2026 8:45 pm

Please don't truncate output when asking for help. But also, some issues like this are expected when backtracking is disabled.

Post by Hu » Tue Mar 24, 2026 9:01 pm

This is related to [topic=1177162]Fixing a broken install[/topic], where OP reported putting the system into a bad state, but decided to create a new thread instead of continuing there.

Post by **pietinger** » Tue Mar 24, 2026 9:09 pm

I interpret the creation of two threads to mean that he asked a GENERAL question there about what one can generally do, while here he wants to address the SPECIFIC problem. So I suspect he wanted to keep them clearly separate - though a note with a link to the other thread would have been nice.

pygoscelis · Post by **pygoscelis** » Tue Mar 24, 2026 9:12 pm

Hu wrote:This is related to [topic=1177162]Fixing a broken install[/topic], where OP reported putting the system into a bad state, but decided to create a new thread instead of continuing there.

Yes these are related but separate as @pietinger says. Sorry didn't think about a link.