cupsys-driver-gimpprint attempts /etc/init.d/cupsys reload

[Daniel Robitaille]

At least one package in universe (cupsys-driver-gimpprint) needs
/etc/init.d/cupsys to accept the option "reload". Currently only "restart" and
"force-reload" are acceptable options.

For the package cupsys-driver-gimpprint, both dpkg's postinst and postrm scripts
try to use the option reload with cupsys
(/etc/init.d/cupsys reload). This actually can prevent cupsys-driver-gimpprint
from being properly installed or properly removed.

[Matt Zimmerman (mdz)]

This is a bug in cupsys-driver-gimpprint, which should use "force-reload" rather
than "reload". This is a universe package, but since the bug was triggered by a
change we made to cupsys, and the fix is completely trivial, it deserves to be
fixed anyway.

[Martin Pitt (pitti)]

Created an attachment (id=324)
interdiff to solve this bug

[Matt Zimmerman (mdz)]

Approved for upload

[Martin Pitt (pitti)]

Fixed in:
 gimp-print (4.2.6-5ubuntu1) warty; urgency=low
 .
   * debian/cupsys-driver-gimpprint.postinst: restart cups with 'force-reload'
     instead of 'reload' since the latter is not accepted any more (Warty bug
     #8783)

Argh, I just saw that I forgot to document that the postrm also uses
force-reload. Well, not such a big deal, I think.

I also submitted a Debian bug report about this (#274820).