On Wed, 2014-02-26 at 09:47 +0100, Gerfried Fuchs wrote: > Erm, no, not at all. A package in stable-bpo can't have a newer > version than testing when we release. With the removal there can be two > situations: > > * After fixing the issue that got the package removed from testing, the > package flows in like usual into testing, and it will definitely have > at least the version it had in testing before, most probably higher, > but never lower. > > * The package doesn't flow into testing anymore before the release. If > this is expected to happen, the package has to be removed from > stable-bpo. > > > What shall we do? Remove from stable-bpo? Hope an update comes around? > > Remove from stable-bpo if it's not expected to come back in is what we > actually do, yes. And to have an overview of these situations I created > myself the diffstats page: > http://backports.debian.org/wheezy-backports/overview/
And if the newer version, for example, has updated a database schema in a non-backward-compatible way? Cheers, Nick -- Nick Phillips / nick.phill...@otago.ac.nz / 03 479 4195 # These statements are mine, not those of the University of Otago
