[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Silo breakage creating woody r2 CDs for sparc

On Tue, Dec 02, 2003 at 09:52:41AM -0500, Ben Collins wrote:
>> >The path to isofs.b needs to be absolute on the build machine (not
>> >relative to the CD root). The "..." is literal, it means use isofs.b to
>> >boot any sort of sparc (sun4c,sun4m,sun4d,sun4u).
>> Some warning of these changes would have been useful. Does this mean
>> that the set of images I've just produced are now useless?
>I had forgotten that I had put silo 1.3.x into stable. Wasn't
>intentional. I didn't realize that mkisofs had changed in woody. That's
>pretty broken in itself (or maybe you are running testing/unstable to do
>the CD builds, which is probably not a good idea either).

No, silo 1.2.x is still in woody. The mkisofs and silo versions I'm
now using are the woody ones, by dint of forcing things in the build
script. My development machine (the one with the mirror attached) is
running unstable, but the silo problem would have shown up there
anyway - the script to make Sparc bootable CDs grabs the latest one
directly out of the mirror. And can you please work out your
differences with Joerg and/or the mkisofs maintainer so we can get
these going again?

>The images you produced are broken, I'm sure. My mistake on the silo
>problem, but you could calm down a bit. Things happen.

<sigh> Is there any easy way to check them? It would be nice not to
have to start _again_. It's becoming impractical already to make CDs
for woody due to the mixture of breakages and the sheer length of time
taken to build them; I shudder to think what sarge is going to be like
at this rate.

For now I'm going to leave the sparc images as they are. If there's no
way to test, then I'm going to wait until the boot-sparc script is
known to work. I'll work on the easier architectures first.

Steve McIntyre, Cambridge, UK.                                steve@einval.com
You raise the blade, you make the change... You re-arrange me 'til I'm sane...

Attachment: pgpZfNv8AmHnK.pgp
Description: PGP signature

Reply to: