From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Daily update fails
Date: Thu, 7 May 2020 09:11:31 +0100 [thread overview]
Message-ID: <20200507091131.073fac0d@digimed.co.uk> (raw)
In-Reply-To: <2e64fbb2-d5c6-b0b3-eb9b-2f97fa4d829b@dmj.nu>
[-- Attachment #1: Type: text/plain, Size: 2011 bytes --]
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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-05-07 8:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 8:04 [gentoo-user] Daily update fails Dan Johansson
2020-05-07 8:11 ` Neil Bothwick [this message]
2020-05-07 11:59 ` Franz Fellner
2020-05-07 14:30 ` Dan Johansson
2020-05-08 14:20 ` Dan Johansson
2020-05-08 16:09 ` Neil Bothwick
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=20200507091131.073fac0d@digimed.co.uk \
--to=neil@digimed.co.uk \
--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