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). Since nothing outside python-defaults should depend on python-minimal this should have a minimal impact on upgrade ordering or dependency resolution complexity. One might argue that the python/python-minimal split is obsolete and ought to be dropped, but I think that's a discussion to have (if at all) for Stretch. Adding the pre-depends is the least invasive solution to this RC bug. Comments/concurrence/etc? Scott K [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769106 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/2336109.MRqKsDn39K@kitterman-optiplex-9020m
