Summary: | portage-2.0.50_pre16: regenworld is broken | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Andreas Simon <andreas.w.simon> |
Component: | [OLD] Core system | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | Inclusion |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | new regenworld script |
Description
Andreas Simon
2004-01-14 06:46:15 UTC
Created attachment 23834 [details]
new regenworld script
partly rewritten regenworld script. Please test and report success/failure.
The new script fixes the KeyError, I can no longer reproduce it with the new script. But one thing: If I delete the old world file it creates a new one but only adds 164 of 496 installed packages to it. Shouldn't that be more? the world file should only contain packages that you emerged (not the dependencies) and are not in the system profile, so 1/3 or all packages sounds reasonable. I no longer get keyword errors. Thank you. However, I haven't a clue of how to deal with ambiguous package names. i.e. ace is an ambiguous package name, candidates are ['dev-libs/ace'. 'game-board/ace'] libnet is an ambiguous package name, candidates are ['dev-perl/libnet', 'net-libs/libnet] I also haven't a clue of how to deal with injected packages. i.e. ignoring broken log entry for nasm-0.98.36 (likely injected) Suggestions? Advice? :-) Hello Marius, this is Marius :-) Thanks for the new script, it helped fix my problem. Since I'm not completly familiar with Python and the internal design of Portage, I lost a lot of time trying to get my workstation fixed by brute-force methods like re-stage3'ing. Of course it didn't help but only made my problems worse. Is it possible to add functionality to portage to detect that a user has the old naming scheme in either the world file and/or the package.(un)mask files so that a portage newbie doesn't get so lost when portage breaks with ugly error messages ? That would help a lot of people when upgrading to 2.0.50. Thanks. It seems /usr/lib/portage/bin/regenworld.sh looks in /var/log/regenworld for new keys. I had the same with : dev-python/Imaging-py21-1.1.4 null/quake3-urbanterror-3 I think the following lines in my emerge.log to be responsible : 1056725890: *** emerge --update --deep dev-python/Imaging-py21-1.1.4 1061332510: *** emerge unmerge quake3-urbanterror-3 it must be a regexp problem in regenworld.sh. Hmm. I've `fixed' it by inserting this line into /usr/lib/portage/bin/regenworld.sh: gawk '/^[a-z/-]*-[0-9]/ { print "="$0 }' | Ugly hack - but it works. Nick, this should go into portage before 2.0.50 goes stable Attached script works for me. Had a similar backtrace to what was reported with -pre22. It's in 2.0.50 |