Summary: | emerge restart failed after change of portage version: No module named missingos | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Jarkko <jval> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | Inclusion |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | patch against portage-2.0.49-r18.ebuild |
Description
Jarkko
2003-12-01 05:58:32 UTC
Hello, What is your python version? And do you have /usr/bin/python2.2? I cannot check that anymore because I decided to build the system from scratch again... Although it was most likely 2.2 because the python is already present after stage2 and I did emerge system which doesn't update packages (only builds the missing ones). Okay I guess it now. The new portage doesn't need missingos anymore because python is newer too. My problem was that python wasn't updated at the moment but portage still removed missingos. Hmm, why was the portage even updated when running emerge system? Updates should only happen with the -u switch. It may be portage-2.0.49-r18 bug. -r18 uses 'which' command to install missings.so. But there is not the command in stage 1 or 2, so missings.so was not installed. I think you reinstalled from stage3 or not using ~x86. right? Yes, stage3 works. OK. we'll fix it. Created attachment 21701 [details, diff]
patch against portage-2.0.49-r18.ebuild
fixed |