Re: Updating scanners and filters in Debian stable (3.1)
* Jesus Climent (firstname.lastname@example.org) [041007 13:10]:
> On Wed, Oct 06, 2004 at 04:12:48PM -0700, Thomas Bushnell BSG wrote:
> > In other words, are your upgrades going to be "install the latest
> > upstream", or are they going to be "fetch the relevant new things from
> > upstream and put them in the old thing"? I agree completely that the
> > latter is more work, but that is not an excuse for choosing the
> > destabilizing strategy.
> It is my point of view that with volatile in place, the policy for allowing
> updates on such repository could introduce things which break other apps.
This policy is even not ok for a normal major debian upgrade. We have
exim and exim4, we have inn and inn2 for exactly that reason, and we should
also provide spamassassin and spamassassin3. This doesn't mean that
spamassassin3 shouldn't be added to volatile.debian.net, but it
definitly means that we should not break api by providing it as
PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C