Summary: | <=sys-apps/portage-2.1.7.16: ValueError in portage.manifest.parseManifest2() | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Tom Densham <tomdensham> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | InVCS |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 302803 | ||
Attachments: | Handle ValueError triggered by corrupt Manifest entry |
Description
Tom Densham
2010-01-23 14:11:00 UTC
Created attachment 217290 [details, diff]
Handle ValueError triggered by corrupt Manifest entry
Save as /tmp/manifest_valueerror.patch and apply as follows:
patch /usr/lib/portage/pym/portage/manifest.py /tmp/manifest_valueerror.patch
Thank you for the patch. Unfortunatly it did not fix the problem, although it did succeed in suppressing the error. This allowed me to discover, by attempting to re-merge firefox, that i could not download the src due to a manifest error? So i decided to try removing my entire portage tree and re-syncing which solved the problem. The fix hasn't been released yet. This is fixed in 2.1.7.17 and 2.2_rc62. |