Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 911239 - All python 3.11 packages fail to install due to misnamed files
Summary: All python 3.11 packages fail to install due to misnamed files
Status: UNCONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: Normal blocker (vote)
Assignee: Python Gentoo Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-07-26 06:34 UTC by zaeleth
Modified: 2023-07-30 05:59 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info (emerge--info.txt,7.17 KB, text/plain)
2023-07-26 06:34 UTC, zaeleth
Details
emerge --info (emerge--info.txt,7.17 KB, text/plain)
2023-07-26 06:35 UTC, zaeleth
Details
emerge -pqv (emerge-pqv.txt,163 bytes, text/plain)
2023-07-26 06:39 UTC, zaeleth
Details
build log for setuptools (build.log,89.50 KB, text/plain)
2023-07-26 06:42 UTC, zaeleth
Details
ebuild environment (environment,162.77 KB, text/plain)
2023-07-26 06:50 UTC, zaeleth
Details

Note You need to log in before you can comment on or make changes to this bug.
Description zaeleth 2023-07-26 06:34:48 UTC
Created attachment 866288 [details]
emerge --info

Issue: 
Any package using python 3.11 will fail to install due to a seemingly misnamed directory inside their build directory, specifically:

/var/tmp/portage/dev-python/{insert python package name here}/work/{insert python package name here}/usr/lib/python3.11
is missing, instead:
/var/tmp/portage/dev-python/{insert python package name here}/work/{insert python package name here}/usr/lib/python3.10 will be in it's place. 

Reproduction: 
Any attempt to emerge any python package with python 3.11 fails the same way, aside from python itself.

Reproducable: Always

Steps to reproduce: emerge any python package


Forcing the package to use python3.10 only will allow the package to install normally, however this requires the old version to be removed using emerge -C beforehand, as Portage absolutely refuses to cooperate otherwise, citing slot conflicts between the installed version and the version to be installed, this has to be done with every single package with python dependencies, so that isn't a solution.
Comment 1 zaeleth 2023-07-26 06:35:58 UTC
Created attachment 866289 [details]
emerge --info
Comment 2 zaeleth 2023-07-26 06:39:01 UTC
Created attachment 866290 [details]
emerge -pqv
Comment 3 zaeleth 2023-07-26 06:42:10 UTC
Created attachment 866291 [details]
build log for setuptools
Comment 4 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2023-07-26 06:43:01 UTC
For more context for others: I assume you're the person I referred here from the forums at https://forums.gentoo.org/viewtopic-t-1164345.html.

Could you upload the environment file as well please? (It's mentioned at the bottom of the build.log.)
Comment 5 zaeleth 2023-07-26 06:50:26 UTC
Created attachment 866293 [details]
ebuild environment

yes, and here you go
Comment 6 zaeleth 2023-07-30 01:24:46 UTC
(In reply to Sam James from comment #4)
> For more context for others: I assume you're the person I referred here from
> the forums at https://forums.gentoo.org/viewtopic-t-1164345.html.
> 
> Could you upload the environment file as well please? (It's mentioned at the
> bottom of the build.log.)

i hit add comment instead of reply, did you see the new comment with the environment file?
Comment 7 zaeleth 2023-07-30 05:59:35 UTC
I MAY have fixed it, I basically reinstalled all of setuptools dependencies with Python3.10, some of them were missing dependencies that for some reason Portage didn't pull in, and dev-python/six had file collisions with itself, I had to do this one at a time because a lot of the dependencies had to be removed via emerge -C before Portage would reinstall them, it seems like emerge -uDN world is proceeding normally, except for more missing Python libraries right off the rip, again they weren't pulled in automatically, strange. 

I did the dependencies for setuptools because basically everything that has the file name problem has setuptools as a dependency, so since setuptools failed it meant one of it's dependencies was probably the smoking gun here.