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. 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. We could also (temporarily?) lower the severity of the bug; but I'd rather wait for Andreas' opinion on the issue. The current piuparts results look good: https://piuparts.debian.org/sid/source/f/fusioninventory-agent.html but AFAICS they only test install and removal of the current version and no upgrades ... Cheers, gregor [0] notfound 792205 1:2.3.16-1 found 792205 1:2.3.10.1-1 [1] "This problem was observed after an squeeze -> wheezy -> jessie -> stretch upgrade." -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- NP: Tom Waits: Step Right Up
signature.asc
Description: Digital Signature
