On 2018-07-02 20:10, gregor herrmann wrote: > On Mon, 02 Jul 2018 09:19:11 +0200, Guillaume Bougard wrote: > >> in fact, and regarding the package history, the bug should have >> been opened with 2.3.10 and closed with not releases 2.3.15... >> >> How to avoid this case becomes blocking for the migration to >> testing planned in 8 days now ? > > Technically, I suppose that "resetting" the affected versions [0] > should do it. I'm just a bit reluctant to do or recommend it since > there must have been a reason why Andreas filed the bug against > 1:2.3.16-1.
even if 1:2.3.16-1 fixed it for new installations, it didn't clean up after upgrades from older versions. Not sure whether it exploded with a dpkg prompt about modified conffiles ... > OTOH, I guess it's a bit hard to test the complete upgrade path any > longer [1], and I'm not sure how much it matters at this point. That's still easily possible - needs 4 -d options for piuparts. > We could also (temporarily?) lower the severity of the bug; but I'd > rather wait for Andreas' opinion on the issue. That's probably OK, or rather remove the fixed version. Andreas
