Bug 301574

Summary:	portage should not downgrade a package in case of a digest verificationissue
Product:	Gentoo Linux	Reporter:	Toralf Förster <toralf>
Component:	Current packages	Assignee:	Gentoo Linux bug wranglers <bug-wranglers>
Status:	RESOLVED INVALID
Severity:	enhancement
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

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.