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

Re: [D-I] Preparing for update in stable

On Fri, Apr 28, 2006 at 08:39:24AM +0200, Martin Schulze wrote:
> Andreas Barth wrote:
> > > The main problem is going to be testing the new images as it will not be 
> > > possible to run an installation and download kernel udebs from s-p-u and 
> > > other udebs from stable.
> > 
> > The question is however: should we try to keep the "old" udebs in stable
> > also? Are they not overwritten by the point release? Or should we try to
> > change stable so that we have two versions of the udebs in stable?
> I fear that they need to be kept since otherwise a lot of installation
> media that are currently used would get suddenly wrecked.
> I guess that it may be a good idea to implement something like a
> public morgue for these udebs for etch and its successors in that the
> installer is able to look into a second (morgue) directory for the
> udebs it requires for installation if they can't be fetched from the
> main source (main archive).

Even the first sarge release, it was ensured that some extra udebs are
kept in pool. Something similar can happen for the point release too, as
long as they don't need to be included in the Packages files.

If they do need to be in the Packages files too (so, multiple entries in
the same Packages file with the exact same package name), we need some
dak changes, and it's a bit risky, because dak assumes at various places
that the (packagename, suite, architecture) tuple is unique (which then,
it isn't anymore). But before exploring that possibility -- is keeping
those udebs in pool enough? Or would it require d-i changes? Would d-i
require changes if all udebs in question were in the Packages files?


Jeroen van Wolffelaar
Jeroen@wolffelaar.nl (also for Jabber & MSN; ICQ: 33944357)

Reply to: