Re: Slink CDs - boot floopy images?
Steve McIntyre <firstname.lastname@example.org> writes:
> On Tue, 1 Dec 1998, Brederlow wrote:
> >Steve McIntyre <email@example.com> writes:
> >You forgot one very important step for your CD creation step:
> >- check all md5sums/signatures for all packages and generate
> > packages.md5sum (or similar name) file for reference.
> True, but I've already got a cron job running on my local mirror anyway
> which checks the md5sums, and I'm currently checking this output before
> even starting with the CD generation scripts.
But I (I as in "the nurd from the street trying debian") don't. Also I
saw more than one broken file on ftp.debian.org (e.g. broken
> >This would mean that all packages are unpacked, which takes some time
> ??? Why?
Sometimes the files get corrupted during upload. Any orig.tar.gz
should be unpacked to see if its fine. Alternatively you could check
its md5sum, if there is a debian file containing sums for source.
You still would have to read in every file multiple times. (Once for
checking and once mkisofs).
> >(better make it an option that defaults to on), but its better to
> >waste time then to burn a CD with broken packages.
> Of course...
> I've also updated the script to add some extras to fill some of the spare
> space, such as the latest Netscape and the latest kernel unstable and
> stable trees. I'll tidy things up and get a new version of the script
> uploaded tonight.
Great. Will one be able to pass an option to include a list of "local"
directories? Maybe even with the distinction between local deb files
and just extras like kernel sources?
May the Source be with you.