Mapping stable-security to proposed-updates.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 06 Nov 2020 16:14:17 +
Source: codemirror-js
Binary: libjs-codemirror
Architecture: source all
Version: 5.43.0-1+deb10u1
Distribution: buster-security
Urgency: high
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 12 Nov 2020 01:00:23 -0500
Source: node-propget
Architecture: source
Version: 1.1.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Andrius Merkys
Changes:
node-propget_1.1.0-3_source.changes uploaded successfully to localhost
along with the files:
node-propget_1.1.0-3.dsc
node-propget_1.1.0-3.debian.tar.xz
node-propget_1.1.0-3_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
--
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 12 Nov 2020 00:32:12 -0500
Source: node-assume
Architecture: source
Version: 2.2.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Andrius Merkys
Changes:
node-assume_2.2.0-3_source.changes uploaded successfully to localhost
along with the files:
node-assume_2.2.0-3.dsc
node-assume_2.2.0-3.debian.tar.xz
node-assume_2.2.0-3_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
--
FYI: The status of the node-moment source package
in Debian's testing distribution has changed.
Previous version: 2.29.1+ds-1
Current version: 2.29.1+ds-2
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you
FYI: The status of the node-json5 source package
in Debian's testing distribution has changed.
Previous version: 2.1.3-1
Current version: 2.1.3-2
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will
FYI: The status of the node-url-parse source package
in Debian's testing distribution has changed.
Previous version: 1.4.7-3
Current version: 1.4.7+repack-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day
FYI: The status of the node-react source package
in Debian's testing distribution has changed.
Previous version: 17.0.1+dfsg+~cs32.23.54-3
Current version: 17.0.1+dfsg+~cs102.92.74-1
--
This email is automatically generated once a day. As the installation of
new packages into testing
FYI: The status of the node-pruddy-error source package
in Debian's testing distribution has changed.
Previous version: 2.0.2-2
Current version: 2.0.2-3
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 11 Nov 2020 15:16:27 +0100
Source: highlight.js
Architecture: source
Version: 9.18.1+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Xavier Guimard
Changes:
FYI: The status of the node-original source package
in Debian's testing distribution has changed.
Previous version: 1.0.2-1
Current version: 1.0.2-2
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will
highlight.js_9.18.1+dfsg1-2_sourceonly.changes uploaded successfully to
localhost
along with the files:
highlight.js_9.18.1+dfsg1-2.dsc
highlight.js_9.18.1+dfsg1-2.debian.tar.xz
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
--
Pkg-javascript-devel mailing
FYI: The status of the gyp source package
in Debian's testing distribution has changed.
Previous version: 0.1+20200513gitcaa6002-1
Current version: 0.1+20200513gitcaa6002-2
--
This email is automatically generated once a day. As the installation of
new packages into testing happens
FYI: The status of the node-sane source package
in Debian's testing distribution has changed.
Previous version: (not in testing)
Current version: 4.1.0+~cs14.16.37-2
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple
FYI: The status of the node-propget source package
in Debian's testing distribution has changed.
Previous version: (not in testing)
Current version: 1.1.0-2
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day
FYI: The status of the node-chart.js source package
in Debian's testing distribution has changed.
Previous version: 2.9.3+dfsg-3
Current version: 2.9.4+dfsg+~cs2.10.1-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple
FYI: The status of the node-assume source package
in Debian's testing distribution has changed.
Previous version: (not in testing)
Current version: 2.2.0-2
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day
Hi Julien,
Quoting Julien Puydt (2020-11-11 21:37:48)
> you have uploaded 4.0.1 to experimental in august 2019 ; is there a
> reason why it didn't get into unstable?
>
> I ask because I want to work on shipping the TypeScript types with the
> package... and the definition are for v4.
>
> So
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 12 Nov 2020 08:09:57 +0800
Source: node-mqtt
Architecture: source
Version: 4.2.4-1
Distribution: unstable
Urgency: low
Maintainer: Debian Javascript Maintainers
Changed-By: Ying-Chun Liu (PaulLiu)
Changes:
node-mqtt_4.2.4-1_source.changes uploaded successfully to localhost
along with the files:
node-mqtt_4.2.4-1.dsc
node-mqtt_4.2.4.orig.tar.gz
node-mqtt_4.2.4-1.debian.tar.xz
node-mqtt_4.2.4-1_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 11 Nov 2020 22:38:39 +0100
Source: pkg-js-tools
Architecture: source
Version: 0.9.47
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Xavier Guimard
Changes:
pkg-js-tools_0.9.47_sourceonly.changes uploaded successfully to localhost
along with the files:
pkg-js-tools_0.9.47.dsc
pkg-js-tools_0.9.47.tar.xz
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
--
Pkg-javascript-devel mailing list
Your message dated Wed, 11 Nov 2020 21:48:34 +
with message-id
and subject line Bug#974201: fixed in node-rimraf 3.0.2-1
has caused the Debian Bug report #974201,
regarding Please ship TypeScript definitions
to be marked as done.
This means that you claim that the problem has been dealt
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 11 Nov 2020 22:20:51 +0100
Source: node-rimraf
Architecture: source
Version: 3.0.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Xavier Guimard
Closes: 974201
node-rimraf_3.0.2-1_sourceonly.changes uploaded successfully to localhost
along with the files:
node-rimraf_3.0.2-1.dsc
node-rimraf_3.0.2.orig-types-rimraf.tar.gz
node-rimraf_3.0.2.orig.tar.gz
node-rimraf_3.0.2-1.debian.tar.xz
Greetings,
Your Debian queue daemon (running on host
Processing commands for cont...@bugs.debian.org:
> tags 974201 + pending
Bug #974201 [node-rimraf] Please ship TypeScript definitions
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
974201:
Your message dated Wed, 11 Nov 2020 21:04:49 +
with message-id
and subject line Bug#974194: fixed in node-proxyquire 2.1.3+~1.0.1+~1.0.2-11
has caused the Debian Bug report #974194,
regarding Please ship TypeScript definitions
to be marked as done.
This means that you claim that the problem
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 11 Nov 2020 21:31:10 +0100
Source: node-proxyquire
Architecture: source
Version: 2.1.3+~1.0.1+~1.0.2-11
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Julien Puydt
Hi,
I advanced quite well since this morning, so right now getting node-
rimraf up to date and with definitions is on the top of my todo list.
I'll work locally at first, but will probably upload in a few days,
unless it's a problem for you?
Cheers
--
Pkg-javascript-devel mailing list
node-proxyquire_2.1.3+~1.0.1+~1.0.2-11_source.changes uploaded successfully to
localhost
along with the files:
node-proxyquire_2.1.3+~1.0.1+~1.0.2-11.dsc
node-proxyquire_2.1.3+~1.0.1+~1.0.2-11.debian.tar.xz
node-proxyquire_2.1.3+~1.0.1+~1.0.2-11_source.buildinfo
Greetings,
Your
Hi Jonas,
you have uploaded 4.0.1 to experimental in august 2019 ; is there a
reason why it didn't get into unstable?
I ask because I want to work on shipping the TypeScript types with the
package... and the definition are for v4.
So basically, I want to work on the package, but don't want to
Processing control commands:
> tag -1 pending
Bug #974194 [node-proxyquire] Please ship TypeScript definitions
Added tag(s) pending.
--
974194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974194
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
Your message dated Wed, 11 Nov 2020 19:04:29 +
with message-id
and subject line Bug#974236: fixed in node-exports-loader 0.7.0-3
has caused the Debian Bug report #974236,
regarding node-exports-loader: autopkgtest must be marked superficial
to be marked as done.
This means that you claim
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 11 Nov 2020 17:32:58 +0100
Source: node-exports-loader
Architecture: source
Version: 0.7.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Xavier Guimard
Closes:
node-exports-loader_0.7.0-3_sourceonly.changes uploaded successfully to
localhost
along with the files:
node-exports-loader_0.7.0-3.dsc
node-exports-loader_0.7.0-3.debian.tar.xz
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
--
Pkg-javascript-devel mailing
Le 09/11/2020 à 12:27, Xavier a écrit :
> Hi,
>
> jest seems ready (all my test passed), but be careful when using it: if
> you embed some components, jest will try to launch their tests even if
> they are not for it. To avoid this, specify a path. Eg: `jest test/`.
>
> Cheers,
> Xavier
>
> PS:
Your message dated Wed, 11 Nov 2020 16:33:47 +
with message-id
and subject line Bug#974237: fixed in node-exit-hook 1.1.1-2
has caused the Debian Bug report #974237,
regarding node-exit-hook: autopkgtest must be marked superficial
to be marked as done.
This means that you claim that the
Processing control commands:
> tag -1 pending
Bug #974236 [src:node-exports-loader] node-exports-loader: autopkgtest must be
marked superficial
Added tag(s) pending.
--
974236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974236
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 11 Nov 2020 17:15:00 +0100
Source: node-exit-hook
Architecture: source
Version: 1.1.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Xavier Guimard
Closes: 974237
node-exit-hook_1.1.1-2_sourceonly.changes uploaded successfully to localhost
along with the files:
node-exit-hook_1.1.1-2.dsc
node-exit-hook_1.1.1-2.debian.tar.xz
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
--
Pkg-javascript-devel mailing list
Processing control commands:
> tag -1 pending
Bug #974237 [src:node-exit-hook] node-exit-hook: autopkgtest must be marked
superficial
Added tag(s) pending.
--
974237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974237
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Wed, 11 Nov 2020 16:18:35 +
with message-id
and subject line Bug#974231: fixed in node-exit 0.1.2-2
has caused the Debian Bug report #974231,
regarding node-exit: autopkgtest must be marked superficial
to be marked as done.
This means that you claim that the problem has
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 11 Nov 2020 17:06:14 +0100
Source: node-exit
Architecture: source
Version: 0.1.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Xavier Guimard
Closes: 974231
node-exit_0.1.2-2_sourceonly.changes uploaded successfully to localhost
along with the files:
node-exit_0.1.2-2.dsc
node-exit_0.1.2-2.debian.tar.xz
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
--
Pkg-javascript-devel mailing list
Your message dated Wed, 11 Nov 2020 17:13:48 +0100
with message-id <160511122856.1983200.157784857387383...@auryn.jones.dk>
and subject line Re: [Pkg-javascript-devel] Bug#974425: The salsa git
repository isn't up to date
has caused the Debian Bug report #974425,
regarding The salsa git
Processing control commands:
> tag -1 pending
Bug #974231 [src:node-exit] node-exit: autopkgtest must be marked superficial
Added tag(s) pending.
--
974231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974231
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
Source: node-import-lazy
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-import-lazy is running a
trivial command that does not provide significant test coverage:
- nodejs -e
Source: node-output-file-sync
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-output-file-sync is running a
trivial command that does not provide significant test coverage:
- nodejs -e
Package: node-proxyquire
Version: 2.1.3+~1.0.1+~1.0.2-10
Severity: minor
From the package's tracker :
The VCS repository is not up to date, push the missing commits. high
vcswatch reports that the current version of the package is not in its
VCS.
Either you need to push your commits and/or your
Source: node-orchestrator
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-orchestrator is running a
trivial command that does not provide significant test coverage:
- nodejs -e
Source: node-is-plain-obj
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-is-plain-obj is running a
trivial command that does not provide significant test coverage:
- nodejs -e
Your message dated Wed, 11 Nov 2020 14:46:59 +
with message-id
and subject line Bug#974240: fixed in node-everything.js 1.0.3-2
has caused the Debian Bug report #974240,
regarding node-everything.js: autopkgtest must be marked superficial
to be marked as done.
This means that you claim that
Source: node-imurmurhash
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-imurmurhash is running a
trivial command that does not provide significant test coverage:
- nodejs -e
Source: node-repeating
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-repeating is running a
trivial command that does not provide significant test coverage:
- nodejs -e
Source: node-request-capture-har
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-request-capture-har is running
a
trivial command that does not provide significant test coverage:
- nodejs -e
Source: node-json-parse-helpfulerror
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-json-parse-helpfulerror is
running a
trivial command that does not provide significant test coverage:
-
Source: node-has-symbol-support-x
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-has-symbol-support-x is
running a
trivial command that does not provide significant test coverage:
- nodejs
Source: node-resolve-cwd
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-resolve-cwd is running a
trivial command that does not provide significant test coverage:
- nodejs -e
Source: node-seedrandom
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-seedrandom is running a
trivial command that does not provide significant test coverage:
- nodejs -e
/handlebars
* New upstream version 4.7.6+~4.1.0
* Add break against node-typescript-types < 20201111~
Checksums-Sha1:
1d1591842b4e3d24840123a6f005b4e64a42645f 3051
node-handlebars_4.7.6+~4.1.0-1.dsc
3fcce9bf88f85fe73dc932240ab3fb682c624850 1099
node-handlebars_4.7.6+~4.1.0.orig-ty
:
sax.js (1.2.4+~1.2.1-1) unstable; urgency=medium
.
* Team upload
* Bump debhelper compatibility level to 13
* Embed @types/sax and repack
* Use dh-sequence-nodejs auto test
* Add break against node-typescript-types < 20201111~
Checksums-Sha1:
59fbaeb565f8bc01a3a3829ea245c8ff5cee8
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 11 Nov 2020 14:49:44 +0100
Source: typescript-types
Architecture: source
Version: 2020-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Xavier Guimard
Changes
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 11 Nov 2020 15:28:32 +0100
Source: node-everything.js
Architecture: source
Version: 1.0.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Xavier Guimard
Closes:
* Use dh-sequence-nodejs
* Embed @types/minimist
* New upstream version 1.2.5+~1.2.1
* Add break against node-typescript-types < 20201111~
Checksums-Sha1:
ec0eca1a9c8c784a0ade615f2583c1207f9347e3 2432 node-minimist_1.2.5+~1.2.1-1.dsc
283f669ff76d7b8260df8ab7a4262cc83d988256 2459
n
highlight.js_9.18.1+dfsg1-2.dsc: Invalid size hash for
highlight.js_9.18.1+dfsg1.orig-types-highlightjs.tar.xz:
According to the control file the size hash should be 2580,
but highlight.js_9.18.1+dfsg1.orig-types-highlightjs.tar.xz has 2516.
If you did not include
w upstream version 9.18.1+dfsg1
* Refresh patches
* Enable more tests using bluebird and jsdom
* Add break against node-typescript-types < 2020~
Checksums-Sha1:
8fe32f8678007bb8015c03a5fe0e38de9cdedc82 3034 highlight.js_9.18.1+dfsg1-1.dsc
b50d7fdfd9fbd91c3ac131322107f1df
Source: node-generator-supported
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-generator-supported is running
a
trivial command that does not provide significant test coverage:
- nodejs -e
Source: node-remove-trailing-separator
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-remove-trailing-separator is
running a
trivial command that does not provide significant test coverage:
Source: node-uglifyjs-webpack-plugin
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-uglifyjs-webpack-plugin is
running a
trivial command that does not provide significant test coverage:
-
Source: node-os-browserify
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-os-browserify is running a
trivial command that does not provide significant test coverage:
- nodejs -e
Source: node-registry-url
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-registry-url is running a
trivial command that does not provide significant test coverage:
- nodejs -e
Source: node-normalize-range
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-normalize-range is running a
trivial command that does not provide significant test coverage:
- nodejs -e
Source: node-shebang-command
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-shebang-command is running a
trivial command that does not provide significant test coverage:
- nodejs -e
Source: node-path-browserify
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-path-browserify is running a
trivial command that does not provide significant test coverage:
- nodejs -e
Source: node-to-object-path
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-to-object-path is running a
trivial command that does not provide significant test coverage:
- nodejs -e
Source: node-performance-now
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-performance-now is running a
trivial command that does not provide significant test coverage:
- nodejs -e
Source: node-mississippi
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-mississippi is running a
trivial command that does not provide significant test coverage:
- nodejs -e
Source: node-is-data-descriptor
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-is-data-descriptor is running a
trivial command that does not provide significant test coverage:
- nodejs -e
Source: node-posix-character-classes
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-posix-character-classes is
running a
trivial command that does not provide significant test coverage:
-
Source: node-get-caller-file
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-get-caller-file is running a
trivial command that does not provide significant test coverage:
- nodejs -e
Source: node-package-json
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-package-json is running a
trivial command that does not provide significant test coverage:
- nodejs -e
Source: node-parallel-transform
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-parallel-transform is running a
trivial command that does not provide significant test coverage:
- nodejs -e
Source: node-json-localizer
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-json-localizer is running a
trivial command that does not provide significant test coverage:
- nodejs -e
Source: node-resolve-from
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-resolve-from is running a
trivial command that does not provide significant test coverage:
- nodejs -e
Source: node-promise-inflight
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-promise-inflight is running a
trivial command that does not provide significant test coverage:
- nodejs -e
Source: node-gulp-load-plugins
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-gulp-load-plugins is running a
trivial command that does not provide significant test coverage:
- nodejs -e
Source: node-gulp-plumber
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-gulp-plumber is running a
trivial command that does not provide significant test coverage:
- nodejs -e
Source: node-generic-pool
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-generic-pool is running a
trivial command that does not provide significant test coverage:
- nodejs -e
Source: node-random-bytes
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-random-bytes is running a
trivial command that does not provide significant test coverage:
- nodejs -e
Source: node-getobject
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-getobject is running a
trivial command that does not provide significant test coverage:
- nodejs -e
Source: node-quick-lru
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-quick-lru is running a
trivial command that does not provide significant test coverage:
- nodejs -e
Source: node-time-stamp
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-time-stamp is running a
trivial command that does not provide significant test coverage:
- nodejs -e
Source: node-term-size
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-term-size is running a
trivial command that does not provide significant test coverage:
- nodejs -e
Source: node-has-unicode
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-has-unicode is running a
trivial command that does not provide significant test coverage:
- nodejs -e
Source: node-lodash-compat
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-lodash-compat is running a
trivial command that does not provide significant test coverage:
- nodejs -e
Source: node-strip-bom
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-strip-bom is running a
trivial command that does not provide significant test coverage:
- nodejs -e
Source: node-time-zone
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-time-zone is running a
trivial command that does not provide significant test coverage:
- nodejs -e
Source: node-text-table
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-text-table is running a
trivial command that does not provide significant test coverage:
- nodejs -e
Source: node-querystringify
X-Debbugs-CC: elb...@debian.org
Severity: important
Usertags: superficialtest
Dear Maintainer,
It has been noticed that the autopkgtest in node-querystringify is running a
trivial command that does not provide significant test coverage:
- nodejs -e
1 - 100 of 280 matches
Mail list logo
