Bug 281857

Summary:	dev-python/pygtk-2.14.1-r1 bad digest
Product:	Gentoo Linux	Reporter:	Robin Bankhead <gentoo>
Component:	New packages	Assignee:	Gentoo Linux Gnome Desktop Team <gnome>
Status:	RESOLVED INVALID
Severity:	normal	CC:	python
Priority:	High
Version:	2008.0
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Robin Bankhead 2009-08-18 03:24:02 UTC

When attempting any merge including dev-python/pygtk-2.14.1-r1, I get this:

!!! Digest verification failed:
!!! /usr/portage/dev-python/pygtk/files/pygtk-2.14.1-ltihooks.patch
!!! Reason: Failed on RMD160 verification                          
!!! Got: 585f8fad596557af1fd28815be7a02b2524361fb                  
!!! Expected: 60856d3e3ad24661a79997b0474b407e7aa92df5

Comment 1 Patrick Lauer gentoo-dev

2009-08-18 13:31:29 UTC

Cannot reproduce here. Try to emerge --sync, reopen bug if it persists ...

Comment 2 Robin Bankhead 2009-08-18 13:42:29 UTC

My server has been syncing (successfully, according to logs) for a week already and the condition is the same.  Yesterday was the first time I've checked since then, I assumed it would have been reported and corrected by now.

If not, I assume there is a problem with the sync mirror.
SYNC="rsync://rsync.uk.gentoo.org/gentoo-portage"

Comment 3 Arfrever Frehtes Taifersar Arahesis (RETIRED) gentoo-dev

2009-08-21 18:28:29 UTC

Try with a different rsync server.

Comment 4 Robin Bankhead 2009-08-23 12:51:59 UTC

Have now also tried:

rsync.de.gentoo.org
rsync.us.gentoo.org

The problem remains. If we assume that the mirrors are OK, what else can the problem be?

Comment 5 Arfrever Frehtes Taifersar Arahesis (RETIRED) gentoo-dev

2009-08-23 17:20:07 UTC

Maybe run:
rm -fr "$(portageq envvar PORTDIR)/dev-python/pygtk"
emerge --sync

Comment 6 Robin Bankhead 2009-08-25 08:25:10 UTC

This fixed it (with original UK mirror). What would have caused it?

Comment 7 Rémi Cardona (RETIRED) gentoo-dev

2009-08-25 10:02:21 UTC

Small rsync error on your machine. ie wrong file content with the correct timestamp. Happens once in a while.

Thanks for the follow up. Closing