cyrus-sasl2 2.1.19 not entering sarge (Re: No libtiff transition for sarge)
On Thu, 12 Aug 2004, Andreas Metzler wrote:
> On 2004-08-12 Adrian Bunk <bunk@fs.tum.de> wrote:
> > Oh, and another frozen package that blocks several other packages is
> > cyrus-sasl2.
And 2.1.19 is actually one of those things we that use cyrus-sasl2 REALLY
would like to have. Preferably with the fixes already in CVS. I contacted
Dima about this yesterday.
Users will go berserk (they already did, actually) if we don't get either
2.1.19 in sarge, or a backport of the "saslauthd -r" patch into 2.1.18 and
of the fixes to the worst bugs.
IMHO sasl 2.1.19 is a fitting t-p-u candidate.
> > In the case of cyrus-sasl2 the maintainer is hardly guilty - the last
> > package was uploaded to unstable three weeks before the first
> > announcement of the freeze. And it's also not a fault of the maintainer
The last package was uploaded to unstable one day before the (extended)
freeze started.
> On top of that cyrus-sasl2 is not even frozen.
Yes, it is. As far as the testing scripts are concerned, at least (which is
all that counts IMHO).
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
Reply to: