Hi, On Tue, Jan 05, 2010 at 09:00:35AM -0800, Tim wrote: > > not have the time (and don't have enbough knowdlege of OOo internals) to > > fix this myswelf anyway, so this better should have been upstream directly. > > (As stated in presubj you swhould have been showed when reporting the bug) > > > Now that I've gone around and around with upstream on this issue: > http://www.openoffice.org/issues/show_bug.cgi?id=108035
Seen it. > They've been able to reproduce it in the Debian version, but in no > other version. Honestly, i doubt this. Upstream often claims that and then it turns out it's a bug in their version too. And, umm. they tried on Windows? Really comparable to Linux, yeah. And you saw the bug on amd64, whereas I am 100% Sure "es" tried on 32-bit. So... (I've reopened it, let's see what happens, sometimes you have to "fight" with Sun to get bugs taken seriously) > Do you think we can now work together to figure out why that is? If you filed it directly after it appeared... I fear digging out in years until back to 2.x when this was introduced (and if it is ooo-build specific in which patch[1]) is quite hard until impossible. Grüße/Regards, Rene [1] also note that I don't know all patches -- .''`. René Engelhard -- Debian GNU/Linux Developer : :' : http://www.debian.org | http://people.debian.org/~rene/ `. `' [email protected] | GnuPG-Key ID: D03E3E70 `- Fingerprint: E12D EA46 7506 70CF A960 801D 0AA0 4571 D03E 3E70 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
