Your message dated Thu, 23 Apr 2020 11:04:31 +0000 with message-id <E1jRZeh-0009cP-HZ@fasolo.debian.org> and subject line Bug#935292: fixed in lintian 2.67.0 has caused the Debian Bug report #935292, regarding lintian: encrypted zip files stall processing 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.) -- 935292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935292 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: lintian: reporing-harness get stuck when lintian deadlocks
- From: Niels Thykier <niels@thykier.net>
- Date: Wed, 21 Aug 2019 13:25:49 +0200
- Message-id: <156638674934.30863.7396441821289931234.reportbug@mangetsu.thykier.net>
Package: lintian Version: 2.18.0 Severity: important Spotted on lindsay.d.o: The reporting framework runs lintian on a timer and can send it SIGTERM if it gets stuck (usually when the processing time is over). However, it seems that the reporting framework sometimes just dies/disappeares after lintian is killed. Below is the log from where lintian was manually killed by me on a stuck package - but there are plenty of examples that suggest it also happens when the reporting-lintian-harness automatically kills lintian on a timeout. """ [2019-08-21T10:26:24]: New lintian log at /srv/lintian.debian.org/logs/lintian.log-bPGtadL [2019-08-21T10:29:05]: [lintian] error processing golang-1.11/1.11.13-1 (time: 122.898s) [2019-08-21T10:29:06]: [lintian] processed golang-github-mcuadros-go-gin-prometheus/0.1.0+git20190723.c7374e9-2 successfully (time: 1.396s) [2019-08-21T10:32:37]: [lintian] processed grass/7.8.0~rc1-1~exp1 successfully (time: 210.685s) [2019-08-21T10:33:45]: [lintian] processed grpc/1.23.0-1 successfully (time: 68.446s) [2019-08-21T10:33:50]: [lintian] processed guake/3.6.3-1 successfully (time: 5.118s) [2019-08-21T10:33:56]: [lintian] processed intel-cmt-cat/3.1.0-2 successfully (time: 5.953s) [2019-08-21T10:34:03]: [lintian] processed intel-processor-trace/2.0.1-1 successfully (time: 6.566s) [2019-08-21T10:34:06]: [lintian] processed libbpp-qt/2.4.1-2 successfully (time: 3.384s) [2019-08-21T10:34:13]: [lintian] processed libbpp-seq-omics/2.4.1-4 successfully (time: 7.356s) [2019-08-21T10:34:17]: [lintian] processed libconfig-model-itself-perl/2.018-1 successfully (time: 3.495s) [2019-08-21T10:34:21]: [lintian] processed libseqlib/1.1.2+dfsg-4 successfully (time: 3.913s) [2019-08-21T10:55:19]: [lintian] processed linux-signed-i386/5.2.9+1 successfully (time: 1258.298s) [2019-08-21T10:55:42]: [lintian] processed mandos/1.8.8-1 successfully (time: 22.420s) [2019-08-21T11:15:26]: Signal SIGTERM acknowledged: disabled timed alarms """ After this, the harness.log simply "stops". The package triggering it in this case was "mgcv" (now blacklisted on lindsay.d.). The lintian log looks like the following: """ N: Finished processing group mandos/1.8.8-1 N: Starting on group mgcv/1.8-28-2 N: Unpacking packages in group mgcv/1.8-28-2 N: Interrupted. """ The last line appeared after I killed lintian. Please see [1] for the last bit of the performance log which tells you what tasks lintian managed to complete on mgcv. This has probably been a key reason for why the lintian.d.o website has not been updated in the past few days. I hope it is helpful in debugging the issue. Thanks, ~Niels [1] Note the first line (mandos) is from the previous source just to ensure that everything from mgcv is present. """ mandos/1.8.8-1,total-group-auto-remove,0.310351 binary:r-cran-mgcv/1.8-28-2/i386,coll/unpacked,1.007855 binary:r-cran-mgcv/1.8-28-2/amd64,coll/unpacked,1.168259 binary:r-cran-mgcv/1.8-28-2/i386,coll/file-info,0.524697 source:mgcv/1.8-28-2,coll/unpacked,0.9776 binary:r-cran-mgcv/1.8-28-2/amd64,coll/file-info,0.662295 binary:r-cran-mgcv/1.8-28-2/i386,coll/md5sums,0.216517 binary:r-cran-mgcv/1.8-28-2/amd64,coll/md5sums,0.187911 source:mgcv/1.8-28-2,coll/md5sums,0.230758 binary:r-cran-mgcv/1.8-28-2/i386,coll/objdump-info,0.317088 binary:r-cran-mgcv/1.8-28-2/amd64,coll/objdump-info,0.31345 binary:r-cran-mgcv/1.8-28-2/i386,coll/strings,0.342909 binary:r-cran-mgcv/1.8-28-2/amd64,coll/strings,0.366867 source:mgcv/1.8-28-2,coll/src-orig-index,0.306694 source:mgcv/1.8-28-2,coll/file-info,2.820701 binary:r-cran-mgcv/1.8-28-2/i386,coll/bin-pkg-control,0.569369 binary:r-cran-mgcv/1.8-28-2/i386,coll/override-file,0.083423 binary:r-cran-mgcv/1.8-28-2/amd64,coll/override-file,0.08031 binary:r-cran-mgcv/1.8-28-2/amd64,coll/bin-pkg-control,0.695504 source:mgcv/1.8-28-2,coll/override-file,0.127517 binary:r-cran-mgcv/1.8-28-2/i386,coll/ar-info,0.095013 binary:r-cran-mgcv/1.8-28-2/amd64,coll/ar-info,0.107359 binary:r-cran-mgcv/1.8-28-2/i386,coll/java-info,0.108112 binary:r-cran-mgcv/1.8-28-2/amd64,coll/java-info,0.125803 binary:r-cran-mgcv/1.8-28-2/i386,coll/copyright-file,0.072609 binary:r-cran-mgcv/1.8-28-2/amd64,coll/copyright-file,0.060382 binary:r-cran-mgcv/1.8-28-2/i386,coll/scripts,0.095971 binary:r-cran-mgcv/1.8-28-2/amd64,coll/scripts,0.096182 source:mgcv/1.8-28-2,coll/diffstat,0.065437 binary:r-cran-mgcv/1.8-28-2/i386,coll/changelog-file,0.138974 """
--- End Message ---
--- Begin Message ---
- To: 935292-close@bugs.debian.org
- Subject: Bug#935292: fixed in lintian 2.67.0
- From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>
- Date: Thu, 23 Apr 2020 11:04:31 +0000
- Message-id: <E1jRZeh-0009cP-HZ@fasolo.debian.org>
- Reply-to: Chris Lamb <lamby@debian.org>
Source: lintian Source-Version: 2.67.0 Done: Chris Lamb <lamby@debian.org> We believe that the bug you reported is fixed in the latest version of lintian, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 935292@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Lamb <lamby@debian.org> (supplier of updated lintian package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmaster@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Thu, 23 Apr 2020 10:21:16 +0000 Source: lintian Architecture: source Version: 2.67.0 Distribution: unstable Urgency: medium Maintainer: Debian Lintian Maintainers <lintian-maint@debian.org> Changed-By: Chris Lamb <lamby@debian.org> Closes: 930679 935292 956146 958113 958182 Changes: lintian (2.67.0) unstable; urgency=medium . * Summary of tag changes: + Added: - debian-rules-uses-as-needed-linker-flag - mailing-list-obsolete-in-debian-infrastructure - native-source-file-without-utf8-name . [ Axel Beckert ] * Stop correcting "extraversion" to "extroversion" as it causes false positives. . [ Chris Lamb ] * Add a warning regarding lists.alioth.debian.org mailing list addresses. (Closes: #958182) * Check for debian/rules files that specify -Wl,--as-needed as this is now the default linking method from bullseye. (Closes: #956146) * Detect "dh $*" as using the Debhlper sequencer. (Closes: #930679) * Also check for "override dh_install" in debian/rules; in 99% of cases this will be an omission of an underscore. . [ Felix Lechner ] * Do not check for circular root references when a file index is empty. (Closes: #958113) * Do not prompt for password for encrypted zip members. (Closes: #935292) * Fix the output for JSON; it is encoded already. * Dynamically generate file names that are not valid UTF-8 in tests. * Add new tag for non-UTF-8 file name in the source tree. . [ Vincent Blut ] * Add 'needs-internet' to the list of permitted values for the restrictions field in autopkgtest control files. Checksums-Sha1: d9570569b8a3ecc18cf10bc1ed2f82393583961c 4131 lintian_2.67.0.dsc ef1953375dc125d65f2d37ebcaad0191bc1df38c 1884524 lintian_2.67.0.tar.xz 811462fe259cb7e3635bee5b019fab8df55c96ae 16543 lintian_2.67.0_amd64.buildinfo Checksums-Sha256: 9a1d55290f81f464c9a78105097842e250117c1df8e0677ae81951053efd2674 4131 lintian_2.67.0.dsc 53c2df5e5caa9ba52d7d47d39b395666e05e9aae28b5f5882ebc3c8801fc000d 1884524 lintian_2.67.0.tar.xz 28aa2bcb3757235b96ff62c80b1e15bf3f1c0e8f687798aeea086aa5346436bf 16543 lintian_2.67.0_amd64.buildinfo Files: 9b6fd930995f2210c5ec31f2d541f624 4131 devel optional lintian_2.67.0.dsc 3d1c76fa4ec6d087290b5c82b11f4c95 1884524 devel optional lintian_2.67.0.tar.xz 1914dd2204c66e21a94de7775b7277ae 16543 devel optional lintian_2.67.0_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAl6hczQACgkQHpU+J9Qx HlhV+Q//cc/DFHK+fiqxTVUY37HunY1KjWGgh+eSiuHJc252iW6DzF/CMAuYiW5b c+IS+7UX68sdVYFGo+uTeb2QWFdSLhInTSHEbc9b89ebCEWEsl9R+wJ7/20ndzvz TauQS5wga7gHso5e7fy9rK9JnBlnlmdjJ9bjSkST0eyyKdUmpvSpTkmMLyQlQpk+ rqKBIkelHQNkXkEFRR2bN95pzx119C98/T5ZBPEZsWjNt8W4AgoAgOSdBA/LfPt7 BhA7DC2f266nKTvnDeAOPDJJ2lCxr20wSTjs6f2J4IA4/7vMcD2hoL5yOq0i79hD nfS9wnvpAtb8Sku/zIa6bhpwFOFJAqGAAbR1hR0m6CxGhwnjTh9awd7u7A4nMwQb 5lS3R5ZtEFCs2DMjD+ewx8cLGDpwEGUVtMlhiomfqTeQrzW136URLz9EM028Dtef nvp16UcjhFBy7nMJQOADV/onuWsFw8iCxApILUjRd3I8Z0WROrKkAI1qhssPa8hu dL4Jq8fjqzGii+xxXGDr3EiDPjvllCtMhH/jrE6O0CqVlDBoUi/pvebfZmYzBLnE Xicb7ZB3oQIrXxcRcoIRhIKPOkl7pafsi2JrUevABFiE8e4hqJb6GVX3PlgAtd/Q 8GRTjloLBG0bJ/fFfIUQAliHxWrNjzqvJFXna61RkFprg0muxeQ= =M6GA -----END PGP SIGNATURE-----
--- End Message ---