get a full name, please.
My full name is in the "from" field of my email. Is it relevant for the bug?
Why didn't you mark it appropriately then? ;-)
It's currently marked as found in >= 2.4.1-11 only.
(And 3.0.0-x is branched off 2.4.1-7)
I chose the current testing version, because my memory is not so good to remember the first version in Debian. True, I could have gone to the developer information, but, at the time I submitted it (daybreak), I would have preferred not to submit it if I had to spend time in the history of the package. In such case, by the way, I would have avoided your rudeness :-)
Aha. And because you have written it there you can't write it
down in this bug, too istewad of pointing to a (waaah!) forum? ;-)
Thanks to this forum you are looking down on we were able to found that the problem is specific of Go-OO. I think this is a valuable piece of information. Do you not think so?
How should one reading this bug offline (bts cache) look at the infos ;-)
All the infos relevant to the bug belong into the bug.
I refer again to two paragraphs above. Regard the submission of this bug as a courtesy to you :-P Furthermore, the title of the bug is self-explanatory :-P
(And BTW, you didn't report it to Go-Oo yet, the BTS for go-oo upstream stuff
is not the Debian BTS - we are just one user of go-oo.org. If you want
to report it on go-oo.org upstream file it in bugzilla.novell.com, as
always it's better if the person who found it does it him/herself then
the Debian person playing proxy or just forwarding it and forgetting about it)
)
Yes, I learnt myself that submitting to the upstream is quicker. But Debian's bug submitting guidelines do not say anything about that, so do not assume that people will guess it.
> I am not submitting it as grave because such severity is not justified, but
I'd have downgraded it immediately anyway.
I already said I was NOT submitting it as grave. Calm down, kids :-P
Yes, we do. Unless you can tell us why this is release-critical, why we
should stop the release for it - and I guess you have the fix already for it?
No, I am not such a skilled programmer.
David