Per Olofsson wrote:
> (BTW, I uploaded the packages you signed so that at least the RC bug
> was solved.)
I had not realized that pcmcia-cs in sarge was so insanely out of date.
I hope the new verson can get into testing soon, it looks like it's
being hinted to go in at high priority, but there is some problem:
joey:/etc/init.d>grep-excuses pcmcia-cs
pcmcia-cs (3.1.33-6 to 3.2.5-2.3)
Maintainer: Brian Mays
Too young, only 1 of 2 days old
out of date on i386: pcmcia-modules-2.4.22-386, pcmcia-modules-2.4.22-586tsc, pcmcia-modules-2.4.22-686, pcmcia-modules-2.4.22-686-smp, pcmcia-modules-2.4.22-k6, pcmcia-modules-2.4.22-k7, pcmcia-modules-2.4.22-k7-smp (from 3.2.5-2); pcmcia-modules-2.4.24-1-386, pcmcia-modules-2.4.24-1-586tsc, pcmcia-modules-2.4.24-1-686, pcmcia-modules-2.4.24-1-686-smp, pcmcia-modules-2.4.24-1-k6, pcmcia-modules-2.4.24-1-k7, pcmcia-modules-2.4.24-1-k7-smp (from 3.2.5-2.2)
out of date on ia64: pcmcia-cs (from 3.2.5-2.2)
pcmcia-cs (source, alpha, arm, i386, ia64, powerpc) is buggy! (1 > 0)
Not considered
I wonder why it thinks the pcmcia-modules packages are out of date?
Maybe the old modules packages it lists need to be removed from unstable;
the new 2.4.25 ones seem to have not been accepted yet though.
--
see shy jo
Attachment:
signature.asc
Description: Digital signature