Bug#706758: python-scientific: preinst/prerm uses python, but python is not configured during upgrades
Andreas Beckmann
anbe at debian.org
Sat May 4 11:29:11 UTC 2013
Package: python-scientific
Version: 2.8-4
Severity: serious
User: debian-qa at lists.debian.org
Usertags: piuparts
Control: affects -1 + python-mpi python
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'squeeze'.
It installed fine in 'squeeze', then the upgrade to 'wheezy' fails.
>From the attached log (scroll to the bottom...):
The following NEW packages will be installed:
... libssl1.0.0 ...
Selecting previously deselected package python2.7-minimal.
(Reading database ... 8561 files and directories currently installed.)
Unpacking python2.7-minimal (from .../python2.7-minimal_2.7.3-6_i386.deb) ...
Preparing to replace python-mpi 2.8-1.2 (using .../python-mpi_2.8-4_all.deb) ...
INFO: using unknown version '/usr/bin/python2.7' (debian_defaults not up-to-date?)
Unpacking replacement python-mpi ...
Preparing to replace python2.6 2.6.6-8+b1 (using .../python2.6_2.6.8-1.1_i386.deb) ...
Unpacking replacement python2.6 ...
Preparing to replace python2.6-minimal 2.6.6-8+b1 (using .../python2.6-minimal_2.6.8-1.1_i386.deb) ...
Unpacking replacement python2.6-minimal ...
Preparing to replace python-scientific 2.8-1.2 (using .../python-scientific_2.8-4_all.deb) ...
/usr/bin/python: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory
dpkg: warning: subprocess old pre-removal script returned error exit status 127
dpkg: trying script from the new package instead ...
/usr/bin/python: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory
dpkg: error processing /var/cache/apt/archives/python-scientific_2.8-4_all.deb (--unpack):
subprocess new pre-removal script returned error exit status 127
configured to not write apport reports
/usr/bin/python: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory
dpkg: error while cleaning up:
subprocess installed post-installation script returned error exit status 127
Processing triggers for python-support ...
/usr/bin/python: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory
dpkg: error processing python-support (--unpack):
subprocess installed post-installation script returned error exit status 127
configured to not write apport reports
Errors were encountered while processing:
/var/cache/apt/archives/python-scientific_2.8-4_all.deb
python-support
Python (indirectly) depends on libssl1.0.0, but that was not yet unpacked while the
newer python* already got unpacked.
There were also similar problems where python was a dangling symlink and not
usable at all...
cheers,
Andreas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: python-mpi_2.8-4.log.gz
Type: application/x-gzip
Size: 23981 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/debian-science-maintainers/attachments/20130504/e6909503/attachment-0001.bin>
More information about the debian-science-maintainers
mailing list