Le 10.01.2019 09:22, Till Kamppeter a écrit :
On 10/01/2019 08:56, Didier 'OdyX' Raboud wrote:
'cups-genppdupdate -x' and restarting cups fixed the problem (-x
allows
update across major Gutenprint releases).
Till: it seems that our trigger is not enough for these. Opinions?
For me it looks like that our trigger needs to run "cups-genppdupdate
-x" instead of simply "cups-genppdupdate".
Well, the CUPS trigger doesn't run "cups-genppdupdate" at all:
https://sources.debian.org/src/cups/2.2.10-3/debian/cups.postinst/#L78
The "-x" is needed only once for the transition of major versions. So
one could perhaps also do a "-x" in postinst depending on the old and
new version number and leave the trigger unchanged.
I implemented it this way:
if [ "$1" = configure ] && dpkg --compare-versions "$2" lt-nl 5.3.1-7~;
then
# Force upgrade of gutenprint PPDs accross major versions
cups-genppdupdate -x
fi
So any upgrade from before the current version will get the -x
treatment
(that's to do it for unstable users with broken PPDs).
I don't think we should be modifying CUPS' trigger code specifically
for
gutenprint. If gutenprint needs different treatment, let's make it
happen
in gutenprint, no?
Cheers,
Didier