reprise of Something is wrong in the daily build process for debian testing netinst and businesscard images
Package: debian-installer
Interestingly enough, though I first discovered this on the "powerpc"
it's not unique to the "powerpc" -- the same thing seems to be
happening for "i386".
Looking at the DebianInstaller/FAQ - Debian Wiki question 29 takes us
to:
http://wiki.debian.org/DebianInstaller/
FAQ#head-1b80545b9731828a5f8298ff1b431748501b4382
Q: What types of media are available? What versions are available?
Where to download?
Which points to
http://www.debian.org/devel/debian-installer/
Going to the testing daily netinst cd image for powerpc takes us to
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/
powerpc/iso-cd/
Which contains:
============================================================
Index of /cdimage/daily-builds/daily/arch-latest/powerpc/iso-cd
Name Last modified Size
Parent Directory -
MD5SUMS 05-Jun-2006 02:17 143
debian-testing-powerpc-businesscard.iso 13-Jun-2006 02:45 59M
debian-testing-powerpc-netinst.iso 13-Jun-2006 02:47 166M
Apache/2.0.53 (Debian GNU/Linux) Server at cdimage.debian.org Port 80
============================================================
Note the respective dates of the MD5SUMS file and the ".iso" images!
The MD5SUMS file contains:
============================================================
b995eaf753314148b780b40f16ce1c45 debian-testing-powerpc-
businesscard.iso
aeba38af24d18e4c3aa81eec2f42cf90 debian-testing-powerpc-netinst.iso
============================================================
When you download the netinst image, its md5 checksum doesn't match
the one given in the MD5SUMS file. Which is not really surprising
given the respective dates.
Something's wrong...
If this is not the right place to get daily testing images, then the
links should be changed -- and incidentally, what *is* this directory
for anyway?
If it is the right place to get daily testing images, then the build
process is broken and ought to be fixed.
For what it's worth, I reported earlier (as bug #370373) the same
symptoms, which mysteriously went away almost as soon as I reported
it. But, like the cat, it came back! Can we get a more permanent fix?
Rick
Reply to: