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.
