On Thu, 7 May 2020 10:04:37 +0200, Dan Johansson wrote: > Today when I tried to do my daily "emerge --update ... @world", portage > spitted out a lot of "Multiple package instances within a single > package slot have been pulled" messages. > > I thought this could be due to the depreciation of python3_6 so I added > */* PYTHON_TARGETS: python3_6 python3_7 > */* PYTHON_SINGLE_TARGET: -* python3_6 > ,as per the news item published, to my package.use and now I get the > following instead: > > !!! The ebuild selected to satisfy "app-office/scribus" has unmet > requirements. > - app-office/scribus-1.5.5-r1::gentoo USE="boost minimal pdf templates > -debug -examples -graphicsmagick -hunspell -osg -scripts -tk" > ABI_X86="(64)" PYTHON_SINGLE_TARGET="-python2_7" > python_single_target_python2_7 > The following REQUIRED_USE flag constraints are unsatisfied: > python_single_target_python2_7 > > The above constraints are a subset of the following complete > expression: exactly-one-of ( python_single_target_python2_7 ) tk? ( > scripts ) > > I tried to unmerge scribus but that just made another package complain > about "python_single_target_python2_7".
You have globally masked python_single_target_python2_7 in package.use, so now you need to unmask it for individual packages, starting with scribus. It's a bit of a game of whack-a-mole, add a package, emerge world, get another failure, add that package, rinse and repeat. I'd suggest putting all these changes in a separate file in package.use so it is easy(er) to track and undo these, hopefully, temporary, changed. I had no issues with the changeover on systems running purely testing, those running stable with a few testing packages required some attention. If you are running such a system, you may find it easier to temporarily unmask testing versions of some packages rather than play around with USE flags. -- Neil Bothwick Top Oxymorons Number 37: Sanitary landfill
pgpKjBhQVpk98.pgp
Description: OpenPGP digital signature
