Your message dated Fri, 15 May 2026 18:31:12 +0530
with message-id <[email protected]>
and subject line Re: Bug#1136356: lintian: exit status of 0 after out-of-memory
error, instead of 1
has caused the Debian Bug report #1136356,
regarding lintian: exit status of 0 after out-of-memory error, instead of 1
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.)
--
1136356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1136356
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: lintian
Version: 2.122.0
Severity: normal
X-Debbugs-Cc: [email protected], [email protected]
Hello,
When running lintian:i386 against binaries made from gcc-16, it ran out of
memory, but still exited with status 0 instead of 1.
It would be great if lintian would trap such errors and exit with 1.
I ran into this in the context of debusine thinking that lintian had completed
successfully when it did not:
https://salsa.debian.org/freexian-team/debusine/-/work_items/1454
Thanks!
--
Michael R. Crusoe
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
On 12/05/26 11:10 pm, Nilesh Patra wrote:
> Control: tags -1 moreinfo
> Control: tags -1 unreproducible
>
> On 12/05/26 6:48 pm, Michael R. Crusoe wrote:
>> Package: lintian
>> Version: 2.122.0
>> Severity: normal
>> X-Debbugs-Cc: [email protected], [email protected]
>>
>> Hello,
>>
>> When running lintian:i386 against binaries made from gcc-16, it ran out of
>> memory, but still exited with status 0 instead of 1.
>>
>> It would be great if lintian would trap such errors and exit with 1.
>>
>> I ran into this in the context of debusine thinking that lintian had
>> completed successfully when it did not:
>> https://salsa.debian.org/freexian-team/debusine/-/work_items/1454
>
> I can't repro this with ulimit or otherwise. Replied to the issue on debusine.
After further discussions, this turned out to be a bug in debusine itself.
Hence, I'm going ahead with closing this bug report.
Additionally, as per the logs, global destruction fails - I've opened up
https://salsa.debian.org/lintian/lintian/-/merge_requests/720 so the
cleanup happens. One may argue that the cleanup not happening is a feature, not
a bug. But let's see.
In any case, the return status is correct and this is not a bug in lintian.
Thanks for reporting!
--- End Message ---
