Bug#769106: python2.7-minimal: fails to upgrade from 'wheezy': python or pycompile not found in public_modules.rtinstall hook.
On 11/21/2014 03:02 PM, Scott Kitterman wrote: On IRC, an alternate solution was suggested. What about moving the rtinstall call from the python2.7-minimal postinst to python2.7's and then have python2.7 depend on python-minimal? That would resolve this issue and not create a dependency loop. Would it cause any other 'bad' things? I don't think this solves the issue. The idea is to have everything about byte-compilation in the -minimal packages. Whoever said that, I think the pre-dependency is the least invasive solution -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769106: python2.7-minimal: fails to upgrade from 'wheezy': python or pycompile not found in public_modules.rtinstall hook.
On Sun, 16 Nov 2014 00:29:58 -0500 Scott Kitterman deb...@kitterman.com wrote: On Wed, 12 Nov 2014 11:07:02 +0100 Matthias Klose d...@debian.org wrote: ... 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. On IRC, an alternate solution was suggested. What about moving the rtinstall call from the python2.7-minimal postinst to python2.7's and then have python2.7 depend on python-minimal? That would resolve this issue and not create a dependency loop. Would it cause any other 'bad' things? Scott K signature.asc Description: This is a digitally signed message part.
Bug#769106: python2.7-minimal: fails to upgrade from 'wheezy': python or pycompile not found in public_modules.rtinstall hook.
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
Processed: Re: Bug#769106: python2.7-minimal: fails to upgrade from 'wheezy': python or pycompile not found in public_modules.rtinstall hook.
Processing control commands: reassign -1 src:python-defaults Bug #769106 [python2.7-minimal] python2.7-minimal: fails to upgrade from 'wheezy': python or pycompile not found in public_modules.rtinstall hook. Bug reassigned from package 'python2.7-minimal' to 'src:python-defaults'. No longer marked as found in versions python2.7/2.7.8-11. Ignoring request to alter fixed versions of bug #769106 to the same values previously set tags -1 + moreinfo Bug #769106 [src:python-defaults] python2.7-minimal: fails to upgrade from 'wheezy': python or pycompile not found in public_modules.rtinstall hook. Added tag(s) moreinfo. -- 769106: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769106 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769106: python2.7-minimal: fails to upgrade from 'wheezy': python or pycompile not found in public_modules.rtinstall hook.
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. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769106: python2.7-minimal: fails to upgrade from 'wheezy': python or pycompile not found in public_modules.rtinstall hook.
On 2014-11-12 11:07, Matthias Klose wrote: looks like python wasn't installed into jessie at all, and then is newly installed. Looking at the build log, you see that 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. I could perform some upgrade tests if you provide test packages (version jessie, somewhere together with a Packages file). Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769106: python2.7-minimal: fails to upgrade from 'wheezy': python or pycompile not found in public_modules.rtinstall hook.
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. cheers, Andreas texlive-music_2014.20141024-1.log.gz Description: application/gzip
