On 20 December 2016 at 21:39, Till Kamppeter <email address hidden> wrote:
> xnox, it seems that the suggested fix of comment #52 is the solution for
> this bug, and I could at any time add a patch to the CUPS package and
> issue it as an SRU. Only problem is, if I do only this, will the SRU
> smoothly install? Or are additional measures required?
>
The new package, may need to have a preinst stanza which version
checks which package version upgrade is happening from and still
execute systemctl stop cups.path unit.
Upgrades after that one should be fine without a preinst.
And preinst should then be dropped after next LTS.
Obviously a new package needs to be prepared and we should test it a bit.
On 20 December 2016 at 21:39, Till Kamppeter <email address hidden> wrote:
> xnox, it seems that the suggested fix of comment #52 is the solution for
> this bug, and I could at any time add a patch to the CUPS package and
> issue it as an SRU. Only problem is, if I do only this, will the SRU
> smoothly install? Or are additional measures required?
>
Looking at: /wiki.debian. org/MaintainerS cripts
https:/
The new package, may need to have a preinst stanza which version
checks which package version upgrade is happening from and still
execute systemctl stop cups.path unit.
Upgrades after that one should be fine without a preinst.
And preinst should then be dropped after next LTS.
Obviously a new package needs to be prepared and we should test it a bit.
Shall we start a https:/ /bileto. ubuntu. com/ devirt PPA for this update
into zesty and eventual SRUs?
--
Regards,
Dimitri.