>Testing in its current state has potential to be more unstable than >sid, has already been, and will be again if the process does not >evolve. My idea to work around it is expressed above, but I'm quite >sure I overlooked some things - as the problems I describe were >overlooked originally. I'm not at all convinced that allowing direct uploads of packages into testing (and hence effectively forking packages) is going to help with stability. If people can upload to testing directly, it will be very difficult to stop maintainers from making inappropriate uploads, either accidentally or deliberately. The whole reason for having `testing' is that packages can only get into it by meeting a particular set of criteria, or by manual intervention from ftpmaster. In the case of your console problem, you could have fixed testing by just re-uploading the old version of the package with a newer version number (using an epoch if necessary) and "urgency=high". p.
Attachment:
pgpzLH_BFqBwk.pgp
Description: PGP signature