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)? The bug was marked > > > > unreproducible, and the OP reported that the problem went away by > > > > installing the latest version. My initial post was NOT about /usr/bin/gs disappearing ... but about a brain-dead GhostScript ... check my follow-up post dated "Thu, 17 Jan 2008 16:21:47 +0100" ... > > > > > > 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. .. will test again within 48 hours to see if problem still exists ... (I need printer to work right now !!) > > > > > > Up to now, I've not seen any indication that the upgrade process is > > > sane and reliable. > > > > 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. Beg to differ, but my follow-up message contained much more info than the initial post ... > > 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. /usr/bin/gs exists ? not the initial bug ... > > And this is something that anyone can do. The maintainer is best placed > for this but you can step in to help... > > Cheers,
Yup, cheers yourself ... -- Loïc Jouanique
