Bug#973308: lintian: Automate importation of valid archive sections via http://
Hello, On 2020-10-28 17:57, Felix Lechner wrote: > Lintian does not presently utilize any network resources, and while > that may change in the future, it would be the wrong way forward. It > makes no sense for Lintian to query the archive for valid sections for > every invocation. I agree. > Ideally, the file from FTP Master that is described below would be > packaged and backported as needed. It is probably not updated often. I > asked Ganneff about this on #debian-ftp but have not heard back. Maybe > it could also be packaged together with other Debian data, such as > policy versions, which are being worked on in this bug: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968154#52 > > Packaging such data for Debian is also found in other areas, for > example in 'dns-root-data'. I completely support packaging sections.822 into some data package so as lintian and possibly other tools could read it without using network. > An alternative would be update ./data in our repo for each new > release, but that data remains static for each release. We keep > scripts for such updates in ./private. Contributions are welcome. If packaging sections.822 is not an option, this alternative could work. I used the following command in 9904e258: curl -sSL https://metadata.ftp-master.debian.org/sections.822 \ | grep ^Section: | cut -d ' ' -f 2 | grep -v / \ | sort > data/fields/archive-sections Best, Andrius
Processed: Bug#973335 marked as pending in lintian
Processing control commands: > tag -1 pending Bug #973335 [lintian] lintian: missing-dep-for-interpreter outdated guile versions Added tag(s) pending. -- 973335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973335 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#973334: lintian: URL in systemd-service-file-uses-deprecated-syslog-facility incorrect
Package: lintian Version: 2.99.0 Severity: normal The URL referenced in systemd-service-file-uses-deprecated-syslog-facility: Refer to https://github.com/systemd/systemd/blob/master/NEWS#L101 for details. This references a changing file by line number, and it tends to get new changes at the top, so the link is very likely to point to the wrong line on any project that is still making updates. It should probably point to a specific revision and/or tag, such as: https://github.com/systemd/systemd/blob/6706384a89ae0c462e7172588c80667190c4d9e2/NEWS#L724 live well, vagrant signature.asc Description: PGP signature
Processed: Bug#973334 marked as pending in lintian
Processing control commands: > tag -1 pending Bug #973334 [lintian] lintian: URL in systemd-service-file-uses-deprecated-syslog-facility incorrect Added tag(s) pending. -- 973334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973334 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#973335: lintian: missing-dep-for-interpreter outdated guile versions
Package: lintian Version: 2.99.0 Severity: normal X-Debbugs-CC: r...@defaultvalue.org The missing-dep-for-interpreter references old guile versions but not the newer versions: missing-dep-for-interpreter guile => guile | guile-2.0 | guile-2.2 guile-2.0 is not currently in bullseye due to RC bugs and I believe the maintainer would very much like to retire it. guile-3.0 is the newest guile present in bullseye. So lintian should at least be updated to: guile | guile-2.2 | guile-3.0 live well, vagrant signature.asc Description: PGP signature
Bug#972878: lintian: Wide character in say at Lintian::Output line 156
Hi Thorsten, On Wed, Oct 28, 2020 at 8:47 PM Thorsten Glaser wrote: > > So lintian maybe behaves different from that testcase? Probably not. The test case was reduced from Lintian. (And yes, we ship a snowman!) Kind regards Felix Lechner
Bug#972878: lintian: Wide character in say at Lintian::Output line 156
Felix Lechner dixit: >Feel free to try it. The test case is attached. tglase@tglase-nb:~ $ perl /tmp/x Wide character in say at /tmp/x line 13. UTF-8: ✓ (☃) So lintian maybe behaves different from that testcase? bye, //mirabilos -- 15:41⎜ Somebody write a testsuite for helloworld :-)
Bug#973333: lintian.d.o: please add a symlink/redirect to the most recent version
Hi Paul, On Wed, Oct 28, 2020 at 7:39 PM Paul Wise wrote: > > Since most folks would only be interested in the lintian results for > the latest version in unstable, it would be nice if the middle click > could be eliminated using a symlink or redirect. An "all versions" link > could be added for folks who are interested in that. We just found a hosting provider for our new dynamic web site. It will be an experiment for the time being, but is expected to bring this feature, as well as many others, based on queries in a Postgres database that is already installed there. Kind regards Felix Lechner
Bug#972878: lintian: Wide character in say at Lintian::Output line 156
Hi Thorsten, On Wed, Oct 28, 2020 at 7:47 PM Thorsten Glaser wrote: > > So it will just go away if we wait long enough. Maybe. I did not see it in a chroot with unstable, but the Perl folks who helped did not use Debian, and still confirmed the behavior. Perhaps someone patched our Perl; the bugs remain open upstream. Feel free to try it. The test case is attached. Kind regards Felix Lechner wide-character-error Description: Binary data
Bug#972878: lintian: Wide character in say at Lintian::Output line 156
Felix Lechner dixit: >The issues have been open since 2007 and 2011. We do not currently >have a plan for mitigation. AIUI this only affects buster anyway and not sid? So it will just go away if we wait long enough. bye, //mirabilos -- (gnutls can also be used, but if you are compiling lynx for your own use, there is no reason to consider using that package) -- Thomas E. Dickey on the Lynx mailing list, about OpenSSL
Bug#973333: lintian.d.o: please add a symlink/redirect to the most recent version
Package: lintian Severity: wishlist When clicking through to lintian.d.o from tracker.d.o and other places, there is an extra click from the source package page to the source package version page containing the actual lintian results. https://tracker.debian.org/pkg/iotop -> https://lintian.debian.org/sources/iotop.html -> https://lintian.debian.org/sources/iotop/0.6-24-g733f3f8-1.1.html Since most folks would only be interested in the lintian results for the latest version in unstable, it would be nice if the middle click could be eliminated using a symlink or redirect. An "all versions" link could be added for folks who are interested in that. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#972878: lintian: Wide character in say at Lintian::Output line 156
Control: retitle -1 lintian: Drop global UTF-8 PerlIO encoding layer Hi, > Wide character in say at > /lcl/lechner/lintian/git/bin/../lib/Lintian/Output.pm line 156. This is a bug in Perl: https://rt.cpan.org/Public/Bug/Display.html?id=69011 in combination with https://github.com/perl/perl5/issues/8997 https://github.com/perl/perl5/issues/8998 The issues have been open since 2007 and 2011. We do not currently have a plan for mitigation. One way would be to drop the global PerlIO encoding layer for UTF-8 and instead use Unicode::UTF8::encode_utf8 explicitly, everywhere. That would generate a fair amount of work, though. Kind regards Felix Lechner
Processed: lintian: Wide character in say at Lintian::Output line 156
Processing control commands: > retitle -1 lintian: Drop global UTF-8 PerlIO encoding layer Bug #972878 [lintian] lintian: Wide character in say at Lintian::Output line 156 Changed Bug title to 'lintian: Drop global UTF-8 PerlIO encoding layer' from 'lintian: Wide character in say at Lintian::Output line 156'. -- 972878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972878 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#973313: lintian: Fix failing Lintian jobs for many if not all packages hosted on Salsa
Package: lintian Severity: important Hi, Since October 22, the Lintian jobs on Salsa pipelines have failed for many packages, including Lintian. [1] In the container, 'groff' cannot find LC_ALL defined even though we reset the environment and explicitly provide LC_ALL=C.UTF-8. [2] It is ineffective, and that is the substance of this bug. I am not sure what changed (my commit could not have done it). I only see a recent upload for bash, but not for groff, perl or libipc-run3-perl. I already asked on #salsci. I was told that the runner images had not been manipulated in some time. The cause would likely be elsewhere. I also asked on #salsa because, on October 22, the runner base system was upgraded to Debian 10 from 9. (That is unrelated to the images provided by Salsa CI.) According to the Salsa admins that change should have had no impact. For the time being we are at a loss. Colin Watson provides a workaround below, but we will try to find the real bug first: "If all else fails then setting MAN_NO_LOCALE_WARNING=1 may be a viable workaround." This bug filing follows discussions on debian-devel@lists.d.o and IRC, the relevant parts of which were copied below. There is also a Salsa issue about this [3], but it's probably better to centralize the discussion here. The bug may indeed belong to Salsa CI but issues filed on that website seem less permanent than a bug in the BTS. Please use this bug to comment on the issue going forward. Thank you! Kind regards Felix Lechner [1] https://lintian.pages.debian.net/-/lintian/-/jobs/1098261/artifacts/debian/output/lintian.html [2] https://salsa.debian.org/lintian/lintian/-/blob/master/checks/documentation/manual.pm#L279-281 [3] https://salsa.debian.org/salsa-ci-team/pipeline/-/issues/182 *** Hello there! My Salsa CI pipeline is blowing up in the lintian step, with lots of warnings of the form: "W: notcurses-bin: groff-message usr/share/man/man1/notcurses-demo.1.gz can't set the locale; make sure $LC_* and $LANG are correct" This is printed for each man page I package. An example run is here: https://salsa.debian.org/debian/notcurses/-/jobs/1107065 The only reference I could find was https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606933, which didn't seem relevant. Is this due to having supra-ascii UTF8 characters in my man pages? Is there anything I can do to work around this? I tried exporting LANG to a UTF-8 locale in my salsa variables section, but that didn't help. I'm using pandoc to generate my man pages, and it happily accepts UTF-8, but I can see a case for restricting them to ASCII. Thanks! -- nick black -=- https://www.nick-black.com * * * Hi Nick, On Sun, Oct 25, 2020 at 6:23 PM Nick Black wrote: > > Is this due to having supra-ascii UTF8 characters in my man > pages? It's not a problem with your package. Lintian's own pipeline is likewise affected, even though our test suite completes fine in an unstable chroot. The issue is being tracked here: https://salsa.debian.org/salsa-ci-team/pipeline/-/issues/182 Kind regards Felix Lechner * * * Felix Lechner left as an exercise for the reader: > It's not a problem with your package. Lintian's own pipeline is > likewise affected, even though our test suite completes fine in an > unstable chroot. The issue is being tracked here: > https://salsa.debian.org/salsa-ci-team/pipeline/-/issues/182 Thanks for the quick response, Felix. You say that "[you] will probably start setting $LANG in that part of Lintian." what LANG will you be using? Attempting to set LANG=en_US.UTF-8 in my salsa ci variables resulted in setlocale(3) failing all over the place, presumably due to the locale not having been generated. -- nick black -=- https://www.nick-black.com * * * On Mon, 26 Oct 2020 at 00:35:45 -0400, Nick Black wrote: > Thanks for the quick response, Felix. You say that "[you] will > probably start setting $LANG in that part of Lintian." what LANG > will you be using? Attempting to set LANG=en_US.UTF-8 in my > salsa ci variables resulted in setlocale(3) failing all over the > place, presumably due to the locale not having been generated. C.UTF-8 is available on all Debian systems. It's the standard C/POSIX locale, except that in the C locale the meaning of bytes 0x80-0xFF is undefined, while in C.UTF-8 they are assumed/defined to be part of a character encoded in UTF-8. If you care about portability to non-Debian systems, note that C.UTF-8 is a somewhat popular extension (I think it originated in the Fedora/Red Hat family before it was adopted by Debian and other distros) but is far from universally available. In particular, I'm aware of Arch Linux specifically *not* having it. The glibc maintainers consider the implementation used in e.g. Fedora and Debian to be a hack rather than something they want to maintain forever, but my understanding is that they would be willing to accept a better implementation. en_US.UTF-8 is indeed not portable. Some OSs (Fedora, I think?) always gen
Bug#973308: lintian: Automate importation of valid archive sections via http://
Package: lintian Severity: wishlist X-Debbugs-CC: Andrius Merkys Commit 9904e258 from Andrius Merkys updated the archive sections at the time of writing, but the process should be automated. Lintian does not presently utilize any network resources, and while that may change in the future, it would be the wrong way forward. It makes no sense for Lintian to query the archive for valid sections for every invocation. Ideally, the file from FTP Master that is described below would be packaged and backported as needed. It is probably not updated often. I asked Ganneff about this on #debian-ftp but have not heard back. Maybe it could also be packaged together with other Debian data, such as policy versions, which are being worked on in this bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968154#52 Packaging such data for Debian is also found in other areas, for example in 'dns-root-data'. An alternative would be update ./data in our repo for each new release, but that data remains static for each release. We keep scripts for such updates in ./private. Contributions are welcome. Kind regards Felix Lechner -- Forwarded message - From: Joerg Jaspert Date: Mon, Oct 26, 2020 at 2:03 AM Subject: New archive sections, central location for sections To: d-d-a [DROPPED GPG SIGNATURE] Hi yesterday I created two new sections, one for go (#847520) and one for raku (#816693) (AKA perl6). And while I was on it, I followed the suggestion from #739934 and created a file that contains a dump of all sections known to the archive, together with their short and long descriptions. The initial value of those descriptions has been taken from the packages.debian.org code, so should be something well known and used. That file is in the 822 format, with stanzas with 3 keys each, Section, Description and Longdesc, like - --8<---cut here---start->8--- Section: tex Description: TeX Longdesc: The famous typesetting software and related programs. Section: text Description: Text Processing Longdesc: Utilities to format and print text documents. - --8<---cut here---end--->8--- This file is now available from https://metadata.ftp-master.debian.org/sections.822 and will automatically be kept in sync with the archive. - -- bye, Joerg
lintian_2.99.0~bpo10+1_source.changes ACCEPTED into buster-backports
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 28 Oct 2020 10:09:44 + Source: lintian Architecture: source Version: 2.99.0~bpo10+1 Distribution: buster-backports Urgency: medium Maintainer: Debian Lintian Maintainers Changed-By: Chris Lamb Closes: 972464 Changes: lintian (2.99.0~bpo10+1) buster-backports; urgency=medium . * Rebuild for buster-backports. . lintian (2.99.0) unstable; urgency=medium . [ Chris Lamb ] * Update the declares-possibly-conflicting-debhelper-compat-versions tag as we could be specifying the level in debian/rules or debian/control. (Closes: #972464) . [ Louis-Philippe Véronneau ] * Bump severity of the script-uses-unversioned-python-in-shebang tag and reword the warning message. . [ Felix Lechner ] * Fix prefix detection for single orig tarball components that only have one directory component. . [ Paul Wise ] * Add several spelling corrections and sort the dictionary. Checksums-Sha1: e117296a236163ae60e6cb8a4ec06e01b3d3b728 2390 lintian_2.99.0~bpo10+1.dsc 6c94befddbe88106cc558eae273233fd665ebaf2 1997692 lintian_2.99.0~bpo10+1.tar.xz e73d09aa28230a0181cbc2bce68650d6dd730847 5901 lintian_2.99.0~bpo10+1_source.buildinfo Checksums-Sha256: 4cb5b8d43b05746cbcc168fe7bd89010dc1efbc0242d46b843c8f1bfdae044b1 2390 lintian_2.99.0~bpo10+1.dsc a28772af02e63cf86726bc526533b485c2bd26d34bb9ce8f91fa0a8d8b081d64 1997692 lintian_2.99.0~bpo10+1.tar.xz 5f0c3afb9e57a09d24cba131704b8bd2d448a7cce8dfc6b0a84f9b3687f1cc5f 5901 lintian_2.99.0~bpo10+1_source.buildinfo Files: cce1e0fef16c0f9f48d7858761361948 2390 devel optional lintian_2.99.0~bpo10+1.dsc b36cb4da5c8281ca68bcec348a6de81d 1997692 devel optional lintian_2.99.0~bpo10+1.tar.xz bc9767c072abde9185d2b65a2b5cab85 5901 devel optional lintian_2.99.0~bpo10+1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAl+ZQ54ACgkQHpU+J9Qx Hlio/w//a3Su8Oz7xpmO2DYn5ls7UIK09ZySarOFQcJKxg8NT0HwRCYLDBKRkyGy Ly6ltcrPO7qFbRT3LmUqq5cLMq+ntGJkV1LgCS8mhMpFSeBbVoQQgk7xmoc0lkHo WfjGj8zAPQhnvjhkRru/t143fhm1V9pdr+mGVHSrfjsrWWbkbFwhPE0cEteH/QcY FOSjNx6JxfdSOAyDPcDtSL3tQFh7/aC+karobuCwvJl2pCaQAST+TgbSvpjB68CS E+a2+EmDMI6em/u+tlikwY74PLWNFcNeqLsLLqFQd8GV6eGgUaR/BITIsz44Xn7A aaXFVUze+Zn84tgfDQrB+6PVMNSTQx5GMJp6T500s+64vbbsbkqpB+ioZP0PZwL3 7I1qizbjtyzg0rVbEz5DZBBfW0Ij8L1F/12Q1SrDt8kipzZ5JX0BHE4ND74dWR7d j8hrEs86bKD1aEFlVOzjSsS+ydaPlepmO1Ym3KmXWt9YUf0iyQMaZ6HYdHzth8Q6 IJ5hEQ0rcM+mY/g3vZ7KNaDcquhyZQJ7szvjZgOTplyHEAYFgvWj9ntPla4VTvE+ BaFTAFH/OYBYUp2oHwxPod1g1+4HD2ZVcI8Y22RAodOA9dSTCOqb5tB2l1CHQpfK DSAVZyMZhJbdMfWfOPsopo0GFaRkrjPNh7SID057S0l+9/3Womg= =XfQg -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of lintian_2.99.0~bpo10+1_source.changes
lintian_2.99.0~bpo10+1_source.changes uploaded successfully to localhost along with the files: lintian_2.99.0~bpo10+1.dsc lintian_2.99.0~bpo10+1.tar.xz lintian_2.99.0~bpo10+1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
[Git][lintian/lintian] Pushed new tag 2.99.0_bpo10+1
Chris Lamb pushed new tag 2.99.0_bpo10+1 at lintian / lintian -- View it on GitLab: https://salsa.debian.org/lintian/lintian/-/tree/2.99.0_bpo10+1 You're receiving this email because of your account on salsa.debian.org.
