[Solved] Update broke libopenscenegraph package

Support for running, installing or compiling OpenMW

Before you submit a bug report for the first time, please read: Bug reporting guidelines
Post Reply
sakuramboo
Posts: 7
Joined: 04 May 2012, 01:09

[Solved] Update broke libopenscenegraph package

Post by sakuramboo »

Code: Select all

sakuramboo@Betsy:~$ sudo apt-get install openmw
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libbulletcollision2.81 libhdb9-heimdal libkdc2-heimdal liblinearmath2.81
  libopenscenegraph123
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
  libopenscenegraph-3.4-130 openmw-data openmw-launcher
The following NEW packages will be installed:
  libopenscenegraph-3.4-130 openmw openmw-data openmw-launcher
0 upgraded, 4 newly installed, 0 to remove and 3 not upgraded.
Need to get 0 B/9,776 kB of archives.
After this operation, 42.8 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 360378 files and directories currently installed.)
Preparing to unpack .../libopenscenegraph-3.4-130_3.4.0+dfsg1-1~trusty1_amd64.deb ...
Unpacking libopenscenegraph-3.4-130:amd64 (3.4.0+dfsg1-1~trusty1) ...
dpkg: error processing archive /var/cache/apt/archives/libopenscenegraph-3.4-130_3.4.0+dfsg1-1~trusty1_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/libosgTerrain.so.3.4.0', which is also in package libopenscenegraph123:amd64 3.4.0-1+trusty6
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Selecting previously unselected package openmw-data.
Preparing to unpack .../openmw-data_0.40.0-1~trusty1_all.deb ...
Unpacking openmw-data (0.40.0-1~trusty1) ...
Selecting previously unselected package openmw.
Preparing to unpack .../openmw_0.40.0-1~trusty1_amd64.deb ...
Unpacking openmw (0.40.0-1~trusty1) ...
Selecting previously unselected package openmw-launcher.
Preparing to unpack .../openmw-launcher_0.40.0-1~trusty1_amd64.deb ...
Unpacking openmw-launcher (0.40.0-1~trusty1) ...
Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
Processing triggers for mime-support (3.54ubuntu1.1) ...
Processing triggers for gnome-menus (3.10.1-0ubuntu2) ...
Processing triggers for desktop-file-utils (0.22-1ubuntu1) ...
Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Errors were encountered while processing:
 /var/cache/apt/archives/libopenscenegraph-3.4-130_3.4.0+dfsg1-1~trusty1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
EDIT: So, after some digging around, it seemed like at some point in time I manually installed libopenscenegraph123. Which is why it complained, because the repo did not manage the package, but the update of openmw required it. So, because of the package name difference, it tried to install it on top of the other one.

I resolved this by uninstalling libopenscenegraph123 and then the install of openmw was successful.
User avatar
psi29a
Posts: 5360
Joined: 29 Sep 2011, 10:13
Location: Belgium
Gitlab profile: https://gitlab.com/psi29a/
Contact:

Re: Update broke libopenscenegraph package on Ubuntu 14.04 L

Post by psi29a »

Yup, everyone will have growing pains here due to switch from openscenegraph to openscenegraph-3.4. I'm going to modify the title to solved so people can come here to read.
User avatar
Shnatsel
Posts: 64
Joined: 31 Oct 2014, 01:06
Location: Moscow
Contact:

Re: [Solved] Update broke libopenscenegraph package

Post by Shnatsel »

This occurs because of a serious bug in packaging.

For people doing the packaging: here is a hotfix.

When you're done applying it and rolling it out to the PPA, contact me and I'll explain how to handle this properly.
User avatar
psi29a
Posts: 5360
Joined: 29 Sep 2011, 10:13
Location: Belgium
Gitlab profile: https://gitlab.com/psi29a/
Contact:

Re: [Solved] Update broke libopenscenegraph package

Post by psi29a »

Thanks for that, applied and are building now.

The problem was due to the fact that the old osg-3.4 was just named osg, so there was a collision waiting to happen when we finally synced up with debian using osg-3.4. We didn't know before hand Debian maintainers would do a rename.

Debian decided not to just upgrade the OSG package, but in the spirit of ogre3d (-1.7, -1.8, -1.9) to create a new package with the version post-fixed. The dangerous thing here is that OSG-3.4 still requires openthreads, which is built by the original OSG package. That means that if there are fixes upstream for openthreads, it won't make it back downstream because OSG (3.2) won't be updated, and OSG-3.4 isn't making its own packages for openthreads. *sigh*
Post Reply