Bug#1012564: marked as done (openssl: ckermit can't connect to telnetd-ssl with openssl 3.0.3-7)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Tue, 21 Jun 2022 08:13:38 +0200 with message-id and subject line Re: Bug#1012564: openssl: ckermit can't connect to telnetd-ssl with openssl 3.0.3-7 has caused the Debian Bug report #1012564, regarding openssl: ckermit can't connect to telnetd-ssl with openssl 3.0.3-7 to be mar

Bug#1006508: marked as done (m2crypto: FTBFS with OpenSSL 3.0)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Tue, 21 Jun 2022 05:04:04 + with message-id and subject line Bug#1006508: fixed in m2crypto 0.38.0-3 has caused the Debian Bug report #1006508, regarding m2crypto: FTBFS with OpenSSL 3.0 to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#997472: marked as done (flask-script: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Tue, 21 Jun 2022 05:00:34 + with message-id and subject line Bug#1000556: Removed package(s) from unstable has caused the Debian Bug report #997472, regarding flask-script: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13 to be mark

Bug#1000556: marked as done (RM: flask-script -- ROM; FTBFS, no support upstream, no reverse dep)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Tue, 21 Jun 2022 05:00:31 + with message-id and subject line Bug#1000556: Removed package(s) from unstable has caused the Debian Bug report #1000556, regarding RM: flask-script -- ROM; FTBFS, no support upstream, no reverse dep to be marked as done. This means that you clai

Bug#1013233: marked as done (RM: flask-script -- RoQA; dead upstream; incompatible with modern flask; FTBFS; no rdeps)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Tue, 21 Jun 2022 05:00:34 + with message-id and subject line Bug#1000556: Removed package(s) from unstable has caused the Debian Bug report #1013233, regarding RM: flask-script -- RoQA; dead upstream; incompatible with modern flask; FTBFS; no rdeps to be marked as done. Th

Bug#1008829: marked as done (pysrs-bin: envfrom2srs and srs2envtol fails with ModuleNotFoundError: No module named 'ConfigParser')

2022-06-20 Thread Debian Bug Tracking System
Your message dated Tue, 21 Jun 2022 00:49:45 + with message-id and subject line Bug#1008829: fixed in pysrs 1.0.4-1 has caused the Debian Bug report #1008829, regarding pysrs-bin: envfrom2srs and srs2envtol fails with ModuleNotFoundError: No module named 'ConfigParser' to be marked as done.

Bug#994192: marked as done (python3-srs uses no longer existing base64 functions (fixed upstream))

2022-06-20 Thread Debian Bug Tracking System
Your message dated Tue, 21 Jun 2022 00:49:45 + with message-id and subject line Bug#994192: fixed in pysrs 1.0.4-1 has caused the Debian Bug report #994192, regarding python3-srs uses no longer existing base64 functions (fixed upstream) to be marked as done. This means that you claim that the

Bug#1010764: marked as done (openafs-modules-dkms: module fails to build for kernel 5.17.0-1-amd64)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Tue, 21 Jun 2022 00:04:25 + with message-id and subject line Bug#1010764: fixed in openafs 1.8.8.1-3 has caused the Debian Bug report #1010764, regarding openafs-modules-dkms: module fails to build for kernel 5.17.0-1-amd64 to be marked as done. This means that you claim th

Bug#1000870: marked as done (nvidia: module verification failed: signature and/or required key missing - tainting kernel)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Tue, 21 Jun 2022 01:48:16 +0200 with message-id <688c2e87e2e7a6194bf37ccd420e54af9dc5c7ff.ca...@decadent.org.uk> and subject line Re: nvidia: module verification failed: signature and/or required key missing - tainting kernel has caused the Debian Bug report #1000870, regarding

Bug#900029: marked as done (yui-compressor: Change README.gz link to README.md)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 22:39:03 + with message-id and subject line Bug#900029: fixed in yui-compressor 2.4.8-3 has caused the Debian Bug report #900029, regarding yui-compressor: Change README.gz link to README.md to be marked as done. This means that you claim that the problem h

Bug#1012309: marked as done (nextcloud-desktop: Missing Dependency to qml-module-qt-labs-platform, does not launch without it)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 22:21:14 + with message-id and subject line Bug#1012309: fixed in nextcloud-desktop 3.5.1-2 has caused the Debian Bug report #1012309, regarding nextcloud-desktop: Missing Dependency to qml-module-qt-labs-platform, does not launch without it to be marked as

Bug#1013286: marked as done (Updating the pmccabe Uploaders list)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 22:05:43 + with message-id and subject line Bug#1013286: fixed in pmccabe 2.8-3 has caused the Debian Bug report #1013286, regarding Updating the pmccabe Uploaders list to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1013031: marked as done (rocm-smi-lib: ftbfs with GCC-12)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 22:05:49 + with message-id and subject line Bug#1013031: fixed in rocm-smi-lib 5.1.0-4 has caused the Debian Bug report #1013031, regarding rocm-smi-lib: ftbfs with GCC-12 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1009437: marked as done (ippsample: FTBFS: dh_auto_test: error: make -j8 test VERBOSE=1 returned exit code 2)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 22:04:33 + with message-id and subject line Bug#1009437: fixed in ippsample 0.0~git20220607.72f89b3-1 has caused the Debian Bug report #1009437, regarding ippsample: FTBFS: dh_auto_test: error: make -j8 test VERBOSE=1 returned exit code 2 to be marked as do

Bug#1009615: marked as done (forcibly starts chromium on several functions)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 23:53:00 +0200 with message-id <1882401.jDFO7f8UVR@tuxin> and subject line Re: [Pkg-owncloud-maintainers] Bug#1009615: forcibly starts chromium on several functions has caused the Debian Bug report #1009615, regarding forcibly starts chromium on several function

Bug#831751: marked as done (openafs-client unreliable after kernel update)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 13:17:01 -0700 with message-id <20220620201701.gc26...@kduck.mit.edu> and subject line resolved: openafs-client unreliable after kernel update has caused the Debian Bug report #831751, regarding openafs-client unreliable after kernel update to be marked as done.

Bug#1011940: marked as done (rails: CVE-2022-21831 code injection vulnerability exists in Active Storage)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 21:31:57 +0200 with message-id and subject line Accepted rails 2:6.1.4.7+dfsg-1 (source) into unstable has caused the Debian Bug report #1011940, regarding rails: CVE-2022-21831 code injection vulnerability exists in Active Storage to be marked as done. This m

Bug#1012606: marked as done (keyutils: key.dns_resolver sets unlimited lifetime for cached records)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 19:21:39 + with message-id and subject line Bug#1012606: fixed in keyutils 1.6.3-1 has caused the Debian Bug report #1012606, regarding keyutils: key.dns_resolver sets unlimited lifetime for cached records to be marked as done. This means that you claim tha

Bug#997302: marked as done (django-pipeline: FTBFS: ImportError: cannot import name 'six' from 'django.utils' (/usr/lib/python3/dist-packages/django/utils/__init__.py))

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 19:19:02 + with message-id and subject line Bug#997302: fixed in django-pipeline 1.6.14-5 has caused the Debian Bug report #997302, regarding django-pipeline: FTBFS: ImportError: cannot import name 'six' from 'django.utils' (/usr/lib/python3/dist-packages/d

Processed: found 1013271 in 1.17.0-1, tagging 1013271, closing 1013271

2022-06-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1013271 1.17.0-1 Bug #1013271 [src:jupyter-server] jupyter-server: CVE-2022-29241 Marked as found in versions jupyter-server/1.17.0-1. > tags 1013271 + upstream Bug #1013271 [src:jupyter-server] jupyter-server: CVE-2022-29241 Added tag(s) up

Bug#1013218: marked as done (rails: ftbfs SyntaxError: Unexpected token 'export')

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 18:56:13 + with message-id and subject line Bug#1013218: fixed in rails 2:6.1.4.7+dfsg-1 has caused the Debian Bug report #1013218, regarding rails: ftbfs SyntaxError: Unexpected token 'export' to be marked as done. This means that you claim that the proble

Bug#1011513: marked as done (config/Arm64: request enable CONFIG_ARM_PSCI_CPUIDLE)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 20:54:38 +0200 with message-id <21f4844bdaf758e97b5193f3c252a9b6f8e39196.ca...@decadent.org.uk> and subject line Re: Bug#1011513: enable CONFIG_ARM_PSCI_CPUIDLE has caused the Debian Bug report #1011513, regarding config/Arm64: request enable CONFIG_ARM_PSCI_CPUI

Bug#995650: marked as done (chktex: reproducible builds: Embedded timestamps in .dvi file)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 18:18:53 + with message-id and subject line Bug#995650: fixed in chktex 1.7.6-5 has caused the Debian Bug report #995650, regarding chktex: reproducible builds: Embedded timestamps in .dvi file to be marked as done. This means that you claim that the proble

Bug#1000070: marked as done (chktex: depends on obsolete pcre3 library)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 18:18:53 + with message-id and subject line Bug#170: fixed in chktex 1.7.6-5 has caused the Debian Bug report #170, regarding chktex: depends on obsolete pcre3 library to be marked as done. This means that you claim that the problem has been dealt w

Bug#1013014: marked as done (pipexec: ftbfs with GCC-12)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 18:06:38 + with message-id and subject line Bug#1013014: fixed in pipexec 2.6.0-1 has caused the Debian Bug report #1013014, regarding pipexec: ftbfs with GCC-12 to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#937312: marked as done (postnews: Python2 removal in sid/bullseye)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 18:00:39 + with message-id and subject line Bug#1008272: Removed package(s) from unstable has caused the Debian Bug report #937312, regarding postnews: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#966775: marked as done (postnews: Unversioned Python removal in sid/bullseye)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 18:00:39 + with message-id and subject line Bug#1008272: Removed package(s) from unstable has caused the Debian Bug report #937312, regarding postnews: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the probl

Bug#1008272: marked as done (RM: postnews -- RoQA; depends on Python 2, unmaintained)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 18:00:36 + with message-id and subject line Bug#1008272: Removed package(s) from unstable has caused the Debian Bug report #1008272, regarding RM: postnews -- RoQA; depends on Python 2, unmaintained to be marked as done. This means that you claim that the p

Bug#1013179: marked as done (likwid: ships /usr/lib//libhwloc.so{,.5})

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 17:20:31 + with message-id and subject line Bug#1013179: fixed in likwid 5.2.1+dfsg1-3 has caused the Debian Bug report #1013179, regarding likwid: ships /usr/lib//libhwloc.so{,.5} to be marked as done. This means that you claim that the problem has been de

Bug#1011369: marked as done (transition: gromacs)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 09:39:14 -0700 with message-id <20220620163914.gd20...@ofb.net> and subject line Re: Bug#1011369: transition: gromacs has caused the Debian Bug report #1011369, regarding transition: gromacs to be marked as done. This means that you claim that the problem has be

Bug#1012100: marked as done (linux-image-5.17-1: KVM LIBVIRT fails to start, slow disk access, and a kernel thread goes wild on Intel Xeon X3430)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 18:39:31 +0200 with message-id <4423757.LvFx2qVVIh@bagend> and subject line Re: Bug#1012100: linux-image-5.17-1: KVM LIBVIRT fails to start, slow disk access, and a kernel thread goes wild on Intel Xeon X3430 has caused the Debian Bug report #1012100, regarding

Bug#1012294: marked as done (ITA: jsonnet -- data templating language)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 16:35:01 + with message-id and subject line Bug#1012294: fixed in jsonnet 0.18.0+ds-1 has caused the Debian Bug report #1012294, regarding ITA: jsonnet -- data templating language to be marked as done. This means that you claim that the problem has been dea

Bug#1012708: marked as done (RFS: jsonnet/0.18.0+ds-1 ds-1 [ITA] -- data templating language)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 18:25:09 +0200 with message-id <179c0010-3cee-4164-f607-888bf27af...@debian.org> and subject line Re: Bug#1012708: RFS: jsonnet/0.18.0 ds-1 [ITA] -- data templating language has caused the Debian Bug report #1012708, regarding RFS: jsonnet/0.18.0+ds-1 ds-1 [ITA]

Bug#999810: marked as done (lintian: dh-sequence-sphinxdoc is valid prerequisite for dh_sphinxdoc)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 14:34:13 + with message-id and subject line Bug#999810: fixed in lintian 2.115.0 has caused the Debian Bug report #999810, regarding lintian: dh-sequence-sphinxdoc is valid prerequisite for dh_sphinxdoc to be marked as done. This means that you claim that t

Bug#999768: marked as done (lintian: false report: adopted-extended-field XS-Autobuild)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 14:34:13 + with message-id and subject line Bug#999768: fixed in lintian 2.115.0 has caused the Debian Bug report #999768, regarding lintian: false report: adopted-extended-field XS-Autobuild to be marked as done. This means that you claim that the problem

Bug#996740: marked as done (lintian: Exempt autotools-generated files from tags for long source lines)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 14:34:13 + with message-id and subject line Bug#996740: fixed in lintian 2.115.0 has caused the Debian Bug report #996740, regarding lintian: Exempt autotools-generated files from tags for long source lines to be marked as done. This means that you claim t

Bug#995286: marked as done (lintian: new-package-should-not-package-python2-module false positive for python-*-doc packages)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 14:34:13 + with message-id and subject line Bug#995286: fixed in lintian 2.115.0 has caused the Debian Bug report #995286, regarding lintian: new-package-should-not-package-python2-module false positive for python-*-doc packages to be marked as done. This

Bug#989381: marked as done (lintian: spelling-error-in-copyright is triggering on names)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 14:34:13 + with message-id and subject line Bug#989381: fixed in lintian 2.115.0 has caused the Debian Bug report #989381, regarding lintian: spelling-error-in-copyright is triggering on names to be marked as done. This means that you claim that the problem

Bug#963099: marked as done (lacks-unversioned-link-to-shared-library false positive)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 14:34:13 + with message-id and subject line Bug#963099: fixed in lintian 2.115.0 has caused the Debian Bug report #963099, regarding lacks-unversioned-link-to-shared-library false positive to be marked as done. This means that you claim that the problem has

Bug#1001651: marked as done (lintian: changelog-file-missing-explicit-entry: false positives with successive stable uploads)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 14:34:13 + with message-id and subject line Bug#941656: fixed in lintian 2.115.0 has caused the Debian Bug report #941656, regarding lintian: changelog-file-missing-explicit-entry: false positives with successive stable uploads to be marked as done. This m

Bug#941656: marked as done (lintian: changelog-file-missing-explicit-entry not working properly)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 14:34:13 + with message-id and subject line Bug#941656: fixed in lintian 2.115.0 has caused the Debian Bug report #941656, regarding lintian: changelog-file-missing-explicit-entry not working properly to be marked as done. This means that you claim that the

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)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 14:34:13 + with message-id and subject line Bug#932634: fixed in lintian 2.115.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 packag

Bug#657390: marked as done (lintian: Please make build-arch and build-indep required targets)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 14:34:13 + with message-id and subject line Bug#657390: fixed in lintian 2.115.0 has caused the Debian Bug report #657390, regarding lintian: Please make build-arch and build-indep required targets to be marked as done. This means that you claim that the pr

Bug#1012090: marked as done (riscv support in lintian tag binary-from-other-architecture)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 14:34:14 + with message-id and subject line Bug#1012090: fixed in lintian 2.115.0 has caused the Debian Bug report #1012090, regarding riscv support in lintian tag binary-from-other-architecture to be marked as done. This means that you claim that the probl

Bug#1007257: marked as done (Please upgrade missing-systemd-timer-for-cron-script to a warning)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 14:34:13 + with message-id and subject line Bug#1007257: fixed in lintian 2.115.0 has caused the Debian Bug report #1007257, regarding Please upgrade missing-systemd-timer-for-cron-script to a warning to be marked as done. This means that you claim that the

Bug#1007140: marked as done (please have a check for chown user.group)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 14:34:13 + with message-id and subject line Bug#1007140: fixed in lintian 2.115.0 has caused the Debian Bug report #1007140, regarding please have a check for chown user.group to be marked as done. This means that you claim that the problem has been dealt w

Bug#1006859: marked as done (lintian: warn about devhelp version 1 files)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 14:34:13 + with message-id and subject line Bug#1006859: fixed in lintian 2.115.0 has caused the Debian Bug report #1006859, regarding lintian: warn about devhelp version 1 files to be marked as done. This means that you claim that the problem has been deal

Bug#1006390: marked as done (Incorrect entry in SEE ALSO section of lintian(1))

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 14:34:13 + with message-id and subject line Bug#1006390: fixed in lintian 2.115.0 has caused the Debian Bug report #1006390, regarding Incorrect entry in SEE ALSO section of lintian(1) to be marked as done. This means that you claim that the problem has bee

Bug#1005762: marked as done (lintian: Update known Java version up to 19)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 14:34:13 + with message-id and subject line Bug#1005762: fixed in lintian 2.115.0 has caused the Debian Bug report #1005762, regarding lintian: Update known Java version up to 19 to be marked as done. This means that you claim that the problem has been deal

Bug#1005046: marked as done (lintian: [false positive] very-long-line-length-in-source-file for pictures and sounds)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 14:34:13 + with message-id and subject line Bug#1005046: fixed in lintian 2.115.0 has caused the Debian Bug report #1005046, regarding lintian: [false positive] very-long-line-length-in-source-file for pictures and sounds to be marked as done. This means t

Bug#1005184: marked as done (lintian: package-does-not-install-examples should not look in tests)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 14:34:13 + with message-id and subject line Bug#1005184: fixed in lintian 2.115.0 has caused the Debian Bug report #1005184, regarding lintian: package-does-not-install-examples should not look in tests to be marked as done. This means that you claim that t

Bug#1004660: marked as done ([PATCH] lintian-annotate-hints: line-wrapping broken when stdin is not a terminal)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 14:34:13 + with message-id and subject line Bug#1004660: fixed in lintian 2.115.0 has caused the Debian Bug report #1004660, regarding [PATCH] lintian-annotate-hints: line-wrapping broken when stdin is not a terminal to be marked as done. This means that y

Bug#1004239: marked as done (tag-display-limit can be overriden via configuration file)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 14:34:13 + with message-id and subject line Bug#1004239: fixed in lintian 2.115.0 has caused the Debian Bug report #1004239, regarding tag-display-limit can be overriden via configuration file to be marked as done. This means that you claim that the problem

Bug#1004240: marked as done (more flexibility wrt command line and confiuration file)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 14:34:13 + with message-id and subject line Bug#1004240: fixed in lintian 2.115.0 has caused the Debian Bug report #1004240, regarding more flexibility wrt command line and confiuration file to be marked as done. This means that you claim that the problem h

Bug#1004231: marked as done (ancient outdated parts in lintian.txt.gz do reduce trust in docs)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 14:34:13 + with message-id and subject line Bug#1004231: fixed in lintian 2.115.0 has caused the Debian Bug report #1004231, regarding ancient outdated parts in lintian.txt.gz do reduce trust in docs to be marked as done. This means that you claim that the

Bug#1003941: marked as done (lintian: FP executable-in-usr-lib for /usr/lib/cgi-bin/)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 14:34:13 + with message-id and subject line Bug#1003941: fixed in lintian 2.115.0 has caused the Debian Bug report #1003941, regarding lintian: FP executable-in-usr-lib for /usr/lib/cgi-bin/ to be marked as done. This means that you claim that the problem h

Bug#1003913: marked as done (lintian: False positive: package-contains-documentation-outside-usr-share-doc)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 14:34:13 + with message-id and subject line Bug#1003913: fixed in lintian 2.115.0 has caused the Debian Bug report #1003913, regarding lintian: False positive: package-contains-documentation-outside-usr-share-doc to be marked as done. This means that you c

Bug#1003817: marked as done (lintian: fpos for update-debian-copyright)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 14:34:13 + with message-id and subject line Bug#1003817: fixed in lintian 2.115.0 has caused the Debian Bug report #1003817, regarding lintian: fpos for update-debian-copyright to be marked as done. This means that you claim that the problem has been dealt

Bug#1003668: marked as done (lintian: FP missing-build-dependency-for-dh-addon with pybuild-plugin-pyproject)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 14:34:13 + with message-id and subject line Bug#1003668: fixed in lintian 2.115.0 has caused the Debian Bug report #1003668, regarding lintian: FP missing-build-dependency-for-dh-addon with pybuild-plugin-pyproject to be marked as done. This means that you

Bug#1003456: marked as done (Excessive memory use with large binaries)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 14:34:13 + with message-id and subject line Bug#1003456: fixed in lintian 2.115.0 has caused the Debian Bug report #1003456, regarding Excessive memory use with large binaries to be marked as done. This means that you claim that the problem has been dealt w

Bug#1003353: marked as done (lintian: Cannot use brackets in suppression rules?)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 14:34:13 + with message-id and subject line Bug#1003353: fixed in lintian 2.115.0 has caused the Debian Bug report #1003353, regarding lintian: Cannot use brackets in suppression rules? to be marked as done. This means that you claim that the problem has be

Bug#1003272: marked as done (lintian: chokes on overrides with "(" but no ")")

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 14:34:13 + with message-id and subject line Bug#1003272: fixed in lintian 2.115.0 has caused the Debian Bug report #1003272, regarding lintian: chokes on overrides with "(" but no ")" to be marked as done. This means that you claim that the problem has been

Bug#1000977: marked as done (lintian: bogus elf-error in debug symbols)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 14:34:13 + with message-id and subject line Bug#1000977: fixed in lintian 2.115.0 has caused the Debian Bug report #1000977, regarding lintian: bogus elf-error in debug symbols to be marked as done. This means that you claim that the problem has been dealt

Bug#1003131: marked as done (debug-suffix-not-dbg references incorrect section of dev ref)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 14:34:13 + with message-id and subject line Bug#1003131: fixed in lintian 2.115.0 has caused the Debian Bug report #1003131, regarding debug-suffix-not-dbg references incorrect section of dev ref to be marked as done. This means that you claim that the prob

Bug#1002828: marked as done (lintian: please add rakudo as known interpreter)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 14:34:13 + with message-id and subject line Bug#1002828: fixed in lintian 2.115.0 has caused the Debian Bug report #1002828, regarding lintian: please add rakudo as known interpreter to be marked as done. This means that you claim that the problem has been

Bug#1000234: marked as done (lintian: Compare Debhelper prerequisites accurately w/r/t multiarch acceptor)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 14:34:13 + with message-id and subject line Bug#1000234: fixed in lintian 2.115.0 has caused the Debian Bug report #1000234, regarding lintian: Compare Debhelper prerequisites accurately w/r/t multiarch acceptor to be marked as done. This means that you cl

Bug#1001655: marked as done (Avoid hardcoding depends on specific lzip implementations)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 14:34:13 + with message-id and subject line Bug#1001655: fixed in lintian 2.115.0 has caused the Debian Bug report #1001655, regarding Avoid hardcoding depends on specific lzip implementations to be marked as done. This means that you claim that the problem

Bug#1013258: marked as done (autoreconf: error: /usr/bin/autoconf failed with exit status: 1)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 14:00:32 +0200 with message-id and subject line Re: Bug#1013258: autoreconf: error: /usr/bin/autoconf failed with exit status: 1 has caused the Debian Bug report #1013258, regarding autoreconf: error: /usr/bin/autoconf failed with exit status: 1 to be marked a

Bug#980969: marked as done (mimedefang: reduce Build-Depends)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 11:18:54 + with message-id and subject line Bug#980969: fixed in mimedefang 2.85-1 has caused the Debian Bug report #980969, regarding mimedefang: reduce Build-Depends to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1010635: marked as done (denemo: Help | Browse Manual opens the wrong directory)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 10:34:04 + with message-id and subject line Bug#1010635: fixed in denemo 2.6.0-1 has caused the Debian Bug report #1010635, regarding denemo: Help | Browse Manual opens the wrong directory to be marked as done. This means that you claim that the problem has

Bug#1004048: marked as done (golang-github-komkom-toml: autopkgtest regression on armhf/i386: -{"hex3":3735928559}, +{"hex3":-559038737})

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 10:04:39 + with message-id and subject line Bug#1004048: fixed in golang-github-komkom-toml 0.0~git20211215.3c8ee9d-2 has caused the Debian Bug report #1004048, regarding golang-github-komkom-toml: autopkgtest regression on armhf/i386: -{"hex3":3735928559}

Processed: close duplicate itp

2022-06-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 830306 ITP: parsimonious -- fast pure-Python PEG parser Bug #830306 [wnpp] RFP: python-parsimonious -- fast pure-Python PEG parser Changed Bug title to 'ITP: parsimonious -- fast pure-Python PEG parser' from 'RFP: python-parsimonious -- f

Bug#1013010: marked as done (openmm: ftbfs with GCC-12)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 07:33:47 + with message-id and subject line Bug#1013010: fixed in openmm 7.7.0+dfsg-6 has caused the Debian Bug report #1013010, regarding openmm: ftbfs with GCC-12 to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#1012802: marked as done (python3-ipykernel: breaks jupyter notebook)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 09:18:43 +0200 with message-id <283db8a509c43c26e3a932be0193ebc06c6f0076.ca...@gmail.com> and subject line Fixed package migrated to testing: closing has caused the Debian Bug report #1012802, regarding python3-ipykernel: breaks jupyter notebook to be marked as d

Bug#730610: marked as done (C-STORE SCU not working with JPIP Transfer Syntax)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 09:02:44 +0200 with message-id and subject line C-STORE SCU not working with JPIP Transfer Syntax has caused the Debian Bug report #730610, regarding C-STORE SCU not working with JPIP Transfer Syntax to be marked as done. This means that you claim that the pro

Bug#718557: marked as done (dcmtk: Missing transition in dcmqrscp)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 08:59:37 +0200 with message-id and subject line dcmtk: Missing transition in dcmqrscp has caused the Debian Bug report #718557, regarding dcmtk: Missing transition in dcmqrscp to be marked as done. This means that you claim that the problem has been dealt with

Bug#697073: marked as done (dcmtk: dcmdjpeg fails to decode a lossless JPEG)

2022-06-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Jun 2022 08:58:24 +0200 with message-id and subject line dcmtk: dcmdjpeg fails to decode a lossless JPEG has caused the Debian Bug report #697073, regarding dcmtk: dcmdjpeg fails to decode a lossless JPEG to be marked as done. This means that you claim that the problem