severity 666523 serious
tag 666523 + moreinfo
thanks
On Sat, Mar 31, 2012 at 03:32:14PM +0200, Christoph Anton Mitterer wrote:
> Package: libreoffice
> Version: 1:3.5.2~rc2-1
> Severity: grave
> Justification: renders package unusable
No, if at least, it would be serious. Because if installed correctly, it would
work.
Installation problems is serious imho because it violates the policy
(obviously!)
> The recent package upgrade fails with:
Have a *full* log?
And what did you do for a upgrade?
(I tried a dist-upgrade before for 3.5.0-1 etc, and that included python-uno...)
Will try one again.
> Preparing to replace libreoffice-officebean 1:3.4.6-2 (using
> .../libreoffice-officebean_1%3a3.5.2~rc2-1_amd64.deb) ...^M
> Unpacking replacement libreoffice-officebean ...^M
> Preparing to replace python-uno 1:3.4.6-2 (using
> .../python-uno_1%3a3.5.2~rc2-1_amd64.deb) ...^M
> ^M
> ERROR: Cannot determine language!^M
> Exception details: ^M
> (com.sun.star.uno.RuntimeException) { { Message = "Cannot determine
> language!", Context = (com.sun.star.uno.XInterface) @0 } }^M
> ^M
> unopkg failed.^M
> terminate called after throwing an instance of
> 'com::sun::star::uno::RuntimeException'^M
> /var/lib/dpkg/tmp.ci/preinst: line 11: 6709 Aborted
> /usr/lib/libreoffice/program/unopkg sync -v --shared
> "-env:BUNDLED_EXTENSIONS_USER=file:///usr/l
> dpkg: error processing
> /var/cache/apt/archives/python-uno_1%3a3.5.2~rc2-1_amd64.deb (--unpack):^M
> subprocess new pre-installation script returned error exit status 134^M
Sounds like it needs some stuff from 3.5 which isn't there yet? Again, full
log, please
(should be obvious, but...)
> /usr/lib/libreoffice/program/unopkg.bin: error while loading shared
> libraries: libjvmaccessgcc3.so.3: cannot open shared object file: No such
> file or directory^M
root@frodo:/# ls -l /usr/lib/libreoffice/ure-link/lib/libjvmaccessgcc3.so.3
-rw-r--r-- 1 root root 22872 Mär 30 13:27
/usr/lib/libreoffice/ure-link/lib/libjvmaccessgcc3.so.3
so should be there and even in the old 3.4 and the new 3.5 ure-link points to
that install
(basis-link/ure-link or basis3.4/ure-link and "just" ure-link in 3.5)
(Thankfully this will be the last path change here, 3.5+ won't have that
changing path anymore.)
(And it is in ure proper:
# dpkg -L ure | grep jvma
/usr/lib/ure/lib/libjvmaccessgcc3.so.3
> ii libreoffice-common 1:3.4.6-2
OK, so probably we need a conflict against that. Was your -core already
upgraded before?
> ii libreoffice-core 1:3.4.6-2
Ah, no...
Sounds like making the extensions then depend on a newer core (and that one
depends on a newer
-common) should do.
Regards,
Rene
P.S: This is "only" wheezy->sid or sid->sid upgrade, a squeeze->wheezy/sid
upgrade is most probably
(oo.o->lo) not affected.
And no - neither do I care about *ANY* upgrade method besides
apt-get/aptitude. Especially not cupt and
graphical stuff like synaptic.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
