Bug#1009891: hexchat locks up hard when connecting to bip server

Quack Seven, I'm involved with bip packaging and upstream and we wondered what version of bip you are using. Did you upgrade bip recently? We have yet no reason to think that it could be triggered by a bug in bip, just checking. Clearly hexchat should behave better anyway. Can you reproduce

Bug#1009441: marked as done (ruby-i18n-inflector: FTBFS: ERROR: Test "ruby3.0" failed: :85:in `require': cannot load such file -

Your message dated Wed, 20 Apr 2022 04:48:44 + with message-id and subject line Bug#1009441: fixed in ruby-i18n-inflector 2.6.7-2 has caused the Debian Bug report #1009441, regarding ruby-i18n-inflector: FTBFS: ERROR: Test "ruby3.0" failed: :85:in `require': cannot load such file --

Bug#1009612: marked as done (ruby-i18n breaks ruby-i18n-inflector autopkgtest: cannot load such file -- i18n/core_ext/hash)

Your message dated Wed, 20 Apr 2022 04:48:44 + with message-id and subject line Bug#1009612: fixed in ruby-i18n-inflector 2.6.7-2 has caused the Debian Bug report #1009612, regarding ruby-i18n breaks ruby-i18n-inflector autopkgtest: cannot load such file -- i18n/core_ext/hash to be marked as

Bug#1009891: hexchat locks up hard when connecting to bip server

Package: hexchat Version: 2.16.0-4+b2 Severity: grave Justification: renders package unusable Dear Maintainer, When connecting hexchat to my bip server it locks up hard. It use to work fine, until I upgraded to 2.16. The bip server connects to OFTC, and when I connect to it, the application just

Bug#1009886: marked as done (cargo: autopkgtest failure on ppc64el)

Your message dated Wed, 20 Apr 2022 02:31:59 +0100 with message-id <97ae487b-f1ef-ae0a-e1ea-cd0c6f760...@debian.org> and subject line Re: [Pkg-rust-maintainers] Bug#1009886: cargo: autopkgtest failure on ppc64el has caused the Debian Bug report #1009886, regarding cargo: autopkgtest failure on

Bug#1009885: marked as done (qbittorrent:src fails to build using dpkg-buildpackage, reports it can't find '-l-pthread')

Your message dated Wed, 20 Apr 2022 01:38:33 +0200 with message-id <87lew0wsna@christian.marillat.net> and subject line Re: Bug#1009885: qbittorrent:src fails to build using dpkg-buildpackage, reports it can't find '-l-pthread' has caused the Debian Bug report #1009885, regarding

Bug#1009396: marked as done (python-m2r: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.10 returned exit code 13)

Your message dated Tue, 19 Apr 2022 22:20:59 + with message-id and subject line Bug#1009396: fixed in python-m2r 0.2.1-7.1 has caused the Debian Bug report #1009396, regarding python-m2r: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.10 returned exit code 13 to be marked

Bug#1009003: marked as done (Please be prepared for hmat-oss upcoming transition)

Your message dated Tue, 19 Apr 2022 21:50:06 + with message-id and subject line Bug#1009003: fixed in openturns 1.18-2 has caused the Debian Bug report #1009003, regarding Please be prepared for hmat-oss upcoming transition to be marked as done. This means that you claim that the problem has

Processed: tagging 1004913

Processing commands for cont...@bugs.debian.org: > tags 1004913 + sid bookworm Bug #1004913 [python-fysom] python-fysom: incompatible import from collections in py3.10 Added tag(s) bookworm and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 1004913:

Processed: tagging 1004446

Processing commands for cont...@bugs.debian.org: > tags 1004446 + sid bookworm Bug #1004446 {Done: Stefano Rivera } [cdist] cdist: FTBFS against python 3.10 Added tag(s) sid and bookworm. > thanks Stopping processing here. Please contact me if you need assistance. -- 1004446:

Bug#1009886: cargo: autopkgtest failure on ppc64el

Source: cargo Version: 0.57.0-5 Severity: serious X-Debbugs-Cc: sramac...@debian.org cargo fails to migrate due to an autopkgtest failure on ppc64el: error: could not compile `cargo` due to previous error warning: build failed, waiting for other jobs to finish... error: linking with `cc` failed:

Bug#1009885: qbittorrent:src fails to build using dpkg-buildpackage, reports it can't find '-l-pthread'

Source: qbittorrent Version: 4.4.2-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: raphael.marion.pilg...@gmail.com Relevant part of the build log: linking qbittorrent-nox /usr/bin/ld : ne peut pas trouver -l-pthread :

Bug#1009541: marked as done (node-lexical-scope: FTBFS: ERROR: Coverage for statements (91.11%) does not meet global threshold (100%))

Your message dated Tue, 19 Apr 2022 21:03:47 + with message-id and subject line Bug#1009541: fixed in node-lexical-scope 1.2.0+dfsg1-6 has caused the Debian Bug report #1009541, regarding node-lexical-scope: FTBFS: ERROR: Coverage for statements (91.11%) does not meet global threshold (100%)

Bug#1009498: marked as done (node-create-require: FTBFS: ERROR: Coverage for statements (54.54%) does not meet global threshold (100%))

Your message dated Tue, 19 Apr 2022 21:03:42 + with message-id and subject line Bug#1009498: fixed in node-create-require 1.1.1-4 has caused the Debian Bug report #1009498, regarding node-create-require: FTBFS: ERROR: Coverage for statements (54.54%) does not meet global threshold (100%) to

Bug#1009541: marked as pending in node-lexical-scope

Control: tag -1 pending Hello, Bug #1009541 in node-lexical-scope reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#1009541 marked as pending in node-lexical-scope

Processing control commands: > tag -1 pending Bug #1009541 [src:node-lexical-scope] node-lexical-scope: FTBFS: ERROR: Coverage for statements (91.11%) does not meet global threshold (100%) Added tag(s) pending. -- 1009541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009541 Debian Bug

Bug#1009498: marked as pending in node-create-require

Control: tag -1 pending Hello, Bug #1009498 in node-create-require reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#1009498 marked as pending in node-create-require

Processing control commands: > tag -1 pending Bug #1009498 [src:node-create-require] node-create-require: FTBFS: ERROR: Coverage for statements (54.54%) does not meet global threshold (100%) Added tag(s) pending. -- 1009498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009498 Debian Bug

Processed: Re: Bug#1009680: ghostscript breaks ocrmypdf autopkgtest: seemingly multiple issues

Processing commands for cont...@bugs.debian.org: > found 1009680 9.56.0~dfsg-1 Bug #1009680 [ghostscript] Ghostscript 9.56 removes hidden (e.g. OCR) text layers when refrying with NEWPDF=true Marked as found in versions ghostscript/9.56.0~dfsg-1. > thanks Stopping processing here. Please

Bug#1009875: marked as done (libtorrent-rasterbar-dev: pkg-config --libs is wrong, leads to FTBFS)

Your message dated Tue, 19 Apr 2022 19:18:46 + with message-id and subject line Bug#1009875: fixed in libtorrent-rasterbar 2.0.6-3 has caused the Debian Bug report #1009875, regarding libtorrent-rasterbar-dev: pkg-config --libs is wrong, leads to FTBFS to be marked as done. This means that

Processed: severity of 1009003 is serious

Processing commands for cont...@bugs.debian.org: > severity 1009003 serious Bug #1009003 [src:openturns] Please be prepared for hmat-oss upcoming transition Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1009003:

Bug#999297: marked as done (screentest: missing required debian/rules targets build-arch and/or build-indep)

Your message dated Tue, 19 Apr 2022 18:04:55 + with message-id and subject line Bug#999297: fixed in screentest 2.0-3 has caused the Debian Bug report #999297, regarding screentest: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you

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

Your message dated Tue, 19 Apr 2022 18:04:55 + with message-id and subject line Bug#965813: fixed in screentest 2.0-3 has caused the Debian Bug report #965813, regarding screentest: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that

Bug#1003045: libreoffice: Since testing update on Jan 2, 2021, libreoffice doesn't start.

Hi, Am 17.04.22 um 18:47 schrieb yg2709: Package: libreoffice Followup-For: Bug #1003045 X-Debbugs-Cc: yg2...@hotmail.com Dear Maintainer, Probbing at a VM debian testing (12), checking with MATE (1.26.0), after upgrading all versions (from 1:7.2.4-1 thru 1:7.3.1-1), it opens sucessfully.

Processed: Re: Bug#1009844: debhelper: Build failed with dh_installalternatives: error: Alternative ...

Processing control commands: > affects -1 src:xterm Bug #1009844 [debhelper] debhelper: Build failed with dh_installalternatives: error: Alternative ... Added indication that 1009844 affects src:xterm > severity -1 serious Bug #1009844 [debhelper] debhelper: Build failed with

Bug#1009875: libtorrent-rasterbar-dev: pkg-config --libs is wrong, leads to FTBFS

Package: libtorrent-rasterbar-dev Version: 2.0.6-2 Severity: grave X-Debbugs-Cc: none, Hilko Bengen Dear Maintainer, nbdkit which build-depends on libtorrent-rasterbar-dev fails to build from source: , | Making all in torrent | make[3]: Entering directory

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

Your message dated Tue, 19 Apr 2022 17:33:58 + with message-id and subject line Bug#965418: fixed in asql 1.6-1.2 has caused the Debian Bug report #965418, regarding asql: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that the

Bug#999113: marked as done (asql: missing required debian/rules targets build-arch and/or build-indep)

Your message dated Tue, 19 Apr 2022 17:33:58 + with message-id and subject line Bug#999113: fixed in asql 1.6-1.2 has caused the Debian Bug report #999113, regarding asql: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you claim

Bug#1009872: dovecot-core: postinst fails when snakeoil cert is removed

Package: dovecot-core Version: 1:2.3.13+dfsg1-2 Severity: serious X-Debbugs-Cc: jcris...@debian.org This bit of dovecot-core.postinst breaks (at least on the second invocation) if the snakeoil cert or key don't exist: test -e returns false, but ln -s fails because the symlink is already there:

Processed: Re: clang-14: address sanitizer creates broken binaries

Processing control commands: > severity -1 important Bug #1008309 [clang-14] clang-14: address sanitizer creates broken binaries Severity set to 'important' from 'grave' -- 1008309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008309 Debian Bug Tracking System Contact

Bug#1009463: marked as done (fonts-junicode: FTBFS: segfaults)

Your message dated Tue, 19 Apr 2022 16:07:17 +0200 with message-id <87da8158a4aed0c65f4e821864cbf...@phys.ethz.ch> and subject line fonts-junicode: FTBFS: segfaults has caused the Debian Bug report #1009463, regarding fonts-junicode: FTBFS: segfaults to be marked as done. This means that you

Processed: Re: [Debian-on-mobile-maintainers] Bug#1007115: squeekboard covers applications in landscape

Processing commands for cont...@bugs.debian.org: > forwarded 1007115 > https://gitlab.gnome.org/World/Phosh/squeekboard/-/issues/327 Bug #1007115 [squeekboard] squeekboard covers applications in landscape Set Bug forwarded-to-address to

Processed: Re: meson: gnome module incorrectly requires gtk4-update-icon-cache

Processing commands for cont...@bugs.debian.org: > affects 1008189 src:gnome-shell-extension-manager Bug #1008189 [src:meson] meson: gnome module incorrectly requires gtk4-update-icon-cache Added indication that 1008189 affects src:gnome-shell-extension-manager > End of message, stopping

Bug#1007115: [Debian-on-mobile-maintainers] Bug#1007115: squeekboard covers applications in landscape

Control: forwarded -1 https://gitlab.gnome.org/World/Phosh/squeekboard/-/issues/327 The upstream report suggests this issue was fixed in the 1.17.1 release. Thank you, Jeremy Bicha

Bug#1009577: marked as done (node-browser-unpack: FTBFS: ERROR: Coverage for statements (80.32%) does not meet global threshold (100%))

Your message dated Tue, 19 Apr 2022 11:49:31 + with message-id and subject line Bug#1009577: fixed in node-browser-unpack 1.4.2-4 has caused the Debian Bug report #1009577, regarding node-browser-unpack: FTBFS: ERROR: Coverage for statements (80.32%) does not meet global threshold (100%) to

Bug#1009602: marked as done (node-optimist: FTBFS: ERROR: Coverage for statements (77.24%) does not meet global threshold (100%))

Your message dated Tue, 19 Apr 2022 11:49:37 + with message-id and subject line Bug#1009602: fixed in node-optimist 0.6.1+~0.0.30-2 has caused the Debian Bug report #1009602, regarding node-optimist: FTBFS: ERROR: Coverage for statements (77.24%) does not meet global threshold (100%) to be

Bug#1009577: marked as pending in node-browser-unpack

Control: tag -1 pending Hello, Bug #1009577 in node-browser-unpack reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#1009577 marked as pending in node-browser-unpack

Processing control commands: > tag -1 pending Bug #1009577 [src:node-browser-unpack] node-browser-unpack: FTBFS: ERROR: Coverage for statements (80.32%) does not meet global threshold (100%) Added tag(s) pending. -- 1009577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009577 Debian Bug

Processed: Bug#1009602 marked as pending in node-optimist

Processing control commands: > tag -1 pending Bug #1009602 [src:node-optimist] node-optimist: FTBFS: ERROR: Coverage for statements (77.24%) does not meet global threshold (100%) Added tag(s) pending. -- 1009602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009602 Debian Bug Tracking

Bug#1009602: marked as pending in node-optimist

Control: tag -1 pending Hello, Bug #1009602 in node-optimist reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#1009814: marked as done (android-platform-tools_29.0.6-8_s390x-buildd.changes REJECTED)

Your message dated Tue, 19 Apr 2022 18:16:07 +0900 with message-id and subject line Re: android-platform-tools_29.0.6-8_s390x-buildd.changes REJECTED has caused the Debian Bug report #1009814, regarding android-platform-tools_29.0.6-8_s390x-buildd.changes REJECTED to be marked as done. This

Bug#1009204: marked as done (vdirsyncer: (autopkgtest) needs update for python3.10: python3.9: command not found)

Your message dated Tue, 19 Apr 2022 09:19:41 + with message-id and subject line Bug#1009204: fixed in vdirsyncer 0.18.0-6.1 has caused the Debian Bug report #1009204, regarding vdirsyncer: (autopkgtest) needs update for python3.10: python3.9: command not found to be marked as done. This

Bug#1008426: marked as done (h2o: FTBFS: wrong number of arguments (given 2, expected 1))

Your message dated Tue, 19 Apr 2022 09:03:50 + with message-id and subject line Bug#1008426: fixed in h2o 2.2.5+dfsg2-6.2 has caused the Debian Bug report #1008426, regarding h2o: FTBFS: wrong number of arguments (given 2, expected 1) to be marked as done. This means that you claim that the

Bug#1009516: marked as done (node-buffer-crc32: FTBFS: ERROR: Coverage for branches (81.25%) does not meet global threshold (100%))

Your message dated Tue, 19 Apr 2022 07:34:17 + with message-id and subject line Bug#1009516: fixed in node-buffer-crc32 0.2.13+~0.2.0-2 has caused the Debian Bug report #1009516, regarding node-buffer-crc32: FTBFS: ERROR: Coverage for branches (81.25%) does not meet global threshold (100%)

Bug#1009516: marked as pending in node-buffer-crc32

Control: tag -1 pending Hello, Bug #1009516 in node-buffer-crc32 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#1009516 marked as pending in node-buffer-crc32

Processing control commands: > tag -1 pending Bug #1009516 [src:node-buffer-crc32] node-buffer-crc32: FTBFS: ERROR: Coverage for branches (81.25%) does not meet global threshold (100%) Added tag(s) pending. -- 1009516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009516 Debian Bug

Bug#1008781: nemiver: Intent to remove from Debian

eremy Bicha wrote: > I intend to file a removal bug for nemiver soon. It has failed to > build for more than a year. It wasn't autoremoved sooner because it > was included in one of the metapackages in meta-gnome3. I agree, it's time to let it go. If you are already in the process of asking for

Bug#1009580: marked as done (node-inline-source-map: FTBFS: ERROR: Coverage for statements (98.18%) does not meet global threshold (100%))

Your message dated Tue, 19 Apr 2022 06:33:55 + with message-id and subject line Bug#1009580: fixed in node-inline-source-map 0.6.2~git-7 has caused the Debian Bug report #1009580, regarding node-inline-source-map: FTBFS: ERROR: Coverage for statements (98.18%) does not meet global threshold

Bug#1009565: marked as done (node-module-deps: FTBFS: ERROR: Coverage for statements (86.71%) does not meet global threshold (100%))

Your message dated Tue, 19 Apr 2022 06:34:00 + with message-id and subject line Bug#1009565: fixed in node-module-deps 6.2.3-3 has caused the Debian Bug report #1009565, regarding node-module-deps: FTBFS: ERROR: Coverage for statements (86.71%) does not meet global threshold (100%) to be

Bug#1009538: marked as done (node-detective: FTBFS: ERROR: Coverage for statements (92.15%) does not meet global threshold (100%))

Your message dated Tue, 19 Apr 2022 06:33:50 + with message-id and subject line Bug#1009538: fixed in node-detective 5.2.0-5 has caused the Debian Bug report #1009538, regarding node-detective: FTBFS: ERROR: Coverage for statements (92.15%) does not meet global threshold (100%) to be marked

Bug#1009513: marked as done (node-object-inspect: FTBFS: ERROR: Coverage for statements (60.76%) does not meet global threshold (100%))

Your message dated Tue, 19 Apr 2022 06:34:05 + with message-id and subject line Bug#1009513: fixed in node-object-inspect 1.11.0+~cs1.8.1-3 has caused the Debian Bug report #1009513, regarding node-object-inspect: FTBFS: ERROR: Coverage for statements (60.76%) does not meet global threshold

Bug#1009507: marked as done (node-deps-sort: FTBFS: ERROR: Coverage for statements (95.23%) does not meet global threshold (100%))

Your message dated Tue, 19 Apr 2022 06:33:45 + with message-id and subject line Bug#1009507: fixed in node-deps-sort 2.0.1-3 has caused the Debian Bug report #1009507, regarding node-deps-sort: FTBFS: ERROR: Coverage for statements (95.23%) does not meet global threshold (100%) to be marked

Processed: Bug#1009565 marked as pending in node-module-deps

Processing control commands: > tag -1 pending Bug #1009565 [src:node-module-deps] node-module-deps: FTBFS: ERROR: Coverage for statements (86.71%) does not meet global threshold (100%) Added tag(s) pending. -- 1009565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009565 Debian Bug

Bug#1009565: marked as pending in node-module-deps

Control: tag -1 pending Hello, Bug #1009565 in node-module-deps reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#1009513 marked as pending in node-object-inspect

Processing control commands: > tag -1 pending Bug #1009513 [src:node-object-inspect] node-object-inspect: FTBFS: ERROR: Coverage for statements (60.76%) does not meet global threshold (100%) Added tag(s) pending. -- 1009513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009513 Debian Bug

Processed: Bug#1009580 marked as pending in node-inline-source-map

Processing control commands: > tag -1 pending Bug #1009580 [src:node-inline-source-map] node-inline-source-map: FTBFS: ERROR: Coverage for statements (98.18%) does not meet global threshold (100%) Added tag(s) pending. -- 1009580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009580

Bug#1009513: marked as pending in node-object-inspect

Control: tag -1 pending Hello, Bug #1009513 in node-object-inspect reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#1009580: marked as pending in node-inline-source-map

Control: tag -1 pending Hello, Bug #1009580 in node-inline-source-map reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#1009592: marked as done (node-process-nextick-args: FTBFS: ERROR: Coverage for statements (10%) does not meet global threshold (100%))

Your message dated Tue, 19 Apr 2022 06:19:36 + with message-id and subject line Bug#1009592: fixed in node-process-nextick-args 2.0.1-3 has caused the Debian Bug report #1009592, regarding node-process-nextick-args: FTBFS: ERROR: Coverage for statements (10%) does not meet global threshold

Bug#1009556: marked as done (node-invariant: FTBFS: ERROR: Coverage for statements (81.25%) does not meet global threshold (100%))

Your message dated Tue, 19 Apr 2022 06:19:19 + with message-id and subject line Bug#1009556: fixed in node-invariant 2.2.4-2 has caused the Debian Bug report #1009556, regarding node-invariant: FTBFS: ERROR: Coverage for statements (81.25%) does not meet global threshold (100%) to be marked

Bug#1009559: marked as done (node-falafel: FTBFS: ERROR: Coverage for statements (98.11%) does not meet global threshold (100%))

Your message dated Tue, 19 Apr 2022 06:19:13 + with message-id and subject line Bug#1009559: fixed in node-falafel 2.2.4-4 has caused the Debian Bug report #1009559, regarding node-falafel: FTBFS: ERROR: Coverage for statements (98.11%) does not meet global threshold (100%) to be marked as

Bug#1009544: marked as done (node-combine-source-map: FTBFS: ERROR: Coverage for statements (93.44%) does not meet global threshold (100%))

Your message dated Tue, 19 Apr 2022 06:19:07 + with message-id and subject line Bug#1009544: fixed in node-combine-source-map 0.8.0+ds-8 has caused the Debian Bug report #1009544, regarding node-combine-source-map: FTBFS: ERROR: Coverage for statements (93.44%) does not meet global threshold

Bug#1009502: marked as done (node-block-stream: FTBFS: ERROR: Coverage for statements (98.24%) does not meet global threshold (100%))

Your message dated Tue, 19 Apr 2022 06:19:00 + with message-id and subject line Bug#1009502: fixed in node-block-stream 0.0.9-4 has caused the Debian Bug report #1009502, regarding node-block-stream: FTBFS: ERROR: Coverage for statements (98.24%) does not meet global threshold (100%) to be

Bug#1009503: marked as done (node-archy: FTBFS: ERROR: Coverage for branches (95.45%) does not meet global threshold (100%))

Your message dated Tue, 19 Apr 2022 06:18:53 + with message-id and subject line Bug#1009503: fixed in node-archy 1.0.0-5 has caused the Debian Bug report #1009503, regarding node-archy: FTBFS: ERROR: Coverage for branches (95.45%) does not meet global threshold (100%) to be marked as done.

Bug#1009486: marked as done (node-isarray: FTBFS: ERROR: Coverage for statements (66.66%) does not meet global threshold (100%))

Your message dated Tue, 19 Apr 2022 06:19:24 + with message-id and subject line Bug#1009486: fixed in node-isarray 2.0.5-4 has caused the Debian Bug report #1009486, regarding node-isarray: FTBFS: ERROR: Coverage for statements (66.66%) does not meet global threshold (100%) to be marked as

Bug#1009507: marked as pending in node-deps-sort

Control: tag -1 pending Hello, Bug #1009507 in node-deps-sort reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#1009507 marked as pending in node-deps-sort

Processing control commands: > tag -1 pending Bug #1009507 [src:node-deps-sort] node-deps-sort: FTBFS: ERROR: Coverage for statements (95.23%) does not meet global threshold (100%) Added tag(s) pending. -- 1009507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009507 Debian Bug Tracking

Processed: Bug#1009538 marked as pending in node-detective

Processing control commands: > tag -1 pending Bug #1009538 [src:node-detective] node-detective: FTBFS: ERROR: Coverage for statements (92.15%) does not meet global threshold (100%) Added tag(s) pending. -- 1009538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009538 Debian Bug Tracking

Bug#1009538: marked as pending in node-detective

Control: tag -1 pending Hello, Bug #1009538 in node-detective reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#1009486 marked as pending in node-isarray

Processing control commands: > tag -1 pending Bug #1009486 [src:node-isarray] node-isarray: FTBFS: ERROR: Coverage for statements (66.66%) does not meet global threshold (100%) Added tag(s) pending. -- 1009486: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009486 Debian Bug Tracking

Bug#1009486: marked as pending in node-isarray

Control: tag -1 pending Hello, Bug #1009486 in node-isarray reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#1009511: marked as pending in node-once

Control: tag -1 pending Hello, Bug #1009511 in node-once reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#1009511 marked as pending in node-once

Processing control commands: > tag -1 pending Bug #1009511 [src:node-once] node-once: FTBFS: ERROR: Coverage for statements (83.33%) does not meet global threshold (100%) Added tag(s) pending. -- 1009511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009511 Debian Bug Tracking System

Bug#1009559: marked as pending in node-falafel

Control: tag -1 pending Hello, Bug #1009559 in node-falafel reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#1009559 marked as pending in node-falafel

Processing control commands: > tag -1 pending Bug #1009559 [src:node-falafel] node-falafel: FTBFS: ERROR: Coverage for statements (98.11%) does not meet global threshold (100%) Added tag(s) pending. -- 1009559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009559 Debian Bug Tracking

Processed: Bug#1009502 marked as pending in node-block-stream

Processing control commands: > tag -1 pending Bug #1009502 [src:node-block-stream] node-block-stream: FTBFS: ERROR: Coverage for statements (98.24%) does not meet global threshold (100%) Added tag(s) pending. -- 1009502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009502 Debian Bug

Bug#1009502: marked as pending in node-block-stream

Control: tag -1 pending Hello, Bug #1009502 in node-block-stream reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#1009544: marked as pending in node-combine-source-map

Control: tag -1 pending Hello, Bug #1009544 in node-combine-source-map reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#1009571: marked as done (node-call-limit: FTBFS: ERROR: Coverage for statements (83.58%) does not meet global threshold (100%))

Your message dated Tue, 19 Apr 2022 06:03:50 + with message-id and subject line Bug#1009571: fixed in node-call-limit 1.1.1-3 has caused the Debian Bug report #1009571, regarding node-call-limit: FTBFS: ERROR: Coverage for statements (83.58%) does not meet global threshold (100%) to be

Processed: Bug#1009544 marked as pending in node-combine-source-map

Processing control commands: > tag -1 pending Bug #1009544 [src:node-combine-source-map] node-combine-source-map: FTBFS: ERROR: Coverage for statements (93.44%) does not meet global threshold (100%) Added tag(s) pending. -- 1009544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009544

Bug#1009530: marked as done (node-arrify: FTBFS: ERROR: Coverage for statements (90.9%) does not meet global threshold (100%))

Your message dated Tue, 19 Apr 2022 06:03:45 + with message-id and subject line Bug#1009530: fixed in node-arrify 2.0.1-3 has caused the Debian Bug report #1009530, regarding node-arrify: FTBFS: ERROR: Coverage for statements (90.9%) does not meet global threshold (100%) to be marked as

Bug#1009545: marked as done (node-jsonstream: FTBFS: ERROR: Coverage for statements (50.89%) does not meet global threshold (100%))

Your message dated Tue, 19 Apr 2022 06:03:55 + with message-id and subject line Bug#1009545: fixed in node-jsonstream 1.3.5-2 has caused the Debian Bug report #1009545, regarding node-jsonstream: FTBFS: ERROR: Coverage for statements (50.89%) does not meet global threshold (100%) to be

Bug#1009556: marked as pending in node-invariant

Control: tag -1 pending Hello, Bug #1009556 in node-invariant reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#1009556 marked as pending in node-invariant

Processing control commands: > tag -1 pending Bug #1009556 [src:node-invariant] node-invariant: FTBFS: ERROR: Coverage for statements (81.25%) does not meet global threshold (100%) Added tag(s) pending. -- 1009556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009556 Debian Bug Tracking

Bug#1009592: marked as pending in node-process-nextick-args

Control: tag -1 pending Hello, Bug #1009592 in node-process-nextick-args reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#1009592 marked as pending in node-process-nextick-args

Processing control commands: > tag -1 pending Bug #1009592 [src:node-process-nextick-args] node-process-nextick-args: FTBFS: ERROR: Coverage for statements (10%) does not meet global threshold (100%) Added tag(s) pending. -- 1009592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009592

Processed: Bug#1009503 marked as pending in node-archy

Processing control commands: > tag -1 pending Bug #1009503 [src:node-archy] node-archy: FTBFS: ERROR: Coverage for branches (95.45%) does not meet global threshold (100%) Added tag(s) pending. -- 1009503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009503 Debian Bug Tracking System

Bug#1009503: marked as pending in node-archy

Control: tag -1 pending Hello, Bug #1009503 in node-archy reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: