Processing control commands:
> tag -1 pending
Bug #1009530 [src:node-arrify] node-arrify: FTBFS: ERROR: Coverage for
statements (90.9%) does not meet global threshold (100%)
Added tag(s) pending.
--
1009530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009530
Debian Bug Tracking System
Control: tag -1 pending
Hello,
Bug #1009530 in node-arrify 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:
Processing control commands:
> tag -1 pending
Bug #1009571 [src:node-call-limit] node-call-limit: FTBFS: ERROR: Coverage for
statements (83.58%) does not meet global threshold (100%)
Added tag(s) pending.
--
1009571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009571
Debian Bug Tracking
Control: tag -1 pending
Hello,
Bug #1009571 in node-call-limit 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:
Control: tag -1 pending
Hello,
Bug #1009545 in node-jsonstream 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:
Processing control commands:
> tag -1 pending
Bug #1009545 [src:node-jsonstream] node-jsonstream: FTBFS: ERROR: Coverage for
statements (50.89%) does not meet global threshold (100%)
Added tag(s) pending.
--
1009545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009545
Debian Bug Tracking
> I've prepared an NMU for vdirsyncer (versioned as 0.18.0-6.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.
As a team member, feel free to reschedule this to 0-day.
I've merged your git tree.
SR
--
Stefano Rivera
http://tumbleweed.org.za/
+1
Your message dated Tue, 19 Apr 2022 03:33:51 +
with message-id
and subject line Bug#1009240: fixed in esys-particle 2.3.5+dfsg2-4.1
has caused the Debian Bug report #1009240,
regarding esys-particle: autopkgtest regression since rebuild for python3.10 as
default
to be marked as done.
This
Your message dated Tue, 19 Apr 2022 03:19:34 +
with message-id
and subject line Bug#981822: fixed in rust-bytemuck 1.9.1-1
has caused the Debian Bug report #981822,
regarding librust-bytemuck-dev: Depends: librust-bytemuck-derive-1+default-dev
but it is not installable
to be marked as done.
Your message dated Tue, 19 Apr 2022 03:19:54 +
with message-id
and subject line Bug#974117: fixed in rust-image 0.23.14-1
has caused the Debian Bug report #974117,
regarding rust-image: FTBFS build-depends on librust-tiff-0.3+default-dev
to be marked as done.
This means that you claim that
Control: tags 999034 + patch
Control: tags 999034 + pending
Dear maintainer,
I've prepared an NMU for squidtaild (versioned as 2.1a6-6.2) and
uploaded it to DELAYED/22. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru squidtaild-2.1a6/debian/changelog
Processing control commands:
> tags 999034 + patch
Bug #999034 [src:squidtaild] squidtaild: missing required debian/rules targets
build-arch and/or build-indep
Added tag(s) patch.
> tags 999034 + pending
Bug #999034 [src:squidtaild] squidtaild: missing required debian/rules targets
build-arch
He Andreas, thanks for the feedback!
Le 2022-04-17 à 10 h 42, Andreas Metzler a écrit :
Yes, a rebuild will get a binary which works against the new
library, however (partial) upgrades from bookworm won't work.
BTW, the symbol file seems to be wrong:
| h_execute_query_sqlite@Base 1.4.15
the
Your message dated Tue, 19 Apr 2022 01:18:47 +
with message-id
and subject line Bug#999095: fixed in clif 0.93-9.2
has caused the Debian Bug report #999095,
regarding clif: missing required debian/rules targets build-arch and/or
build-indep
to be marked as done.
This means that you claim
Your message dated Tue, 19 Apr 2022 01:18:47 +
with message-id
and subject line Bug#965462: fixed in clif 0.93-9.2
has caused the Debian Bug report #965462,
regarding clif: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.
This means that you claim that the
Processing control commands:
> tags 999018 + patch
Bug #999018 [src:xvier] xvier: missing required debian/rules targets build-arch
and/or build-indep
Added tag(s) patch.
> tags 999018 + pending
Bug #999018 [src:xvier] xvier: missing required debian/rules targets build-arch
and/or build-indep
Processing control commands:
> tags 965595 + patch
Bug #965595 [src:info2www] info2www: Removal of obsolete debhelper compat 5 and
6 in bookworm
Added tag(s) patch.
> tags 965595 + pending
Bug #965595 [src:info2www] info2www: Removal of obsolete debhelper compat 5 and
6 in bookworm
Added tag(s)
Control: tags 999018 + patch
Control: tags 999018 + pending
Dear maintainer,
I've prepared an NMU for xvier (versioned as 1.0-7.7) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards.
diff -u xvier-1.0/debian/changelog xvier-1.0/debian/changelog
---
Control: tags 965595 + patch
Control: tags 965595 + pending
Dear maintainer,
I've prepared an NMU for info2www (versioned as 1.2.2.9-24.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards.
diff -u info2www-1.2.2.9/debian/changelog
Your message dated Mon, 18 Apr 2022 23:18:46 +
with message-id
and subject line Bug#999015: fixed in clamassassin 1.2.4-1.2
has caused the Debian Bug report #999015,
regarding clamassassin: missing required debian/rules targets build-arch and/or
build-indep
to be marked as done.
This means
Your message dated Mon, 18 Apr 2022 23:18:46 +
with message-id
and subject line Bug#965468: fixed in clamassassin 1.2.4-1.2
has caused the Debian Bug report #965468,
regarding clamassassin: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.
This means that you
} > Upstream changed paths for the framework manifest files in recent
} > releases and did not maintain backward compatibility links resulting
} > in 4.3.4 no longer being able to install the frameworks.
}
} Had a quick look, and it's worse than that. Not just a change in paths,
} but an entire
Your message dated Mon, 18 Apr 2022 20:52:29 +
with message-id
and subject line Bug#1009054: fixed in openshot-qt 2.6.1+dfsg1-2
has caused the Debian Bug report #1009054,
regarding Just crashes
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Mon, 18 Apr 2022 20:48:48 +
with message-id
and subject line Bug#965457: fixed in choosewm 0.1.6-3.1
has caused the Debian Bug report #965457,
regarding choosewm: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.
This means that you claim that
Control: tag -1 pending
Hello,
Bug #1009054 in openshot-qt 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:
Processing control commands:
> tag -1 pending
Bug #1009054 [openshot-qt] Just crashes
Added tag(s) pending.
--
1009054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009054
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
This bug is blocking openimageio, which blocks blender. Can this be
fixed, is it still not reproducible?
Best Regards,
Jonathan Rubenstein
la...@debian.org dixit:
>On my bullseye machine sudo rpm -qa creates the subdirectory in
>/root/.rpmdb as root. So IMO this works correct.
Not with !env_reset in sudoers, though :( as I wrote in the last mail.
bye,
//mirabilos
--
Gestern Nacht ist mein IRC-Netzwerk explodiert. Ich hatte nicht
Package: python3-pylsp-flake8
Version: 0.4.0-2
Severity: serious
The debian/copyright file for this package currently does not state
the location of the upstream sources. (Marked "serious" because this
is a violation of Policy section 12.5.)
I'm happy to fix this myself if you would like me to.
Processing commands for cont...@bugs.debian.org:
> found 1009415 0.5.3+ds-1
Bug #1009415 [src:gemmi] gemmi: FTBFS with tao-pegtl v3
Marked as found in versions gemmi/0.5.3+ds-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1009415:
Processing control commands:
> close -1 1.3.1-1
Bug #1009833 [src:connectagram] src:connectagram: fails to migrate to testing
for too long: new build dependency not available on s390x
Marked as fixed in versions connectagram/1.3.1-1.
Bug #1009833 [src:connectagram] src:connectagram: fails to
Source: connectagram
Version: 1.2.11-2
Severity: serious
Control: close -1 1.3.1-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 60
Processing control commands:
> close -1 1.6.1.1-1
Bug #1009832 [src:tanglet] src:tanglet: fails to migrate to testing for too
long: new build dependency not available on s390x
Marked as fixed in versions tanglet/1.6.1.1-1.
Bug #1009832 [src:tanglet] src:tanglet: fails to migrate to testing for
Source: tanglet
Version: 1.5.6-1
Severity: serious
Control: close -1 1.6.1.1-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 60 days
Hi,
The FTBFS is reproducable `debuild -uc -us`.
Below is a screenshot of my repair attempt.
8<--8<--8<--8<--
stappers@myhost:~/src/lirc
$ cd python-pkg/tests/
stappers@myhost:~/src/lirc/python-pkg/tests
$ python3 -m unittest discover && rm backend.log
E
Processing control commands:
> close -1 2.2.0-1
Bug #1009831 [src:tetzle] src:tetzle: fails to migrate to testing for too long:
new build dependency not available on s390x
Marked as fixed in versions tetzle/2.2.0-1.
Bug #1009831 [src:tetzle] src:tetzle: fails to migrate to testing for too long:
Source: tetzle
Version: 2.1.6-1
Severity: serious
Control: close -1 2.2.0-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 60 days as
Processing control commands:
> close -1 2.2+ds1-1
Bug #1009830 [src:uncalled] src:uncalled: fails to migrate to testing for too
long: new build-dependency doesn't migrate
Marked as fixed in versions uncalled/2.2+ds1-1.
Bug #1009830 [src:uncalled] src:uncalled: fails to migrate to testing for too
Source: uncalled
Version: 2.2+ds-3
Severity: serious
Control: close -1 2.2+ds1-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 60 days
Processing commands for cont...@bugs.debian.org:
> affects 1008189 src:ghex
Bug #1008189 [src:meson] meson: gnome module incorrectly requires
gtk4-update-icon-cache
Added indication that 1008189 affects src:ghex
>
End of message, stopping processing here.
Please contact me if you need
Package: hfst
Version: 3.16.0-2
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
hfst is currently not able to migrate due to dependency issues on armel
and mipsel:
Issues preventing migration:
∙ ∙ Impossible Depends: hfst -> libfst8/1.6.3-2/armel
∙ ∙ Impossible Depends: hfst ->
On Mon, Apr 18, 2022 at 07:46:34PM +0200, Sascha Steinbiss wrote:
> Hi,
> > > Do you think we should wait for this to be fixed? As I said before I (just
> > > from my practical point of view) would be in favor of just removing the
> > > problematic architectures.
> > I have no opinion on this.
On Mon, Apr 18, 2022 at 06:32:07PM +0200, Thomas Lange wrote:
> > On Mon, 18 Apr 2022 16:16:18 +0300, Peter Pentchev
> > said:
>
>
> > If you run sudo without the "set_home" option, thus making it preserve
> > the HOME environment variable, rpm run as root with HOME set to
>
Hm, good question. What I'd start doing is looking at the
~/.cache/chromium and ~/.config/chromium snapshots, making copies, and
then trying to run chromium with random stuff deleted.
For example, on my system I have ~/.cache/chromium/Profile
1/old_Cache_000 and ~/.cache/chromium/System
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package lxqt-build-tools
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user
Hi,
Do you think we should wait for this to be fixed? As I said before I (just
from my practical point of view) would be in favor of just removing the
problematic architectures.
I have no opinion on this. But if you want the package to be releasable,
you will need to change it so that it is
Source: halide
Version: 14.0.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
halide FTBFS on arm64:
317/569 Test #317: correctness_strided_load ...
Passed1.12 sec
Start 318:
Source: gnss-sdr
Version: 0.0.16-1
Severity: serious
Tags: sid bookworm
gnss-sdr's autopkgtest fail with gr-osmosdr 0.2.3-6
autopkgtest [14:10:33]: test testgnsssdr: [---
terminate called after throwing an instance of 'std::runtime_error'
what(): rpcmanager: Aggregator not
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:r-bioc-biostrings
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:libpdf-builder-perl
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user
Package: snort
Version: 2.9.15.1-5
Severity: critical
Tags: security upstream
Justification: root security hole
X-Debbugs-Cc: sec-advis...@ait.ac.at
Dear Maintainer,
The path of the logdirectory of snort can be manipulated by user
Snort in Debian Bullseye:
# ls -ld /var/log/snort/
drwxr-s--- 3
Processing commands for cont...@bugs.debian.org:
> severity 981680 important
Bug #981680 [src:golang-github-canonical-go-dqlite]
golang-github-canonical-go-dqlite FTBFS: test failures
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need
Control: severtiy -1 important
On Fri, 26 Nov 2021 14:43:09 +0200 Adrian Bunk wrote:
> Control: reopen -1
>
> On Fri, Nov 26, 2021 at 12:21:09PM +, Debian Bug Tracking System wrote:
> >...
> > golang-github-canonical-go-dqlite (1.10.1-1) unstable; urgency=medium
> >...
> >* Add patches
Control: tags -1 patch
On 2022-04-02 Adrian Bunk wrote:
> Package: freeradius-python3
> Version: 3.0.25+dfsg-1
> Severity: serious
> Forwarded: https://github.com/FreeRADIUS/freeradius-server/issues/4441
> Package: freeradius-python3
> Version: 3.0.25+dfsg-1+b1
> Depends: freeradius (=
Processing control commands:
> tags -1 patch
Bug #1008832 [freeradius-python3] freeradius-python3: Module not linked with
libpython when built with Python 3.10
Added tag(s) patch.
--
1008832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008832
Debian Bug Tracking System
Contact
Processing control commands:
> tags 965480 + patch
Bug #965480 [src:d52] d52: Removal of obsolete debhelper compat 5 and 6 in
bookworm
Added tag(s) patch.
> tags 965480 + pending
Bug #965480 [src:d52] d52: Removal of obsolete debhelper compat 5 and 6 in
bookworm
Added tag(s) pending.
--
Control: tags 965480 + patch
Control: tags 965480 + pending
Dear maintainer,
I've prepared an NMU for d52 (versioned as 3.4.1-1.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards.
diff -u d52-3.4.1/debian/changelog d52-3.4.1/debian/changelog
---
> On Mon, 18 Apr 2022 16:16:18 +0300, Peter Pentchev
> said:
> If you run sudo without the "set_home" option, thus making it preserve
> the HOME environment variable, rpm run as root with HOME set to
> /home/something will indeed do the wrong thing.
I have no set_home entry
Processing control commands:
> notforwarded -1
Bug #997767 [src:open-ath9k-htc-firmware] open-ath9k-htc-firmware: FTBFS:
patching fails
Unset Bug forwarded-to-address
> tags -1 - pending
Bug #997767 [src:open-ath9k-htc-firmware] open-ath9k-htc-firmware: FTBFS:
patching fails
Removed tag(s)
Control: notforwarded -1
Control: tags -1 - pending
On Sun, 24 Oct 2021 13:05:15 + John Scott wrote:
The fix is currently waiting in the NEW queue.
It seems the upload has not passed the NEW queue.
Can you please hand in the fix again?
I would very much like this package to be available
Control: tags 1009204 + patch
Control: tags 1009204 + pending
Dear maintainer,
I've prepared an NMU for vdirsyncer (versioned as 0.18.0-6.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
I also prepared a repository update at
Processing control commands:
> tags 1009204 + patch
Bug #1009204 [src:vdirsyncer] vdirsyncer: (autopkgtest) needs update for
python3.10: python3.9: command not found
Added tag(s) patch.
> tags 1009204 + pending
Bug #1009204 [src:vdirsyncer] vdirsyncer: (autopkgtest) needs update for
python3.10:
Source: android-platform-tools
Version: 29.0.6-8
Severity: serious
On 2022-04-18 14:49, Debian FTP Masters wrote:
>
>
> Version check failed:
> Your upload included the binary package android-sdk-libsparse-utils, version
> 29.0.6-8, for s390x,
> however testing already has version
Your message dated Mon, 18 Apr 2022 14:44:43 +0100
with message-id <3cf2c1b4-5993-c24f-f33b-302022506...@debian.org>
and subject line close
has caused the Debian Bug report #1009472,
regarding fckit: FTBFS: dh_auto_test: error: cd debian/build-gfortran && make
-j8 test ARGS\+=-j8 returned exit
Your message dated Mon, 18 Apr 2022 14:33:26 +0100
with message-id <8c614014-ee02-1cef-3e5b-852da8e4a...@debian.org>
and subject line Close - transient build errror
has caused the Debian Bug report #1009435,
regarding ecbuild: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make
-j8 test
On Mon, Apr 18, 2022 at 02:56:37PM +0200, la...@debian.org wrote:
>
> > On one side, “rpm -qa” will create the directory in my home directory as
> > myself, but “sudo rpm -qa” will do the wrong thing.
>
> What do you mean by wrong?
>
> On my bullseye machine sudo rpm -qa creates the
Your message dated Mon, 18 Apr 2022 14:47:18 +0200
with message-id
and subject line closed by previous spades upload
has caused the Debian Bug report #1009203,
regarding unicycler: (autopkgtest) needs update for python3.10: fails on
deprecation warning on stderr
to be marked as done.
This means
> On one side, “rpm -qa” will create the directory in my home directory as
> myself, but “sudo rpm -qa” will do the wrong thing.
What do you mean by wrong?
On my bullseye machine sudo rpm -qa creates the subdirectory in
/root/.rpmdb as root. So IMO this works correct.
rpm -qa without sudo
Processing control commands:
> reassign -1 src:spades 3.13.1+dfsg-2
Bug #1009203 [src:unicycler] unicycler: (autopkgtest) needs update for
python3.10: fails on deprecation warning on stderr
Bug reassigned from package 'src:unicycler' to 'src:spades'.
No longer marked as found in versions
Source: pytest-salt-factories
Version: 0.907.0-4
Severity: serious
Tags: sid bookworm
pytest-salt-factories' autopkgtests fail with python3.10:
=== 229 passed, 2 skipped, 60 warnings in 133.67s (0:02:13)
autopkgtest [03:46:37]: test pytest: ---]
Your message dated Mon, 18 Apr 2022 06:33:57 +
with message-id
and subject line Bug#1009520: fixed in node-parents 1.0.1+~1.0.1-1
has caused the Debian Bug report #1009520,
regarding node-parents: FTBFS: ERROR: Coverage for statements (96.29%) does not
meet global threshold (100%)
to be
Your message dated Mon, 18 Apr 2022 06:18:59 +
with message-id
and subject line Bug#1009570: fixed in node-dashdash 2.0.0-3
has caused the Debian Bug report #1009570,
regarding node-dashdash: FTBFS: ERROR: Coverage for statements (81.9%) does not
meet global threshold (100%)
to be marked as
Your message dated Mon, 18 Apr 2022 06:19:26 +
with message-id
and subject line Bug#1009561: fixed in node-parse-base64vlq-mappings 0.1.4-7
has caused the Debian Bug report #1009561,
regarding node-parse-base64vlq-mappings: FTBFS: ERROR: Coverage for statements
(79.31%) does not meet global
Your message dated Mon, 18 Apr 2022 06:19:14 +
with message-id
and subject line Bug#1009560: fixed in node-mute-stream 0.0.8+~0.0.1-2
has caused the Debian Bug report #1009560,
regarding node-mute-stream: FTBFS: ERROR: Coverage for statements (75.36%) does
not meet global threshold (100%)
to
Your message dated Mon, 18 Apr 2022 06:19:04 +
with message-id
and subject line Bug#1009514: fixed in node-http-signature 1.3.6-2
has caused the Debian Bug report #1009514,
regarding node-http-signature: FTBFS: ERROR: Coverage for statements (88.86%)
does not meet global threshold (100%)
to
Your message dated Mon, 18 Apr 2022 06:19:20 +
with message-id
and subject line Bug#1009521: fixed in node-nopt 5.0.0-3
has caused the Debian Bug report #1009521,
regarding node-nopt: FTBFS: ERROR: Coverage for statements (87.95%) does not
meet global threshold (100%)
to be marked as done.
Processing control commands:
> tag -1 pending
Bug #1009520 [src:node-parents] node-parents: FTBFS: ERROR: Coverage for
statements (96.29%) does not meet global threshold (100%)
Added tag(s) pending.
--
1009520: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009520
Debian Bug Tracking
Control: tag -1 pending
Hello,
Bug #1009520 in node-parents 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:
Processing control commands:
> tag -1 pending
Bug #1009514 [src:node-http-signature] node-http-signature: FTBFS: ERROR:
Coverage for statements (88.86%) does not meet global threshold (100%)
Added tag(s) pending.
--
1009514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009514
Debian Bug
Control: tag -1 pending
Hello,
Bug #1009514 in node-http-signature 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:
Processing control commands:
> tag -1 pending
Bug #1009570 [src:node-dashdash] node-dashdash: FTBFS: ERROR: Coverage for
statements (81.9%) does not meet global threshold (100%)
Added tag(s) pending.
--
1009570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009570
Debian Bug Tracking
Control: tag -1 pending
Hello,
Bug #1009570 in node-dashdash 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:
Processing control commands:
> tag -1 pending
Bug #1009561 [src:node-parse-base64vlq-mappings] node-parse-base64vlq-mappings:
FTBFS: ERROR: Coverage for statements (79.31%) does not meet global threshold
(100%)
Added tag(s) pending.
--
1009561:
Control: tag -1 pending
Hello,
Bug #1009561 in node-parse-base64vlq-mappings 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:
Control: tag -1 pending
Hello,
Bug #1009560 in node-mute-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:
Processing control commands:
> tag -1 pending
Bug #1009560 [src:node-mute-stream] node-mute-stream: FTBFS: ERROR: Coverage
for statements (75.36%) does not meet global threshold (100%)
Added tag(s) pending.
--
1009560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009560
Debian Bug
Your message dated Mon, 18 Apr 2022 06:04:01 +
with message-id
and subject line Bug#1009604: fixed in node-ieee754 1.2.1-3
has caused the Debian Bug report #1009604,
regarding node-ieee754: FTBFS: ERROR: Coverage for statements (77.96%) does not
meet global threshold (100%)
to be marked as
Your message dated Mon, 18 Apr 2022 06:03:55 +
with message-id
and subject line Bug#1009534: fixed in node-bunyan 2.0.5+~cs4.4.3-2
has caused the Debian Bug report #1009534,
regarding node-bunyan: FTBFS: ERROR: Coverage for statements (60.48%) does not
meet global threshold (100%)
to be
Your message dated Mon, 18 Apr 2022 06:04:07 +
with message-id
and subject line Bug#1009501: fixed in node-immediate 3.3.0+dfsg-3
has caused the Debian Bug report #1009501,
regarding node-immediate: FTBFS: ERROR: Coverage for statements (65.68%) does
not meet global threshold (100%)
to be
Control: tag -1 pending
Hello,
Bug #1009521 in node-nopt 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:
Processing control commands:
> tag -1 pending
Bug #1009521 [src:node-nopt] node-nopt: FTBFS: ERROR: Coverage for statements
(87.95%) does not meet global threshold (100%)
Added tag(s) pending.
--
1009521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009521
Debian Bug Tracking System
91 matches
Mail list logo
