On Tuesday, November 18, 2014 08:28:29 AM Julien Cristau wrote: > On Mon, Nov 17, 2014 at 18:24:00 -0500, Scott Kitterman wrote: > > It appears that the appropriate resolution of #769106 [1] is to add a new > > pre-depends on python-minimal in python. > > > > This issue at hand is that at the time python2.7-minimal is configured, > > python is unpacked, but python-minimal is not. Since python-2.7-minimal > > doesn't have a direct depends on python-minimal, this is allowable > > (policy 7.2, Depends). > > > > In order for python2.7-minimal to configure, python-minimal needs to be at > > least unpacked to provide /usr/bin/pycompile. The only way for python to > > ensure this is the case is to declare a pre-depends relation (also policy > > 7.2). > > Can you explain why/how the python package enters into the picture here > at all?
texlive-music grew a depends on python between wheezy and jessie, so in the upgrade test that led to the the bug it was being freshly installed (test being done in a minimal chroot. python depends (among other things) python2.7 and python-minimal. python- minimal then depends on python2.7-minimal. As part of python2.7-minimal's configuration, /usr/share/python/runtime.d/public_modules.rtinstall gets executed. It's part of the python package. Since the dependency chain was texlive-music -> python -> python2.7-minimal, python is already unpacked, so the script is available. The tricky part is that /usr/share/python/runtime.d/public_modules.rtinstall needs /usr/bin/pycompile in order to work. That's in (you guessed it) python- minimal. It's not available (and there's nothing in policy that says it has to be). Eventually, python-minimal will get unpacked, but it hadn't yet in this test run. Does that clarify it? Scott K
signature.asc
Description: This is a digitally signed message part.
