On Mon, 2006-06-12 at 05:37 -0700, Steve Langasek wrote: > Hi Drew, > > Given that users will not be able to keep the sarge version of xprint on > their systems when upgrading to etch due to the /usr/X11R6/bin transition, > currently the choices for users are to have an xprint with this bug, or no > xprint at all. In light of this, do you believe that grave is the correct > severity for this bug?
I had been assuming the new libxfont would arrive sooner rather than later, and was therefore expecting to summarily dismiss this bug once it was in. Unfortunately the freetype2.2 fiasco (#370149) has complicated the situation more than we were expecting. > I have *never* found xprint usable on any of my systems, so I can't > adequately judge whether this particular bug renders the package unusable or > mostly so. We can work why xprint doesn't work for you once X11R7.1 is safe and settled :) As for the severity here, thinking it through dispassionately it's not true that xprint is unusable. It prints just fine, it's just that it currently uses bitmap fonts since libxfont isn't supplying it with the proper truetype fonts, so it comes out butt-ugly. In a pinch, you can use the output. It contains the text of the web page you're after, it's legible. You wouldn't want to use it to print and send off a job resumé, however. I'd say therefore it's not "unusable", and so can be downgraded from "grave" to "important". I'd be deeply dismayed if it shipped this way in the final etch, however. But I understand we're agreed to release etch with X11R7.1 anyway, so these Xprint woes will be resolved happily along with the rest of X11R7. Drew
