Re: Bug#619487: lintian: dh_python2 dropped ${python:Breaks} and triggers old-versioned-python-dependency again

2011-03-25 Thread Jakub Wilk
* Piotr Ożarowski , 2011-03-24, 14:26: IMHO old-versioned-python-dependency tag should be simply removed from lintian. These dependencies can be valid even if dh_py{central,support,thon2} is not used (debian-python@l.d.o CCed for confirmation) Agreed. old-version-python-dependency was meant t

dh_python2 dropped ${python:Breaks}

2011-03-24 Thread Scott Kitterman
Most of you probably figured this out already from the cc: of 619487 to debian-python, but just in case ... dh_python2 dropped ${python:Breaks} - This means you should remove Breaks: ${python:Breaks} from packages as you update them. In the mean time, it's presence is harmless so there

Re: Bug#619487: lintian: dh_python2 dropped ${python:Breaks} and triggers old-versioned-python-dependency again

2011-03-24 Thread Piotr Ożarowski
[Stefano Rivera, 2011-03-24] > Hi, since #604167 was resolved, dh_python2 changed behaviour in > python-defaults 2.6.6-12, and doesn't use ${python:Breaks} any more. > Thus all packages installing public modules with dh_python2 will trigger > old-versioned-python-dependency. >

Re: ${python:Breaks}

2011-03-10 Thread Barry Warsaw
On Mar 10, 2011, at 04:12 PM, Josselin Mouette wrote: >Le jeudi 10 mars 2011 à 09:00 -0500, Scott Kitterman a écrit : >> The upstream Python position is (I'll paraphrase), "There will not be >> a Python 2.8. If there is a new feature release of Python 2 it will be >> because someone forked it - it

Re: ${python:Breaks}

2011-03-10 Thread Barry Warsaw
On Mar 10, 2011, at 12:15 PM, Raphael Hertzog wrote: >On Thu, 10 Mar 2011, Piotr Ożarowski wrote: >> seriously, THERE WILL BE NO NEW PYTHON 2.X VERSION RELEASED UPSTREAM¹, >> we don't have to worry about 2.X transitions when 2.7 will become the >> only supported one. If you don't like Breaks, I wi

Re: ${python:Breaks}

2011-03-10 Thread Josselin Mouette
Le jeudi 10 mars 2011 à 09:00 -0500, Scott Kitterman a écrit : > The upstream Python position is (I'll paraphrase), "There will not be > a Python 2.8. If there is a new feature release of Python 2 it will be > because someone forked it - it's Free software, so we can't prevent > that". > > There a

Re: ${python:Breaks}

2011-03-10 Thread Scott Kitterman
On Thursday, March 10, 2011 06:15:01 am Raphael Hertzog wrote: > On Thu, 10 Mar 2011, Piotr Ożarowski wrote: > > seriously, THERE WILL BE NO NEW PYTHON 2.X VERSION RELEASED UPSTREAM¹, > > we don't have to worry about 2.X transitions when 2.7 will become the > > only supported one. If you don't like

Re: ${python:Breaks}

2011-03-10 Thread Raphael Hertzog
On Thu, 10 Mar 2011, Piotr Ożarowski wrote: > seriously, THERE WILL BE NO NEW PYTHON 2.X VERSION RELEASED UPSTREAM¹, > we don't have to worry about 2.X transitions when 2.7 will become the > only supported one. If you don't like Breaks, I will remove it, it > really doesn't matter - that's why at t