Processed: Bug#993908 marked as pending in lintian

2021-09-07 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #993908 [lintian] lintian: piping the output thru a pager generates single-word description Added tag(s) pending. -- 993908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993908 Debian Bug Tracking System Contact ow...@bugs.debian.org with p

Bug#993908: lintian: piping the output thru a pager generates single-word description

2021-09-07 Thread Sandro Tosi
Package: lintian Version: 2.105.0 Severity: normal X-Debbugs-Cc: mo...@debian.org Hello, i just upgraded from 2.104.0 and when piping the ouput thru a pager, i get: W: pytest source: no-nmu-in-changelog N: N: When N: you N: NMU N: a N: package, N: that N: fact N: should N: be N:

Bug#992465: marked as done ([lintian] systemd-service-file-outside-lib should not flag /usr/lib/systemd/system/)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#992465: fixed in lintian 2.105.0 has caused the Debian Bug report #992465, regarding [lintian] systemd-service-file-outside-lib should not flag /usr/lib/systemd/system/ to be marked as done. This means that y

Bug#984678: marked as done (Please add check for tmpfiles similar to systemd-service-file-pidfile-refers-to-var-run)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#984678: fixed in lintian 2.105.0 has caused the Debian Bug report #984678, regarding Please add check for tmpfiles similar to systemd-service-file-pidfile-refers-to-var-run to be marked as done. This means th

lintian_2.105.0_amd64.changes ACCEPTED into unstable

2021-09-07 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 07 Sep 2021 09:43:56 + Source: lintian Architecture: source Version: 2.105.0 Distribution: unstable Urgency: medium Maintainer: Debian Lintian Maintainers Changed-By: Chris Lamb Closes: 898867 927476 932870

Bug#993531: marked as done (lintian: doesn't know about conffile remove-on-upgrade tag)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#993711: fixed in lintian 2.105.0 has caused the Debian Bug report #993711, regarding lintian: doesn't know about conffile remove-on-upgrade tag to be marked as done. This means that you claim that the problem

Bug#993651: marked as done (lintian: "Profile debian/main references unknown checks" when run from Debian package)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#993651: fixed in lintian 2.105.0 has caused the Debian Bug report #993651, regarding lintian: "Profile debian/main references unknown checks" when run from Debian package to be marked as done. This means that

Bug#993711: marked as done (lintian: Emits conffile-is-not-in-package, non-etc-file-marked-as-conffile and relative-conffile for itself)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#993711: fixed in lintian 2.105.0 has caused the Debian Bug report #993711, regarding lintian: Emits conffile-is-not-in-package, non-etc-file-marked-as-conffile and relative-conffile for itself to be marked as

Bug#993711: marked as done (lintian: Emits conffile-is-not-in-package, non-etc-file-marked-as-conffile and relative-conffile for itself)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#993531: fixed in lintian 2.105.0 has caused the Debian Bug report #993531, regarding lintian: Emits conffile-is-not-in-package, non-etc-file-marked-as-conffile and relative-conffile for itself to be marked as

Bug#993531: marked as done (lintian: doesn't know about conffile remove-on-upgrade tag)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#993531: fixed in lintian 2.105.0 has caused the Debian Bug report #993531, regarding lintian: doesn't know about conffile remove-on-upgrade tag to be marked as done. This means that you claim that the problem

Bug#991242: marked as done (lintian: fpos python3-depends-but-no-python3-helper)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#991242: fixed in lintian 2.105.0 has caused the Debian Bug report #991242, regarding lintian: fpos python3-depends-but-no-python3-helper to be marked as done. This means that you claim that the problem has bee

debian-lint-maint@lists.debian.org

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#988591: fixed in lintian 2.105.0 has caused the Debian Bug report #988591, regarding lintian: please error if Test-Command ends with an & to be marked as done. This means that you claim that the problem has be

Bug#983598: marked as done (lintian: package-installs-apt-sources emitted for packages whose names end in -archive-keyring)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#983598: fixed in lintian 2.105.0 has caused the Debian Bug report #983598, regarding lintian: package-installs-apt-sources emitted for packages whose names end in -archive-keyring to be marked as done. This m

Bug#986400: marked as done (lintian: false positive about permissions for read-only GNAT .ali files)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#986400: fixed in lintian 2.105.0 has caused the Debian Bug report #986400, regarding lintian: false positive about permissions for read-only GNAT .ali files to be marked as done. This means that you claim tha

Bug#983219: marked as done (lintian: warn about incorrect DEB_BUILD_MULTIARCH usage)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#983219: fixed in lintian 2.105.0 has caused the Debian Bug report #983219, regarding lintian: warn about incorrect DEB_BUILD_MULTIARCH usage to be marked as done. This means that you claim that the problem has

Bug#985064: marked as done (lintian: Can't call method "errstr" on an undefined value)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#985064: fixed in lintian 2.105.0 has caused the Debian Bug report #985064, regarding lintian: Can't call method "errstr" on an undefined value to be marked as done. This means that you claim that the problem h

Bug#982834: marked as done (lintian: dh_dkms can also be satisfied by dh-sequence-dkms)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#982834: fixed in lintian 2.105.0 has caused the Debian Bug report #982834, regarding lintian: dh_dkms can also be satisfied by dh-sequence-dkms to be marked as done. This means that you claim that the problem

Bug#982322: marked as done (lintian: data/files/generic-header-files: add utils\.h)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#982322: fixed in lintian 2.105.0 has caused the Debian Bug report #982322, regarding lintian: data/files/generic-header-files: add utils\.h to be marked as done. This means that you claim that the problem has

Bug#982630: marked as done (lintian: example-unusual-interpreter is confused/confusing when example script has #!/usr/bin/env python)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#982630: fixed in lintian 2.105.0 has caused the Debian Bug report #982630, regarding lintian: example-unusual-interpreter is confused/confusing when example script has #!/usr/bin/env python to be marked as don

Bug#981935: marked as done (lintian: warn about packages using Rubygems pages in the Homepage field)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#981935: fixed in lintian 2.105.0 has caused the Debian Bug report #981935, regarding lintian: warn about packages using Rubygems pages in the Homepage field to be marked as done. This means that you claim tha

Bug#981712: marked as done (no-dh-sequencer false positive on faketime)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#981712: fixed in lintian 2.105.0 has caused the Debian Bug report #981712, regarding no-dh-sequencer false positive on faketime to be marked as done. This means that you claim that the problem has been dealt w

Bug#981932: marked as done (lintian: warn about packages using PyPI pages in the Homepage field)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#981932: fixed in lintian 2.105.0 has caused the Debian Bug report #981932, regarding lintian: warn about packages using PyPI pages in the Homepage field to be marked as done. This means that you claim that the

Bug#981279: marked as done (lintian: False positive: pkg-js-autopkgtest-file-does-not-exist packages/*/test)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#981279: fixed in lintian 2.105.0 has caused the Debian Bug report #981279, regarding lintian: False positive: pkg-js-autopkgtest-file-does-not-exist packages/*/test to be marked as done. This means that you c

Bug#981163: marked as done (triggers invalid-arch-string-in-source-relation for valid gnu-any-any)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#981163: fixed in lintian 2.105.0 has caused the Debian Bug report #981163, regarding triggers invalid-arch-string-in-source-relation for valid gnu-any-any to be marked as done. This means that you claim that t

Bug#981268: marked as done (lintian: False positive for entry_points.txt in Python packages (package-contains-documentation-outside-usr-share-doc))

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#981268: fixed in lintian 2.105.0 has caused the Debian Bug report #981268, regarding lintian: False positive for entry_points.txt in Python packages (package-contains-documentation-outside-usr-share-doc) to be

Bug#980247: marked as done (lintian: Should emit paths to patches consistently with or without path, but not once with and once without (patch-not-forwarded-upstream vs quilt-patch-missing-description

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#980247: fixed in lintian 2.105.0 has caused the Debian Bug report #980247, regarding lintian: Should emit paths to patches consistently with or without path, but not once with and once without (patch-not-forwa

Bug#980987: marked as done (lintian: check for duplicates in debian/py3dist-overrides)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#980987: fixed in lintian 2.105.0 has caused the Debian Bug report #980987, regarding lintian: check for duplicates in debian/py3dist-overrides to be marked as done. This means that you claim that the problem h

Bug#980824: marked as done (no-op-testsuite: many false positives)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#980824: fixed in lintian 2.105.0 has caused the Debian Bug report #980824, regarding no-op-testsuite: many false positives to be marked as done. This means that you claim that the problem has been dealt with.

Bug#978534: marked as done (lintian: do not emit source-is-missing for symbolic links)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#978534: fixed in lintian 2.105.0 has caused the Debian Bug report #978534, regarding lintian: do not emit source-is-missing for symbolic links to be marked as done. This means that you claim that the problem h

Bug#980560: marked as done (lintian: unknown-field not meaningfully overridable)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#980560: fixed in lintian 2.105.0 has caused the Debian Bug report #980560, regarding lintian: unknown-field not meaningfully overridable to be marked as done. This means that you claim that the problem has bee

Bug#978144: marked as done (lintian debian-rules-uses-supported-python-versions-without-python-all-build-depends false positive)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#978144: fixed in lintian 2.105.0 has caused the Debian Bug report #978144, regarding lintian debian-rules-uses-supported-python-versions-without-python-all-build-depends false positive to be marked as done.

Bug#977976: marked as done (lintian: "unknown-runtime-tests-field Architecture")

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#977976: fixed in lintian 2.105.0 has caused the Debian Bug report #977976, regarding lintian: "unknown-runtime-tests-field Architecture" to be marked as done. This means that you claim that the problem has bee

Bug#977261: marked as done (lintian: incorrect program name in --help & --version lines of new commands)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#977261: fixed in lintian 2.105.0 has caused the Debian Bug report #977261, regarding lintian: incorrect program name in --help & --version lines of new commands to be marked as done. This means that you claim

Bug#976681: marked as done (bad-jar-name: false positive for version numbers with a tilde)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#976681: fixed in lintian 2.105.0 has caused the Debian Bug report #976681, regarding bad-jar-name: false positive for version numbers with a tilde to be marked as done. This means that you claim that the probl

Bug#977332: marked as done (Confusing debhelper tags (or perhaps duplicates))

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#977332: fixed in lintian 2.105.0 has caused the Debian Bug report #977332, regarding Confusing debhelper tags (or perhaps duplicates) to be marked as done. This means that you claim that the problem has been d

Bug#976643: marked as done (regression: handling of component tarballs broken)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#976643: fixed in lintian 2.105.0 has caused the Debian Bug report #976643, regarding regression: handling of component tarballs broken to be marked as done. This means that you claim that the problem has been

Bug#974575: marked as done (Test suite aborts early on SIGWINCH)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#974575: fixed in lintian 2.105.0 has caused the Debian Bug report #974575, regarding Test suite aborts early on SIGWINCH to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#974175: marked as done (Exempt dh_elpa-related packages from executable-in-usr-lib)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#974175: fixed in lintian 2.105.0 has caused the Debian Bug report #974175, regarding Exempt dh_elpa-related packages from executable-in-usr-lib to be marked as done. This means that you claim that the problem

Bug#972876: marked as done (lintian: Wide character in say at Lintian::Output line 156)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#972878: fixed in lintian 2.105.0 has caused the Debian Bug report #972878, regarding lintian: Wide character in say at Lintian::Output line 156 to be marked as done. This means that you claim that the problem

Bug#972878: marked as done (lintian: Drop global UTF-8 PerlIO encoding layer)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#972878: fixed in lintian 2.105.0 has caused the Debian Bug report #972878, regarding lintian: Drop global UTF-8 PerlIO encoding layer to be marked as done. This means that you claim that the problem has been d

Bug#972876: marked as done (lintian: Wide character in say at Lintian::Output line 156)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#972876: fixed in lintian 2.105.0 has caused the Debian Bug report #972876, regarding lintian: Wide character in say at Lintian::Output line 156 to be marked as done. This means that you claim that the problem

Bug#972878: marked as done (lintian: Drop global UTF-8 PerlIO encoding layer)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#972876: fixed in lintian 2.105.0 has caused the Debian Bug report #972876, regarding lintian: Drop global UTF-8 PerlIO encoding layer to be marked as done. This means that you claim that the problem has been d

Bug#969762: marked as done (warn about invalid field names in debian/upstream/metadata)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#969762: fixed in lintian 2.105.0 has caused the Debian Bug report #969762, regarding warn about invalid field names in debian/upstream/metadata to be marked as done. This means that you claim that the problem

Bug#962601: marked as done (wrong-manual-section does not work for manual pages shared among multiple executables)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:03 + with message-id and subject line Bug#962601: fixed in lintian 2.105.0 has caused the Debian Bug report #962601, regarding wrong-manual-section does not work for manual pages shared among multiple executables to be marked as done. This means that

Bug#969398: marked as done (lintian-annotate-tags: Repeats tag name)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#969398: fixed in lintian 2.105.0 has caused the Debian Bug report #969398, regarding lintian-annotate-tags: Repeats tag name to be marked as done. This means that you claim that the problem has been dealt with

Bug#972181: marked as done (possible-gpl-code-linked-with-openssl tag/test can be retired)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#972181: fixed in lintian 2.105.0 has caused the Debian Bug report #972181, regarding possible-gpl-code-linked-with-openssl tag/test can be retired to be marked as done. This means that you claim that the probl

Bug#947258: marked as done (lintian: spare-manual-page is too strict (false positives for subcommand man pages))

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:03 + with message-id and subject line Bug#947258: fixed in lintian 2.105.0 has caused the Debian Bug report #947258, regarding lintian: spare-manual-page is too strict (false positives for subcommand man pages) to be marked as done. This means that y

Bug#968011: marked as done (lintian: Stop shipping modules in system path)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:04 + with message-id and subject line Bug#968011: fixed in lintian 2.105.0 has caused the Debian Bug report #968011, regarding lintian: Stop shipping modules in system path to be marked as done. This means that you claim that the problem has been deal

Bug#965208: marked as done (lintian: fpos for non-consecutive-debian-revision)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:03 + with message-id and subject line Bug#942013: fixed in lintian 2.105.0 has caused the Debian Bug report #942013, regarding lintian: fpos for non-consecutive-debian-revision to be marked as done. This means that you claim that the problem has been

Bug#935907: marked as done (lintian: Build only needed test packages on partial tests)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:03 + with message-id and subject line Bug#935907: fixed in lintian 2.105.0 has caused the Debian Bug report #935907, regarding lintian: Build only needed test packages on partial tests to be marked as done. This means that you claim that the problem h

Bug#927476: marked as done (lintian: Please explicitly detect and warn if/when build-test-packages has not been called)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:03 + with message-id and subject line Bug#927476: fixed in lintian 2.105.0 has caused the Debian Bug report #927476, regarding lintian: Please explicitly detect and warn if/when build-test-packages has not been called to be marked as done. This means

Bug#942013: marked as done (lintian: non-consecutive-debian-revision: false positive for NMUs)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:03 + with message-id and subject line Bug#942013: fixed in lintian 2.105.0 has caused the Debian Bug report #942013, regarding lintian: non-consecutive-debian-revision: false positive for NMUs to be marked as done. This means that you claim that the p

Processing of lintian_2.105.0_amd64.changes

2021-09-07 Thread Debian FTP Masters
lintian_2.105.0_amd64.changes uploaded successfully to localhost along with the files: lintian_2.105.0.dsc lintian_2.105.0.tar.xz lintian_2.105.0_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#898867: marked as done (lintian: embedded-php-library libmarkdown-php vs. php-markdown confusion)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:03 + with message-id and subject line Bug#898867: fixed in lintian 2.105.0 has caused the Debian Bug report #898867, regarding lintian: embedded-php-library libmarkdown-php vs. php-markdown confusion to be marked as done. This means that you claim th

Bug#932870: marked as done (lintian: check that there are some autopkgtests that don't have Restrictions: superficial)

2021-09-07 Thread Debian Bug Tracking System
Your message dated Tue, 07 Sep 2021 10:05:03 + with message-id and subject line Bug#932870: fixed in lintian 2.105.0 has caused the Debian Bug report #932870, regarding lintian: check that there are some autopkgtests that don't have Restrictions: superficial to be marked as done. This means

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

2021-09-07 Thread Chris Lamb (@lamby)
Chris Lamb pushed new tag 2.105.0 at lintian / lintian -- View it on GitLab: https://salsa.debian.org/lintian/lintian/-/tree/2.105.0 You're receiving this email because of your account on salsa.debian.org.

lintian 2.105.0 released

2021-09-07 Thread Chris Lamb
Hi, The Lintian maintainers are pleased to announce the release of Lintian version 2.105.0. Lintian dissects Debian packages and reports bugs and policy violations. It contains automated checks for many aspects of Debian policy as well as some checks for common errors. This version includes the