Ubuntu
octave package

octave fails to configure when removing a libhdf5 variant and an octave-* package in the same apt command

Bug #1482007 reported by Steven Wawryk
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
octave (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Installing a package (libgdal-dev I think??) in synaptic has broken my octave install.

synaptic "Broken dependencies" now shows lioctave2 and octave-communications as having broken dependencies.

The packages gmsh and octave-msh were mentioned in the error as being uninstalled, but I've lost the message.

Ubuntu 14.04.3 LTS

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: octave 3.8.1-1ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-45.60~14.04.1-generic 3.16.7-ckt14
Uname: Linux 3.16.0-45-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
Date: Thu Aug 6 10:55:56 2015
DuplicateSignature: package:octave:3.8.1-1ubuntu1:subprocess installed post-installation script returned error exit status 127
ErrorMessage: subprocess installed post-installation script returned error exit status 127
InstallationDate: Installed on 2015-07-06 (30 days ago)
InstallationMedia: Ubuntu-Server 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
SourcePackage: octave
Title: package octave 3.8.1-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Steven Wawryk (stevenw-z) wrote :
Apport retracing service (apport)
tags: removed: need-duplicate-check
Revision history for this message
Raj Bhattacharjea (raj-b) wrote :

I saw a similar error when I updated packages this morning, but to no effect: Octave seems to run just fine still and the package system seems to think it is installed correctly. I did a reinstall of octave (3.8.1-1ubuntu1) just to be safe, but everything was working fine.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in octave (Ubuntu):
status: New → Confirmed
Revision history for this message
Mike Miller (mtmiller) wrote :

Confirmed, thanks for reporting this bug.

Here are steps I've used to be able to reproduce this bug, starting from a clean install with no Octave packages installed:

# apt-get install -y octave-bim octave-msh
# apt-get install -y libhdf5-dev libhdf5-openmpi-7-

The error message is the same:

Removing octave-bim (1.1.3-1) ...
Removing octave-msh (1.0.6-1) ...
Removing gmsh (2.8.3+dfsg-4ubuntu2) ...
Removing libmed1:amd64 (3.0.6-2ubuntu1) ...
dpkg: libhdf5-openmpi-7:amd64: dependency problems, but removing anyway as you requested:
 liboctave2:amd64 depends on libhdf5-7; however:
  Package libhdf5-7 is not installed.
  Package libhdf5-openmpi-7:amd64 which provides libhdf5-7 is to be removed.

Removing libhdf5-openmpi-7:amd64 (1.8.11-5ubuntu7) ...
Processing triggers for octave (3.8.1-1ubuntu1) ...
/usr/bin/octave-cli: error while loading shared libraries: libhdf5.so.7: cannot open shared object file: No such file or directory
dpkg: error processing package octave (--remove):
 subprocess installed post-installation script returned error exit status 127

and the system is left without any libhdf5* packages installed.

Running

# apt-get -f install

does what it's supposed to do, fixes the problem by installing the missing dependency, libhdf5-7 in this case, but libhdf5-dev is not installed.

Revision history for this message
Mike Miller (mtmiller) wrote :

Also note that this only affects Ubuntu 14.04, later releases have introduced libhdf5* packages that can be co-installed so this situation will not arise.

Mike Miller (mtmiller)
summary: - package octave 3.8.1-1ubuntu1 failed to install/upgrade: subprocess
- installed post-installation script returned error exit status 127
+ octave fails to configure when removing a libhdf5 variant and an
+ octave-* package in the same apt command
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.