Summary: | portage 2.0.49-r18 breaks itself (xpak module gone) | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Manfred Stienstra <manfred.stienstra> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | critical | CC: | phil |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Manfred Stienstra
2003-11-29 05:18:06 UTC
It works for me. I'd like to know more infomation. What did do you? emerge foo? And please show us # ls -l /usr/lib/portage/pym/ # ls -l /usr/lib/python2.2/site-packages/ # grep xpak /var/db/pkg/sys-apps/portage-2.0.49-r18/CONTENTS # which xpak # xpak And what was the previous portage version in the machine. -r17 or -r16 or etc? I copied xpak.py from the tarball to the right place and after emerging r15 and r18 again everything works again. I can't recreate te problem... Sorry. OK. if the bug appears again, please reopen this bug. Thanks Using the "actual" (quite old) stage3 tarball reveals all the old problem. Had the same here when used in conjunction with --buildpkg. emerge failed in the same way. It seems that after a re-emerge of portage all runs well again, which is strange as it got merged the first time. |