Le Sunday 17 February 2008 20:19:10 Raphael Hertzog, vous avez écrit : > On Sun, 17 Feb 2008, Kamaraju Kusumanchi wrote: > > > > I am wondering if this bug can be downgraded from severity grave to > > > > normal (or even be closed if possible)? Well, for me, some things have to be done first : - during an upgrade from gs-* to ghostscript, the "foomatic-filters" package still retain its (old, gs-*) configuration ... that is why there is no log at all in Cups or others ... (still puzzles me why some pages were printed in half, through ...)
So, in the ghostscipt upgrade scripts, one has to force a reconfiguration of foomatic-filters (or some equivalent packages) ... dont know enough about Debian packages to do that .. > > > > The bug was marked unreproducible, and the OP reported that the > > > > problem went away by installing the latest version. Not MY original post, but somehow related ... > > > If you want to close the bug, make sure it doesn't exist any more. > > > Install an etch chroot with the old gs-* packages and dist-upgrade to > > > sid and check if the /usr/bin/gs still exists. Well ... changed those packages (from Stable) : gs-common (0.3.11) gs-esp (8.15.3.dfsg.1-1) gs-gpl (8.54.dfsg.1-5) With that one (from Unstable) : ghostscript (8.61.dfsg.1-1) Worked for me ... althrough I havent tested for /usb/bin/gs's disappearance (I only did REMOVE the gs-* ... then purged them; that is maybe why I still have a /usb/bin/gs binary lying around ... > > > Up to now, I've not seen any indication that the upgrade process is > > > sane and reliable. Well .. not sane for "foomatic-filters", at the very least ... > > Ok. But I do not have access to the printer the OP is talking about. I > > hope someone else steps into and does it... > > I don't think that this printer problem deserves a grave bug. However > since the bug contained no info except a "it's not working" I assumed that > it might be the same problem than me which was that /usr/bin/gs disappeared > during the upgrade. That is strange .. havent anyone received my mails ? > And this is not too difficult to verify... and once that verification is > done and that the upgrade scripts have been proofread with that problem in > mind, one could close the bug. yes, the (ORIGINAL, mine) bug can be closed ... if someone fixes the installation script (update foomatic-filters along the way) > And this is something that anyone can do. The maintainer is best placed > for this but you can step in to help... > > Cheers, -- Loïc JOUANIQUE -- Of course you can't flap your arms and fly to the moon. After a while you'd run out of air to push against. !!
