Le samedi 16 février 2013 à 16:35 +0100, Andreas Beckmann a écrit : > 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...): > > Preparing to replace python-numpy 1:1.4.1-5 (using > .../python-numpy_1%3a1.6.2-1.1_amd64.deb) ... > /var/lib/dpkg/info/python-numpy.prerm: 6: update-python-modules: not found > dpkg: warning: subprocess old pre-removal script returned error exit status > 127 > dpkg: trying script from the new package instead ... > /var/lib/dpkg/tmp.ci/prerm: 6: update-python-modules: not found > dpkg: error processing > /var/cache/apt/archives/python-numpy_1%3a1.6.2-1.1_amd64.deb (--unpack): > subprocess new pre-removal script returned error exit status 127 > configured to not write apport reports > /var/lib/dpkg/info/python-numpy.postinst: 6: update-python-modules: not > found > dpkg: error while cleaning up: > subprocess installed post-installation script returned error exit status > 127
Here is what happens: when the prerm script is started, /usr/bin/python symlink points to /usr/bin/python2.7, but the latter has not yet been unpacked. So the python script update-python-modules cannot be run… Said otherwise, python-minimal 2.7.3-4 has been unpacked, but python2.7-minimal has not yet been. It is clear that this is not a python-numpy bug, but at this stage I don’t know which package to reassign it to (python-defaults, python-support, or even apt ?). -- .''`. Sébastien Villemot : :' : Debian Developer `. `' http://www.dynare.org/sebastien `- GPG Key: 4096R/381A7594
signature.asc
Description: This is a digitally signed message part
