* Cyril Brulebois <kibi@debian.org> [2023-10-28 14:43]:
Marc Haber <mh+debian-packages@zugschlus.de> (2023-10-09):On Mon, Oct 09, 2023 at 02:06:58AM +0200, Cyril Brulebois wrote:That exception only hides the root of the bug, which includes (at least) a messed up version sorting.What is the recommended way to get rid of this? Re-sorting changelog entries? Adding an override?On the lintian user side: Ignoring silly results works for me.On the lintian developer side: Fixing whatever produces the weird and of course incorrect ordering that's then expected and complained about.Adding another exception for bookworm will only lead to more whack-a-mole down the line (see #1051140).I don't see the connection here.Adding an exception hides the bug. Then it's going to appear again when the next suite is around the corner, until an exception is added again, etc. That doesn't seem like a good idea to me.
I have the impression that the discussion went astray. The original reported issue is that the sequence of versions:
0.18.3-1 ⇒ 0.18.3-1+deb12u1 ⇒ 0.18.3-1+deb12u2
is perfectly valid but, yet, Lintian says that the third one is not
allowed to follow the second one.
According to the Debian Developer's Reference, section 5.14.3:“Version numbers are usually selected by appending +debXuY, where X is the major release number of Debian and Y is a counter starting at 1. e.g. 1:2.4.3-4+deb12u1.”
Mu understanding is that the last number (Y) is expected to increase in successive releases.
Could the code in Lintian be changed such that the warning changelog-file-missing-explicit-entry will only be triggered when Z+debXu1 does not follow Z? For now, it seems to be triggered whenever Z+debXu\d+ follows Z.
Best, Rafael Laboissière