Summary: | emerge -Up world throws error | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Subodh Shrivastava <subodh> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | andreas.kotowicz, latexer, mholzer, Rainmaker526, wilscarlet |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Subodh Shrivastava
2004-04-07 12:54:10 UTC
*** Bug 47145 has been marked as a duplicate of this bug. *** How I solved this: 1) unmasking portage-2.0.50-r4 (adding =sys-apps/portage-2.0.50-r4 to /etc/portage/package.unmask) 2) emerge =portage-2.0.50-r4 3) emerge -p world 4) wait for a while (strange messages may appear) 5) Problem solved. Can anyone verify that using portage-2.0.50-r4 solves this? The problem has been fixed in -r4. But -r4 is UNMASKED version now. It includes other fixes and some new features. You should know that if you use it. *** Bug 47182 has been marked as a duplicate of this bug. *** *** Bug 24695 has been marked as a duplicate of this bug. *** *** Bug 47181 has been marked as a duplicate of this bug. *** *** Bug 47225 has been marked as a duplicate of this bug. *** I got this too after rsyncing last night, but rsyncing today made it go away. If you can reproduce this with a stable version of portage, please re-open. reproduced on sys-apps/portage-2.0.51.22-r2 on 2 different PC's, one ~x86 and one x86. Fixed! After an update of I think, shadow, the default PATH after su'ing was set to /bin:/usr/bin:/usr/ucb:/usr/local/bin After adding /usr/sbin to the path variable, portage worked fine again. |