Bug#892304: lintian: Warn about "old" X-Python3-Version fields?

[Chris Lamb]

tags 892304 + pending
thanks

Hi Scott,

> old: =< lowest version supported in stable (for backports)
> ancient: =< lowest version supported in oldstable (for sloppy backports)

Perfect! I've implemented this in Git, pending upload:

  
https://salsa.debian.org/lintian/lintian/commit/d1463b430e4aa71ee5f65ace237ec34bc14fc182


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#892304: lintian: Warn about "old" X-Python3-Version fields?

[Scott Kitterman]

On Friday, May 04, 2018 04:17:37 PM Nicholas D Steeves wrote:
> I remember this   Thanks for mentioning this bug in
> #debian-python.  I followed
> https://wiki.debian.org/Python/LibraryStyleGuide#Python_versions and
> it would seem it also needs to be updated.
...
> 
> Should articles in the wiki be updated before or after lintian?

Before is fine.  I've done it.  We should also update Python policy to get rid 
of X-Python-Version, but that's a different day.

Scott K

signature.asc
Description: This is a digitally signed message part.

Bug#892304: lintian: Warn about "old" X-Python3-Version fields?

[Nicholas D Steeves]

Hello,

On Fri, May 04, 2018 at 03:53:31PM -0400, Scott Kitterman wrote:
> On Thu, 08 Mar 2018 02:07:36 + Chris Lamb  wrote:
> > Package: lintian
> > Version: 2.5.77
> > Severity: wishlist
> > 
> > Hi,
> > 
> > Should we warn about "old" X-Python3-Version fields? For example, I
> > just saw a new package from a sponsee with:
> > 
> >   X-Python3-Version: >= 3.2
> > 
> > This seems a little silly given that 3.2 is only in wheezy, jessie has
> > 3.4 and stretch has 3.5.
> >

I remember this ;-)  Thanks for mentioning this bug in
#debian-python.  I followed
https://wiki.debian.org/Python/LibraryStyleGuide#Python_versions and
it would seem it also needs to be updated.
 
> > If the idea is fundamentally sound, we could even avoid most of the
> > "What versions should we I: or P: at..." bikeshedding by having an
> > "ancient" and "old" tags with differing severities.  :)
> > 
> > Thoughts?
> 
> I also applies to X-Python-Version (even more so - I didn't check if this is 
> already covered in another test).
> 
> Here's a rule of thumb I would suggest:
> 
> old: =< lowest version supported in stable (for backports)
> ancient: =< lowest version supported in oldstable (for sloppy backports)
> 
> Currently that would be:
> 
> Python:
> 
> old: Presence of any X-Python-Version as there's only Python2.7 in stable
> ancient: Same.  Even though oldstable shipped the python2.6 interpreter, it 
> was not a supported version for module building.
> 
> Python3:
> 
> old: X-Python3-Version: >= 3.5
> ancient: X-Python3-Version: >= 3.4
> 
> Backport no longer remains open for LTS, so there's no need to consider 
> backports to oldoldstable.

Should articles in the wiki be updated before or after lintian?

Cheers,
Nicholas


signature.asc
Description: PGP signature

Bug#892304: lintian: Warn about "old" X-Python3-Version fields?

[Scott Kitterman]

On Thu, 08 Mar 2018 02:07:36 + Chris Lamb  wrote:
> Package: lintian
> Version: 2.5.77
> Severity: wishlist
> 
> Hi,
> 
> Should we warn about "old" X-Python3-Version fields? For example, I
> just saw a new package from a sponsee with:
> 
>   X-Python3-Version: >= 3.2
> 
> This seems a little silly given that 3.2 is only in wheezy, jessie has
> 3.4 and stretch has 3.5.
> 
> If the idea is fundamentally sound, we could even avoid most of the
> "What versions should we I: or P: at..." bikeshedding by having an
> "ancient" and "old" tags with differing severities.  :)
> 
> Thoughts?

I also applies to X-Python-Version (even more so - I didn't check if this is 
already covered in another test).

Here's a rule of thumb I would suggest:

old: =< lowest version supported in stable (for backports)
ancient: =< lowest version supported in oldstable (for sloppy backports)

Currently that would be:

Python:

old: Presence of any X-Python-Version as there's only Python2.7 in stable
ancient: Same.  Even though oldstable shipped the python2.6 interpreter, it 
was not a supported version for module building.

Python3:

old: X-Python3-Version: >= 3.5
ancient: X-Python3-Version: >= 3.4

Backport no longer remains open for LTS, so there's no need to consider 
backports to oldoldstable.

Scott K

Bug#892304: lintian: Warn about "old" X-Python3-Version fields?

[Chris Lamb]

Package: lintian
Version: 2.5.77
Severity: wishlist

Hi,

Should we warn about "old" X-Python3-Version fields? For example, I
just saw a new package from a sponsee with:

  X-Python3-Version: >= 3.2

This seems a little silly given that 3.2 is only in wheezy, jessie has
3.4 and stretch has 3.5.

If the idea is fundamentally sound, we could even avoid most of the
"What versions should we I: or P: at..." bikeshedding by having an
"ancient" and "old" tags with differing severities.  :)

Thoughts?


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-