On Fri, Feb 25, 2005 at 09:25:05AM +0100, Sébastien Chaumat wrote:
My package (replicator) depends heavily on the exact behavior of the
deboostrap package : debootstrap is called with a list of additional
packages to install and I always must sync this list with the actual
dependencies in sarge.
Thus I always need a delay (mainly because regression tests take a long
time) each time debootstrap or a dependency in base is modified. I will
need this delay again when the freeze will happen to be able to upload
the correct version of replicator for sarge.
Why would there be an additional delay when freezing, instead of just when
debootstrap changes?
Can we now take this into account in the release process. I think it
would be better if I can have a single contact in the release team to
allow better coordination.
It's very unlikely that we would delay the release over design flaws in a
single priority: optional package such as this one. The inability of
debootstrap to resolve package dependencies on its own is a design flaw that
we have to live with for sarge because the cost of changing it in the
installer is high, but there's no reason why replicator should inherit this
design flaw. As Goswin notes, cdebootstrap is a more robust solution to
your problem.