Re: >2000 packages still waiting to enter testing, > 1500 over age
> I object. Not entering testing could very well happen if the
> package's dependencies are broken/buggy/uninstallable.
Yes, there are many reasons for a package to get stuck in unstable.
But I believe it is the maintainers responsibility to make sure his
packages do enter testing, and if he fail to do so for _300_ days, the
package is not well maintained and can probably be removed.
If there is a problem with one of the depends, he should assist the
maintainer of the problematic package, or drop the depend on the
package. There are several options available for a maintainer with a
package stuck in unstable, and waiting until the problem fixes itself
is not the best of them.
And there is not very many packages older then 300 days listed on
Most of us are doing a good job. It is just a few problematic
Some of them are the responsibility of the buildd maintainers, and
just seem to need a reschedule on the missing architecture, but I
believe it is the maintainers responsiblitiy to tell this to the
> Anyway, common sense should be (and is, by the RM,) applied.