On Tuesday, August 25, 2020 2:23:57 A.M. AEST Grant Edwards wrote:
> On 2020-08-24, Franz Fellner <alpine.art...@gmail.com> wrote:
> > On Mo 24 Aug 2020 11:21:10 +0200, Hogren <hog...@iiiha.com> wrote:
> >> Maybe try to :
> >>
> >> - Unmerge all python and python-setuptools versions
> >
> > No, don't do that!!!
> > Unmerging all python version will leave you with a non-working portage.
>
> Indeed -- I've done that. It's not fun. You certainly won't do it a
> second time.
>
> --
> Grant
I'm trying again.
I started by removing all the Python version stuff I'd added under /etc/
portage to try and bring things back to standard.
Now I'm seeing instances where a package has had multiple
"python_single_target" variable set, like the example below.
I'm not sure how this is possible, or where they are coming from.
It makes it look like something may be wrong in my profile, but that should get
corrected every time I sync portage with the mirrors, shouldn't it?
######################################
[Tue Aug 25 11:42:14]# emerge --autounmask-keep-masks y --verbose \
--quiet-fail y --backtrack=99 --keep-going --jobs 6 --with-bdeps y \
--quiet --update --buildpkg --deep --reinstall changed-use --usepkg n \
-a -e world
!!! The ebuild selected to satisfy ">=dev-util/gdbus-codegen-2.48" has unmet
requirements.
- dev-util/gdbus-codegen-2.62.6::gentoo USE="" ABI_X86="(64)"
PYTHON_SINGLE_TARGET="python3_6 python3_7 -python3_8"
The following REQUIRED_USE flag constraints are unsatisfied:
exactly-one-of ( python_single_target_python3_6
python_single_target_python3_7 python_single_target_python3_8 )
######################################
--
Reverend Paul Colquhoun, ULC. http://andor.dropbear.id.au/
Asking for technical help in newsgroups? Read this first:
http://catb.org/~esr/faqs/smart-questions.html#intro
