On Thu, May 09, 2019 at 11:40:24AM +0000, Holger Levsen wrote: > On Thu, May 09, 2019 at 12:56:18PM +0200, Santiago Vila wrote: > > Hello Holger. I'd like to work on this issue. > > > > My plan is to change "exit 1" to "exit 0" (as proposed) in both > > stretch and buster. If that's not enough I will also add a > > Breaks: debian-security-support (<= 2019.02.02~deb9u1) in base-files. > > this is not enough. and no, if I had time to explain, I would fix it myself. > > again: we need a fix which works in buster only, without touching stretch. > > we probably need to touch base-files in buster though.
The Breaks I'm offering in base-files will allow upgrades without touching stretch. Updating the package in stretch will only be a small improvement to not force a given upgrade path, but not the "fix". The fix for upgrades from stretch is the Breaks in base-files. But before I can write <= 2019.02.02~deb9u1 in base-files we should make sure there are not bad versions in testing, because otherwise "<= 2019.02.02~deb9u1" could be not enough. Maybe we should let the current package propagate to testing before going any further? Thanks.
