Re: No libtiff transition for sarge

[Adrian Bunk <bunk@fs.tum.de>]

On Thu, Aug 12, 2004 at 03:53:17PM +0200, 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.
> 
> > 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 
> > that the unstable package didn't go into testing because the gcc-3.4  
> > issue wasn't resolved before the start of the freeze.
> 
> I wonder what you are talking about, it cannot be cyrus-sasl2, none of
> the facts match.
> [2004-08-01] Accepted cyrus-sasl2 2.1.19-1 (i386 source)
> [2004-05-21] Accepted cyrus-sasl2 2.1.18-4.1 (hppa source) 
> 
> (2.1.18-4.1 is in sarge.)

Interesting, I only looked at the changelog:

  cyrus-sasl2 (2.1.19-1) unstable; urgency=medium
  ...
  -- Dima Barsky <dima@debian.org>  Sun,  4 Jul 2004 20:38:53 +0100


> On top of that cyrus-sasl2 is not even frozen.
> http://release.debian.org/base-packages.txt

This list doesn't contain all frozen packages.

cyrus-sasl2 falls under "packages of priority standard and higher" [1]
which are also frozen but not listed.

>              cu andreas

cu
Adrian

[1] http://lists.debian.org/debian-devel-announce/2004/07/msg00016.html

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed