Summary: | dev-python/markupsafe et al: bad magic number in setuptools | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Eric Westbrook <gentoo> |
Component: | Current packages | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | gentoo, sam |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Build log
emerge --info emerge -pqv |
Description
Eric Westbrook
2020-08-02 21:27:45 UTC
Created attachment 652440 [details]
Build log
Created attachment 652442 [details]
emerge --info
Created attachment 652444 [details]
emerge -pqv
It seems likely to me your setuptools is corrupt. What happens if you re-emerge (with -1) it? I would also be worried about other files being corrupt. That occurred to me too. Unfortunately re-emerging setuptools was not curative. In fact, re-emerging python as well as all other installed python modules did not help. Since this does not occur on another very similarly configured system, I too suspect corruption somewhere, but I have no idea where or how to correct it. Turns out that the packages in question had been emerged with FEATURES="buildpkg". Removing the existing binary package tarballs from the packages directory allowed the emerge to succeed. I now wonder whether the binary packages that were previously built should have been deemed a system match. Seems to me that they shouldn't have, but it's unclear to me how portage could determine that. The root cause of this ended up being a misguided PYTHONPATH setting in root's .bashrc which wrongly put an old python library directory at the front of the list. Upon removing that footgun, all proceeds well. |