Bug#843662: marked as done (lintian.d.o: Missing visual clue for arch tags)
Your message dated Mon, 28 Jun 2021 16:54:57 -0700 with message-id and subject line Re: lintian.d.o: Missing visual clue for arch tags has caused the Debian Bug report #843662, regarding lintian.d.o: Missing visual clue for arch tags 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 ow...@bugs.debian.org immediately.) -- 843662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843662 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lintian Version: 2.5.49 Missing manpages are reported twice in some cases: https://lintian.debian.org/tags/binary-without-manpage.html E.g. for 0install-core, 389-dsgw, aapt, abw2epub and many more. --- End Message --- --- Begin Message --- Hi, > Missing manpages are reported twice in some cases: The new lintian.d.o uses a PostgreSQL backend and shows only hints for a particular port. (Hints are tag names plus identifying context.) We currently generate runs only for 'amd64'. [1] The website's browser interface may eventually offer a selection, if we generate hints for other ports in the future. At this point, 'arm64' would be the most likely candidate. We do not currently aggregate results across ports as described in earlier comments in this bug. That can be seen very clearly here [2] but we may relax that at some point for overview pages if flipping through multiple ports makes those pages too hard to read (overview pages for single tags, for example). At that point, all hints on those pages would probably show in which ports they were found. That would allow a reader to ascertain immediately whether a tag occurred in the wild—without having to flip through ports. If you are okay with it, I am now closing this bug. Thanks! Kind regards Felix Lechner [1] https://salsa.debian.org/lintian/detagtive/-/blob/master/node.js/routers/sources.js#L91 [2] https://salsa.debian.org/lintian/detagtive/-/blob/master/node.js/routers/tags.js#L129-142--- End Message ---
[Git][lintian/lintian][master] Fix a test that did not run locally due to a conflict with dh-buildinfo.
Felix Lechner pushed to branch master at lintian / lintian Commits: 62a19dca by Felix Lechner at 2021-06-28T16:26:14-07:00 Fix a test that did not run locally due to a conflict with dh-buildinfo. The output format for many tags in the check debian/rules changed slightly in commit 1c8fee7c. Gbp-Dch: ignore - - - - - 1 changed file: - t/recipes/checks/debian/rules/rules-including-deprecated-makefiles/eval/tags Changes: = t/recipes/checks/debian/rules/rules-including-deprecated-makefiles/eval/tags = @@ -1 +1 @@ -rules-including-deprecated-makefiles (source): debian-rules-uses-deprecated-makefile line 4 /usr/share/cdbs/1/rules/simple-patchsys.mk +rules-including-deprecated-makefiles (source): debian-rules-uses-deprecated-makefile (line 4) /usr/share/cdbs/1/rules/simple-patchsys.mk View it on GitLab: https://salsa.debian.org/lintian/lintian/-/commit/62a19dcaa9b0cb8353b77639251827b757376d9a -- View it on GitLab: https://salsa.debian.org/lintian/lintian/-/commit/62a19dcaa9b0cb8353b77639251827b757376d9a You're receiving this email because of your account on salsa.debian.org.
Processed: Bug#986400 marked as pending in lintian
Processing control commands: > tag -1 pending Bug #986400 [lintian] lintian: false positive about permissions for read-only GNAT .ali files Added tag(s) pending. -- 986400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986400 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#971732: lintian: font-in-non-font-package triggers on non-font files
Hi Ross, On Tue, Oct 6, 2020 at 7:28 PM Ross Vandegrift wrote: > > I think it's > better for me to add overrides for now. Lintian gained a facility recently [1] that makes granting such extensions a breeze. The goal is to accommodate toolchains or upstream package sets that are out of Debian's control, and hence hard to fix. Do you have a way to identify the class of packages affected? For an example related to Emacs, please see here. [2] You can simply respond to this bug if you would like to explore a solution for Eolian. Otherwise, please feel free to close this bug. Thank you! Kind regards Felix Lechner [1] https://salsa.debian.org/lintian/lintian/-/commit/8c3d587559cfbdf5dd41e9ba1f66c9ab52de577e [2] https://salsa.debian.org/lintian/lintian/-/commit/24c509ee83ab2a1530a52ab3875c57ab99ad2085
Bug#986369: marked as done (lintian.d.o: out-of-date reports)
Your message dated Mon, 28 Jun 2021 14:53:49 -0700 with message-id and subject line Re: Bug#986369: lintian.d.o: out-of-date reports has caused the Debian Bug report #986369, regarding lintian.d.o: out-of-date reports 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 ow...@bugs.debian.org immediately.) -- 986369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986369 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lintian Version: 2.104.0 Severity: normal Hello, It seems the lintian.d.o pages are not up to date, for instance: https://lintian.debian.org/sources/orca.html version 3.38.0-1 was replaced by version 3.38.0-2 since novembre 1st. As a consequence, the lintian columns of the QA page is little useful. With best regards, Samuel -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'proposed-updates'), (500, 'oldoldstable'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.11.0 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lintian depends on: ii binutils2.35.2-2 ii bzip2 1.0.8-4 ii diffstat1.64-1 ii dpkg1.20.7.1 ii dpkg-dev1.20.7.1 ii file1:5.39-3 ii gettext 0.21-4 ii gpg 2.2.27-1 ii intltool-debian 0.35.0+20060710.5 ii libapt-pkg-perl 0.1.39 ii libarchive-zip-perl 1.68-1 ii libcapture-tiny-perl0.48-1 ii libclass-xsaccessor-perl1.19-3+b7 ii libclone-perl 0.45-1+b1 ii libconfig-tiny-perl 2.26-1 ii libcpanel-json-xs-perl 4.25-1+b1 ii libdata-dpath-perl 0.58-1 ii libdata-validate-domain-perl0.10-1.1 ii libdevel-size-perl 0.83-1+b2 ii libdpkg-perl1.20.7.1 ii libemail-address-xs-perl1.04-1+b3 ii libfile-basedir-perl0.08-1 ii libfile-find-rule-perl 0.34-1 ii libfont-ttf-perl1.06-1.1 ii libhtml-html5-entities-perl 0.004-1.1 ii libipc-run3-perl0.048-2 ii libjson-maybexs-perl1.004003-1 ii liblist-compare-perl0.55-1 ii liblist-moreutils-perl 0.430-2 ii liblist-utilsby-perl0.11-1 ii libmoo-perl 2.004004-1 ii libmoox-aliases-perl0.001006-1.1 ii libnamespace-clean-perl 0.27-1 ii libpath-tiny-perl 0.118-1 ii libperlio-gzip-perl 0.19-1+b7 ii libproc-processtable-perl 0.59-2+b1 ii libsereal-decoder-perl 4.018+ds-1+b1 ii libsereal-encoder-perl 4.018+ds-1+b1 ii libtext-glob-perl 0.11-1 ii libtext-levenshteinxs-perl 0.03-4+b8 ii libtext-markdown-discount-perl 0.12-1+b1 ii libtext-xslate-perl 3.5.8-1+b1 ii libtime-duration-perl 1.21-1 ii libtime-moment-perl 0.44-1+b3 ii libtimedate-perl2.3300-2 ii libtry-tiny-perl0.30-1 ii libtype-tiny-perl 1.012001-2 ii libunicode-utf8-perl0.62-1+b2 ii liburi-perl 5.08-1 ii libxml-libxml-perl 2.0134+dfsg-2+b1 ii libyaml-libyaml-perl0.82+repack-1+b1 ii lzip1.22-3 ii lzop1.04-2 ii man-db 2.9.4-2 ii patchutils 0.4.2-1 ii perl [libdigest-sha-perl] 5.32.1-3 ii t1utils 1.41-4 ii unzip 6.0-26 ii xz-utils5.2.5-2 lintian recommends no packages. Versions of packages lintian suggests: pn binutils-multiarch ii libtext-template-perl 1.59-1 -- no debconf information -- Samuel je déteste import parce que lorsque tu fais du python et que tu oublies le #!/bin/env python et que tu mets le fichier exécutable import est exécuté -+- #ens-mim - pourquoi mon script python chang
Bug#755405: marked as done (lintian.d.o: Please add information about processing speed)
Your message dated Mon, 28 Jun 2021 14:39:28 -0700 with message-id and subject line Re: lintian.d.o: Please add information about processing speed has caused the Debian Bug report #755405, regarding lintian.d.o: Please add information about processing speed 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 ow...@bugs.debian.org immediately.) -- 755405: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755405 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lintian Version: 2.5.25 Severity: important Could be possible to track day to day change of Rescheduled groups: 19455 (-53), both absolute and relative change ? It will help to see long term speed variation of lintian. Could be possible to get statistic of lintian run publically available ? Bastien --- End Message --- --- Begin Message --- Hi, > Could be possible to get statistic of lintian run publically available? The new lintian.d.o now publishes the time it took to generate each individual run. Unfortunately, Lintian no longer runs in batch mode across the archive, though, so we cannot provide the aggregate statistics requested herein. We may, at a later time, provide appropriate performance measures for the automated queue. Closing this bug. Thank you! Kind regards, Felix Lechner--- End Message ---
Bug#863068: lintian: Merge pages from same contributor (but different email) into one page
Hi, > lintian.d.o generates a maintainer > page per unique email and not per contributor. The new lintian.d.o groups the packages listed in a maintainer overview by the email "phrase" as defined in RFC 5322. I believe it accomplished your goals with this bug. A maintainer now merely has to ensure that their name (but not the email) matches across packages. Does that resolve your bug, please? There are some fine points around people with identical names, and the 'carnivore' package may ultimately provide a better solution, but I haven't gotten that far yet. > We can do this by exporting the following data from > contributors.debian.org Unfortunately, I do not believe my automated environment—large parts of which are not yet hosted on DSA equipment—can currently obtain access via an SSO certificate. I am also not comfortable handling access-controlled information with a view to publicize it, when some consider the same private or otherwise sensitive. Please feel free to close this bug. Thanks! Kind regards Felix Lechner
Bug#958763: lintian: Please allow language extensions in packages for specific teams
Hi, On Fri, Apr 24, 2020 at 11:12 PM Andreas Tille wrote: > > This should happen for the teams Lintian gained a facility recently [1] that makes granting such extensions a breeze. The goal is to accommodate toolchains or upstream package sets that are out of Debian's control, and hence hard to fix. Unfortunately your desired method of selelction—by Debian team—does not qualify as a meaningful indicator for being outside your control. Do you have another way to identify the class of packages affected? For an example related to Emacs, please see here. [2] Also, please allow me to point out the JSON facilities on Lintian's new website. [3] Several other teams love it. Thank you! Kind regards Felix Lechner [1] https://salsa.debian.org/lintian/lintian/-/commit/8c3d587559cfbdf5dd41e9ba1f66c9ab52de577e [2] https://salsa.debian.org/lintian/lintian/-/commit/24c509ee83ab2a1530a52ab3875c57ab99ad2085 [3] https://lintian.debian.org/query
Bug#973333: marked as done (lintian.d.o: please add a symlink/redirect to the most recent version)
Your message dated Mon, 28 Jun 2021 08:21:34 -0700 with message-id and subject line Re: Bug#97: lintian.d.o: please add a symlink/redirect to the most recent version has caused the Debian Bug report #97, regarding lintian.d.o: please add a symlink/redirect to the most recent version 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 ow...@bugs.debian.org immediately.) -- 97: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=97 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- 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 --- End Message --- --- Begin Message --- Hi Paul, On Wed, Oct 28, 2020 at 7:39 PM Paul Wise wrote: > > there is an extra click from the source package page to the source > package version page containing the actual lintian results. I believe the issue is no longer present on the new dynamic web page. You should immediately see Lintian hints from a preferred package version, which is presently the most recent run for that source. [1] Kind regards, Felix Lechner [1] https://salsa.debian.org/lintian/detagtive/-/blob/master/node.js/routers/sources.js#L244--- End Message ---
Processed: Bug#974175 marked as pending in lintian
Processing control commands: > tag -1 pending Bug #974175 [lintian] Exempt dh_elpa-related packages from executable-in-usr-lib Added tag(s) pending. -- 974175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974175 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
