Drew Parsons <[EMAIL PROTECTED]> writes: > After a standard period of time (10 days for normal packages I > think), the package gets copied (symlink) to testing if the > following conditions are met: > - binaries are available for main architectures (i386, alpha, > sparc, but the others are lagging behind, so they won't hold > up the package from testing) > - no serious errors (normal errors don't hold it up)
You can check easily whether you're package fails one of those conditions, by looking at <URL:http://ftp-master.debian.org/testing/update_excuses.html> For example, xdrawchem is listed there with "only 2/10 days old -- not considered". In 8 days, additional checking is done. > - the packages it depends on are also in testing > > The third one can be the tricky one to follow, since there might > dependencies on dependencies and they have to be fulfilled all the way down. Actually you ensuring that the direct dependencies (those mentioned in your "Depends:" field) are in testing suffices, since *they* would have been kept out of testing if their dependencies were broken -- blocking your package, too, in this case. If all direct dependencies seem in order, your package will vanish from the "update_excuses" list, meaning that it has been installed into testing. Otherwise, it will stay on the list with "out of date by X days" and "valid candidate". Unfortunately, the specific dependency/ies why a package was not installed are not listed there In case you want to help fixing those packages, you'd have to track them by hand. -- Robbe
signature.ng
Description: PGP signature
