On Saturday, November 22, 2014 05:06:25 PM Jakub Wilk wrote: > * Wouter Verhelst <wou...@debian.org>, 2014-11-22, 08:25: > >>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). > > > >This is inaccurate. > > s/inaccurate/confusing as hell/ :-P > > >A python2.7-minimal pre-depends on python-minimal ensures that > >python-minimal is unpackaged _and configured_ before python2.7-minimal > >is unpacked. > > There are three packages involved is this mess: > > python2.7-minimal > python-minimal > python > > python depends on python-minimal. > python2.7-minimal does NOT depend on python or python-minimal (that'd be > a dependency loop). > python2.7-minimal tries to run a hook shipped by python, which might not > work when python is not configured yet. > > Hence the proposed Pre-Depends: python -> python-minimal.
Thanks for making it clearer. Here's a possible alternate solution: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769106#31 Feedback? Scott K -- 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/3938090.NBIyXZJU4x@kitterman-optiplex-9020m
