Summary: | [PATCH] Portage crashes when updating cache | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Priit Laes (IRC: plaes) <plaes> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | 3.14159, alanh, brodigan, chutz+bugs.gentoo.org, craig, fade, HowardZ1, jakub, kavli, matkaw, radek, ron, sebastian, taken, xzx |
Priority: | High | Keywords: | InVCS |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 106648, 108082 | ||
Attachments: | portage-2.0.51.22-emerge-cleanse_cache-has_key(cat).patch |
Description
Priit Laes (IRC: plaes)
2005-07-27 01:49:56 UTC
Created attachment 64585 [details, diff]
portage-2.0.51.22-emerge-cleanse_cache-has_key(cat).patch
We are trying to cleanse_cache() a category or package that does not exist in
the cache. It should be safe to make cleanse_cache() a "no op" in cases where
there is nothing to be cleansed.
variation of this I just commited (catch and discard KeyError exception) *** Bug 105332 has been marked as a duplicate of this bug. *** (In reply to comment #2) > variation of this I just commited (catch and discard KeyError exception) There is still a KeyError thrown from another part of cleanse_cache in portage-2.0.52-r1 (see bug 105332). *** Bug 105951 has been marked as a duplicate of this bug. *** *** Bug 105943 has been marked as a duplicate of this bug. *** *** Bug 106864 has been marked as a duplicate of this bug. *** *** Bug 96410 has been marked as a duplicate of this bug. *** *** Bug 107097 has been marked as a duplicate of this bug. *** This is fixed in portage-2.0.53_rc3. *** Bug 109674 has been marked as a duplicate of this bug. *** *** Bug 113416 has been marked as a duplicate of this bug. *** *** Bug 118536 has been marked as a duplicate of this bug. *** 1. boot from LiveCD & others
2. chroot /mnt/gentoo /bin/bash
3. env-update
4. source /etc/profile
5. export PS1="(chroot) $PS1"
6. patch the emerge file
6. emerge sync
>>> Updating Portage cache:
Traceback (most recent call last):
File "/usr/bin/emerge", line 2706, in ?
oldcat = portage.catsplit(cp_list[0])[0]
IndexError: list index out of range
new emerge file size is:
-rwxr-xr-x 1 root root 109515 Jan 11 12:00 /usr/lib/portage/bin/emerge
I think patch not working...
Greets
(In reply to comment #14) > I think patch not working... The cache update is not absolutely critical, so after the error occurs, emerge will still allow you upgrade to portage-2.0.53 or higher. `emerge -u portage && emerge --metadata` *** Bug 118921 has been marked as a duplicate of this bug. *** *** Bug 120276 has been marked as a duplicate of this bug. *** *** Bug 123372 has been marked as a duplicate of this bug. *** |