[Pkg-javascript-devel] Bug#922093: marked as done (node-commander: FTBFS in sid (AssertionError: expected '' to be 'SIGHUPn'))
Your message dated Tue, 12 Feb 2019 21:49:33 + with message-id and subject line Bug#922093: fixed in node-commander 2.12.2-3 has caused the Debian Bug report #922093, regarding node-commander: FTBFS in sid (AssertionError: expected '' to be 'SIGHUPn') to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 922093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922093 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:node-commander Version: 2.12.2-2 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in sid but it failed: [...] debian/rules build-indep dh build-indep --with nodejs dh_update_autotools_config -i dh_autoreconf -i dh_auto_configure -i dh_auto_test --buildsystem=nodejs -i /bin/sh -e debian/tests/pkg-js/test make[1]: Entering directory '/<>' [90m test.arguments.js[0m [36mâ[0m [90m test.command.action.js[0m [36mâ[0m [90m test.command.alias.help.js[0m [36mâ[0m [90m test.command.allowUnknownOption.js[0m [36mâ[0m [90m test.command.executableSubcommand.js[0m [36mâ[0m [90m test.command.executableSubcommand.signals.hup.js[0m [31mâ[0m /usr/lib/nodejs/should/lib/assertion.js:72 throw new AssertionError(params); ^ AssertionError: expected '' to be 'SIGHUP\n' at Assertion.fail (/usr/lib/nodejs/should/lib/assertion.js:92:17) at Assertion.value (/usr/lib/nodejs/should/lib/assertion.js:164:19) at Timeout._onTimeout (/<>/test/test.command.executableSubcommand.signals.hup.js:19:19) at ontimeout (timers.js:436:11) at tryOnTimeout (timers.js:300:5) at listOnTimeout (timers.js:263:5) at Timer.processTimers (timers.js:223:10) make[1]: *** [Makefile:5: test] Error 1 make[1]: Leaving directory '/<>' dh_auto_test: /bin/sh -e debian/tests/pkg-js/test returned exit code 2 make: *** [debian/rules:8: build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 The build was made in my autobuilder with "dpkg-buildpackage -A" and it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-commander.html If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks. --- End Message --- --- Begin Message --- Source: node-commander Source-Version: 2.12.2-3 We believe that the bug you reported is fixed in the latest version of node-commander, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 922...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated node-commander package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 12 Feb 2019 22:25:03 +0100 Source: node-commander Binary: node-commander Architecture: source Version: 2.12.2-3 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Xavier Guimard Closes: 922093 Description: node-commander - Complete solution for Node.js command-line interfaces Changes: node-commander (2.12.2-3) unstable; urgency=medium . * Ignore signal based tests (Closes: #922093) Checksums-Sha1: 04c97683b1597d4d46478f0b8392794437240cab 2133 node-commander_2.12.2-3.dsc 8b9dc8a0265d1673b522970da6834fae5b39e360 3544 node-commander_2.12.2-3.debian.tar.xz Checksums-Sha256: 14b4d2eac5da2a0a1c15e635567945988521bf3c142911200a5867592f9da99c 2133 node-commander_2.12.2-3.dsc 0b48f681a6bf00a348af9ba6eae1e361cafe2eabc1b855c9c2ce7696740fae20 3544 node-commander_2.12.2-3.debian.tar.xz Files: 1768f68b0225223ec409328ef2380b9d 2133 javascript optional node-commander_2.12.2-3.dsc 0672cbb41282f1bce0ac47912e38a1f0 3544 javascript optional node-commander_2.12.2-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAlxjOjkACgkQ9tdMp8mZ 7ulXxRAAgVjvmelXLpX5fjwajZTQSRO6NLl36DhAepHyoLOyL4pb266tjsFTc58V
[Pkg-javascript-devel] node-commander_2.12.2-3_sourceonly.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 12 Feb 2019 22:25:03 +0100 Source: node-commander Binary: node-commander Architecture: source Version: 2.12.2-3 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Xavier Guimard Closes: 922093 Description: node-commander - Complete solution for Node.js command-line interfaces Changes: node-commander (2.12.2-3) unstable; urgency=medium . * Ignore signal based tests (Closes: #922093) Checksums-Sha1: 04c97683b1597d4d46478f0b8392794437240cab 2133 node-commander_2.12.2-3.dsc 8b9dc8a0265d1673b522970da6834fae5b39e360 3544 node-commander_2.12.2-3.debian.tar.xz Checksums-Sha256: 14b4d2eac5da2a0a1c15e635567945988521bf3c142911200a5867592f9da99c 2133 node-commander_2.12.2-3.dsc 0b48f681a6bf00a348af9ba6eae1e361cafe2eabc1b855c9c2ce7696740fae20 3544 node-commander_2.12.2-3.debian.tar.xz Files: 1768f68b0225223ec409328ef2380b9d 2133 javascript optional node-commander_2.12.2-3.dsc 0672cbb41282f1bce0ac47912e38a1f0 3544 javascript optional node-commander_2.12.2-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAlxjOjkACgkQ9tdMp8mZ 7ulXxRAAgVjvmelXLpX5fjwajZTQSRO6NLl36DhAepHyoLOyL4pb266tjsFTc58V yxMMcxSypXkuty+kplRq4F9q6qT9ZoAeOym6hDrGXF6giXND/fwsOpQSfuZpox7/ T6exHipO4exNUjHcZT1TCaKhqbqo/l39N1R1SCpaXfouYUv9LK+gOF//JEv0AHF/ jfizfbFMC0s0VyOM/wsAZbqs3TdgFCjwnIFtb2wf4Tp+sSXWRZ6jUATVZyU3DvQC D1cQbOx8f27iDGitDSXhJaFiF4bAm+slk6bubVFck4hf4SkaMfJXvaI+pVDgwx4j BPdzqTjLHwEssPPgIGLSE/L79LY00wWOYnUySIl7BcRMjvMBNhdTywQavEid22E2 3eK1iPqe/gSITXyv7orHl41zvBIug7wzu0ILxRynHjWwe18OQhNKA/z7bBF9In5c fRK8cRkUMP7I0/H3AmrM13ZLgWj1yalTYQwy9YRGDnC2h0Rt8Zd77ZibYzymV4S2 d7aKCVaQnU/iSDcyw3zRv2A4TR4UWAO84aqbcrQznqxarc3uGJiC3N7LwyaY0U+E EGUNr1oxAENLJXE1v8biasO/umAs6FKoWVVbVOyDGYiYrKKjS5SvzGF0j8YJoCSt 2CVvsltwFX9vrJ+7rfhtWlCnQGcD2hnoEdwV6Zvv3IlaaeqYGss= =GF0G -END PGP SIGNATURE- Thank you for your contribution to Debian. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Processing of node-commander_2.12.2-3_sourceonly.changes
node-commander_2.12.2-3_sourceonly.changes uploaded successfully to localhost along with the files: node-commander_2.12.2-3.dsc node-commander_2.12.2-3.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org) -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Processed: Bug #922093 in node-commander marked as pending
Processing control commands: > tag -1 pending Bug #922093 [src:node-commander] node-commander: FTBFS in sid (AssertionError: expected '' to be 'SIGHUPn') Added tag(s) pending. -- 922093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922093 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] pkg-js-tools_0.5_sourceonly.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 12 Feb 2019 21:50:37 +0100 Source: pkg-js-tools Binary: pkg-js-autopkgtest pkg-js-tools Architecture: source Version: 0.5 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Xavier Guimard Description: pkg-js-autopkgtest - collection of autopktest scripts for Nodejs packages pkg-js-tools - collection of tools to aid packaging Node modules in Debian Changes: pkg-js-tools (0.5) unstable; urgency=medium . * Fix typo in README.md * Use tar to copy test files * Launch test with "sh -e" Checksums-Sha1: c429aeb8a9d7b72695773f616c6db3dd1cf779d3 1870 pkg-js-tools_0.5.dsc 4834e16218081d209b40829460a5200b788bcbae 6464 pkg-js-tools_0.5.tar.xz Checksums-Sha256: 07ffa8e1106c3c20e108b3562d59286e6b798049ce020ef34b16557d9ce8e2b8 1870 pkg-js-tools_0.5.dsc 011e806f4b5949e235097cbb96426a43a898cbbe4305cbfa60f2f562fc042bdd 6464 pkg-js-tools_0.5.tar.xz Files: afc45fdbc1c426c32b1a0eb6ebc1aba9 1870 devel optional pkg-js-tools_0.5.dsc 5939f4cad391417a50a518e61a8fe746 6464 devel optional pkg-js-tools_0.5.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAlxjMzUACgkQ9tdMp8mZ 7unQDxAAhaKO6nKo/CLWzlWgVRvHmNnMqoRwTyK9R8KwBCi161hn+OoX7K1eMOAy 9r7NhysnN+8T3cL0nvLRLYgICOPniyaa7Ut++ujw87U4PPrwcxCiypR/jbunQD/Q Ib07vGJNYTV3dbR37k/NDnnOo6cLVEBw1Z9CsoylbaDUdY672UoHNCIF6UIvsJap 6cFX+p9zssXIT5lMYZQdGZngZsoSgTgNDKJLRQHTBqY3Sbx+FDNNq9js057pPwE0 exNWeJJGMaPZhwtClIszYqMc+eIs6sB0hRaWUjDVdrnBMesqj3oeeiSeM4WyT4i2 fn4811hnD5NfSQG3obrWByVRH70trSNyw1D2gBVTlZfMhyqnjdtrfXWzyltXeC3F wU6yKK5ufoOf7WzpZkniE9YJORSeeXHvYfowL67AfjSN4DxZWXoL7x5HnZqIQbbI dd3Nc1fFaS3t+CaufPrLHnvSh1iAA0EoaNNJk75vVWhJL8dcsaK8abkKYJQCxjUT 9BG+Nmg5/iw/kJAwlPCMnR2m2pMpRXyDMuKHkKxZpdYgvBtcLwmTfIQXgaHtHoiV uYcdiWojXhb/7K2fAqnYeHmjWNHujWSGZMRDXEQAJrKXNMjUvp3UIr1YfSJVs0qx 93JpnhB6051w0Te1IE63zumWk++jeGXihJGLN/15nH2sUY+y1EY= =LFL+ -END PGP SIGNATURE- Thank you for your contribution to Debian. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Processing of pkg-js-tools_0.5_sourceonly.changes
pkg-js-tools_0.5_sourceonly.changes uploaded successfully to localhost along with the files: pkg-js-tools_0.5.dsc pkg-js-tools_0.5.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org) -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#922093: node-commander: Unable to reproduce FTBFS
Hi, even on a very slow machine with some parallel schroot builds, I'm unable to reproduce this FTBFS failure. Maybe related to LXC infrastructure. I'll test later. Cheers, Xavier -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] libjs-sdp_2.9.0-6_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 12 Feb 2019 14:49:07 +0100 Source: libjs-sdp Architecture: source Version: 2.9.0-6 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Jonas Smedegaard Changes: libjs-sdp (2.9.0-6) unstable; urgency=medium . * Update watch file: Fix regular expressions. * Fix (really) have autopkgtest depend on nodejs. Checksums-Sha1: eb8ae0d16ea130abe8351b81c1f8b418cb85b581 2106 libjs-sdp_2.9.0-6.dsc 0ba1f8054a92a0554a70b3dca00590e6152cd555 3740 libjs-sdp_2.9.0-6.debian.tar.xz ad5d916c7153b3e13896d82796f1d22ea28bf6d3 7279 libjs-sdp_2.9.0-6_amd64.buildinfo Checksums-Sha256: 7993f5c3c50a5fbbe616ddf898826339f16c73e7372ac6314cc098426b2c3c40 2106 libjs-sdp_2.9.0-6.dsc cbeb8cce9dfbcb9494d30c958c3fed0748a7dd0a3f29c5eb3967cfb863f6d0fa 3740 libjs-sdp_2.9.0-6.debian.tar.xz 3aa8e784f2ca4dd861c95c2d55a8955e3bc9c686834da25ce9dbe3a80cbe1b79 7279 libjs-sdp_2.9.0-6_amd64.buildinfo Files: 96e0f2e20d929d4213d9bd1f5f33cd9e 2106 javascript optional libjs-sdp_2.9.0-6.dsc 24a8c04797442b161263df0a0b816096 3740 javascript optional libjs-sdp_2.9.0-6.debian.tar.xz 3ff14a81c6cd61ffa1e8740ca3ef430f 7279 javascript optional libjs-sdp_2.9.0-6_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlxizzYACgkQLHwxRsGg ASGFdQ//TZj1IMLIbYoV6k+I2yDk5NsjbjCPZX1qEboCO6034TC7b43M9D9QtGZV Oix5/egq/CCLjOFIr59FG8x3RsVwhQfm5s0LPKeAHnss8jNeaWA1QwWog/w/BWR1 hU7Zkd2uSAC+DxSUNaWrvJ3txx2LBhfWHDuhqQikPEWELBwaLwRE95bjT/wh/Ymu ydn2W8sAQD8UBGC9aOYfyWQcEcO1tORZ/eLrYGi+V4di6ydUvLJFC3C34QiZhVfv h7bjNk+KasEIcuoIh6oaokx85VMXet98wnFOA3TsBUUy9kL7aqKnFxP0k4q4EZuk P5nIdZTszFmGL6mjX8sXp7s/WoZXFGntleD2/fDr51no02SCkZ3DlyaxFDm7MNkC 3clYvpXcDHCb2mYOWqneCYyzigo2nluJxxFApAs5mdw3o0k2vDR/tq2gj8SMmPpd uHh3yBYwZosz+2TPC99syoFM8PzI6lAbqdbFJP0zT6QMuppKgF6wtfdkMS+rl1lm QYnXyFUi54SFang1HS2XEn0qgweZxsY/NJ3syL1gecLrjtIuBYrRR0BZR9TrBXBZ lwLgEOqSH1G+LgyDzXNcW70V2c7rI8qOH2n8u3aa7nbJk5MDcuqT/1g2ApDTczAr 7QBNK2EFWwmYxO0gYpg5vuOsmGSurTriols7ZyDH80B/jsH0BA0= =LQEc -END PGP SIGNATURE- Thank you for your contribution to Debian. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Processing of libjs-sdp_2.9.0-6_source.changes
libjs-sdp_2.9.0-6_source.changes uploaded successfully to localhost along with the files: libjs-sdp_2.9.0-6.dsc libjs-sdp_2.9.0-6.debian.tar.xz libjs-sdp_2.9.0-6_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#922075: Bug#922075: npm: segfault during extract on i386
On Tue, Feb 12, 2019 at 12:01 AM, Jérémy Lal wrote: Do you get some log in ~/.npm ? Since nodejs has a test suite, and since it crashes when extracting tgz, obvious culprit is node-tar, but i can't shoot something blindly if i don't have a (javascript) stack trace. No, I don't see any logs under ~/.npm. If you have an idea on how to get one, let me know. Best, Teemu -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] V8 depends from outdated and unmaintained libv8 with security issues
On Fri, Feb 08, 2019 at 11:48:57AM +0100, Jérémy Lal wrote: > > That would be absolutely fantastic, yes. Also a symlink from > > libv8.so-> libnode.so woulde be handy, because libv8 doesn't use > > pkg-config anywhere else so most bindings just test for linking with > > -lv8. > > > > Ok then no pkgconfig and a symlink instead. > I suppose i need to ask a removal of libv8 from unstable (it's removed from > testing) to > be able to "take" libv8-dev. Or maybe declare a libv8-in-nodejs-dev package > ? Conflicts: libv8-dev (<= version) Replaces: libv8-dev Provides: libv8-dev > In any case i don't know if i should make a libv8-xx package (which would > basically be > symlinks to libnode). > Any advice is welcome... That should be fine. Kind regards Andreas. -- http://fam-tille.de -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#904422: Bug#904422: npm: complains about too-new nodejs
Op di 12 feb. 2019 om 11:15 schreef Pirate Praveen : > npm was not updated for over 3 years and was removed from stretch. See > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870460 > > My motivation for updating it was for gitlab (I'd have been happy with > even npm 1.4 as I only wanted 'npm install yarn' from npm) and 5.x was > perfectly suitable, not only for my usecase but that was the latest > upstream version at that time (5.8 is also available in > stretch-backports). Now yarn (node-yarnpkg) is already packaged and I > don't have any motivation to keep npm updated. Its a team maintained > package and anyone is free to update it (just like how I updated it to > 5.x from 1.x). Is there any specific feature that you are looking for > in npm 6? No, it's just the noise regarding nodejs version that I'd like to avoid. In general it's nice to have the latest stable versions in a release though, as in other cases you do hit bugs or features that aren't available due to an older version being present. -- Olaf -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#904422: Bug#904422: npm: complains about too-new nodejs
On ചൊ, ഫെബ്രു 12, 2019 at 2:59 വൈകു, Olaf van der Spek wrote: Op di 12 feb. 2019 om 10:25 schreef Pirate Praveen : > npm 6 has been available for some time.. > If that introduce any rc bugs, there won't be enough time to fix it and I don't want to risk it at this point. Makes sense. 6 has been available since May though, right? Why wasn't it uploaded earlier? npm was not updated for over 3 years and was removed from stretch. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870460 My motivation for updating it was for gitlab (I'd have been happy with even npm 1.4 as I only wanted 'npm install yarn' from npm) and 5.x was perfectly suitable, not only for my usecase but that was the latest upstream version at that time (5.8 is also available in stretch-backports). Now yarn (node-yarnpkg) is already packaged and I don't have any motivation to keep npm updated. Its a team maintained package and anyone is free to update it (just like how I updated it to 5.x from 1.x). Is there any specific feature that you are looking for in npm 6? -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#904422: Bug#904422: npm: complains about too-new nodejs
Op di 12 feb. 2019 om 10:25 schreef Pirate Praveen : > > npm 6 has been available for some time.. > > > > If that introduce any rc bugs, there won't be enough time to fix it and > I don't want to risk it at this point. Makes sense. 6 has been available since May though, right? Why wasn't it uploaded earlier? -- Olaf -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#904422: Bug#904422: npm: complains about too-new nodejs
On ചൊ, ഫെബ്രു 12, 2019 at 2:49 വൈകു, Olaf van der Spek wrote: Op di 12 feb. 2019 om 10:13 schreef Pirate Praveen : On ചൊ, ഫെബ്രു 12, 2019 at 2:34 വൈകു, Olaf van der Spek wrote: > Could npm 6 be packaged? We won't be able to get it into buster (soft freeze starting today), 2019-02-12 Soft freeze (no new packages, no re-entry, 10 day migration) It'd not be a new package would it? Starting 2019-02-12, only small, targeted fixes are appropriate for buster. https://release.debian.org/buster/freeze_policy.html So we are not expected to upload new upstream releases. but we can try for buster + 1 or possibly buster-backports. npm 6 has been available for some time.. If that introduce any rc bugs, there won't be enough time to fix it and I don't want to risk it at this point. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#904422: Bug#904422: npm: complains about too-new nodejs
Op di 12 feb. 2019 om 10:13 schreef Pirate Praveen : > On ചൊ, ഫെബ്രു 12, 2019 at 2:34 വൈകു, Olaf van > der Spek wrote: > > Could npm 6 be packaged? > > We won't be able to get it into buster (soft freeze starting today), > 2019-02-12 Soft freeze (no new packages, no re-entry, 10 day migration) It'd not be a new package would it? > but we can try for buster + 1 or possibly buster-backports. npm 6 has been available for some time.. -- Olaf -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#904422: Bug#904422: npm: complains about too-new nodejs
On ചൊ, ഫെബ്രു 12, 2019 at 2:34 വൈകു, Olaf van der Spek wrote: Could npm 6 be packaged? We won't be able to get it into buster (soft freeze starting today), but we can try for buster + 1 or possibly buster-backports. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#904422: npm: complains about too-new nodejs
Hi, Could npm 6 be packaged? Greetings, -- Olaf -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
