Re: why are these packages in testing?

[Jeroen van Wolffelaar <jeroen@wolffelaar.nl>]

On Mon, Jun 07, 2004 at 12:02:01PM +0200, Andreas Barth wrote:
> Hi,
> 
> I came across some strange outputs. For example:
> 
> aba@merkel:~$ madison aiksaurus
>  aiksaurus | 1.0.1+cvs.2004.02.20-1 |       testing | source
>  aiksaurus | 1.0.1+cvs.2004.03.15-1 |      unstable | source, alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc
> aba@merkel:~$
> 
> There is a current removal suggestion by vorlon:
> # 20040509
> # bug #241279
> remove aiksaurus/1.0.1+cvs.2004.02.20-1
> 
> Why is there only the source in testing?

Because 7 out of 9 binary packages of that source are still in testing:
http://lintian.wolffelaar.nl/histmadison/?source=aiksaurus&package=&date=2004-06-07

Note that the testing output says removal fails due to buggyness of the
package: http://packages.qa.debian.org/a/aiksaurus.html

# Trying to remove package, not update it
# libaiksaurus-data (alpha, arm, hppa, i386, ia64, m68k, mips, mipsel,
  powerpc, s390, sparc) is buggy! (1 > 0)
# Not considered

I guess the textual representation is bogus, otherwise removals can't
really have worked before.

> Similar, for libapache-mod-filter, there is:
> aba@merkel:~$ madison libapache-mod-filter
> libapache-mod-filter |      1.4-5 |        stable | source, alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc
> libapache-mod-filter |      1.4-8 |       testing | source, alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc
> libapache-mod-filter |      1.4-8 |      unstable | source, alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc
> aba@merkel:~$
> but there is also a removal suggestion, and the excuses-file on
> ftp-master says according to
> http://bjorn.haxx.se/debian/testing.pl?package=libapache-mod-filter
> that this package is removed today from testing. So, why is this still
> there? How many hours after the generation of the excuses list are the
> packages really updated?

'today' means 'just before next mirror pulse', i.e., it will be gone
after tonight.

Testing scripts run just after a mirror pulse, and have effect only upon
next one, so there generally is a delay of about 20 hours iirc.

--Jeroen

-- 
Jeroen van Wolffelaar
Jeroen@wolffelaar.nl (also for Jabber & MSN; ICQ: 33944357)
http://Jeroen.A-Eskwadraat.nl