Re: checksum error sarge-1.jigdo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 18 January 2004 10:59 am, Richard Atterer wrote: > On Sun, Jan 18, 2004 at 09:45:59AM -0900, Greg Madden wrote: > > I ran jigdo-lite, built an iso image using sarge-i386-1.jigdo, > > Jan-16-2004. When the checksum part runs it fails. I mounted the > > new sarge-i386-1.iso as a loop device and ran jigdo-lite again, I > > get the following error. There may be another file with mis-matched > > checksum. > > > > Found 7323 of the 7325 files required by the template > > Error: `/pub/iso/loop/pool/main/g/gtk+1.2/ > > libgtk1.2-dbg_1.2.10-16_i386.deb' does not match checksum in > > template data jigdo-file failed with code 2 - aborting. > > This means that jigdo-file read the file two times, once to find out > its md5sum and once to copy it to the output image. The second time, > the file no longer had the same md5sum. > > Two possible causes for this are undetected read errors with old, > faulty CDs (unlikely in your case since you seem to be loop-mounting > stuff), and a corrupt jigdo-file-cache.db file. If you enter > > jigdo-file --cache jigdo-file-cache.db md5sum > /pub/iso/loop/pool/main/g/gtk+1.2/libgtk1.2-dbg_1.2.10-16_i386.deb > > twice and delete the cache file inbetween, does the output change? > > Cheers, > Trying to resume building the iso with the original .template & .jigdo file didn't work.I dl'd the .template & .jigdo files again and used the iso made from my first atempt. There where three files that did not match, were missing from the iso or bad checksums?, I used ~/ gluck.debian.org/cdimage/testing/dvd/jigdo-area/i386/snapshot/ to grab the three packages and the new iso's checksum went okay. - -- Greg Madden Debian GNU/Linux -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFACx3Jk7rtxKWZzGsRAt2KAJ9fITSrp1XPKD2+PNrH6HFDIJw+ggCbBTL1 86Zp0/C+UUl9hifZsTh+/dw= =GZpa -END PGP SIGNATURE-
Re: checksum error sarge-1.jigdo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 18 January 2004 10:59 am, Richard Atterer wrote: > On Sun, Jan 18, 2004 at 09:45:59AM -0900, Greg Madden wrote: > > I ran jigdo-lite, built an iso image using sarge-i386-1.jigdo, > > Jan-16-2004. When the checksum part runs it fails. I mounted the > > new sarge-i386-1.iso as a loop device and ran jigdo-lite again, I > > get the following error. There may be another file with mis-matched > > checksum. > > > > Found 7323 of the 7325 files required by the template > > Error: `/pub/iso/loop/pool/main/g/gtk+1.2/ > > libgtk1.2-dbg_1.2.10-16_i386.deb' does not match checksum in > > template data jigdo-file failed with code 2 - aborting. > > This means that jigdo-file read the file two times, once to find out > its md5sum and once to copy it to the output image. The second time, > the file no longer had the same md5sum. > > Two possible causes for this are undetected read errors with old, > faulty CDs (unlikely in your case since you seem to be loop-mounting > stuff), and a corrupt jigdo-file-cache.db file. If you enter > > jigdo-file --cache jigdo-file-cache.db md5sum > /pub/iso/loop/pool/main/g/gtk+1.2/libgtk1.2-dbg_1.2.10-16_i386.deb > > twice and delete the cache file inbetween, does the output change? > > Cheers, > Trying to resume building the iso with the original .template & .jigdo file didn't work.I dl'd the .template & .jigdo files again and used the iso made from my first atempt. There where three files that did not match, were missing from the iso or bad checksums?, I used ~/ gluck.debian.org/cdimage/testing/dvd/jigdo-area/i386/snapshot/ to grab the three packages and the new iso's checksum went okay. - -- Greg Madden Debian GNU/Linux -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFACx3Jk7rtxKWZzGsRAt2KAJ9fITSrp1XPKD2+PNrH6HFDIJw+ggCbBTL1 86Zp0/C+UUl9hifZsTh+/dw= =GZpa -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Status of the cd building (NEW: bootable cd images for hppa)
On Sunday 18 January 2004 18:49, Raphael Hertzog wrote: > Le Sat, Jan 17, 2004 at 05:22:06PM +0100, Santiago Garcia Mantinan écrivait: > > Well, aside all that, I'm thinking in how could I reschedule the full cd > > set and dvd set builds, as now it takes really long to build and I cannot > > build all cds in the same day like we used to do. > > > > So I'm wondering... should I spread the build throughout the week? or > > would it be better for gluck if I could build the most each day and have > > the machine building cds all day long during 3 or 4 days? > > Do not generate full CD set, nobody is downloading them isn't it ? > Generate daily netinst & businesscard CD for all arches. Full CD and DVD > can be done once a week. And even for that I'm sure we could do only the > 3 first CD. if I might download these files vie rsync I'll do it every single night. So rsync or ftp daemon, please. Probably the lack of rsync and/or ftp is the reason nobody downloads them. Please let us use these files more easily. -- pub 4096R/0E4BD0AB 2003-03-18 fingerprint 1AE7 7C66 0A26 5BFF DF22 5D55 1C57 0C89 0E4B D0AB
Re: Status of the cd building (NEW: bootable cd images for hppa)
On Sunday 18 January 2004 18:49, Raphael Hertzog wrote: > Le Sat, Jan 17, 2004 at 05:22:06PM +0100, Santiago Garcia Mantinan écrivait: > > Well, aside all that, I'm thinking in how could I reschedule the full cd > > set and dvd set builds, as now it takes really long to build and I cannot > > build all cds in the same day like we used to do. > > > > So I'm wondering... should I spread the build throughout the week? or > > would it be better for gluck if I could build the most each day and have > > the machine building cds all day long during 3 or 4 days? > > Do not generate full CD set, nobody is downloading them isn't it ? > Generate daily netinst & businesscard CD for all arches. Full CD and DVD > can be done once a week. And even for that I'm sure we could do only the > 3 first CD. if I might download these files vie rsync I'll do it every single night. So rsync or ftp daemon, please. Probably the lack of rsync and/or ftp is the reason nobody downloads them. Please let us use these files more easily. -- pub 4096R/0E4BD0AB 2003-03-18 fingerprint 1AE7 7C66 0A26 5BFF DF22 5D55 1C57 0C89 0E4B D0AB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
MD5 discrepancies with 3.0 r2 ISO contents
I found several discrepancies between the md5sum.txt and the contents for the ISO images (downloaded from mirror ftp://ftp.lug.udel.edu/ pub/iso-images/Debian/3.0_r2/i386/) for 3.0 r2. Most of the CDs consistently show two problems: 1. './README.html', which I see others have reported, and 2. a bunch of files in ./dists/testing - a directory that doesn't exist. (./dists/testing is a zero byte plain file, not a directory on my CDs.) I assume these are harmless, and might be good things to note on http://www.debian.org/CD/. I also noticed the problem with './pool/main/f/fgfs-base/ fgfs-base_0.7.9-1_all.deb' on disk 3, as someone else reported on the list. That's FlightGear flight simulator? Seems like another item worth adding to the last minute notes. Lastly, I'm seeing far more extensive problems on disk 1 (about 1700 files not matching). So much so, that I'm suspecting the integrity of the image I downloaded. Though it could be a messed up md5sum.txt. Unlike for the other disks, which had 16 files from the ./dists/testing/ directory listed in the md5sum.txt, this one includes 1122. Similarly there are a whole bunch of files listed from the './dists/woody/ main/disks-i386/current/ directory, which doesn't exist on the CD. (Similar to testing it is just a plain file.) In addition to the missing files, there were a bunch of MD5 mismatches, such as: md5sum: MD5 check failed for './dists/woody/main/disks-i386/3.0.23-2002-05-21/images-1.44/safe/driver-1.bin' md5sum: MD5 check failed for './dists/woody/main/disks-i386/3.0.23-2002-05-21/images-1.44/safe/driver-2.bin' md5sum: MD5 check failed for './dists/woody/main/disks-i386/3.0.23-2002-05-21/images-1.44/safe/driver-3.bin' md5sum: MD5 check failed for './dists/woody/main/disks-i386/3.0.23-2002-05-21/images-1.44/safe/driver-4.bin' md5sum: MD5 check failed for './dists/woody/main/disks-i386/3.0.23-2002-05-21/images-1.20/safe/driver-1.bin' md5sum: MD5 check failed for './dists/woody/main/disks-i386/3.0.23-2002-05-21/images-1.20/safe/driver-2.bin' md5sum: MD5 check failed for './dists/woody/main/disks-i386/3.0.23-2002-05-21/images-1.20/safe/driver-3.bin' md5sum: MD5 check failed for './dists/woody/main/disks-i386/3.0.23-2002-05-21/images-1.20/safe/driver-4.bin' md5sum: MD5 check failed for './dists/woody/main/disks-i386/3.0.23-2002-05-21/images-1.20/safe/driver-5.bin' [...] md5sum: MD5 check failed for './dists/testing/main/binary-i386/Release' md5sum: MD5 check failed for './dists/testing/main/binary-i386/Packages' md5sum: MD5 check failed for './dists/testing/main/binary-i386/Packages.gz' Probably not a good sign if './dists/testing/main/binary-i386/Release' doesn't match, yet the file on the CD appears fine: - Archive: stable Version: 3.0r2 Component: main Origin: Debian Label: Debian Architecture: i386 - This adds to my suspicion that the md5sum.txt is where the problem is, though I would have expected someone else to have reported this by now if that was the case. It'd be handy to be able to check the MD5 of the ISO images, but there doesn't appear to be an md5sum.txt distributed with the mirrored images, or posted on http://www.debian.org/CD/. -Tom __ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/
Re: checksum error sarge-1.jigdo
On Sun, Jan 18, 2004 at 09:45:59AM -0900, Greg Madden wrote: > I ran jigdo-lite, built an iso image using sarge-i386-1.jigdo, > Jan-16-2004. When the checksum part runs it fails. I mounted the new > sarge-i386-1.iso as a loop device and ran jigdo-lite again, I get the > following error. There may be another file with mis-matched checksum. > > Found 7323 of the 7325 files required by the template > Error: `/pub/iso/loop/pool/main/g/gtk+1.2/ > libgtk1.2-dbg_1.2.10-16_i386.deb' does not match checksum in template > data jigdo-file failed with code 2 - aborting. This means that jigdo-file read the file two times, once to find out its md5sum and once to copy it to the output image. The second time, the file no longer had the same md5sum. Two possible causes for this are undetected read errors with old, faulty CDs (unlikely in your case since you seem to be loop-mounting stuff), and a corrupt jigdo-file-cache.db file. If you enter jigdo-file --cache jigdo-file-cache.db md5sum /pub/iso/loop/pool/main/g/gtk+1.2/libgtk1.2-dbg_1.2.10-16_i386.deb twice and delete the cache file inbetween, does the output change? Cheers, Richard -- __ _ |_) /| Richard Atterer | GnuPG key: | \/¯| http://atterer.net | 0x888354F7 ¯ '` ¯
MD5 discrepancies with 3.0 r2 ISO contents
I found several discrepancies between the md5sum.txt and the contents for the ISO images (downloaded from mirror ftp://ftp.lug.udel.edu/ pub/iso-images/Debian/3.0_r2/i386/) for 3.0 r2. Most of the CDs consistently show two problems: 1. './README.html', which I see others have reported, and 2. a bunch of files in ./dists/testing - a directory that doesn't exist. (./dists/testing is a zero byte plain file, not a directory on my CDs.) I assume these are harmless, and might be good things to note on http://www.debian.org/CD/. I also noticed the problem with './pool/main/f/fgfs-base/ fgfs-base_0.7.9-1_all.deb' on disk 3, as someone else reported on the list. That's FlightGear flight simulator? Seems like another item worth adding to the last minute notes. Lastly, I'm seeing far more extensive problems on disk 1 (about 1700 files not matching). So much so, that I'm suspecting the integrity of the image I downloaded. Though it could be a messed up md5sum.txt. Unlike for the other disks, which had 16 files from the ./dists/testing/ directory listed in the md5sum.txt, this one includes 1122. Similarly there are a whole bunch of files listed from the './dists/woody/ main/disks-i386/current/ directory, which doesn't exist on the CD. (Similar to testing it is just a plain file.) In addition to the missing files, there were a bunch of MD5 mismatches, such as: md5sum: MD5 check failed for './dists/woody/main/disks-i386/3.0.23-2002-05-21/images-1.44/safe/driver-1.bin' md5sum: MD5 check failed for './dists/woody/main/disks-i386/3.0.23-2002-05-21/images-1.44/safe/driver-2.bin' md5sum: MD5 check failed for './dists/woody/main/disks-i386/3.0.23-2002-05-21/images-1.44/safe/driver-3.bin' md5sum: MD5 check failed for './dists/woody/main/disks-i386/3.0.23-2002-05-21/images-1.44/safe/driver-4.bin' md5sum: MD5 check failed for './dists/woody/main/disks-i386/3.0.23-2002-05-21/images-1.20/safe/driver-1.bin' md5sum: MD5 check failed for './dists/woody/main/disks-i386/3.0.23-2002-05-21/images-1.20/safe/driver-2.bin' md5sum: MD5 check failed for './dists/woody/main/disks-i386/3.0.23-2002-05-21/images-1.20/safe/driver-3.bin' md5sum: MD5 check failed for './dists/woody/main/disks-i386/3.0.23-2002-05-21/images-1.20/safe/driver-4.bin' md5sum: MD5 check failed for './dists/woody/main/disks-i386/3.0.23-2002-05-21/images-1.20/safe/driver-5.bin' [...] md5sum: MD5 check failed for './dists/testing/main/binary-i386/Release' md5sum: MD5 check failed for './dists/testing/main/binary-i386/Packages' md5sum: MD5 check failed for './dists/testing/main/binary-i386/Packages.gz' Probably not a good sign if './dists/testing/main/binary-i386/Release' doesn't match, yet the file on the CD appears fine: - Archive: stable Version: 3.0r2 Component: main Origin: Debian Label: Debian Architecture: i386 - This adds to my suspicion that the md5sum.txt is where the problem is, though I would have expected someone else to have reported this by now if that was the case. It'd be handy to be able to check the MD5 of the ISO images, but there doesn't appear to be an md5sum.txt distributed with the mirrored images, or posted on http://www.debian.org/CD/. -Tom __ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: checksum error sarge-1.jigdo
On Sun, Jan 18, 2004 at 09:45:59AM -0900, Greg Madden wrote: > I ran jigdo-lite, built an iso image using sarge-i386-1.jigdo, > Jan-16-2004. When the checksum part runs it fails. I mounted the new > sarge-i386-1.iso as a loop device and ran jigdo-lite again, I get the > following error. There may be another file with mis-matched checksum. > > Found 7323 of the 7325 files required by the template > Error: `/pub/iso/loop/pool/main/g/gtk+1.2/ > libgtk1.2-dbg_1.2.10-16_i386.deb' does not match checksum in template > data jigdo-file failed with code 2 - aborting. This means that jigdo-file read the file two times, once to find out its md5sum and once to copy it to the output image. The second time, the file no longer had the same md5sum. Two possible causes for this are undetected read errors with old, faulty CDs (unlikely in your case since you seem to be loop-mounting stuff), and a corrupt jigdo-file-cache.db file. If you enter jigdo-file --cache jigdo-file-cache.db md5sum /pub/iso/loop/pool/main/g/gtk+1.2/libgtk1.2-dbg_1.2.10-16_i386.deb twice and delete the cache file inbetween, does the output change? Cheers, Richard -- __ _ |_) /| Richard Atterer | GnuPG key: | \/¯| http://atterer.net | 0x888354F7 ¯ '` ¯ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Problem in sarge DVD 1
Hi, I´m try to download the DVD 1 for i386 of Sarge but always (4 times) receive this message: Error - template checksum mismatch! The .template file does not belong to the .jigdo file - the chances are high that the image generation process will break. I will abort now. If you know better than me and want this error to be ignored, enter the string "42" to proceed. This is the server where I´m obtain the .template. Downloading .template file --13:21:34-- http://ftp.fsn.hu/pub/CDROM-Images/debian-unofficial/sarge-dvd/jigdo/sar ge-i386-1.template => `sarge-i386-1.template' I´m using jigdo 0.7.0 on a Linux. A lot of thanks for your help. PD: The Sarge DVD 2 download without problems.
checksum error sarge-1.jigdo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I ran jigdo-lite, built an iso image using sarge-i386-1.jigdo, Jan-16-2004. When the checksum part runs it fails. I mounted the new sarge-i386-1.iso as a loop device and ran jigdo-lite again, I get the following error. There may be another file with mis-matched checksum. Found 7323 of the 7325 files required by the template Error: `/pub/iso/loop/pool/main/g/gtk+1.2/ libgtk1.2-dbg_1.2.10-16_i386.deb' does not match checksum in template data jigdo-file failed with code 2 - aborting. - -- Greg Madden Debian GNU/Linux -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFACtRnk7rtxKWZzGsRAjZ6AKCnUP3cesIPEeaMfMX3G9CWt7VsMgCfR3cX HMVf/WiPuPzXly50tU4ypZ8= =C6GD -END PGP SIGNATURE-
Problem in sarge DVD 1
Hi, I´m try to download the DVD 1 for i386 of Sarge but always (4 times) receive this message: Error - template checksum mismatch! The .template file does not belong to the .jigdo file - the chances are high that the image generation process will break. I will abort now. If you know better than me and want this error to be ignored, enter the string "42" to proceed. This is the server where I´m obtain the .template. Downloading .template file --13:21:34-- http://ftp.fsn.hu/pub/CDROM-Images/debian-unofficial/sarge-dvd/jigdo/sar ge-i386-1.template => `sarge-i386-1.template' I´m using jigdo 0.7.0 on a Linux. A lot of thanks for your help. PD: The Sarge DVD 2 download without problems. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
checksum error sarge-1.jigdo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I ran jigdo-lite, built an iso image using sarge-i386-1.jigdo, Jan-16-2004. When the checksum part runs it fails. I mounted the new sarge-i386-1.iso as a loop device and ran jigdo-lite again, I get the following error. There may be another file with mis-matched checksum. Found 7323 of the 7325 files required by the template Error: `/pub/iso/loop/pool/main/g/gtk+1.2/ libgtk1.2-dbg_1.2.10-16_i386.deb' does not match checksum in template data jigdo-file failed with code 2 - aborting. - -- Greg Madden Debian GNU/Linux -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFACtRnk7rtxKWZzGsRAjZ6AKCnUP3cesIPEeaMfMX3G9CWt7VsMgCfR3cX HMVf/WiPuPzXly50tU4ypZ8= =C6GD -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Status of the cd building (NEW: bootable cd images for hppa)
Le Sat, Jan 17, 2004 at 05:22:06PM +0100, Santiago Garcia Mantinan écrivait: > Well, aside all that, I'm thinking in how could I reschedule the full cd set > and dvd set builds, as now it takes really long to build and I cannot build > all cds in the same day like we used to do. > > So I'm wondering... should I spread the build throughout the week? or would > it be better for gluck if I could build the most each day and have the > machine building cds all day long during 3 or 4 days? Do not generate full CD set, nobody is downloading them isn't it ? Generate daily netinst & businesscard CD for all arches. Full CD and DVD can be done once a week. And even for that I'm sure we could do only the 3 first CD. Just my 2¢, feel free to decide whatever please you better. Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org
broken link on netinst page
("aftryk" means image. Danish word :))
*Eduard Blochs netinst-aftryk
Re: Status of the cd building (NEW: bootable cd images for hppa)
Le Sat, Jan 17, 2004 at 05:22:06PM +0100, Santiago Garcia Mantinan écrivait: > Well, aside all that, I'm thinking in how could I reschedule the full cd set > and dvd set builds, as now it takes really long to build and I cannot build > all cds in the same day like we used to do. > > So I'm wondering... should I spread the build throughout the week? or would > it be better for gluck if I could build the most each day and have the > machine building cds all day long during 3 or 4 days? Do not generate full CD set, nobody is downloading them isn't it ? Generate daily netinst & businesscard CD for all arches. Full CD and DVD can be done once a week. And even for that I'm sure we could do only the 3 first CD. Just my 2¢, feel free to decide whatever please you better. Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Formation Linux et logiciel libre : http://www.logidee.com Earn money with free software: http://www.geniustrader.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
broken link on netinst page
("aftryk" means image. Danish word :))
*Eduard Blochs netinst-aftryk
