Bug#891555: Detect and warn about debhelper >= 11 instead of 11~ b-d

[Thomas Goirand]

On 02/26/2018 10:02 PM, Niels Thykier wrote:
> Thomas Goirand:
>> [...]
>>
>> And then debhelper 12 is released, people start to use it, and guess
>> what happens... :)
>>
> 
> I am prototyping an alternative in debhelper that may make this issue
> obsolete.  At the moment (since 11.1.5) you can use:
> 
>  Build-Depends: debhelper-compat (= 11)
> 
> as a replacement for:
> 
>  Build-Depends: debhelper (>= 11~)
>  and d/compat set to 11.

Oh, great improvement. I always thought that debian/compat file was kind
of too much, just to express the debhelper version... :)

Thanks for this,

Thomas Goirand (zigo)

Bug#891555: Detect and warn about debhelper >= 11 instead of 11~ b-d

[Niels Thykier]

Thomas Goirand:
> [...]
> 
> And then debhelper 12 is released, people start to use it, and guess
> what happens... :)
> 

I am prototyping an alternative in debhelper that may make this issue
obsolete.  At the moment (since 11.1.5) you can use:

 Build-Depends: debhelper-compat (= 11)

as a replacement for:

 Build-Depends: debhelper (>= 11~)
 and d/compat set to 11.

Note the lack of "~" in the debhelper-compat version.


It spews out tons of warnings as it is still experimental.  Nonetheless,
feedback appreciated.

Thanks,
~Niels

Bug#891555: Detect and warn about debhelper >= 11 instead of 11~ b-d

[Thomas Goirand]

On 02/26/2018 06:10 PM, Raphael Hertzog wrote:
> Hi,
> 
> On Mon, 26 Feb 2018, Thomas Goirand wrote:
>> Currently, there's debhelper 11~bpo9+1 in Stretch. However, mostly everyone
>> build-depends on debhelper (>= 11), making it impossible to use the 
>> backported
>> debhelper without fixing the debhelper version of the software to backport.
>>
>> It'd be nice if Lintian was warning about this, and nicely suggesting to
>> build- depend on version 11~, to allow backports.
> 
> I think it would be better to backport 11.1.4 (as 11.1.4~bpo9+1) and
> forget about this. Otherwise we will be asking developers to update this
> field for months if not years to come when in fact the problem will go
> away in a few days/weeks.
> 
> Cheers,

And then debhelper 12 is released, people start to use it, and guess
what happens... :)

So, perhaps my description wasn't broad enough, but I thought it was
obvious that we'd need something that would work forever.

BTW, to even make the scope broader, this is a general problem with
native packages and backports. We don't have the issue with non-native,
because lintian warns about the debian release number that comes after
the upstream version, which makes the problem solved. So lintian would
need to know about all native packages and suggest the addition of a ~
after the version, always (I don't think it'd be hard to embed a list of
native packages in the archive, would it?).

Your thoughts?

Cheers,

Thomas Goirand (zigo)

Bug#891555: Detect and warn about debhelper >= 11 instead of 11~ b-d

[Chris Lamb]

tags 891555 + wontfix
thanks

Thanks for providing the background detail re. the backport.

> Just bear with it for some weeks for few packages...

Mmm, that's the most sensible approach IMHO too. Closing the bug
to match, but thanks Zigo for raising this so we can get some
explicit explanation. :)


Best wishes,

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

Bug#891555: Detect and warn about debhelper >= 11 instead of 11~ b-d

[Mattia Rizzolo]

Agreed.
Just bear with it for some weeks for few packages...

On Mon, 26 Feb 2018, 6:10 p.m. Raphael Hertzog,  wrote:

> Hi,
>
> On Mon, 26 Feb 2018, Thomas Goirand wrote:
> > Currently, there's debhelper 11~bpo9+1 in Stretch. However, mostly
> everyone
> > build-depends on debhelper (>= 11), making it impossible to use the
> backported
> > debhelper without fixing the debhelper version of the software to
> backport.
> >
> > It'd be nice if Lintian was warning about this, and nicely suggesting to
> > build- depend on version 11~, to allow backports.
>
> I think it would be better to backport 11.1.4 (as 11.1.4~bpo9+1) and
> forget about this. Otherwise we will be asking developers to update this
> field for months if not years to come when in fact the problem will go
> away in a few days/weeks.
>
> Cheers,
> --
> Raphaël Hertzog ◈ Debian Developer
>
> Support Debian LTS: https://www.freexian.com/services/debian-lts.html
> Learn to master Debian: https://debian-handbook.info/get/
>

Bug#891555: Detect and warn about debhelper >= 11 instead of 11~ b-d

[Raphael Hertzog]

Hi,

On Mon, 26 Feb 2018, Thomas Goirand wrote:
> Currently, there's debhelper 11~bpo9+1 in Stretch. However, mostly everyone
> build-depends on debhelper (>= 11), making it impossible to use the backported
> debhelper without fixing the debhelper version of the software to backport.
> 
> It'd be nice if Lintian was warning about this, and nicely suggesting to
> build- depend on version 11~, to allow backports.

I think it would be better to backport 11.1.4 (as 11.1.4~bpo9+1) and
forget about this. Otherwise we will be asking developers to update this
field for months if not years to come when in fact the problem will go
away in a few days/weeks.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

Bug#891555: Detect and warn about debhelper >= 11 instead of 11~ b-d

[Thomas Goirand]

Package: lintian
Version: 2.5.50.4
Severity: wishlist

Hi,

Currently, there's debhelper 11~bpo9+1 in Stretch. However, mostly everyone
build-depends on debhelper (>= 11), making it impossible to use the backported
debhelper without fixing the debhelper version of the software to backport.

It'd be nice if Lintian was warning about this, and nicely suggesting to build-
depend on version 11~, to allow backports.

Cheers,

Thomas Goirand (zigo)