Bug#1009510: marked as done (node-cached-path-relative: FTBFS: ERROR: Coverage for statements (86.66%) does not meet global threshold (100%))

2022-04-16 Thread Debian Bug Tracking System
Your message dated Sun, 17 Apr 2022 05:48:48 + with message-id and subject line Bug#1009510: fixed in node-cached-path-relative 1.1.0+~1.0.0-2 has caused the Debian Bug report #1009510, regarding node-cached-path-relative: FTBFS: ERROR: Coverage for statements (86.66%) does not meet global

Bug#1009505: marked as done (node-concat-stream: FTBFS: ERROR: Coverage for statements (97.27%) does not meet global threshold (100%))

2022-04-16 Thread Debian Bug Tracking System
Your message dated Sun, 17 Apr 2022 05:48:59 + with message-id and subject line Bug#1009505: fixed in node-concat-stream 2.0.0-3 has caused the Debian Bug report #1009505, regarding node-concat-stream: FTBFS: ERROR: Coverage for statements (97.27%) does not meet global threshold (100%) to be

Bug#1009499: marked as done (node-proto-list: FTBFS: ERROR: Coverage for statements (68.62%) does not meet global threshold (100%))

2022-04-16 Thread Debian Bug Tracking System
Your message dated Sun, 17 Apr 2022 05:49:05 + with message-id and subject line Bug#1009499: fixed in node-proto-list 1.2.4-3 has caused the Debian Bug report #1009499, regarding node-proto-list: FTBFS: ERROR: Coverage for statements (68.62%) does not meet global threshold (100%) to be

Bug#1009492: marked as done (node-coffeeify: FTBFS: ERROR: Coverage for statements (71.42%) does not meet global threshold (100%))

2022-04-16 Thread Debian Bug Tracking System
Your message dated Sun, 17 Apr 2022 05:48:54 + with message-id and subject line Bug#1009492: fixed in node-coffeeify 2.1.0-5 has caused the Debian Bug report #1009492, regarding node-coffeeify: FTBFS: ERROR: Coverage for statements (71.42%) does not meet global threshold (100%) to be marked

Bug#722188: marked as done (Optimizations are not properly applied)

2022-04-16 Thread Debian Bug Tracking System
Your message dated Sun, 17 Apr 2022 04:18:51 + with message-id and subject line Bug#722188: fixed in libdvbcsa 1.1.0-3 has caused the Debian Bug report #722188, regarding Optimizations are not properly applied to be marked as done. This means that you claim that the problem has been dealt

Bug#1007828: marked as done (faketime: autopkgtest regression)

2022-04-16 Thread Debian Bug Tracking System
Your message dated Sun, 17 Apr 2022 01:48:46 + with message-id and subject line Bug#1007828: fixed in faketime 0.9.10-2 has caused the Debian Bug report #1007828, regarding faketime: autopkgtest regression to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1008028: marked as done (hydra: fails to propagate errors from sub-configure to make)

2022-04-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 Apr 2022 23:33:53 + with message-id and subject line Bug#1008028: fixed in hydra 9.3-3 has caused the Debian Bug report #1008028, regarding hydra: fails to propagate errors from sub-configure to make to be marked as done. This means that you claim that the problem

Bug#1009699: marked as done (qalculate-gtk: Memory Leaks)

2022-04-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 Apr 2022 14:49:00 -0700 with message-id <7f241ee2-f87d-6294-62a1-c7bdd3d29...@overdrivenetworks.com> and subject line Re: qalculate-gtk: Memory Leaks has caused the Debian Bug report #1009699, regarding qalculate-gtk: Memory Leaks to be marked as done. This means that

Bug#1004446: marked as done (cdist: FTBFS against python 3.10)

2022-04-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 Apr 2022 21:48:49 + with message-id and subject line Bug#1004446: fixed in cdist 6.9.8-1 has caused the Debian Bug report #1004446, regarding cdist: FTBFS against python 3.10 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1009405: marked as done (python-django-parler: FTBFS: ModuleNotFoundError: No module named 'parser')

2022-04-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 Apr 2022 21:18:52 + with message-id and subject line Bug#1009405: fixed in python-django-parler 2.3-2 has caused the Debian Bug report #1009405, regarding python-django-parler: FTBFS: ModuleNotFoundError: No module named 'parser' to be marked as done. This means

Processed: closing 1009150

2022-04-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1009150 Bug #1009150 [jacktrip] Please add jacktrip to bullseye-backports Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1009150:

Bug#1009736: marked as done (python-django-netfields: autopkgtest regression: No module named 'django')

2022-04-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 Apr 2022 20:34:08 + with message-id and subject line Bug#1009736: fixed in python-django-netfields 1.3.0-2 has caused the Debian Bug report #1009736, regarding python-django-netfields: autopkgtest regression: No module named 'django' to be marked as done. This

Bug#965400: marked as done (aa3d: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2022-04-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 Apr 2022 17:03:46 + with message-id and subject line Bug#965400: fixed in aa3d 1.0-8.1 has caused the Debian Bug report #965400, regarding aa3d: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that the

Bug#965401: marked as done (aa3d: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2022-04-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 Apr 2022 17:03:46 + with message-id and subject line Bug#965400: fixed in aa3d 1.0-8.1 has caused the Debian Bug report #965400, regarding aa3d: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that the

Bug#1008844: marked as done (gitsome gh fails to run with python3.10)

2022-04-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 Apr 2022 16:18:56 + with message-id and subject line Bug#1008844: fixed in gitsome 0.8.0+ds-7 has caused the Debian Bug report #1008844, regarding gitsome gh fails to run with python3.10 to be marked as done. This means that you claim that the problem has been

Bug#935088: marked as done (libgif7: ABI break in 5.2 - GifQuantizeBuffer)

2022-04-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 Apr 2022 14:33:50 + with message-id and subject line Bug#935088: fixed in giflib 5.2.1-2.2 has caused the Debian Bug report #935088, regarding libgif7: ABI break in 5.2 - GifQuantizeBuffer to be marked as done. This means that you claim that the problem has been

Bug#1009453: marked as done (python-opcua: FTBFS: ImportError: cannot import name 'Iterable' from 'collections' (/usr/lib/python3.10/collections/__init__.py))

2022-04-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 Apr 2022 14:24:31 + with message-id and subject line Bug#1009453: fixed in python-opcua 0.98.11-2 has caused the Debian Bug report #1009453, regarding python-opcua: FTBFS: ImportError: cannot import name 'Iterable' from 'collections'

Processed: RFS: php-dragonmantank-cron-expression/3.3.1-1 -- cron expression parser for PHP

2022-04-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1009688 Bug #1009688 [sponsorship-requests] RFS: php-dragonmantank-cron-expression/3.3.1-1 -- cron expression parser for PHP Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 1009688:

Bug#995942: marked as done (/usr/bin/ibus-ui-emojier-plasma: does not show any emojis)

2022-04-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 Apr 2022 14:04:54 +0200 with message-id <10165468.nUPlyArG6x@delta-one> and subject line has caused the Debian Bug report #995942, regarding /usr/bin/ibus-ui-emojier-plasma: does not show any emojis to be marked as done. This means that you claim that the problem has

Bug#1009375: marked as done (O: rust-rustls -- Modern TLS library)

2022-04-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 Apr 2022 11:49:16 + with message-id and subject line Bug#1009375: fixed in rust-rustls 0.18.1-1 has caused the Debian Bug report #1009375, regarding O: rust-rustls -- Modern TLS library to be marked as done. This means that you claim that the problem has been dealt

Bug#1008615: marked as done (qcoro FTBFS with riscv)

2022-04-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 Apr 2022 11:35:09 + with message-id and subject line Bug#1008615: fixed in qcoro 0.4.0-5 has caused the Debian Bug report #1008615, regarding qcoro FTBFS with riscv to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#1002082: marked as done (mpi4py: FTBFS: testJoin socket.gaierror: Name or service not known)

2022-04-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 Apr 2022 13:32:55 +0200 with message-id <5e985d0a6b43dded0dd5e6c23bdd3...@debian.org> and subject line Re: Bug#1002082 mpi4py: FTBFS: testJoin socket.gaierror: Name or service not known has caused the Debian Bug report #1002082, regarding mpi4py: FTBFS: testJoin

Bug#1008174: marked as done (libc6: poll() spuriously returns EINTR)

2022-04-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 Apr 2022 11:18:56 + with message-id and subject line Bug#1008174: fixed in glibc 2.34-0experimental4 has caused the Debian Bug report #1008174, regarding libc6: poll() spuriously returns EINTR to be marked as done. This means that you claim that the problem has

Bug#1006692: marked as done (glibc: libc6 postinst: do not re-exec init if DPKG_ROOT is set)

2022-04-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 Apr 2022 11:18:56 + with message-id and subject line Bug#1006692: fixed in glibc 2.34-0experimental4 has caused the Debian Bug report #1006692, regarding glibc: libc6 postinst: do not re-exec init if DPKG_ROOT is set to be marked as done. This means that you claim

Bug#998106: marked as done (mpi4py: test_io.TestIOSelf failures on i386)

2022-04-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 Apr 2022 11:04:19 + with message-id and subject line Bug#998106: fixed in mpi4py 3.1.3-2 has caused the Debian Bug report #998106, regarding mpi4py: test_io.TestIOSelf failures on i386 to be marked as done. This means that you claim that the problem has been dealt

Bug#1006882: marked as done (podman fails to install - unable to open podman.socket.dpkg-new)

2022-04-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 Apr 2022 11:04:14 + with message-id and subject line Bug#1009374: fixed in libpod 4.0.3+ds1-1 has caused the Debian Bug report #1009374, regarding podman fails to install - unable to open podman.socket.dpkg-new to be marked as done. This means that you claim that

Bug#1009374: marked as done (podman: fails to install: unable to open '/usr/lib/systemd/user/podman.socket.dpkg-new': No such file or directory)

2022-04-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 Apr 2022 11:04:14 + with message-id and subject line Bug#1009374: fixed in libpod 4.0.3+ds1-1 has caused the Debian Bug report #1009374, regarding podman: fails to install: unable to open '/usr/lib/systemd/user/podman.socket.dpkg-new': No such file or directory to

Bug#1000521: marked as done (libpod: please provide podman-remote binary)

2022-04-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 Apr 2022 11:04:13 + with message-id and subject line Bug#1000521: fixed in libpod 4.0.3+ds1-1 has caused the Debian Bug report #1000521, regarding libpod: please provide podman-remote binary to be marked as done. This means that you claim that the problem has been

Bug#1008910: marked as done (mount-functions: Only allows for LABEL/UUID)

2022-04-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 Apr 2022 09:50:25 + with message-id and subject line Bug#1008910: fixed in sysvinit 3.03-1 has caused the Debian Bug report #1008910, regarding mount-functions: Only allows for LABEL/UUID to be marked as done. This means that you claim that the problem has been

Bug#1009682: marked as done (ghostscript breaks openscad autopkgtest)

2022-04-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 Apr 2022 09:20:55 + with message-id and subject line Bug#1009682: fixed in openscad 2021.01-5 has caused the Debian Bug report #1009682, regarding ghostscript breaks openscad autopkgtest to be marked as done. This means that you claim that the problem has been

Processed: unarchiving 1005666, reassign 1005509 to src:llvm-toolchain-13, forcibly merging 1005666 1005509 ...

2022-04-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unarchive 1005666 Bug #1005666 {Done: Sylvestre Ledru } [src:llvm-toolchain-13] iwyu: FTBFS: The imported target "RemoteIndexProto" references the file "/usr/lib/llvm-13/lib/libRemoteIndexProto.a" but this file does not exist. Bug #1005345

Bug#1009579: marked as done (node-qs: FTBFS: Error: module util in /<>/node_modules/object-inspect not found)

2022-04-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 Apr 2022 07:19:12 + with message-id and subject line Bug#1009579: fixed in pkg-js-tools 0.14.19 has caused the Debian Bug report #1009579, regarding node-qs: FTBFS: Error: module util in /<>/node_modules/object-inspect not found to be marked as done. This means

Bug#1009734: marked as done (mutt: CVE-2022-1328)

2022-04-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 Apr 2022 08:47:43 +0200 with message-id and subject line ftpmas...@ftp-master.debian.org: Accepted mutt 2.2.3-1 (source) into unstable has caused the Debian Bug report #1009734, regarding mutt: CVE-2022-1328 to be marked as done. This means that you claim that the

Bug#1009540: marked as done (node-prr: FTBFS: ERROR: Coverage for statements (88%) does not meet global threshold (100%))

2022-04-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 Apr 2022 06:49:06 + with message-id and subject line Bug#1009540: fixed in node-prr 1.0.1-3 has caused the Debian Bug report #1009540, regarding node-prr: FTBFS: ERROR: Coverage for statements (88%) does not meet global threshold (100%) to be marked as done. This

Bug#1009610: marked as done (node-querystring: FTBFS: ERROR: Coverage for statements (89.09%) does not meet global threshold (100%))

2022-04-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 Apr 2022 06:34:26 + with message-id and subject line Bug#1009610: fixed in node-querystring 0.2.1-2 has caused the Debian Bug report #1009610, regarding node-querystring: FTBFS: ERROR: Coverage for statements (89.09%) does not meet global threshold (100%) to be

Bug#1009496: marked as done (node-pseudomap: FTBFS: ERROR: Coverage for statements (91.93%) does not meet global threshold (100%))

2022-04-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 Apr 2022 06:34:21 + with message-id and subject line Bug#1009496: fixed in node-pseudomap 1.0.2-3 has caused the Debian Bug report #1009496, regarding node-pseudomap: FTBFS: ERROR: Coverage for statements (91.93%) does not meet global threshold (100%) to be marked

Bug#1009491: marked as done (node-quote-stream: FTBFS: ERROR: Coverage for statements (94.54%) does not meet global threshold (100%))

2022-04-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 Apr 2022 06:34:31 + with message-id and subject line Bug#1009491: fixed in node-quote-stream 1.0.2-9 has caused the Debian Bug report #1009491, regarding node-quote-stream: FTBFS: ERROR: Coverage for statements (94.54%) does not meet global threshold (100%) to be

Bug#1009489: marked as done (node-read: FTBFS: ERROR: Coverage for statements (70.42%) does not meet global threshold (100%))

2022-04-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 Apr 2022 06:34:36 + with message-id and subject line Bug#1009489: fixed in node-read 1.0.7-4 has caused the Debian Bug report #1009489, regarding node-read: FTBFS: ERROR: Coverage for statements (70.42%) does not meet global threshold (100%) to be marked as done.

Bug#1008940: marked as done (angelfish: fails to start)

2022-04-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 Apr 2022 06:03:48 + with message-id and subject line Bug#1008940: fixed in angelfish 22.02-2 has caused the Debian Bug report #1008940, regarding angelfish: fails to start to be marked as done. This means that you claim that the problem has been dealt with. If this