On Fri, Jul 01, 2005 at 01:52:38PM +0200, Willi Mann wrote: > >Willi, > > > >Its already there, and (I'm fairly sure) was there before I posted the > >bug. (I meant to check but I forgot!) I think that the Sarge tag also > >means this. > > > ># apt-cache showsrc spamassassin > >Package: spamassassin > >Binary: spamassassin, spamc > >Version: 3.0.4-2 > > No, it wasn't. 3.0.4-2 is in testing (etch),
sorry, I did realise that ... > but not in sarge, because new > upstream versions are a big no-no for stable. Granted, my apologies. I should really think before I hit send ! > See > > http://packages.qa.debian.org/s/spamassassin.html > > I asked for the fixed package for stable, which would be some 3.0.3-x, > because I don't want to install new upstream versions to fix security bugs, > and I want to avoid version chaos. Again, apologies. I misunderstood. > BTW: This bug can be closed, as the new spamassassin 3.0.3-2 was released > tonight. Kudos to all! I see the DSA, but I don't see the files on s.d.o yet ... ... maybe I'm doing something wrong. > I won't close it as I'm not submitter, maintainer or member of the > security team. I think I'm the submitter, and closing a bug sounds rather fun, but doesn't the release process do that automatically ? (besides I don't feel like I've done anything to earn the priviledge). Regards, Paddy -- Perl 6 will give you the big knob. -- Larry Wall -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
