On Sat 23 Dec 2000, Anthony Towns wrote:
>
> Since libadns0 and libadns0-dev seem to be out of date on all architectures,
> it probably means they're not being built anymore, and need to be removed
> from unstable. Whether there are up to date bins on an arch is more just
> to give a hint at what might be causing the problem, rather than anything
> particularly important.
The same seems to be the problem with the following:
* jed-ja 0.99.10.jp0-3 (currently 0.98.7.j055-2) (low)
+ Maintainer: "Kikutani Makoto" <[EMAIL PROTECTED]>
+ jed-ja is 106 days out of date!
+ out of date on alpha: jed-sl-ja (from 0.98.7.j055-2)
+ there are up to date bins in alpha also
+ out of date on arm: jed-sl-ja (from 0.98.7.j055-2)
+ there are up to date bins in arm also
+ out of date on i386: jed-sl-ja (from 0.98.7.j055-2)
+ there are up to date bins in i386 also
+ out of date on m68k: jed-sl-ja (from 0.98.7.j055-2)
+ there are up to date bins in m68k also
+ out of date on powerpc: jed-sl-ja (from 0.98.7.j055-2)
+ there are up to date bins in powerpc also
+ out of date on sparc: jed-sl-ja (from 0.98.7.j055-2)
+ there are up to date bins in sparc also
+ not considered
jed-sl-ja is not built anymore (note that it is "out of date" on
ALL architectures). Does this mean it won't be installed into
woody until someone manually removes jed-sl-ja_0.98.7.j055-2.deb from
all architectures in sid?
> > Is there a build-info for all the other platforms, too? How can I see why
> > the alpha failed to build my package?
See bug 81379 :-)
Paul Slootman
--
home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/
work: [EMAIL PROTECTED] http://www.murphy.nl/
debian: [EMAIL PROTECTED] http://www.debian.org/
isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.org/
