/usr/bin/python2 overwrites file in old versions of python-minimal

[Colin Watson]

In a test upgrade from lucid to precise:

Selecting previously unselected package python2.7.
Unpacking python2.7 (from .../python2.7_2.7.3~rc1-1ubuntu2_i386.deb) ...
dpkg: error processing /var/cache/apt/archives/python2.7_2.7.3~rc1-1ubuntu2_i386.deb (--unpack):
 trying to overwrite '/usr/bin/python2', which is also in package python-minimal 2.6.5-0ubuntu1

At minimum, a Replaces is needed here.

Wasn't the old layout better, though? This seems to make more sense in a -defaults package than in a versioned package; although I realise that it's arguably a moot point given that there won't be a python2.8. But still.

[Scott Kitterman (kitterman)]

The new /usr/bin/python2 madness comes straight to us from upstream, so it's
in the 2.7 package. The old one was self inflicted.

[Steve Langasek (vorlon)]

For reference, this was in python-minimal in lucid but not in any later releases. So Replaces: python-minimal (<< 2.6.6-2ubuntu1) should suffice.

[Matthias Klose (doko)]

no madness, but a now accepted PEP. these files should go into the python-defaults package for the LTS. they are removed in python2.7

[Scott Kitterman (kitterman)]

Since upstream provides them as part of python2.7, it seems like unnecessary
work to remove it from python2.7 and add it to python-defaults.

[Matthias Klose (doko)]

now fixed in precise