Julien Cristau <jcris...@debian.org> writes: > On 01/15/2018 08:32 AM, Carsten Leonhardt wrote: >> Julien Cristau <jcris...@debian.org> writes: >> >>> Control: tag -1 moreinfo >>> >>> On Thu, Nov 16, 2017 at 00:02:29 +0100, Carsten Leonhardt wrote: >>> >>>> 2) Bug #880529: When updating from jessie to stretch, the package >>>> "bacula-director-common" will be removed, but the postrm will stay >>>> around. Upon purging this package, postrm unconditionally removes the >>>> main bacula configuration file /etc/bacula/bacula-dir.conf, leaving >>>> bacula unusable. We fix this by introducing a transitional package that >>>> can then be safely removed. >>>> >>> It sounds like this won't solve the issue for anyone who has already >>> upgraded but hasn't yet purged bacula-director-common. Couldn't >>> bacula-director's postinst neuter the old postrm instead? >> >> Are you sure? I'd say that these people will get the upgrade to the >> transitional package and this will remove the old postrm. >> > How would they get an update to a removed package? (Yes, I'm pretty sure.)
I see your point now. My proposed solution only helps people that still have the package installed. I'll work on a better solution. Regards, Carsten
