Re: [gentoo-user] Re: meson build woes
On Tuesday, August 25, 2020 2:23:57 A.M. AEST Grant Edwards wrote: > On 2020-08-24, Franz Fellner wrote: > > On Mo 24 Aug 2020 11:21:10 +0200, Hogren 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
[gentoo-user] Re: meson build woes
On 2020-08-24, Thomas Mueller wrote: >> >> - 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. > How did you recover? You couldn't even use setup.py at that stage. Right. > Did you have to download the python distfile if you didn't have it > already, and build using configure and make directly? IIRC, I copied Python binaries and libraries from another computer. That took some trial-and-error, but I eventually got to the point where I could do an "emerge python". -- Grant
Re: [gentoo-user] Re: meson build woes
On 2020-08-24 17:24, Thomas Mueller wrote: > > How did you recover? You couldn't even use setup.py at that stage. > > Did you have to download the python distfile if you didn't have it > already, and build using configure and make directly? You can find someone you trust with the same architecture and get a binary or quickpkg copy of the python package from them. Failing that, you can use the livecd or one of openstack VM images from gentoo.org to boot into a working system and create the binary package there.
[gentoo-user] Re: meson build woes
> >> - 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 How did you recover? You couldn't even use setup.py at that stage. Did you have to download the python distfile if you didn't have it already, and build using configure and make directly? Tom
[gentoo-user] Re: meson build woes
On 2020-08-24, Franz Fellner wrote: > On Mo 24 Aug 2020 11:21:10 +0200, Hogren 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
