On Fri, 12. Oct 15:27 gregor herrmann <gre...@debian.org> wrote: > On Sat, 29 Sep 2012 15:53:05 +0200, Markus Koschany wrote: > > > 1. I still think the bug isn't release critical. > > I tend to agree here, and Julien has also argued the same in #599083.
Hi gregor, thanks for stopping by. > > 2. My packaged version of wbar, 2.3.4, fixes all outstanding > > bugs including this one. > > I haven't looked at 2.3.4, but in general new upstream releases are > not the way to go during a freeze. Agreed. This should be a last resort. I just don't think that this is a bug where changing two lines of code can solve everything. It is more of a usability issue. IMO a grave bug is something which makes a package unusable and i can prove that's not the case here. > > 3. I have prepared another fix for the > > "broken-path-to-a-font-file-problem" and attached it. > > Yeah, might make sense if this bug is considered RC (although it also > doesn't "make it work", just the diagnostics seem to be nicer). > In case this patch is needed, it should be trimmed down (most of the > changes are removed trailing whitespaces). Thanks, i will take care of it, if the patch should really be necessary. I'm in favor of downgrading this bug to important again but i would like to hear Barts opinion first. Regards, Markus
signature.asc
Description: Digital signature
