[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#544621: openoffice.org-common: unopkg.bin can't find libjvmaccessgcc3.so.3



On Wed, Sep 02, 2009 at 03:32:17AM +0200, Rene Engelhard wrote:
> On Wed, Sep 02, 2009 at 07:05:10AM +0800, Michael Deegan wrote:
> > I hope this report is against the right package (I chose the one that
> > provided unopkg, but of course it is a shell wrapper around a binary
> > living in a different package).
> > 
> > While upgrading from 3.0.1-9 to 3.1.0-5 I noticed several errors. I suspect
> 
> And why did you do that NOW? 3.0.1-9 is LOOOONG gone.

Well, not as long gone as 2.4.1. :P

3.0.1-9 reflects the first (and last) time I needed to open a docx file. :P

If it makes you more comfortable, I get a similar result when upgrading
from the 2.4.1 in stable:

    root@wibble:/etc/apt# apt-get install -t testing openoffice.org-writer openoffice.org-writer2latex openoffice.org-style-andromeda-
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    The following extra packages will be installed:
      openoffice.org-base-core openoffice.org-common openoffice.org-core openoffice.org-style-galaxy ure
    Suggested packages:
      openoffice.org-base openoffice.org-style-industrial openoffice.org-style-hicontrast openoffice.org-gcj cli-uno-bridge
    Recommended packages:
      openoffice.org-style-tango openoffice.org-style-crystal xfonts-mathml openoffice.org-filter-binfilter openoffice.org-emailmerge
      openoffice.org-math
    The following packages will be REMOVED:
      openoffice.org-style-andromeda*
    The following NEW packages will be installed:
      openoffice.org-style-galaxy ure
    The following packages will be upgraded:
      openoffice.org-base-core openoffice.org-common openoffice.org-core openoffice.org-writer openoffice.org-writer2latex
    5 upgraded, 2 newly installed, 1 to remove and 1048 not upgraded.
    Need to get 0B/79.0MB of archives.
    After this operation, 21.0MB of additional disk space will be used.
    Do you want to continue [Y/n]?
    (Reading database ... 185896 files and directories currently installed.)
    Preparing to replace openoffice.org-writer 1:2.4.1+dfsg-1 (using .../openoffice.org-writer_1%3a3.1.0-5_amd64.deb) ...
    Unpacking replacement openoffice.org-writer ...
    Preparing to replace openoffice.org-base-core 1:2.4.1+dfsg-1 (using .../openoffice.org-base-core_1%3a3.1.0-5_amd64.deb) ...
    Unpacking replacement openoffice.org-base-core ...
    Preparing to replace openoffice.org-core 1:2.4.1+dfsg-1 (using .../openoffice.org-core_1%3a3.1.0-5_amd64.deb) ...
    Unpacking replacement openoffice.org-core ...
    Preparing to replace openoffice.org-writer2latex 0.5-8 (using .../openoffice.org-writer2latex_0.5.0.2-4_all.deb) ...
    /usr/lib/openoffice/program/unopkg.bin: error while loading shared libraries: libunopkgapp.so: cannot open shared object file: No such file
     or directory
    /usr/lib/openoffice/program/unopkg.bin: error while loading shared libraries: libunopkgapp.so: cannot open shared object file: No such file
     or directory
    Removing extension .../usr/lib/openoffice/program/unopkg.bin: error while loading shared libraries: libunopkgapp.so: cannot open shared obj
    ect file: No such file or directory
     done.
    Unpacking replacement openoffice.org-writer2latex ...
    Selecting previously deselected package ure.
    Unpacking ure (from .../ure_1.5.0+OOo3.1.0-5_amd64.deb) ...
    Preparing to replace openoffice.org-common 1:2.4.1+dfsg-1 (using .../openoffice.org-common_1%3a3.1.0-5_all.deb) ...
    Unpacking replacement openoffice.org-common ...
    Unknown media type in type 'all/all'

    Unknown media type in type 'all/allfiles'

    Unknown media type in type 'uri/mms'

    Unknown media type in type 'uri/mmst'

    Unknown media type in type 'uri/mmsu'

    Unknown media type in type 'uri/pnm'

    Unknown media type in type 'uri/rtspt'

    Unknown media type in type 'uri/rtspu'

    Unknown media type in type 'fonts/package'

    Unknown media type in type 'interface/x-winamp-skin'

    Processing triggers for man-db ...
    Processing triggers for menu ...
    (Reading database ... 186120 files and directories currently installed.)
    Removing openoffice.org-style-andromeda ...
    Selecting previously deselected package openoffice.org-style-galaxy.
    (Reading database ... 186111 files and directories currently installed.)
    Unpacking openoffice.org-style-galaxy (from .../openoffice.org-style-galaxy_1%3a3.1.0-5_all.deb) ...
    Setting up ure (1.5.0+OOo3.1.0-5) ...
    Setting up openoffice.org-style-galaxy (1:3.1.0-5) ...
    Setting up openoffice.org-common (1:3.1.0-5) ...
    Installing new version of config file /etc/bash_completion.d/ooffice.sh ...
    Installing new version of config file /etc/openoffice/sofficerc ...
    Unknown media type in type 'all/all'

    Unknown media type in type 'all/allfiles'

    Unknown media type in type 'uri/mms'

    Unknown media type in type 'uri/mmst'

    Unknown media type in type 'uri/mmsu'

    Unknown media type in type 'uri/pnm'

    Unknown media type in type 'uri/rtspt'

    Unknown media type in type 'uri/rtspu'

    Unknown media type in type 'fonts/package'

    Unknown media type in type 'interface/x-winamp-skin'

    Setting up openoffice.org-core (1:3.1.0-5) ...
    Setting up openoffice.org-base-core (1:3.1.0-5) ...
    Setting up openoffice.org-writer (1:3.1.0-5) ...
    Setting up openoffice.org-writer2latex (0.5.0.2-4) ...
    Adding extension /usr/lib/openoffice/share/extension/install/writer2latex.oxt.../usr/lib/openoffice/program/unopkg.bin: error while loading shared libraries: libjvmaccessgcc3.so.3: cannot open shared object file: No such file or directory
     done.
    Processing triggers for menu ...

(the "Unknown media type in type" messages are of course due to #469833)

> ARGH. If you use unstable or testing (see below), why not just use dist-upgrade
> instead of apt-get'ing every package?

Because a dist-upgrade wants to uninstall a bunch of KDE packages (thanks
to xine), and install the new dependencies of held packages.

> > -- System Information:
> > Debian Release: 5.0.2
> >   APT prefers oldstable
> >   APT policy: (500, 'oldstable'), (500, 'stable'), (490, 'testing'), (480, 'unstable')
> > Architecture: amd64 (x86_64)
> 
> This is more than interesting, this is a broken config. Prefer oldstable?
> Using stable? With testings/unstables packages? This is doomed to failure...

I don't know why APT says I prefer oldstable, given that stable has the
same priority, and I do not set APT::Default-Release anywhere. The machine
is effectively all lenny with selected bits of squeeze. I'm pretty sure the
only etch packages I still have installed are those that are identical in
lenny.

    root@wibble:/etc/apt# rgrep -i Default-Release .
    root@wibble:/etc/apt# cat preferences
    Package: *
    Pin: release l=Unofficial Multimedia Packages, a=stable
    Pin-Priority: 470

    Package: *
    Pin: release l=Unofficial Multimedia Packages, a=testing
    Pin-Priority: 460

    Package: *
    Pin: release a=testing
    Pin-Priority: 490

    Package: *
    Pin: release a=unstable
    Pin-Priority: 480

IMHO mixed distributions are sometimes good for catching missing
dependencies.

-MD

-- 
-------------------------------------------------------------------------------
Michael Deegan           Hugaholic          http://wibble.darktech.org/gallery/
------------------------- Nyy Tybel Gb Gur Ulcabgbnq! -------------------------



Reply to: