[Git][lintian/lintian][master] bitbucket.org no more supports Mercurial

2023-01-16 Thread Axel Beckert (@abe)
Axel Beckert pushed to branch master at lintian / lintian Commits: 78d9ec4f by Axel Beckert at 2023-01-17T08:06:55+01:00 bitbucket.org no more supports Mercurial https://bitbucket.org/blog/sunsetting-mercurial-support-in-bitbucket - - - - - 1 changed file: - data/fields/vcs-hosters

lintian_2.116.0_source.changes ACCEPTED into unstable

2023-01-16 Thread Debian FTP Masters
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 17 Jan 2023 01:37:56 +0100 Source: lintian Architecture: source Version: 2.116.0 Distribution: unstable Urgency: medium Maintainer: Debian Lintian Maintainers

Bug#932634: marked as done (lintian: false-positive embedded-library libyaml due to matching string (defined in data/binaries/embedded-libs) with package rust-yaml-rust)

2023-01-16 Thread Debian Bug Tracking System
Your message dated Tue, 17 Jan 2023 07:00:29 + with message-id and subject line Bug#932634: fixed in lintian 2.116.0 has caused the Debian Bug report #932634, regarding lintian: false-positive embedded-library libyaml due to matching string (defined in data/binaries/embedded-libs) with

Bug#1027399: marked as done (lintian: misspelled spelling corrections)

2023-01-16 Thread Debian Bug Tracking System
Your message dated Tue, 17 Jan 2023 07:00:30 + with message-id and subject line Bug#1027399: fixed in lintian 2.116.0 has caused the Debian Bug report #1027399, regarding lintian: misspelled spelling corrections to be marked as done. This means that you claim that the problem has been dealt

Bug#1028975: marked as done (allegedly, tar warnings are not errors)

2023-01-16 Thread Debian Bug Tracking System
Your message dated Tue, 17 Jan 2023 07:00:30 + with message-id and subject line Bug#1028975: fixed in lintian 2.116.0 has caused the Debian Bug report #1028975, regarding allegedly, tar warnings are not errors to be marked as done. This means that you claim that the problem has been dealt

Bug#1026920: marked as done (New upstream version of file/libmagic breaks autopkgtest)

2023-01-16 Thread Debian Bug Tracking System
Your message dated Tue, 17 Jan 2023 07:00:30 + with message-id and subject line Bug#1026920: fixed in lintian 2.116.0 has caused the Debian Bug report #1026920, regarding New upstream version of file/libmagic breaks autopkgtest to be marked as done. This means that you claim that the problem

Bug#1025868: marked as done (lintian autopkgtest fails on all but amd64: x86_64-linux-gnu expected build-and-evaluate-test-packages/eval/checks/desktop/gnome/gir/gir/generic.t)

2023-01-16 Thread Debian Bug Tracking System
Your message dated Tue, 17 Jan 2023 07:00:30 + with message-id and subject line Bug#1025868: fixed in lintian 2.116.0 has caused the Debian Bug report #1025868, regarding lintian autopkgtest fails on all but amd64: x86_64-linux-gnu expected

Bug#1028274: marked as done (lintian: Warning in processable […].dsc: Error open (<) on '[…].orig.tar.gz.asc': No such file or directory at /usr/share/perl5/Path/Tiny.pm line 2419.)

2023-01-16 Thread Debian Bug Tracking System
Your message dated Tue, 17 Jan 2023 07:00:30 + with message-id and subject line Bug#1028274: fixed in lintian 2.116.0 has caused the Debian Bug report #1028274, regarding lintian: Warning in processable […].dsc: Error open (<) on '[…].orig.tar.gz.asc': No such file or directory at

Bug#1027323: marked as done (lintian: broken symlink reporting/harness)

2023-01-16 Thread Debian Bug Tracking System
Your message dated Tue, 17 Jan 2023 07:00:30 + with message-id and subject line Bug#1027323: fixed in lintian 2.116.0 has caused the Debian Bug report #1027323, regarding lintian: broken symlink reporting/harness to be marked as done. This means that you claim that the problem has been dealt

Bug#1025436: marked as done (lintian: Silence executable-stack-in-shared-library tag on mips*)

2023-01-16 Thread Debian Bug Tracking System
Your message dated Tue, 17 Jan 2023 07:00:30 + with message-id and subject line Bug#1025436: fixed in lintian 2.116.0 has caused the Debian Bug report #1025436, regarding lintian: Silence executable-stack-in-shared-library tag on mips* to be marked as done. This means that you claim that the

Bug#1025644: marked as done (lintian: should not have the update-debian-copyright tag at all)

2023-01-16 Thread Debian Bug Tracking System
Your message dated Tue, 17 Jan 2023 07:00:30 + with message-id and subject line Bug#1025644: fixed in lintian 2.116.0 has caused the Debian Bug report #1025644, regarding lintian: should not have the update-debian-copyright tag at all to be marked as done. This means that you claim that the

Bug#1025164: marked as done (lintian: missing-prerequisite-for-pyproject-backend tag needs to check Build-Depends-Indep too)

2023-01-16 Thread Debian Bug Tracking System
Your message dated Tue, 17 Jan 2023 07:00:30 + with message-id and subject line Bug#1025164: fixed in lintian 2.116.0 has caused the Debian Bug report #1025164, regarding lintian: missing-prerequisite-for-pyproject-backend tag needs to check Build-Depends-Indep too to be marked as done.

Bug#1024361: marked as done (lintian: complains about bpo version when package built with salsa-CI/pipeline (+salsaci))

2023-01-16 Thread Debian Bug Tracking System
Your message dated Tue, 17 Jan 2023 07:00:30 + with message-id and subject line Bug#1024361: fixed in lintian 2.116.0 has caused the Debian Bug report #1024361, regarding lintian: complains about bpo version when package built with salsa-CI/pipeline (+salsaci) to be marked as done. This

Bug#1016147: marked as done (lintian: false positive missing-build-dependency-for-dh-addon python3 when using dh-sequence-python3)

2023-01-16 Thread Debian Bug Tracking System
Your message dated Tue, 17 Jan 2023 07:00:29 + with message-id and subject line Bug#1016147: fixed in lintian 2.116.0 has caused the Debian Bug report #1016147, regarding lintian: false positive missing-build-dependency-for-dh-addon python3 when using dh-sequence-python3 to be marked as

Bug#1014956: marked as done (More understandable text for inconsistent-appstream-metadata-license tag)

2023-01-16 Thread Debian Bug Tracking System
Your message dated Tue, 17 Jan 2023 07:00:29 + with message-id and subject line Bug#1014956: fixed in lintian 2.116.0 has caused the Debian Bug report #1014956, regarding More understandable text for inconsistent-appstream-metadata-license tag to be marked as done. This means that you claim

Bug#1019851: marked as done (lintian: init.d-script-needs-depends-on-lsb-base is obsolete + wrong)

2023-01-16 Thread Debian Bug Tracking System
Your message dated Tue, 17 Jan 2023 07:00:30 + with message-id and subject line Bug#1019851: fixed in lintian 2.116.0 has caused the Debian Bug report #1019851, regarding lintian: init.d-script-needs-depends-on-lsb-base is obsolete + wrong to be marked as done. This means that you claim that

Bug#1019541: marked as done (lintian: New spelling corrections should be automatically checked against an american and a british english dictionary)

2023-01-16 Thread Debian Bug Tracking System
Your message dated Tue, 17 Jan 2023 07:00:29 + with message-id and subject line Bug#1019541: fixed in lintian 2.116.0 has caused the Debian Bug report #1019541, regarding lintian: New spelling corrections should be automatically checked against an american and a british english dictionary to

Bug#1019235: marked as done (lintian: 'licence' is not a misspelling)

2023-01-16 Thread Debian Bug Tracking System
Your message dated Tue, 17 Jan 2023 07:00:29 + with message-id and subject line Bug#1019235: fixed in lintian 2.116.0 has caused the Debian Bug report #1019235, regarding lintian: 'licence' is not a misspelling to be marked as done. This means that you claim that the problem has been dealt

Bug#1013314: marked as done (lintian: REUSE license text should suppress very-long-line-length-in-source-file)

2023-01-16 Thread Debian Bug Tracking System
Your message dated Tue, 17 Jan 2023 07:00:29 + with message-id and subject line Bug#1013314: fixed in lintian 2.116.0 has caused the Debian Bug report #1013314, regarding lintian: REUSE license text should suppress very-long-line-length-in-source-file to be marked as done. This means that

Bug#1002053: marked as done (lintian: false positive inconsistent-appstream-metadata-license (gpl-2.0+ != gpl-2+))

2023-01-16 Thread Debian Bug Tracking System
Your message dated Tue, 17 Jan 2023 07:00:29 + with message-id and subject line Bug#1002053: fixed in lintian 2.116.0 has caused the Debian Bug report #1002053, regarding lintian: false positive inconsistent-appstream-metadata-license (gpl-2.0+ != gpl-2+) to be marked as done. This means

Bug#1006631: marked as done (lintian: Recommend moving D-Bus policy files from /etc to /usr)

2023-01-16 Thread Debian Bug Tracking System
Your message dated Tue, 17 Jan 2023 07:00:29 + with message-id and subject line Bug#1006631: fixed in lintian 2.116.0 has caused the Debian Bug report #1006631, regarding lintian: Recommend moving D-Bus policy files from /etc to /usr to be marked as done. This means that you claim that the

Bug#1014175: marked as done (warning: cannot run debian/readme check on package binary:postgresql-15_15~beta2-2+salsaci_amd64)

2023-01-16 Thread Debian Bug Tracking System
Your message dated Tue, 17 Jan 2023 07:00:29 + with message-id and subject line Bug#1014175: fixed in lintian 2.116.0 has caused the Debian Bug report #1014175, regarding warning: cannot run debian/readme check on package binary:postgresql-15_15~beta2-2+salsaci_amd64 to be marked as done.

Bug#1029055: Debian Expat and SPDX MIT License Text

2023-01-16 Thread Soren Stoutner
SPDX itself might have an answer that is satisfactory: "The original replaceable text appears on the SPDX License List webpage in red text." "Omittable text appears on the SPDX License List webpage in blue text."

Bug#1029055: Debian Expat and SPDX MIT License Text

2023-01-16 Thread Axel Beckert
Hi, Soren Stoutner wrote: > There appears to be some question of opinion Not opinion. Just the point of what the meaning of _text colors_ *rollingeyes* in a license do mean. I just ignored them and then those two licenses differ. > as to if the Debian MIT (Expat) License is > the same as the

Processing of lintian_2.116.0_source.changes

2023-01-16 Thread Debian FTP Masters
lintian_2.116.0_source.changes uploaded successfully to localhost along with the files: lintian_2.116.0.dsc lintian_2.116.0.tar.xz lintian_2.116.0_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#1029055: Debian Expat and SPDX MIT License Text

2023-01-16 Thread Soren Stoutner
There appears to be some question of opinion as to if the Debian MIT (Expat) License is the same as the SPDX MIT License. https://www.debian.org/legal/licenses/mit[1] https://spdx.org/licenses/MIT.html[2] Can somebody at Debian Legal please comment? -- Soren Stoutner so...@stoutner.com

[Git][lintian/lintian] Pushed new tag 2.116.0

2023-01-16 Thread Axel Beckert (@abe)
Axel Beckert pushed new tag 2.116.0 at lintian / lintian -- View it on GitLab: https://salsa.debian.org/lintian/lintian/-/tree/2.116.0 You're receiving this email because of your account on salsa.debian.org.

Bug#1029055: MIT License Text

2023-01-16 Thread Axel Beckert
Axel Beckert wrote: > As mentioned before exactly that exception is the reason why I think > that these two license texts are not the same. I though see no > explanation what the meaning of the colors on the SPDX website is. > Until that is clarified, for me, the two texts clearly differ for me.

Processed: Re: Bug#1029055: MIT License Text

2023-01-16 Thread Debian Bug Tracking System
Processing control commands: > tag -1 + moreinfo Bug #1029055 [lintian] lintian: Lintian does not recognize the AppStream's metainfo.xml MIT license is the same as Debian's Expat license Added tag(s) moreinfo. -- 1029055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029055 Debian Bug

Bug#1029055: MIT License Text

2023-01-16 Thread Axel Beckert
Control: tag -1 + moreinfo Hi, thanks for the separate bug report. Soren Stoutner wrote: > I just noticed that AppStream specifies that their licenses use the text > listed by SPDX. > > As the text of the MIT License at https://spdx.org/licenses/MIT.html[1] is > the same as the > Debian MIT

Bug#1029055: MIT License Text

2023-01-16 Thread Soren Stoutner
I just noticed that AppStream specifies that their licenses use the text listed by SPDX. As the text of the MIT License at https://spdx.org/licenses/MIT.html[1] is the same as the Debian MIT License (Expat) at https://www.debian.org/legal/licenses/mit (except for the instructions in blue),

Bug#1002053: lintian: false positive inconsistent-appstream-metadata-license (gpl-2.0+ != gpl-2+)

2023-01-16 Thread Soren Stoutner
I created a new bug report to discuss this issue as the root cause ends up being different than what was originally reported here. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029055[1] -- Soren Stoutner so...@stoutner.com [1]

Bug#1029055: lintian: Lintian does not recognize the AppStream's metainfo.xml MIT license is the same as Debian's Expat license

2023-01-16 Thread Soren Stoutner
Package: lintian Version: 2.115.3 Severity: wishlist Debian has recently started requesting that graphical programs install AppStream metainfo.xml files. https://appstream.debian.org/sid/main/issues/electrum.html The AppStream specification has a very restricted listed of possible licenses

[Git][lintian/lintian][master] 3 commits: debian/control: Bump Standards-Version in Description to 4.6.2

2023-01-16 Thread Axel Beckert (@abe)
Axel Beckert pushed to branch master at lintian / lintian Commits: 861bcc1e by Axel Beckert at 2023-01-17T01:53:09+01:00 debian/control: Bump Standards-Version in Description to 4.6.2 Gbp-Dch: Ignore - - - - - abf85a66 by Axel Beckert at 2023-01-17T02:15:44+01:00 run-private-scripts.t: Do

Re: New lintian release?

2023-01-16 Thread Axel Beckert
Hi again, Axel Beckert wrote: > Close to doing an upload. So let's check: > > > > 1. it seems "t/scripts/run-private-scripts.t" is broken again? > […] > > That error seems to be a real error when calling > > private/generate-tag-summary. So the error is not in > > t/scripts/run-private-scripts.t

Bug#1029053: lintian: Should report Vcs-Browser fields pointing to Salsa/Gitlab/Github and ending in .git

2023-01-16 Thread Axel Beckert
Package: lintian Version: 2.115.4~git Severity: wishlist In https://salsa.debian.org/lintian/lintian/-/merge_requests/390#note_367701 Willian Desportes (X-Debbugs-Cc'ed) suggested to implement the same as Lintian MR !390 (GitHub and GitLab URLs shouldn't end with .git) also for Vcs-Browser. With

Processed: Bug#1013314 marked as pending in lintian

2023-01-16 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1013314 [lintian] lintian: REUSE license text should suppress very-long-line-length-in-source-file Added tag(s) pending. -- 1013314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013314 Debian Bug Tracking System Contact

Bug#1025436: Bug#1022787: Bug#1025436: Bug#1022787: libc6-dev: Lintian warns that all mips*el executables have executable stack

2023-01-16 Thread Axel Beckert
Hi, Axel Beckert wrote: > Aurelien Jarno wrote: > > Given we got no decision from the MIPS porters before the toolchain > > freeze, we'll have to live with the executable stack on mips*el for > > bookworm. > > > > Therefore I believe it's a good idea to disable that tag on mips*el on > > the

Processed: Bug#1025436 marked as pending in lintian

2023-01-16 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1025436 [lintian] lintian: Silence executable-stack-in-shared-library tag on mips* Added tag(s) pending. -- 1025436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025436 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1025436: Bug#1022787: libc6-dev: Lintian warns that all mips*el executables have executable stack

2023-01-16 Thread Axel Beckert
Hi Aurelien, your reply is just in time! Because about five minutes ago, I started to continue working on Lintian for this evening. The plan: Making the long overdue upload as I fixed the last part of arm64 autopkgtest failures last night. :-) Aurelien Jarno wrote: > Given we got no decision

Bug#1025436: Bug#1022787: libc6-dev: Lintian warns that all mips*el executables have executable stack

2023-01-16 Thread Aurelien Jarno
Hi, On 2023-01-16 13:26, Guillem Jover wrote: > Hi! > > On Mon, 2023-01-16 at 12:47:23 +0100, Axel Beckert wrote: > > Aurelien Jarno wrote: > > > On 2022-10-26 22:09, Aurelien Jarno wrote: > > > > Note that the other official architecture still have a kernel > > > > compatibility set to 3.2, so

Bug#1025868: lintian autopkgtest fails on all but amd64: x86_64-linux-gnu expected build-and-evaluate-test-packages/eval/checks/desktop/gnome/gir/gir/generic.t

2023-01-16 Thread Paul Gevers
Hi Axel, On 15-01-2023 23:07, Axel Beckert wrote: TL;DR: [...] You're awesome. And indeed, what a shame of your time. Paul OpenPGP_signature Description: OpenPGP digital signature

Bug#1002053: lintian: false positive inconsistent-appstream-metadata-license (gpl-2.0+ != gpl-2+)

2023-01-16 Thread Axel Beckert
Hi Soren, Soren Stoutner wrote: > On Sunday, January 15, 2023 5:17:10 PM MST Axel Beckert wrote: > > > Debian, of course, prefers the Expat name as it is more precise. > > > > According to > > https://wiki.debian.org/Proposals/CopyrightFormat#Differences_between_DEP5_a > > nd_SPDX SPDX does not

Bug#1002053: lintian: false positive inconsistent-appstream-metadata-license (gpl-2.0+ != gpl-2+)

2023-01-16 Thread Soren Stoutner
On Sunday, January 15, 2023 5:17:10 PM MST Axel Beckert wrote: > > Debian, of course, prefers the Expat name as it is more precise. > > According to > https://wiki.debian.org/Proposals/CopyrightFormat#Differences_between_DEP5_a > nd_SPDX SPDX does not have the Expat license. They do have though

Processed: Re: Bug#1027399: lintian: misspelled spelling corrections

2023-01-16 Thread Debian Bug Tracking System
Processing control commands: > tag -1 + pending Bug #1027399 [lintian] lintian: misspelled spelling corrections Ignoring request to alter tags of bug #1027399 to the same tags previously set -- 1027399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027399 Debian Bug Tracking System Contact

Bug#1027399: lintian: misspelled spelling corrections

2023-01-16 Thread Axel Beckert
Control: tag -1 + pending Hi Jakub, Axel Beckert wrote: > Jakub Wilk wrote: > > I heard you like spell-checking, so I ran your spell-checker on your > > spell-checker: > > > >$ grep '^[^#]' /usr/share/lintian/data/spelling/corrections | cut -d '|' > > -f3 | sort -u | spellintian | grep -vF

Processed: Bug#1027399 marked as pending in lintian

2023-01-16 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1027399 [lintian] lintian: misspelled spelling corrections Added tag(s) pending. -- 1027399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027399 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1025436: Bug#1022787: libc6-dev: Lintian warns that all mips*el executables have executable stack

2023-01-16 Thread Guillem Jover
Hi! On Mon, 2023-01-16 at 12:47:23 +0100, Axel Beckert wrote: > Aurelien Jarno wrote: > > On 2022-10-26 22:09, Aurelien Jarno wrote: > > > Note that the other official architecture still have a kernel > > > compatibility set to 3.2, so that will make a difference between > > > architectures.

Bug#1025436: Bug#1022787: libc6-dev: Lintian warns that all mips*el executables have executable stack

2023-01-16 Thread Axel Beckert
Hi, writing this with my Lintian maintainer hat on. Nearly full quote due to Cc'ing another bug report and bug reporter: Aurelien Jarno wrote: > On 2022-10-26 22:09, Aurelien Jarno wrote: > > control: tag -1 + moreinfo > > > > On 2022-10-25 21:07, Simon McVittie wrote: > > > Package: libc6-dev

Processed: Re: Bug#1027323: lintian: broken symlink reporting/harness

2023-01-16 Thread Debian Bug Tracking System
Processing control commands: > tag -1 + confirmed pending Bug #1027323 [src:lintian] lintian: broken symlink reporting/harness Added tag(s) pending and confirmed. -- 1027323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027323 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1027323: lintian: broken symlink reporting/harness

2023-01-16 Thread Axel Beckert
Control: tag -1 + confirmed pending Hi Jakub, Jakub Wilk wrote: > $ file lintian-2.115.3/reporting/harness > lintian-2.115.3/reporting/harness: broken symbolic link to ../frontend/dplint Good find, thanks! Regards, Axel -- ,''`. | Axel Beckert ,

Processed: Re: Bug#1027399: lintian: misspelled spelling corrections

2023-01-16 Thread Debian Bug Tracking System
Processing control commands: > tag -1 + confirmed Bug #1027399 [lintian] lintian: misspelled spelling corrections Added tag(s) confirmed. -- 1027399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027399 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1027399: lintian: misspelled spelling corrections

2023-01-16 Thread Axel Beckert
Control: tag -1 + confirmed Hi Jakub, Jakub Wilk wrote: > I heard you like spell-checking, so I ran your spell-checker on your > spell-checker: > >$ grep '^[^#]' /usr/share/lintian/data/spelling/corrections | cut -d '|' > -f3 | sort -u | spellintian | grep -vF '(duplicate word)' >

Re: Understanding and handling a "groff-message 734" failure

2023-01-16 Thread c . buhtz
Hi, I was pointed to the solution in the German Debian-Forum [1]. Please take this as a feature request. "groff-message" doesn't help to know which commandline tool generated that error? Depending on your docu [2] it seems to be "man" itself and not a tool called "groff" or something else.

[Git][lintian/lintian][master] Fix false positive for license-problem-php-license for pear.php.net source code

2023-01-16 Thread Axel Beckert (@abe)
Axel Beckert pushed to branch master at lintian / lintian Commits: 53f5b4d2 by William Desportes at 2023-01-16T02:54:14+00:00 Fix false positive for license-problem-php-license for pear.php.net source code - - - - - 2 changed files: - lib/Lintian/Check/Cruft.pm -