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

${python:Breaks}

2011-03-10 Thread Piotr Ożarowski
e same semantics as: > > > Depends: python (>= 2.5), python (<< 2.8) > > > > Yes it does; if you will not add ${python:Breaks} in debian/control, > > that's what dh_python2 will generate actually. > > Having a different behaviour depending on whethe