[Pkg-javascript-devel] node-css-what 3.2.0-1 MIGRATED to testing

FYI: The status of the node-css-what source package in Debian's testing distribution has changed. Previous version: 3.1.0-2 Current version: 3.2.0-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will

[Pkg-javascript-devel] rainbow.js is marked for autoremoval from testing

rainbow.js 2.1.4+ds-1 is marked for autoremoval from testing on 2019-10-31 It is affected by these RC bugs: 941604: rainbow.js: rollup 0.56 transition: rainbow.js build fails with 'Unknown option found: moduleName, dest' -- Pkg-javascript-devel mailing list

[Pkg-javascript-devel] Processed: reassign 942045 to leaflet, tagging 941685

Processing commands for cont...@bugs.debian.org: > reassign 942045 leaflet 1.5.1~dfsg-2 Bug #942045 [leaftlet] rollup 0.68.2 transition: build fails with TypeError: magic_string_1.SourceMap is not a constructor Warning: Unknown package 'leaftlet' Bug reassigned from package 'leaftlet' to

[Pkg-javascript-devel] leaflet-markercluster is marked for autoremoval from testing

leaflet-markercluster 1.4.1~dfsg-6 is marked for autoremoval from testing on 2019-10-31 It is affected by these RC bugs: 941601: leaflet-markercluster: rollup 0.56 transition: Add node-rollup-plugin-json to build depends and fix 'format is now output.format' error -- Pkg-javascript-devel

Re: [Pkg-javascript-devel] build node-i18next with webpack instead or rollup?

On 2019, ഒക്‌ടോബർ 9 3:23:33 AM IST, Nicolas Mora wrote: >although I didn't squash the commits in the master branch, only pushed >as it is in my personnal repo. Should I rebase all the commits in the >master branch from the start? Well, if you had not pushed to js-team, squashing makes sense as

Re: [Pkg-javascript-devel] build node-i18next with webpack instead or rollup?

Le 19-10-09 à 02 h 47, Pirate Praveen a écrit : > > > Well, if you had not pushed to js-team, squashing makes sense as it require > force push. It is not recommended to force push to team repo after it is > published. In this case since we have not uploaded it, you can squash and > force push

[Pkg-javascript-devel] Bug#931571: Bug#931571: Bug#931571: rollup: please update to upstream release 0.61.0 or newer

On Sat, 05 Oct 2019 19:34:48 +0530 Pirate Praveen wrote: > > > On Sat, Oct 5, 2019 at 14:10, Pirate Praveen > wrote: > > I fixed this error with the following patch, it'd be good if someone > > can confirm this is okay. > > > > Now with master-0.68 branch simple bundling with command line

Re: [Pkg-javascript-devel] build node-i18next with webpack instead or rollup?

On Wed, Oct 9, 2019 at 07:08, Nicolas Mora wrote: Le 19-10-09 à 02 h 47, Pirate Praveen a écrit : Well, if you had not pushed to js-team, squashing makes sense as it require force push. It is not recommended to force push to team repo after it is published. In this case since we have

[Pkg-javascript-devel] Processing of node-rollup_0.68.2-1_source.changes

node-rollup_0.68.2-1_source.changes uploaded successfully to localhost along with the files: node-rollup_0.68.2-1.dsc node-rollup_0.68.2.orig-acorn-import-meta.tar.gz node-rollup_0.68.2.orig-turbocolor.tar.gz node-rollup_0.68.2.orig.tar.gz node-rollup_0.68.2-1.debian.tar.xz

Re: [Pkg-javascript-devel] The (long) way to update rollup

Hi team, rollup 0.56 is in unstable/testing and 0.68.2 in experimental. Need help with fixing the packages that fail with new version. List here Thanks Praveen -- Pkg-javascript-devel mailing list

[Pkg-javascript-devel] Bug#931571: marked as done (rollup: please update to upstream release 0.61.0 or newer)

Your message dated Wed, 09 Oct 2019 20:09:19 +0530 with message-id <1570631959.1771...@onenetbeyond.org> and subject line Re: [Pkg-javascript-devel] Bug#931571: Bug#931571: rollup: please update to upstream release 0.61.0 or newer has caused the Debian Bug report #931571, regarding rollup: please

[Pkg-javascript-devel] Bug#942054: node-oauth does not honor "nocheck" build profile

Source: node-oauth Version: 0.9.11-1 Severity: normal Debian policy defines the "nocheck" build profile to enable skipping any tests. I would need to skip tests because the tests access the network (see http://bugs.debian.org/830214) and my build machine doesn't allow DNS resolution. The

[Pkg-javascript-devel] node-rollup_0.68.2-1_source.changes ACCEPTED into experimental

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 09 Oct 2019 19:20:11 +0530 Source: node-rollup Architecture: source Version: 0.68.2-1 Distribution: experimental Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Pirate Praveen Changes:

[Pkg-javascript-devel] Processed: Fwd: Processed (with 6 errors): Re: Bug#931571: Bug#931571: rollup: please update to upstream release 0.61.0 or newer

Processing commands for cont...@bugs.debian.org: > fixed 931571 0.68.2-1 Bug #931571 {Done: Pirate Praveen } [rollup] rollup: please update to upstream release 0.61.0 or newer There is no source info for the package 'rollup' at version '0.68.2-1' with architecture '' Unable to make a source

Re: [Pkg-javascript-devel] build node-i18next with webpack instead or rollup?

Le 2019-10-09 09:36, Pirate Praveen a écrit : I guess one of the gitlab acl bugs/features as you have maintainer access there, if you wish you can make master branch as unprotected and force push. But I think lets leave it as it is. I tried to find out how to change it but so far no luck,

Re: [Pkg-javascript-devel] ?==?utf-8?q? build node-i18next with webpack instead or rollup?

Le Mercredi, Octobre 09, 2019 18:52 CEST, Nicolas Mora a écrit: > Le 2019-10-09 09:36, Pirate Praveen a écrit : > > > > I guess one of the gitlab acl bugs/features as you have maintainer > > access there, if you wish you can make master branch as unprotected > > and force push. But I think

[Pkg-javascript-devel] jsbundle-web-interfaces_1.1.0+~2.0.1~ds+~4.0.2+~0~20180821-1_amd64.changes is NEW

binary:node-auth-header is NEW. binary:node-standard-error is NEW. binary:node-standard-http-error is NEW. binary:node-webidl-conversions is NEW. binary:node-standard-error is NEW. binary:node-webidl-conversions is NEW. binary:node-auth-header is NEW. binary:node-standard-http-error is NEW.

[Pkg-javascript-devel] Bug#941700: Bug#941700: Bug#941700: Update babel to version 7

[14:53:55] ReferenceError: [BABEL] /home/pravi/forge/debian/git/js-team/node-babel/packages/babel-parser/src/x.js: Unknown option: base.envName. Check out for more information about options. The reason for this error and other errors is that this version

[Pkg-javascript-devel] Bug#942054: Bug#942054: node-oauth does not honor "nocheck" build profile

Le Mercredi, Octobre 09, 2019 18:12 CEST, Sven Mueller a écrit: > Source: node-oauth > Version: 0.9.11-1 > Severity: normal > > Debian policy defines the "nocheck" build profile to enable skipping any > tests. I would need to skip tests because the tests access the network (see >

[Pkg-javascript-devel] Processing of jsbundle-web-interfaces_1.1.0+~2.0.1~ds+~4.0.2+~0~20180821-1_amd64.changes

jsbundle-web-interfaces_1.1.0+~2.0.1~ds+~4.0.2+~0~20180821-1_amd64.changes uploaded successfully to localhost along with the files: jsbundle-web-interfaces_1.1.0+~2.0.1~ds+~4.0.2+~0~20180821-1.dsc jsbundle-web-interfaces_1.1.0+~2.0.1~ds+~4.0.2+~0~20180821.orig-Xauth.tar.gz

[Pkg-javascript-devel] Processed: notfixed 941306 in 1:9-1, fixed 941306 in 1:9-2, reassign 942021 to postgresql-common, tagging 939648 ...

Processing commands for cont...@bugs.debian.org: > notfixed 941306 1:9-1 Bug #941306 {Done: Gianfranco Costamagna } [llvm-9-dev] LLVMExports.cmake references lit-cpuid that does not exist No longer marked as fixed in versions llvm-toolchain-9/1:9-1. > fixed 941306 1:9-2 Bug #941306 {Done:

[Pkg-javascript-devel] Processed: Bug#830214 marked as pending in node-oauth

Processing control commands: > tag -1 pending Bug #830214 [src:node-oauth] node-oauth: accesses the internet during build Added tag(s) pending. -- 830214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830214 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --

[Pkg-javascript-devel] Processing of node-oauth_0.9.15-1_sourceonly.changes

node-oauth_0.9.15-1_sourceonly.changes uploaded successfully to localhost along with the files: node-oauth_0.9.15-1.dsc node-oauth_0.9.15.orig.tar.gz node-oauth_0.9.15-1.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org) -- Pkg-javascript-devel

[Pkg-javascript-devel] jsbundle-web-interfaces_1.1.0+~2.0.1~ds+~4.0.2+~0~20180821-1_amd64.changes ACCEPTED into unstable, unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 09 Oct 2019 19:02:25 +0200 Source: jsbundle-web-interfaces Binary: node-auth-header node-standard-error node-standard-http-error node-webidl-conversions Architecture: source all Version:

Re: [Pkg-javascript-devel] build node-i18next with webpack instead or rollup?

Le 2019-10-09 13:02, Xavier a écrit : No but it's a git-buildpackage bug. Commit the good file using: $ pristine-tar commit ../node-i18next-17.0.18.tar.gz upstream/17.0.18 Then push to salsa (using `salsa push` which pushes all what is needed) Got it, thanks. Also, I could push force in

[Pkg-javascript-devel] node-oauth_0.9.15-1_sourceonly.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 09 Oct 2019 21:45:32 +0200 Source: node-oauth Architecture: source Version: 0.9.15-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Xavier Guimard Closes: 792224

[Pkg-javascript-devel] Bug#830214: marked as done (node-oauth: accesses the internet during build)

Your message dated Wed, 09 Oct 2019 20:40:57 + with message-id and subject line Bug#830214: fixed in node-oauth 0.9.15-1 has caused the Debian Bug report #830214, regarding node-oauth: accesses the internet during build to be marked as done. This means that you claim that the problem has

[Pkg-javascript-devel] Bug#942054: marked as done (node-oauth does not honor "nocheck" build profile)

Your message dated Wed, 09 Oct 2019 20:40:57 + with message-id and subject line Bug#942054: fixed in node-oauth 0.9.15-1 has caused the Debian Bug report #942054, regarding node-oauth does not honor "nocheck" build profile to be marked as done. This means that you claim that the problem has

[Pkg-javascript-devel] Bug#792224: marked as done (node-oauth: FTBFS without networking: Error: getaddrinfo ENOTFOUND)

Your message dated Wed, 09 Oct 2019 20:40:57 + with message-id and subject line Bug#792224: fixed in node-oauth 0.9.15-1 has caused the Debian Bug report #792224, regarding node-oauth: FTBFS without networking: Error: getaddrinfo ENOTFOUND to be marked as done. This means that you claim that

[Pkg-javascript-devel] Bug#935845: marked as done (node-globule: autopkgtest fails on deprecation warning with new version of node-lodash)

Your message dated Wed, 9 Oct 2019 22:14:38 +0200 with message-id and subject line Fixed by pkg-js-tools upgrade has caused the Debian Bug report #935845, regarding node-globule: autopkgtest fails on deprecation warning with new version of node-lodash to be marked as done. This means that you

[Pkg-javascript-devel] Processing of node-promise-retry_1.1.1-4_sourceonly.changes

node-promise-retry_1.1.1-4_sourceonly.changes uploaded successfully to localhost along with the files: node-promise-retry_1.1.1-4.dsc node-promise-retry_1.1.1-4.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org) -- Pkg-javascript-devel mailing list

[Pkg-javascript-devel] node-promise-retry_1.1.1-4_sourceonly.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 09 Oct 2019 22:56:06 +0200 Source: node-promise-retry Architecture: source Version: 1.1.1-4 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Xavier Guimard Changes: