On Fri, Mar 10, 2017 at 12:00:22 +0100, Philip Hands wrote: > One ought to be able to sort out the specific upgrade bug in an updated > unstable package, but that does nothing to fix the package in stretch. > > I'd expect to see more bugs related to this code. > > I'm not sure if that counts as RC, but it seems clear that plastering > over the cracks with patches to the unstable package does nothing to > address the underlying problems of cruft in /etc and sloppy scripting. > > Unfortunately, now we're frozen, fixing the stretch package might be a > problem, although if we agree that this is RC, then I guess we can still > fix it :-) > We can also remove the package from stretch, which should give the maintainer more time to figure out a reasonable path forward for their maintainer scripts and upgrade issues.
Cheers, Julien
