Your message dated Tue, 29 Mar 2022 05:34:01 +
with message-id
and subject line Bug#1007894: fixed in node-inquirer 8.2.1+~cs26.8.6-1
has caused the Debian Bug report #1007894,
regarding FTBFS: fails with pkg-js-tools dh_auto_build debian/nodejs/rxjs/build
to be marked as done.
This means
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 29 Mar 2022 07:04:20 +0200
Source: node-inquirer
Architecture: source
Version: 8.2.1+~cs26.8.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Yadd
Closes:
node-inquirer_8.2.1+~cs26.8.6-1_sourceonly.changes uploaded successfully to
localhost
along with the files:
node-inquirer_8.2.1+~cs26.8.6-1.dsc
node-inquirer_8.2.1+~cs26.8.6.orig-figures.tar.gz
node-inquirer_8.2.1+~cs26.8.6.orig-ora.tar.gz
node-inquirer_8.2.1+~cs26.8.6.orig-rxjs.tar.gz
Processing control commands:
> tag -1 pending
Bug #1007894 [node-inquirer] FTBFS: fails with pkg-js-tools dh_auto_build
debian/nodejs/rxjs/build
Added tag(s) pending.
--
1007894: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007894
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Your message dated Tue, 29 Mar 2022 04:49:03 +
with message-id
and subject line Bug#1008514: fixed in node-immutable 4.0.0-3
has caused the Debian Bug report #1008514,
regarding FTBFS -- upstream test suite failure
to be marked as done.
This means that you claim that the problem has been
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 29 Mar 2022 06:30:21 +0200
Source: node-immutable
Architecture: source
Version: 4.0.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Yadd
Closes: 1008514
node-immutable_4.0.0-3_sourceonly.changes uploaded successfully to localhost
along with the files:
node-immutable_4.0.0-3.dsc
node-immutable_4.0.0-3.debian.tar.xz
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
--
Pkg-javascript-devel mailing list
FYI: The status of the node-openid source package
in Debian's testing distribution has changed.
Previous version: 2.0.10+~2.0.2-2
Current version: 2.0.10+~2.0.2-3
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a
FYI: The status of the node-i18next-browser-languagedetector source package
in Debian's testing distribution has changed.
Previous version: 6.1.3-1
Current version: 6.1.4-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens
FYI: The status of the node-postcss-loader source package
in Debian's testing distribution has changed.
Previous version: 4.2.0+~cs11.2.14-2
Current version: 6.2.1+~cs7.0.11-2
--
This email is automatically generated once a day. As the installation of
new packages into testing happens
FYI: The status of the eslint source package
in Debian's testing distribution has changed.
Previous version: 6.4.0~dfsg+~6.1.9-4
Current version: 6.4.0~dfsg+~6.1.9-5
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple
FYI: The status of the node-sockjs-client source package
in Debian's testing distribution has changed.
Previous version: 1.5.2+dfsg1-2
Current version: 1.6.0+dfsg1-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple
Hi,
On Mon, Mar 28, 2022 at 08:36:19PM +, Debian FTP Masters wrote:
nodejs_16.14.2+dfsg-2.changes: Does not match re_file_changes
I have consult the ftp master folks about the issue, their giveback is
daklib/regexes.py:re_file_changes = re.compile(_re_file_prefix +
Processing commands for cont...@bugs.debian.org:
> reassign 1008283 exim4-config 4.95-4
Bug #1008283 [exim-config] Really confusing update-exim4.conf(8) man page
Warning: Unknown package 'exim-config'
Bug reassigned from package 'exim-config' to 'exim4-config'.
No longer marked as found in
nodejs_16.14.2+dfsg-2.changes: Does not match re_file_changes
===
Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.
--
Pkg-javascript-devel mailing list
nodejs_16.14.2+dfsg-2.changes uploaded successfully to localhost
along with the files:
nodejs_16.14.2+dfsg-2.dsc
nodejs_16.14.2+dfsg.orig-node-acorn.tar.xz
nodejs_16.14.2+dfsg.orig-types-node.tar.xz
nodejs_16.14.2+dfsg.orig.tar.xz
nodejs_16.14.2+dfsg-2.debian.tar.xz
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 28 Mar 2022 20:43:15 +0200
Source: node-ts-jest
Architecture: source
Version: 27.1.4+~cs0.2.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Yadd
Changes:
node-ts-jest_27.1.4+~cs0.2.6-2_sourceonly.changes uploaded successfully to
localhost
along with the files:
node-ts-jest_27.1.4+~cs0.2.6-2.dsc
node-ts-jest_27.1.4+~cs0.2.6-2.debian.tar.xz
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
--
Pkg-javascript-devel
nodejs_16.14.2+dfsg-2.changes: Does not match re_file_changes
===
Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.
--
Pkg-javascript-devel mailing list
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 28 Mar 2022 23:40:55 +0530
Source: node-rewire
Architecture: source
Version: 6.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Nilesh Patra
Changes:
node-rewire_6.0.0-2_source.changes uploaded successfully to localhost
along with the files:
node-rewire_6.0.0-2.dsc
node-rewire_6.0.0-2.debian.tar.xz
node-rewire_6.0.0-2_amd64.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
--
Pkg-javascript-devel
nodejs_16.14.2+dfsg-2.changes uploaded successfully to localhost
along with the files:
nodejs_16.14.2+dfsg-2.dsc
nodejs_16.14.2+dfsg.orig-node-acorn.tar.xz
nodejs_16.14.2+dfsg.orig-types-node.tar.xz
nodejs_16.14.2+dfsg.orig.tar.xz
nodejs_16.14.2+dfsg-2.debian.tar.xz
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 11 Mar 2022 15:29:41 +0100
Source: node-popper2
Binary: node-popper2
Architecture: source all
Version: 2.11.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By:
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 28 Mar 2022 09:43:37 +0200
Source: node-mj-context-menu
Binary: node-mj-context-menu
Architecture: source all
Version: 0.6.1+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 24 Mar 2022 03:24:29 +0530
Source: node-rewire
Binary: node-rewire
Architecture: source all
Version: 6.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Nilesh
Processing control commands:
> tag -1 pending
Bug #1008514 [node-immutable] FTBFS -- upstream test suite failure
Added tag(s) pending.
--
1008514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008514
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
Your message dated Mon, 28 Mar 2022 15:21:20 +
with message-id
and subject line Bug#1008512: fixed in node-https-proxy-agent 5.0.0+~cs8.0.0-4
has caused the Debian Bug report #1008512,
regarding FTBFS in upstream test suite
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: Mon, 28 Mar 2022 16:40:16 +0200
Source: node-https-proxy-agent
Architecture: source
Version: 5.0.0+~cs8.0.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Yadd
Real error is:
Transforming async functions is not implemented. Use `transforms: {
asyncAwait: false }` to skip transformation and disable this error.
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
node-https-proxy-agent_5.0.0+~cs8.0.0-4_sourceonly.changes uploaded
successfully to localhost
along with the files:
node-https-proxy-agent_5.0.0+~cs8.0.0-4.dsc
node-https-proxy-agent_5.0.0+~cs8.0.0-4.debian.tar.xz
Greetings,
Your Debian queue daemon (running on host
Processing control commands:
> tag -1 pending
Bug #1008512 [node-https-proxy-agent] FTBFS in upstream test suite
Added tag(s) pending.
--
1008512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008512
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
Your message dated Mon, 28 Mar 2022 09:18:36 +
with message-id
and subject line Bug#1008510: fixed in node-base64url 3.0.1-8
has caused the Debian Bug report #1008510,
regarding FTBFS unsufficient coverage
to be marked as done.
This means that you claim that the problem has been dealt with.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 28 Mar 2022 03:39:23 -0400
Source: node-wikibase-sdk
Architecture: source
Version: 7.14.4+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Andrius Merkys
binary:node-mj-context-menu is NEW.
binary:node-mj-context-menu is NEW.
source:node-mj-context-menu is NEW.
Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 28 Mar 2022 09:48:49 +0200
Source: node-base64url
Architecture: source
Version: 3.0.1-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Jonas Smedegaard
Closes:
node-base64url_3.0.1-8_source.changes uploaded successfully to localhost
along with the files:
node-base64url_3.0.1-8.dsc
node-base64url_3.0.1-8.debian.tar.xz
node-base64url_3.0.1-8_amd64.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
--
node-mj-context-menu_0.6.1+ds-1_amd64.changes uploaded successfully to localhost
along with the files:
node-mj-context-menu_0.6.1+ds-1.dsc
node-mj-context-menu_0.6.1+ds.orig.tar.xz
node-mj-context-menu_0.6.1+ds-1.debian.tar.xz
node-mj-context-menu_0.6.1+ds-1_all.deb
node-wikibase-sdk_7.14.4+ds-1_source.changes uploaded successfully to localhost
along with the files:
node-wikibase-sdk_7.14.4+ds-1.dsc
node-wikibase-sdk_7.14.4+ds.orig.tar.xz
node-wikibase-sdk_7.14.4+ds-1.debian.tar.xz
node-wikibase-sdk_7.14.4+ds-1_source.buildinfo
Greetings,
Processing control commands:
> tag -1 pending
Bug #1008510 [node-base64url] FTBFS unsufficient coverage
Added tag(s) pending.
--
1008510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008510
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
Pkg-javascript-devel
Package: node-recast
Version:
Severity: serious
Tags: ftbfs
Trying to build the package in an unstable sbuild, I get the following
failure:
1) TypeScript
basic printing:
SyntaxError: Initializers are not allowed in ambient contexts.
(2:27)
at instantiate
Your message dated Mon, 28 Mar 2022 07:09:05 +
with message-id
and subject line Bug#1008513: fixed in node-ignore 5.2.0-2
has caused the Debian Bug report #1008513,
regarding FTBFS unsufficient coverage
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 28 Mar 2022 08:42:28 +0200
Source: node-ignore
Architecture: source
Version: 5.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Yadd
Closes: 1008513
Changes:
node-ignore_5.2.0-2_sourceonly.changes uploaded successfully to localhost
along with the files:
node-ignore_5.2.0-2.dsc
node-ignore_5.2.0-2.debian.tar.xz
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
--
Pkg-javascript-devel mailing list
binary:dh-nodejs is NEW.
binary:dh-nodejs is NEW.
Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so please be patient.
Packages are routinely
Processing control commands:
> tag -1 pending
Bug #1008513 [node-ignore] FTBFS unsufficient coverage
Added tag(s) pending.
--
1008513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008513
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
Pkg-javascript-devel
pkg-js-tools_0.14.11~bpo11+1_amd64.changes uploaded successfully to localhost
along with the files:
pkg-js-tools_0.14.11~bpo11+1.dsc
pkg-js-tools_0.14.11~bpo11+1.tar.xz
dh-nodejs_0.14.11~bpo11+1_all.deb
pkg-js-autopkgtest_0.14.11~bpo11+1_all.deb
pkg-js-tools_0.14.11~bpo11+1_all.deb
Package: node-immutable
Version: 4.0.0-2
Severity: serious
Tags: ftbfs
Trying to build the package in an unstable sbuild, I get the following
failure:
+ NODE_PATH=node_modules:/usr/share/nodejs jest --ci
__tests__/ArraySeq.ts
Error
at Function.missingTransform
Package: node-https-proxy-agent
Version: 5.0.0+~cs8.0.0-3
Severity: serious
Tags: ftbfs
Trying to rebuild the package in an unstable sbuild gives the following
failure in upstream test suite:
1) HttpsProxyAgent
"http" module
should receive the 407 authorization code on the
Package: node-ignore
Version: 5.2.0-1
Severity: serious
Tags: ftbfs
Building the package in an unstable sbuild, I get:
ERROR: Coverage for lines (92.3%) does not meet global threshold (100%)
ERROR: Coverage for functions (91.66%) does not meet global threshold
(100%)
ERROR: Coverage for branches
Package: node-configurable-http-proxy
Version: 4.5.0+~cs15.1.4-3
Severity: serious
Tags: ftbfs
Building the package in an unstable sbuild, I get failures:
Randomized with seed 97263
Started
..F...06:23:50.587 [ConfigProxy]
ESC[31merrorESC[39m: 404 GET /nope
06:23:50.860
Package: node-base64url
Version: 3.0.1-7
Severity: serious
Tags: ftbfs
Trying to build the package in an unstable sbuild, the upstream test
suite fails because it doesn't find a 100% coverage:
ERROR: Coverage for lines (97.22%) does not meet global threshold
(100%)
ERROR: Coverage for branches
Package: node-config
Version: 3.3.7-1
Severity: serious
Tags: ftbfs
While rebuilding your package with an unstable sbuild, it failed at six
points in the upstream test suite, with the same error:
ยป An unexpected error was caught: TypeError: Cannot set
property offset of [object Object]
52 matches
Mail list logo
