Summary: | repoman from portage 2.2_rc21 didnt update manifests if Manifest alrady exist | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Alexey Shvetsov <alexxy> |
Component: | Repoman | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | InVCS |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 210077, 254662 |
Description
Alexey Shvetsov
2009-01-13 13:35:12 UTC
This is the intended behavior. You can force it to update the digest like this: ebuild --force kdebase-4.1.4.ebuild digest *** This bug has been marked as a duplicate of bug 253856 *** Reopening since the error message isn't very good. We can make it better. It's fixed in svn r12498 to look like this: !!! No write access to '/usr/portage/distfiles' !!! Previously fetched file: 'kdebase-4.1.4.tar.bz2' !!! Reason: Filesize does not match recorded size !!! Got: 4403306 !!! Expected: 4402975 !!! File kdebase-4.1.4.tar.bz2 is incorrect size, but unable to retry. !!! Fetch failed for kdebase-4.1.4.tar.bz2, can't update Manifest !!! If you would like to forcefully replace the existing Manifest entry !!! for kdebase-4.1.4.tar.bz2, use the following command: !!! ebuild --force kdebase-4.1.4.ebuild manifest This is fixed in 2.1.6.6 and 2.2_rc22. |