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

Re: Building boot images with boot-floppies on PowerMac

On Mon, 23 Jun 2003, Eduard Bloch wrote:

> #include <hallo.h>
> * debian@computerdatasafe.com.au [Mon, Jun 23 2003, 07:19:54AM]:
> > /archive/debian/download/var/lib/apt/lists/debootstrap.invalid_dists_woody_main_binary-powerpc_Packages
> > E: Couldn't download pcmcia-modules-2.4.18-newpmac
> > E: ./kernel.sh abort
> > make[1]: *** [linuxnewpmac.bin] Error 1
> > make[1]: Leaving directory `/root/cvs/bf/boot-floppies'
> > make: *** [build] Error 2
> According to madison's output, the package is in unstable only. The
> reason may be some temporary RC bug that prevented the package from
> beeing accepted in Woody.
> > > Stable still has 3.0.22. Is there a reason 3.0.23 never moved to
> > > stable, Eduard?
> See above. Woody has been moved to stable under our asses, and to this
> time there were an RC bug about potential security problems. One of the
> problems with Debian's release system.
I have tried the testing version. It fails too:
1393+1 records out
I: downloading packages modconf, modutils, whiptail-utf8
I: this arch/subarch supports PCMCIA, downloading pcmcia-cs
I: extracting packages into driver extract area
I: tarring pcmcia materials into incorporated tarball,
I: removing unneeded message catalogs from modconf
I: patching modconf to work with LANG_CHOOSER
I: moving from extra area into staging area for driver tarball,
I: finishing up /var/tmp/boot-floppies/drivers-529
I: moving /var/tmp/boot-floppies/drivers-529 into driverspmac.tgz
I: splitting drivers into floppy-sized chunks
1440+0 records in
1440+0 records out
1440+0 records in
1440+0 records out
I: downloading kernel-image-2.4.18-newpmac
I: downloading PCMCIA module package, 'pcmcia-modules-2.4.18-newpmac'
I: Validating
I: Validating
E: Couldn't download pcmcia-modules-2.4.18-newpmac
E: ./kernel.sh abort
make[1]: *** [linuxnewpmac.bin] Error 1
make: *** [build] Error 2

real    27m8.803s
user    11m56.990s
sys     5m3.070s

The current position is;
Woody fails
CVS fails
Sarge fails.

It seems to me part of the problem is that it has hard-coded into it
versions of kernels to use, and the kernel maintainers have replaced
those packages.

I don't know what kernel versions to use for what, or OTOH how to build
my own kernels so as to get things in sync.

I'm sure I can hack this thing to build the bootfloppies _I_ need, but
that won't help others. Part of what I would do is prevent it from
building for boxes I don't have.

What I think should be happening is this:
1. Default to using mirror(s) from /etc/apt/sources.list. That would
eliminate one of the customisations I must make.
2. Parse the Packages to the extent necessary to discover the most
recent of each of the packages needed.
3. Maybe source a site configuration file from /etc/bootfloppies/ where
the results of steps 1 and 2 can be adjusted.
4. Source a personal configuration file for further fine-tuning.

I'm sure you can argue whether this idea is slightly broken: the main
objective is to achieve something that is robust enough to work for the
unsuspecting (me, for example) and to simplify customisation for more
advanced use. Customising the config file doesn't seem to me especially
elegant or robust, and I can imagine it causing problems with updates
from CVS.

> > What should be in stable is working tools that may be used to create the
> > binaries created;-) How else can uses enjoy their GPL-given rights?
> It should. My bug report against ftp.debian.org has been closed quickly,
> so blame those guys.


John Summerfield

Please, no off-list mail at all at all. This address accepts mail only
from Debian addresses.

Reply to: