Re: libc6_2.0.7r-3 considered harmful
On Mon, Jul 06, 1998 at 08:19:17PM +0100, Philip Hands wrote:
> > Philip Hands <phil@hands.com> writes:
> > > How many people have been bitten by this since the bug was found ?
> > > We should have been able to prevent this damage in some way --- even
> > > if it means having no libc6 available for a couple of days, this
> > > seems preferable to breaking people's systems when we could avoid
> > > it.
> >
> > Well, in my mind, the real way to fix this sort of thing is by
> > reworking our release engineering process. No packages should
> > propogated into stable (or beta) unless it has been tested by X number
> > of people, where X > 2. Testers are just users or developers who
> > install the package on a supported platform (i.e., stable or frozen)
> > and ensure that the pkg functions. Ideally we have regression testing
> > for *everything*, but I think that's a pipe dream.
>
> This would certainly limit the number of times this sort of thing could
> happen, but it will still happen.
>
> We need a way of dealing with it when it does.
save the last n *diff.gz on master.
with this files alle developers can make a new 'old' package and upload
a NMU to master (a old Version).
Alle diffs on master have a size of 50MB. So we need n*50MB on master.
I think is is ok.
Grisu
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: