Anthony Towns wrote: > Yesterday, glibc 2.3.999.2-10 was accidently uploaded to unstable instead of experimental [...] Would anyone like to contribute their thoughts, so we can do an "air crash" style failure analysis to work out how we can avoid this class of problem in future, given the safety net that caught us this time is going away?
Is there any sensible reason for ever uploading a package in unstable with a higher version than in experimental? If not, such uploads can simply be forbidden altogether. Gerardo