> > Here are the MD5 checksums of the files I downloaded: > > eb2f763d967286313bd339f781ce664d sarge-i386-businesscard.iso > > 52a66d5290a43e17dd0216467962bfc9 sarge-i386-netinst.iso > > When checking CD's integrity, it says that the > > file ./dists/sarge/main/binary-i386/Release is corrupted. > > It's right in complaining, the MD5 sums of 20040429 were: > 6248f2d30f37ad0d82bd2622d0b7a7f1 sarge-i386-businesscard.iso > 251d25b5b0aaa0d2c4c911e4047053e7 sarge-i386-netinst.iso
This is not what I see on the directory where I downloaded my files from: http://cdimage.debian.org/pub/cdimage-testing/sarge_d-i/i386/beta4/MD5SUMS I perhaps badly expressed myself when saying I was using 20040429. I downloaded beta4, which was built on 20040429, according to the help at beginning of installation. Sorry for that. So the MD5 sums of my images are ok, but the integrity test still fails on ./dists/sarge/main/binary-i386/Release, on both images. I compare the md5 sum of this file with what is written in md5sum.txt, at the root of the CD, and this file is ok. I suppose there is a path problem: I'm not absolutely sure about that, but when I run a shell it seems that the current directory is '/' (# export [...] export PWD='/' [...] ) So ./dists/sarge/main/binary-i386/Release maybe refers to /dists/sarge/main/binary-i386/Release instead of /cdrom/dists/sarge/main/binary-i386/Release. ./dists/sarge/main/binary-i386/Release is the first file to be checked, according to md5sum.txt. Running md5sum -c md5sum.txt in directory /cdrom succeed for every file on the the cdrom except for README.html. I still have my problem loading libc-udeb on my computer, but it worked on two other. Thanks Nicolas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
