Summary: | dev-lang/python-2.5.1-r3: After installation of binary package, python broken | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Alexander Skwar <askwar> |
Component: | Core | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED INVALID | ||
Severity: | blocker | CC: | ade05fr, dev-portage, karpi.web |
Priority: | High | ||
Version: | 2.1 | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://public-files.askwar.gentoo-packages.s3.amazonaws.com/GentooUSB/packages/All/ | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
/etc/make.conf
/etc/portage/package.use |
Description
Alexander Skwar
2007-11-08 13:12:23 UTC
Created attachment 135484 [details]
/etc/make.conf
Created attachment 135485 [details]
/etc/portage/package.use
It's python that's borked, not portage. Well, okay. Effect is, that portage doesn't work :) Anyway. The breakage really IS reproducible. Insall stage3-i686-2007.0.tar, install a current portage tree, use attached make.conf & package.use and run emerge -v --usepkgonly python Result: Broken. No surprise, as the binary package is the issue (it's apparently missing at least one file). Any progress on making --buildpkg work with python? (In reply to comment #6) > Any progress on making --buildpkg work with python? AFAIK, --buildpkg usually works with python as well as any other package. According to comment #4 you were using --usepkgonly. Of course it's reproducible using the _same_ binary package. Can you reproducibly build a bad binary package though? If it was easily reproducible, then more people would have reported this. I can't reproduce the problem here. Can you reproduce a bad binary package as Zac said? If yes, can you try re-emerging openssl and try again? *** Bug 245162 has been marked as a duplicate of this bug. *** is there any solution ??? (In reply to comment #9) > *** Bug 245162 has been marked as a duplicate of this bug. *** > You can try manually unpacking a python tarball from the tinderbox: http://tinderbox.dev.gentoo.org/html/ (In reply to comment #11) > You can try manually unpacking a python tarball from the tinderbox: > > http://tinderbox.dev.gentoo.org/html/ > i solved my problem with a method to recover portage : "Manually fixing broken portage installations" thanks Hello, ive fallen into this horrible bug too. Only upgreading one old system, following conflict instruction in order to install e2fsprogs ive unmerged ss, mktemp, com_err -> and portage becomes totally unusable. Nothig do with python, but this error appears: ImportError: No module named _md5 Ive manually repaired this: Find somewhere 4 files and copy them into broken system: /usr/lib/python2.5/lib-dynload/_md5.so /usr/lib/python2.5/lib-dynload/_sha.so /usr/lib/python2.5/lib-dynload/_sha256.so /usr/lib/python2.5/lib-dynload/_sha512.so it works for me.. Hello, This is due to a broken python. Missing files in a python installation in Gentoo is BAD. Please, if you broke, missed, misplaced or played with your existing python and get this error, please follow Zac's advice and install python from tinderbox and then emerge python again. Closing this bug as invalid. Best regards, |