Mattia Rizzolo wrote:
> In my opinion your statements here doesn't make any sense: using a
> Debian revision when you are not relying on a single upstream tarball
> (i.e., non-native) really is going against the implied meaning of a
> Debian revision: something that is not supposed to change the upstream
> part.
Whilst I would broadly agree with Mattia's view, I would also concede
that there is something just a little unsatisfactory about an upload
just changing, for example, a single entry in debian/control and that
bumping the [upstream] version number.
However, I would be minded to not adjust Lintian in this particular
case regardless of the above: I suspect in the overwhelming majority
of cases where this tag is emitted it is due to a temporary mistake
such as a typo on behalf of the maintainer which is then immediately
corrected locally. Indeed, I am often guilty of "dch -v 1.0-1" for
packages where I definitely do not intend this suffix and I would very
much like to see that prior to an upload.
Have you considered adding a (commented!) override for this particular
package? I suspect your response may be to suggest we allow this for
1.0 version source packages, but I must confess it would need
explaining to me that the version (eg. "native (1.0)" vs "native
(3.0)") is a distinction to be made here at all.
Best wishes,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org 🍥 chris-lamb.co.uk
`-
