[09:14] <ogra> lool, weird, the nighly alternate build works, the manual build i did before going to bed produced an image that was 512 byte to small to fit the VFAT on
[09:14] <ogra> i suspect we need to keep an eye on that
[09:29] <lool> So it hit the check on th size of the vfat?
[09:29] <ogra> yeah
[09:29] <lool> It's hard to tell whether stuff will fit in the vfat; I should probably allocate some extra space but then it's lost space  :-/
[09:30] <ogra> did we take the 512 bytes into account we need for the MBR ?
[09:30] <ogra> it bothers me that its excatly 512 bytes
[09:30] <lool> What is the vfat on the disk image or in the vfat?
[09:31] <lool> What's the output?
[09:31] <lool> If it's in the disk image, it might be solved by the CHS work I had done in jaunty
[09:31] <lool> But didnt deploy as I had found the real bug sometimes afterwards
[09:33] <ogra> creating VFAT partition...
[09:33] <ogra> WARNING: You are not superuser.  Watch out for permissions.
[09:33] <ogra> VFAT partition length is 688913920B and doesn't leave enough room for VFAT 688914432B
[09:33] <ogra> make: *** [bin-images] Error 1
[09:33] <ogra> ERROR WHILE BUILDING OFFICIAL IMAGES !!
[09:34] <ogra> sorry took a moment
[09:34] <lool> So that's in the disk image
[09:34] <ogra> we really should have splitted logs
[09:34] <ogra> its very hard to find something
[09:34] <lool> Could you try with antimony ~lool/debian-cd-chs-addressing.patch ?
[09:35] <ogra> well, it worked with the automatic build some hours later
[09:35] <lool> Ah
[09:35] <ogra> i'm not sure its easily reproducable
[09:35] <lool> Well if it rehappens, please try that patch
[09:35] <ogra> i will