Hello, if i take for example:
http://ftp-master.debian.org/~ajt/update_excuses.html adns 1.0-3 (low) Maintainer: Bernd Eckenfels <[EMAIL PROTECTED]> adns is 27 days out of date! out of date on alpha: libadns0, libadns0-dev (from 0.8-2) out of date on i386: libadns0, libadns0-dev (from 0.8-2) there are up to date bins in i386 also out of date on m68k: libadns0, libadns0-dev (from 0.8-2) there are up to date bins in m68k also out of date on powerpc: libadns0, libadns0-dev (from 0.8-2) there are up to date bins in powerpc also out of date on sparc: libadns0, libadns0-dev (from 0.8-2) there are up to date bins in sparc also not considered Does that mean that it is not considered because on alpha there are no up-to-date bins? The line "out of date" can be ignored as long as there is also a line "there are up to date bins in * also"? Is there a build-info for all the other platforms, too? How can I see why the alpha failed to build my package? The "valid candidate (will be installed unless it's dependent upon other buggy pkgs)" is printed, even if the package is already installed in woody? Greetings Bernd -- (OO) -- [EMAIL PROTECTED] -- ( .. ) [EMAIL PROTECTED],linux.de,debian.org} http://home.pages.de/~eckes/ o--o *plush* 2048/93600EFD [EMAIL PROTECTED] +497257930613 BE5-RIPE (O____O) When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl!