Backport of fix for upstream issue?

Hi, are there any plans to backport the fix for upstream issue 29023? (http://www.openoffice.org/issues/show_bug.cgi?id=29023) It's about deadlocking threads, which render the package unusable on a network I administrate, where this makes OO.o freeze about every second time it is started from

Recently used files not displayed in woody backport

Hi, since upgrading to my home-built backport of version 1.1.1, OpenOffice no longer displays recently used files at the bottom of the file menu. It creates and writes a freedesktop.org-compliant ~/.recently-used but obviously it doesn't read it (well, it actually does, as I could see running s

Re: Problems when building on woody (gcc-2.95 vs. gcc-3.0)

On Wednesday 31 March 2004 14:06, Chris Halls wrote: > Did you need to make any more changes to the packages? Well, I have built and I am using, amongst others, backports of X 4.3.0, fontconfig and libfreetype. So I can't really make a statement regarding a pure woody system, but besides the rem

Problems when building on woody (gcc-2.95 vs. gcc-3.0)

Hi, I tried to build 1.1.0+1.1.1rc3-1 on woody and ran across the following problem: When configured with "--with-system-db" and "--with-system-myspell", the build fails due to undefined symbols when using backports of both libdb3 and libmyspell3 that are built with gcc-2.95. It works if I use

Re: cvs commit to oo-deb/debian/patches by rene

On Thursday 26 June 2003 11:58, Debian Openoffice CVS wrote: > Log Message: > compile with -O2 on i386 too I compiled 1.0.3-2 for woody with Adrian's patch applied. Besides not noticing any increase in startup speed, the result was that some Calc files could still be opened, but when I tried t