Summary: | Portage 2.0.49-r5(-r7) kills new build packages | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Sven Sternberger <sven.sternberger> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | CC: | mholzer, rmrf, robert.w.thomas, wstevenso |
Priority: | Highest | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 29136 | ||
Bug Blocks: |
Description
Sven Sternberger
2003-09-22 04:28:42 UTC
Wow now I have a problem. After emerge the r4 release I don't have any portage :-/ because the buggy r5 kills first r5 and then unmerged r4 use the rescue portage in /usr/portage/sys-apps/portage/files/ Thanks! This helped! The only thing I have to do additionally is to manually remove the "killed" packages from the portage database /var/db, because everytime I emerged with the rescue system for example "portage" at the end emerge said that the protected version (which was deleted in the beginning) is protected and that the new installed version should be cleaned out and I couldn't make an emerge -C I found the reason for this! In bug 29136 I saw a problem with sort and locales other then C. Of course I make an export LANG=C before I start emerge, but the sub processes get the wrong locale again. I decided to set the locale to C now in global manner and now emerge works :-/ bye! *** Bug 29960 has been marked as a duplicate of this bug. *** *** Bug 26460 has been marked as a duplicate of this bug. *** Martin, could you check that bug #26460 is really a duplicate please? As explained there, I really don't see what it would share with this one. Thanks. *** Bug 26167 has been marked as a duplicate of this bug. *** *** Bug 27843 has been marked as a duplicate of this bug. *** -r10 & -r12 is in cvs now |