[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1006347: marked as done (lintian: Tag ‘improbable-bug-number-in-closes’ description inaccurate)

Your message dated Thu, 24 Feb 2022 10:47:49 +1100
with message-id <YhbHpevlmobf2lUC@benfinney.id.au>
and subject line Re: lintian: Tag ‘improbable-bug-number-in-closes’ description inaccurate
has caused the Debian Bug report #1006347,
regarding lintian: Tag ‘improbable-bug-number-in-closes’ description inaccurate
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1006347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006347
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: lintian
Version: 2.111.0
Severity: minor
Tags: patch

The description for Lintian tag ‘improbable-bug-number-in-closes’
currently reads:

    The most recent changelog closes a bug numbered less than 2000.
    While this is distantly possible, it's more likely a typo or a
    placeholder value that mistakenly wasn't filled in.

That implies the tag will not match any bug number 2000 or higher.

That description is inaccurate and misleading. The condition currently
matches any bug number < 50004 (so, higher than the 2000 described);
and matches any bug number > 1000000 (the description does not mention
any upper limit).

I suggest this change to the description, to accurately represent the
condition:

-----
modified   checks/changelog-file.desc
@@ -268,9 +268,10 @@ Ref: devref 6.3.4
 Tag: improbable-bug-number-in-closes
 Severity: normal
 Certainty: possible
-Info: The most recent changelog closes a bug numbered less than 2000.
- While this is distantly possible, it's more likely a typo or a
- placeholder value that mistakenly wasn't filled in.
+Info: The most recent changelog closes a bug report with a number that
+ is very low or very high. While this is distantly possible, it's more
+ likely a typo, or a placeholder value that was mistakenly left
+ unchanged.
 
 Tag: wrong-bug-number-in-closes
 Severity: normal
-----

An improvement might be to have the description include the current
values from the data file ‘data/changelog-file/bugs-number’, but I
don't know whether Lintian tag descriptions can be dynamically
populated that way.

-- 
 \            “Technology is neither good nor bad; nor is it neutral.” |
  `\                       —Melvin Kranzberg's First Law of Technology |
_o__)                                                                  |
Ben Finney <bignose@debian.org>

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 
Control: notfound -1 lintian/2.111.0
Control: fixed -1 lintian/2.5.79

On 24-Feb-2022, Ben Finney wrote:
> Package: lintian
> Version: 2.111.0

This bug was fixed some time ago, in Lintian version 2.5.79. I'm
closing this bug report.

-- 
 \     “Not to be absolutely certain is, I think, one of the essential |
  `\                         things in rationality.” —Bertrand Russell |
_o__)                                                                  |
Ben Finney <bignose@debian.org>

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: