[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: python-reportbug in jessie-backports has invalid version

On Fri, Jul 28, 2017 at 05:03:16PM -0500, Dan Rue wrote:
> On Fri, Jul 28, 2017 at 11:31:45PM +0200, Rene Engelhard wrote:
> > On Fri, Jul 28, 2017 at 03:20:29PM -0300, Antonio Terceiro wrote:
> > > 6.6.6~bpo8 is the _Debian_ version. The Python version is 6.6.6, and has
> > > no effect on the upgradeability of the package. Also, we dont't go
> > > around changing upstream version numbers on any backports, so I can't
> > > see any good reason to do that in this case, even condidering that
> > > reportbug is a native package.
> > 
> > So Debian version == upstream version (you say yourself it's a native
> > package). So 6.6.6 would be wrong and 6.6.6~bpo8 is correct. You would
> > be right if it was non-native, but...
> I thought changing the python version of reportbug would be the least
> invasive fix. Alternatively, is there any appetite to touch python-pip?
> The following patch has been in pip since 6.0, and solves the version
> issue generally:
> https://github.com/pypa/pip/commit/6cab71f422f2425b4d2283023c9e955f9663dde6
> Increasing the amount of invasiveness, we could backport a newer
> python-pip. Upgrading pip to any version newer than 1.5.6 solves the
> issue (but of course could introduce other issues).

It might make sense to do that, yes. I think upgrading python-pip to whatever's
in the appropriate suite right now should be enough, and then you can
make python-reportbug depend on that version.

Could you people please use IRC like normal people?!?

  -- Amaya Rodrigo Sastre, trying to quiet down the buzz in the DebConf 2008

Reply to: