Your message dated Sat, 14 Feb 2026 15:12:34 +0100
with message-id <[email protected]>
and subject line no longer relevant as archive no longer runs lintian
has caused the Debian Bug report #1025697,
regarding ftp.debian.org: lintian autorejects: include verbose info in reject
message
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 [email protected]
immediately.)
--
1025697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025697
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: wishlist
Usertags: lintian
If lintian decides to autoreject a package, the REJECT message contains the
reasoning in the form of the lintian error that triggered the message.
This is cool.
However, sometimes this info is not enough.
Esp. since lintian has become a faster-moving target, where lintian-overrides
developed and tested on sid might be useless on the the lintian as run by dak
(which i understand is running Debian/stable).
I therefore suggest to include some more information in the REJECT message,
namely:
- the lintian version used by dak
- a full output of lintian (including at least all E and W tags)
in *addition* to the actual tags that triggered the reject.
e.g. recently my package "libogg" got autorejected with the following message:
```
libogg source: lintian output: 'license-problem-non-free-RFC doc/rfc3533.txt',
automatically rejected package.
libogg source: If you have a good reason, you may override this lintian tag.
```
In this particular case, the RFC text has been relicensed so we can ship it, and
therefore the package ships a debian/source/lintian-overrides with the following
content:
```
# see debian/copyright
license-problem-non-free-RFC [doc/rfc3533.txt]
license-problem-non-free-RFC-BCP78 [doc/rfc5334.txt]
```
Unfortunately the lintian_2.104.0 does not understand the "[filepattern]" syntax
yet, so lintian detected a REJECT-tag *and* a mismatched override.
It would have helped me a lot, if the REJECT message had contained something
like:
```
libogg source: lintian output: 'license-problem-non-free-RFC doc/rfc3533.txt',
automatically rejected package.
libogg source: If you have a good reason, you may override this lintian tag.
This rejection message was triggered by Lintian v2.104.0.
Lintian reported the following issues:
E: libogg source: license-problem-non-free-RFC doc/rfc3533.txt
E: libogg source: license-problem-non-free-RFC-BCP78 doc/rfc5334.txt
W: libogg source: mismatched-override license-problem-non-free-RFC
[doc/rfc3533.txt]
W: libogg source: mismatched-override license-problem-non-free-RFC-BCP78
[doc/rfc5334.txt]
W: libogg source: newer-standards-version 4.6.1 (current is 4.5.1)
N: 0 hints overridden; 3 unused overrides
```
thanks for your consideration.
fmas
IOhannes
--- End Message ---
--- Begin Message ---
Closing as this is no longer relevant. The archive no longer runs
lintian in the remaining cases (sourceful uploads) for various reasons.
Ansgar
--- End Message ---
