Bug 291941

Summary:	The md5sum of portage-latest.tar.bz2 differs from portage-latest.tar.bz2.md5sum.
Product:	Gentoo Release Media	Reporter:	Olaf Dreyer <olaf>
Component:	Other	Assignee:	Gentoo Infrastructure <infra-bugs>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	olaf
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
URL:	http://de-mirror.org/distro/gentoo/snapshots/
Whiteboard:
Package list:		Runtime testing required:	---

Description Olaf Dreyer 2009-11-05 07:11:37 UTC

Due to some problems with our web-proxy, I'm not able to use rsync and web-rsync.
So I wrote a script, which downloads portage-latest.tar.bz2 and portage-latest.tar.bz2.md5sum and checks the integrity of the file. After that, it's replacing the portage tree and so on ...
That works like a charm. But since a few days, the md5sum and the content of the md5sum-file are different.

Looking at the directory shows the problem: The md5sum-file is 1 day too old.
If I use the portage-YYYYMMDD.tar.bz2* files, it's all ok.

The same effect happens on different mirrors.

Greetings

Olaf


Reproducible: Always

Comment 1 Andrew Gaffney (RETIRED) gentoo-dev

2009-11-07 21:15:06 UTC

The portage snapshots are handled by infra

Comment 2 Olaf Dreyer 2009-11-16 06:02:22 UTC

Today, the md5sum was ok. Has somebody fix the bug?

Comment 3 Olaf Dreyer 2009-11-18 06:49:52 UTC

In the last days, the problem is gone...