-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, 28 May 2006 22:07:01 -0400 Joey Hess <[EMAIL PROTECTED]> wrote: > > --447a5b42_7346d134_4354 > > Daniel Dickinson wrote: > > Well, I just loop mounted the 27th's floppy image and copied it's > > contents to a temporary directory for comparison with the 25th, but > >=20 > > The 25th's floppy image was empty! > >=20 > > And so was the 24th's. That would explain why the disk was ejected > > almost immediately after boot; there was no boot code on the disk, > > for that matter there was nothing on disk. > >=20 > > Is there something wrong with the build process? > > Here's the logs for the 25th build: > > http://people.debian.org/~cjwatson/d-i/images/2006-05-25/ > > Not seeing any obvious differences to the 27th logs.. > > Daniel Dickinson wrote: > > Well, I just loop mounted the 27th's floppy image and copied it's > > contents to a temporary directory for comparison with the 25th, but > > > > The 25th's floppy image was empty! > > > > And so was the 24th's. That would explain why the disk was ejected > > almost immediately after boot; there was no boot code on the disk, > > for that matter there was nothing on disk. > > > > Is there something wrong with the build process? > > Here's the logs for the 25th build: > > http://people.debian.org/~cjwatson/d-i/images/2006-05-25/ > > Not seeing any obvious differences to the 27th logs.. >
Erm, I seem to have downloaded the wrong image for the 27th After doing the 27th's download again, it also was empty. Which makes sense given the following: DOING MIBOOT /bin/sh: line 3: miboot: command not found MIBOOT DONE since miboot doesn't exist, it doesn't install the necessary files on the floppy and we have an empty floppy. Actually there is definitely something weird going on because I just checked the 23rd and it is also empty. Maybe dd is not zeroing sectors that are empty?? and a working boot doesn't go away even though I've used a different image? I was pretty sure I download the right day's image, but apparently not. Okay, there is something very strange going on here. I just checked the 13th, and it's image is now empty as well, and it was the first image that worked for me. I just tested that image, just in case not seeing anything on the mounted floppy was really inconsequential, but that image is no longer bootable. This is consistent with the build logs, but is very odd given that I've got working images that I downloaded from the same urls as now show up as empty disks. It explains why in the BTS I've seen intermittent reports of working and non-working images for the same day, but WTF?!? There is something *very* strange going on with the server. - -- And that's my crabbing done for the day. Got it out of the way early, now I have the rest of the afternoon to sniff fragrant tea-roses or strangle cute bunnies or something. -- Michael Devore -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFEemJAhvWBpdQuHxwRAlbIAKCuStBly5klGQXNXciOwrK1LzXtuACfRKod 1LkR2dOeIJqoz4vCzUHkre0= =s3Eq -----END PGP SIGNATURE-----
