Your message dated Tue, 3 Feb 2026 22:37:26 +0530
with message-id <[email protected]>
and subject line Fixed in latest lintian release
has caused the Debian Bug report #1126453,
regarding dpkg's latest upload breaks lintian testsuite
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.)
--
1126453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1126453
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dpkg
Severity: serious
X-Debbugs-Cc: [email protected]
<mailto:[email protected]>.org
Control: affects -1 + src:lintian
Version: 1.23.5
Hi Guillem,
Lintian’s test suite has started to fail with huge number of errors.
| dpkg-source: error: 'Marc 'HE' Brockschmidt <he@unknown>, Jeroen van
Wolffelaar<[email protected]>,
| Frank <[email protected]>, Yama@gotchi, Josip, I am afraid of spam and think
this helps <no_spam_please AT debian.org>’ is
| not a valid email |address list
This looks like the consequence of latest dpkg upload.
| dpkg (1.23.5) unstable; urgency=medium
| .
| [ Guillem Jover ]
| * dpkg-source: Do not error out on empty fields. Closes: #1125985
| * Perl modules:
| - Dpkg::Email::Address: Do not construct invalid objects.
A large amount of test suite uses legacy tests and there’s even a
"malformed-contact” tag that lintian emits. Fixing all of this
is well, annoying since this is a large number.
OTOH I don’t understand the reasoning behind completely failing to build a
package due to one wrong email address.
The lintian tag of error severity combined with a dpkg warning of malformed
email address looks like a pretty good
check to me already.
Do you think dpkg can emit a warning here instead?
--
Best,
Nilesh
--- End Message ---
--- Begin Message ---
Version: 2.129.0
These are fixed in the latest upload (2.129.0) hence closing.
--
Best,
Nilesh
--- End Message ---