| View previous topic :: View next topic |
| Author |
Message |
mqduck
n00b
Joined: 04 Apr 2006
Posts: 63
|
 Posted: Fri Dec 15, 2017 8:18 am Post subject: emerging any package in main portage tree segfaults |
 |
|
Emerging a package in the main portage tree always immediately segfaults. For example:
| Code: | # emerge udftools
These are the packages that would be merged, in reverse order:
Calculating dependencies... done!
[ebuild N ] sys-fs/udftools-1.1::gentoo 642 KiB
Total: 1 package (1 new), Size of downloads: 642 KiB
Would you like to merge these packages? [Yes/No]
>>> Verifying ebuild manifests
Segmentation fault |
Trying to create a new manifest also segfaults:
| Quote: | # cd /usr/portage/sys-fs/udftools/
# ebuild udftools-1.1.ebuild manifest
>>> Creating Manifest for /usr/portage/sys-fs/udftools
Segmentation fault |
However, if I copy that ebuild file to my local portage tree and 'ebuild <package-version>.ebuild manifest' it, it can emerge just fine.
This problem has persisted for several days now. Even deleting /usr/portage entirely (except /usr/portage/distfiles) and resyncing doesn't solve it.
_________________
Property is theft. |
|
| Back to top |
|
 |
fedeliallalinea
Administrator
Joined: 08 Mar 2003
Posts: 30905
Location: here
|
|
| Back to top |
|
|
mqduck
n00b
Joined: 04 Apr 2006
Posts: 63
|
| Posted: Sat Dec 16, 2017 7:52 am Post subject: |
|
|
Unmerging and re-emerging dev-python/pyblake2 did the trick. Thanks!
_________________
Property is theft. |
|
| Back to top |
|
|
|
Portage & Programming
