severity 413136 important thanks > PS I'm downgrading this report to severity: normal. And please, as a > favor to the developers, resist the urge to use "severity: important" > for reports of this sort. That severity is intended for somewhat > more dire circumstances than "I read the documentation but I can't > make it work and can't figure out why." Although I do certainly > understand that this issue is important *to you*!
I think the original severity was quite justified. At least three people have now independently had this bug, and the bug makes the package unusable. I do not think that this is a question of misconfiguration, since the package from upstream does in fact work. I would really appreciate it if you could see to getting this fixed. thanks! Thijs -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
