[This is in reply to an off-list mail from Wookey.] On Thu, Nov 22, 2001 at 02:04:31PM +0000, Wookey wrote: > On Thu 22 Nov, Richard Atterer wrote: > > So, did it work? :) > > not quite :-( > > I left it overnight and it said it had failed to get all files, > please go round again. I've just done that 3 times and it keeps > getting doc/debian-keyring.tar.gz and doc/bug-reporting.txt which > download OK but then I gwt this: > Downloaded 4,008,436 bytes in 2 files > Found 0 of the 2 files required by the template > Copied input files to temporary file 'debian-2.2r4-arm-1-nonus.iso.tmp - > repeat.... > > And I'm just going round this loop. Why isn't it happy with the > downloaded files (failed MD5 check?).
Did jigdo-file start merging the keyring data into the image? (i.e. show the "% done" messages and the keyring filename to the right of it) If not, a failed MD5 check is probably the reason: debian-keyring.tar.gz and bug-reporting.txt seem to have changed on the FTP server since I generated the .jigdo/.template files. I'll regenerate them over the weekend and also exclude some paths on the FTP server that might change in the nearer future. (Hmm, probably all of doc/; that will increase the size of the templates quite a bit :-/ ) > And once the debian-keyring file download had timed out at ~3550K of > 4Mb and the restart though it had '-3Mb to go' and so was reading > 1108%, 1110% etc! It still seemed to stop at the right file size but > obviously got rather confused! Yaargh! I doubt that the timeout is responsible for that; if not all of the keyring was downloaded, its MD5 sum won't match so it just won't be recognized as being part of the image. Hm, will investigate. > So, any ideas? And have I now got 4 copies of the debian keyring on > the end of my tmp image? No - as long as the MD5 sum doesn't match, nothing is transferred to the image. The tmp image is already very close to being the actual ISO image. The only differences are a small amount of administrative data that's still tacked on at the end, and that the two files' data isn't there. I think you could actually loop-mount it as an ISO image. If you did, the contents of the two missing files will be all zeroes. > > > For my purposes PIK is useful because it generates a list of > > > files that are missing so I can tell ncftp to get them all and > > > put them in my archive then run PIK again. This ensures my local > > > archive is uptodate wrt current CDs. So far as I can see jigdo > > > doesn't generate such a list of missing files, so whilst it will > > > make nice CD images it doesn't help keep the archive updated. > > > In fact, jigdo-file does generate such a list, Cheers, Richard -- __ _ |_) /| Richard Atterer | \/¯| http://atterer.net ¯ ´` ¯ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
