Re: cvs commit to debian-installer/build/debian by mckinstry
I'd already done the upload when I received this mail, but yes, I think
the build-installer package deserves more discussion than its received.
I tried to trigger this on debian-boot, but mostly got little reply.
Is the build-installer route the way to go, as in should we use a
package of some form to get d-i built, or should we use some other
If we go for some other mechanism, we need to go the following:
- be capable of automatically triggering builds on each arch
frequently, if not daily. (I was anticipating every 2-3 days)
- Have somewhere to store these images.
- Do so quickly. We need a lot of testing to be done for d-i to release
In retrospect I should have put build-installer into "experimental"
rather than "unstable", as it is _expected_ to have a lot of breakage at
this stage (Do experimental packages get autobuilt the same as
unstable?). It is expected to prompt discussion about what we expect to
be in dists/sarge/main/disks-* when we release sarge. Other than the
images themselves (and documentation, etc.) later I feel that the files
in /usr/share/doc/, diskusage-*.txt and missing.txt , which show which
files are missing (due to breakage in the build process), and the size
of the various modules,etc on the target images are important: we need
those to properly decide what goes in net, cdrom, cdrom144, netboot,
The build process in build-installer needs work, too. But I have taken
the attitude that we need to get things built as soon as possible to get
a full list of whats broken, and the work that needs doing, hence
releasing build-installer with a "0.0.001" version, and lots of caveats.
So in short, I expect, and welcome, reports on things to be fixed in
On Sat, 2003-04-05 at 23:47, Martin Sjögren wrote:
> sön 2003-04-06 klockan 00.40 skrev Debian Boot CVS Master:
> > Repository: debian-installer/build/debian
> > who: mckinstry
> > time: Sat Apr 5 15:40:41 MST 2003
> > Log Message:
> > Prepare for upload
> I talked to elmo about build-installer today and he thought the packages
> looked weird. I think we need to think this through and discuss it with
> the ftp-master team before doing anything drastic.
Alastair McKinstry <email@example.com>
GPG Key fingerprint = 9E64 E714 8E08 81F9 F3DC 1020 FA8E 3790 9051 38F4
He that would make his own liberty secure must guard even his enemy from
oppression; for if he violates this duty he establishes a precedent that
will reach to himself.
- --Thomas Paine