Bug#994577: lintian: node-* arch:all package should depends on nodejs:any and b-d on nodejs:native
Package: lintian Version: 2.104.0 Severity: wishlist Dear Maintainer, In order to improve cross build of nodejs ecosystem, node-* arch:all package should depends on nodejs:any and b-d on nodejs:native Maybe this test should be restricted to ma: foreign package Bastien
Bug#994576: node-* package should not depends on nodejs except if it include an executable file under /usr/bin
Package: lintian Version: 2.104.0 Severity: wishlist Dear Maintainer, node-* package should not depend on nodejs except if they ship a script under /usr/bin This is the current javascript policy and here lintian could help Bastien
Bug#994571: lintian: please warn javascript package including .node files "*/nodejs/.*\.node$' and ma:foreign
Le ven. 17 sept. 2021 à 21:20, Felix Lechner a écrit : > > Hi, > > On Fri, Sep 17, 2021 at 1:39 PM Bastien Roucariès > wrote: > > > > Package that include "/usr/(?:lib|share)/(?:[^/]+/)?/nodejs/.*\.node$' are > > arch:any package (include node plugin) and thus should be arch:any > > Thank you for this suggestion! > > The files in question are shipped in installable packages that do not > contain the Arch:any designation. (It appears in d/control in the > sources.) The installable architecture in DEBIAN/control is either the > actual port or 'all'. Furthermore, I believe the wildcarded directory > level before 'nodejs' must be a known multi-arch triplet. yes it is > Is it okay > if Lintian instead requires that the multi-arch component of the file > paths found matches the target architecture of the installable package > in which they were shipped? Yes it is > If that is acceptable, Lintian already has checks to constrain the > installation paths for shared libraries, although they may need to be > expanded. (And we have to watch out for -cross packages.) Do you have > candidates for examination besides node-iconv (which I found locally) > that should trigger the condition? I am fixing node-expat-expat that ship under /usr/lib/ > > Moreover in this case ma:foreign is a error (they are plugins) > > That will be addressed at the same time, although I am not yet sure how. Thanks > Kind regards > Felix Lechner
Bug#994571: lintian: please warn javascript package including .node files "*/nodejs/.*\.node$' and ma:foreign
Hi, On Fri, Sep 17, 2021 at 1:39 PM Bastien Roucariès wrote: > > Package that include "/usr/(?:lib|share)/(?:[^/]+/)?/nodejs/.*\.node$' are > arch:any package (include node plugin) and thus should be arch:any Thank you for this suggestion! The files in question are shipped in installable packages that do not contain the Arch:any designation. (It appears in d/control in the sources.) The installable architecture in DEBIAN/control is either the actual port or 'all'. Furthermore, I believe the wildcarded directory level before 'nodejs' must be a known multi-arch triplet. Is it okay if Lintian instead requires that the multi-arch component of the file paths found matches the target architecture of the installable package in which they were shipped? If that is acceptable, Lintian already has checks to constrain the installation paths for shared libraries, although they may need to be expanded. (And we have to watch out for -cross packages.) Do you have candidates for examination besides node-iconv (which I found locally) that should trigger the condition? > Moreover in this case ma:foreign is a error (they are plugins) That will be addressed at the same time, although I am not yet sure how. Kind regards Felix Lechner
Bug#994571: lintian: please warn javascript package including .node files "*/nodejs/.*\.node$' and ma:foreign
Package: lintian Version: 2.104.0 Severity: minor Dear Maintainer, Package that include "/usr/(?:lib|share)/(?:[^/]+/)?/nodejs/.*\.node$' are arch:any package (include node plugin) and thus should be arch:any Moreover in this case ma:foreign is a error (they are plugins) Bastien
Bug#512265: #512265: clarifying the intent of the bug report
Control: retitle -1 lintian: flag upstream tests missing from autopkgtest Hi Andrius, On Fri, Sep 17, 2021 at 9:21 AM Andrius Merkys wrote: > > I doubt this reflects the original intent of this bug > report. I agree with you, and picked yet another title. Please let me know what you think. > * lintian: Warn about unused autopkgtests Upon reflection and refactoring the code [1] I do not think it can be implemented. With Test-Directory set to '.' all files in the source package are candidates, and would produce hints for not being used. > * lintian: Warn about unused build time tests I am not sure how to implement the original request. Your suggestions are welcome. Thank you for figuring out the purpose of this report! Kind regards Felix Lechner [1] https://salsa.debian.org/lintian/lintian/-/commit/7428997ded64b57ccf9a7c5874c683b7b8fd188e#02c42ce39affeca72ca4ed5d708e75a7bc945171_203_207
Processed: Re: Bug#512265: #512265: clarifying the intent of the bug report
Processing control commands: > retitle -1 lintian: flag upstream tests missing from autopkgtest Bug #512265 [lintian] lintian: Warn about unused autopkgtests Changed Bug title to 'lintian: flag upstream tests missing from autopkgtest' from 'lintian: Warn about unused autopkgtests'. -- 512265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=512265 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#512265: #512265: clarifying the intent of the bug report
Hi Felix, I noticed you changed the title of the bug report from "lintian: Warn if a test suite exists but is not run" to "lintian: Warn about unused autopkgtests", and I doubt this reflects the original intent of this bug report. I read the initial Raphael's message as asking to detect test suites not run at the build time (as per the subject of the message). Not run autopkgtests are not less important, but this is a separate topic. I suggest splitting this bug report into two: * lintian: Warn about unused autopkgtests * lintian: Warn about unused build time tests What do you think? Best wishes, Andrius
Processed: Re: Bug#743694: lintian: Downgrade most of privacy-breach* tags from severity: error to pedantic
Processing control commands: > severity -1 normal Bug #743694 [lintian] Downgrade most of privacy-breach* tags from severity: error to pedantic Bug #765503 [lintian] lintian: privacy-breach should be a warning, not an error Severity set to 'normal' from 'important' Severity set to 'normal' from 'important' -- 743694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743694 765503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765503 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#743694: lintian: Downgrade most of privacy-breach* tags from severity: error to pedantic
Control: severity -1 normal
Hi,
On Fri, Sep 10, 2021 at 6:21 AM Daniel Leidert wrote:
>
> I would doubt our FTP masters if they accept packages with
> lintian errors
Actually, they do! The FTP Masters publish the list of tags they do
not accept. [1] The privacy tags are not on it. Lintian offers a
command line option ('--ftp-master-rejects') to check prospective
uploads against the list. For convenience, we also dedicated a page to
it on our website. [2]
When this bug was filed over seven years ago, the potential rejection
of uploads supported an elevated severity. The cited reason holds no
longer. Somewhat sadly, the privacy topic also does not resonate with
contributors. [3][4] As another point of evidence Bug#765503—filed
half a year later and then merged into this report—reached us with a
more appropriate 'normal' severity. [5]
In consideration of the changed circumstances, the present report is
likewise downgraded to 'normal'.
Kind regards
Felix Lechner
[1] https://ftp-master.debian.org/static/lintian.tags
[2] https://lintian.debian.org/autoreject
[3] https://lists.debian.org/debian-vote/2021/09/msg1.html
[4] https://lists.debian.org/debian-vote/2021/09/msg5.html
[5] https://bugs.debian.org/765503
Processed: retitle 971732 to lintian: exempt Eolian output from font-in-non-font-package using new screen facility
Processing commands for cont...@bugs.debian.org: > retitle 971732 lintian: exempt Eolian output from font-in-non-font-package > using new screen facility Bug #971732 [lintian] lintian: Centrally manage overrides for package families Changed Bug title to 'lintian: exempt Eolian output from font-in-non-font-package using new screen facility' from 'lintian: Centrally manage overrides for package families'. > thanks Stopping processing here. Please contact me if you need assistance. -- 971732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971732 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 993613 is important
Processing commands for cont...@bugs.debian.org: > severity 993613 important Bug #993613 [lintian] lintian: Complex regular subexpression recursion limit exceeded in cruft check Severity set to 'important' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 993613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993613 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
lintian_2.106.1~bpo11+1_amd64.changes is NEW
binary:lintian is NEW. binary:lintian is NEW. source:lintian is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will receive an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html or https://ftp-master.debian.org/backports-new.html for *-backports
lintian_2.106.1~bpo10+1_amd64.changes ACCEPTED into buster-backports->backports-policy
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 17 Sep 2021 08:46:28 +0100 Source: lintian Binary: lintian Architecture: source all Version: 2.106.1~bpo10+1 Distribution: buster-backports Urgency: medium Maintainer: Debian Lintian Maintainers Changed-By: Chris Lamb Description: lintian- Debian package checker Closes: 898867 927476 932870 935907 942013 947258 962601 968011 969398 969762 972181 972876 972878 974175 974575 976643 976681 976801 977261 977332 977976 978144 978534 980247 980560 980824 980987 981163 981268 981279 981712 981932 981935 982322 982630 982834 983219 983598 984678 985064 986400 988591 991242 992465 993531 993651 993711 993758 993908 993955 993975 994088 Changes: lintian (2.106.1~bpo10+1) buster-backports; urgency=medium . * Rebuild for buster-backports. . lintian (2.106.1) unstable; urgency=medium . [ Felix Lechner ] * Add Breaks: libconfig-model-dpkg-perl (<< 2.151) to debian/control. This avoids blocking testing migration in the Debci infrastructure. (See: #968000) * Fix an autopkgtest failure on i386 related to the shared-libs-non-pic-i386 test. . lintian (2.106.0) unstable; urgency=medium . * Summary of tag changes: + Added: - file-included-already - source-ships-excluded-file - superfluous-file-pattern + Removed: - copyright-excludes-files-in-native-package - source-includes-file-in-files-excluded - unused-file-paragraph-in-dep5-copyright - wildcard-matches-nothing-in-dep5-copyright . [ Felix Lechner ] * Drop recommendation to implement usr-merge for individual packages. (Closes: #993955) * Use default output width of 80 characters. (Closes: #993908) * Issue homepage-in-binary-package only when there is none in the source. (Closes: #993975) * Implement Files-Included field in DEP-5 copyright files. (Closes: #993758) * Parse path to source .dsc using a more robust method. (Closes: #994088) . [ gregor herrmann ] * Refresh data/fields/perl-provides. . lintian (2.105.0) unstable; urgency=medium . * Summary of tag changes: + Added: - backgrounded-test-command - crossing-screens - duplicate-p3dist-override - elevated-privileges - illegal-variable - misplaced-systemd-tmpfiles - missing-conffile - no-versioned-debhelper-prerequisite - nodejs-missing-version-override - obsolete-vim-addon-manager - pypi-homepage - python-traceback-in-manpage - ruby-interpreter-is-deprecated - rubygem-homepage - rules-require-build-prerequisite - rust-boilerplate - source-contains-editor-backup-file - source-contains-patch-failure-file - source-contains-quilt-control-dir - superficial-tests - systemd-service-in-odd-location - systemd-tmpfile-in-var-run - unexpected-conffile - unknown-conffile-instruction - unmerged-usr - upstream-metadata-field-unknown - wrong-team + Removed: - ancient-standards-version - conffile-is-not-in-package - missing-build-dependency - missing-python-build-dependency - octal-permissions - package-lacks-versioned-build-depends-on-debhelper - package-needs-versioned-debhelper-build-depends - setgid-binary - setuid-binary - setuid-gid-binary - systemd-service-file-outside-lib - systemd-tmpfiles.d-outside-usr-lib . [ Chris Lamb ] * Check for Python tracebacks in manual pages, usually caused by failing help2man calls (and cause reproducibility issues). * Correct confusion between left and right parens that was leading to output such as ")2 errors)". * Bump Standards-Version to 4.6.0.1. . [ Felix Lechner ] * Implement usr-merge; flag files shipped in /bin, /sbin or /lib. * Flag systemd temporary files placed in /var/run. (Closes: #984678) * Do not repeat tag name when annotating hints. (Closes: #969398) * Refuse to read installable control data in national encodings. * Stop shipping modules in system path. (Closes: #968011) - Provide a dedicated, non-public executable to obtain the latest policy version from Lintian data. (See: #978672) * Flag the use of DEB_BUILD_MULTIARCH in some Debian files. (Closes: #983219) * For team-maintained packages, flag names in another team's name space. * Provide a generalized method to grant exemptions to package families (screens). - Exempt ELPA packaging scripts for Emacs modules from executable-in-usr-lib. (Closes: #974175) - Exempt GNAT's read-only .ali files from non-standard-file-perm. (Closes: #986400) * Treat NMU edge cases for non-consecutive-debian-revision. (Closes: #942013) * Recommend the newer php-markdown over libmarkdown-php when embedded. (Closes: #898867) *
Processing of lintian_2.106.1~bpo11+1_amd64.changes
lintian_2.106.1~bpo11+1_amd64.changes uploaded successfully to localhost along with the files: lintian_2.106.1~bpo11+1.dsc lintian_2.106.1~bpo11+1.tar.xz lintian_2.106.1~bpo11+1_all.deb lintian_2.106.1~bpo11+1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
[Git][lintian/lintian] Pushed new tag 2.106.1_bpo11+1
Chris Lamb pushed new tag 2.106.1_bpo11+1 at lintian / lintian -- View it on GitLab: https://salsa.debian.org/lintian/lintian/-/tree/2.106.1_bpo11+1 You're receiving this email because of your account on salsa.debian.org.
Processing of lintian_2.106.1~bpo10+1_amd64.changes
lintian_2.106.1~bpo10+1_amd64.changes uploaded successfully to localhost along with the files: lintian_2.106.1~bpo10+1.dsc lintian_2.106.1~bpo10+1.tar.xz lintian_2.106.1~bpo10+1_all.deb lintian_2.106.1~bpo10+1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
[Git][lintian/lintian] Pushed new tag 2.106.1_bpo10+1
Chris Lamb pushed new tag 2.106.1_bpo10+1 at lintian / lintian -- View it on GitLab: https://salsa.debian.org/lintian/lintian/-/tree/2.106.1_bpo10+1 You're receiving this email because of your account on salsa.debian.org.
