On Wed, 12 Nov 2014 11:07:02 +0100 Matthias Klose <d...@debian.org> wrote: > Control: reassign -1 src:python-defaults > Control: tags -1 + moreinfo > > Am 11.11.2014 um 12:38 schrieb Andreas Beckmann: > > Package: python2.7-minimal > > Version: 2.7.8-11 > > Severity: serious > > User: debian...@lists.debian.org > > Usertags: piuparts > > > > Hi, > > > > during a test with piuparts I noticed your package fails to upgrade from > > 'wheezy'. > > It installed fine in 'wheezy', then the upgrade to 'jessie' fails. > > > >>From the attached log (scroll to the bottom...): > > > > Setting up python2.7-minimal (2.7.8-11) ... > > python or pycompile not found in public_modules.rtinstall hook. > > dpkg: error processing package python2.7-minimal (--configure): > > subprocess installed post-installation script returned error exit status 1 > > Errors were encountered while processing: > > python2.7-minimal > > > > This was observed during an upgrade test of texlive-music. > > looks like python wasn't installed into jessie at all, and then is newly > installed. Looking at the build log, you see that > > Selecting previously unselected package python. > (Reading database ... 14654 files and directories currently installed.) > Preparing to unpack .../python_2.7.8-1_amd64.deb ... > Unpacking python (2.7.8-1) ... > Selecting previously unselected package python2.7. > Preparing to unpack .../python2.7_2.7.8-11_amd64.deb ... > Unpacking python2.7 (2.7.8-11) ... > Selecting previously unselected package python2.7-minimal. > Preparing to unpack .../python2.7-minimal_2.7.8-11_amd64.deb ... > Unpacking python2.7-minimal (2.7.8-11) ... > Selecting previously unselected package libpython2.7-minimal:amd64. > Preparing to unpack .../libpython2.7-minimal_2.7.8-11_amd64.deb ... > Unpacking libpython2.7-minimal:amd64 (2.7.8-11) ... > Setting up libpython2.7-minimal:amd64 (2.7.8-11) ... > Setting up python2.7-minimal (2.7.8-11) ... > python or pycompile not found in public_modules.rtinstall hook. > dpkg: error processing package python2.7-minimal (--configure): > subprocess installed post-installation script returned error exit status 1 > > Note that python-minimal isn't yet touched, although python depends on it. > > Wondering why this is not seen for updates to wheezy, and wondering if that > could be resolved if python would pre-depend on python-minimal.
Reading policy 7.2 again, I think think pre-depends is best answer. Depends only ensures that python-minimal is at least unpacked when python is configured. It makes no assurance that python-minimal is unpacked when python2.7-minimal is unpacked (since python2.7-minimal doesn't depend on python-minimal). Adding the pre-depends would ensure python-minimal was at least unpacked when python was unpacked. That's sufficient to avoid this bug. I did some manual testing with dpkg --unpack and am convinced this'll solve it. Alternately, I this could (in theory) be solved by making python2.7-minimal depend on python-minimal, but that would create a dependency loop. Scott K -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
