Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 301574 - portage should not downgrade a package in case of a digest verificationissue
Summary: portage should not downgrade a package in case of a digest verificationissue
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High enhancement (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-19 20:56 UTC by Toralf Förster
Modified: 2010-01-20 13:12 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Toralf Förster gentoo-dev 2010-01-19 20:56:38 UTC 
Today I got :

...
Calculating dependencies  .. * Digest verification failed:
 * /usr/portage/x11-libs/libXfontcache/libXfontcache-1.0.5.ebuild
 * Reason: Failed on RMD160 verification
 * Got: fcfdfea69ce55e0c73959d08bbb3ac4635d2ab78
 * Expected: 60d820c2aac51712c607829c290a623e1557400a
... done!

and portage tried to downgrade it :
...
[ebuild     UD]    x11-libs/libXfontcache-1.0.4 [1.0.5] USE="-debug" 210 kB
...

IN this case portage shouldn't do anything isn't it ?

Reproducible: Always
Comment 1 Rafał Mużyło 2010-01-19 20:59:10 UTC 
INVALID.
If digest verification fails, ebuild is correctly treated
as not existing. You never known what exactly got corrupted.
Comment 2 Graham Murray 2010-01-20 13:12:13 UTC 
(In reply to comment #1)
> INVALID.
> If digest verification fails, ebuild is correctly treated
> as not existing. You never known what exactly got corrupted.
> 

Yet that is no reason to downgrade the already installed and (assumed to be) working version. If the change to the ebuild was deliberate and the digests correctly updated in the manifest, then (as the version number is unchanged) unless the --newuse or --reinstall change-use flags were given and the use flags changed then portage would not have attempted to re-install the package so surely that is also the correct behaviour in the case where the digest fails on an already installed package.