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)
