[Pkg-javascript-devel] Bug#898024: trying to overwrite '/usr/include/nodejs/common.gypi', which is also in package nodejs-dev 10.0.0~dfsg-2

2018-05-06 3:19 GMT+02:00 積丹尼 Dan Jacobson : > Package: nodejs-dev > > Unpacking libnode64-dev (10.0.0~dfsg1-3) ... > dpkg: error processing archive /tmp/apt-dpkg-install-NI7HKh/ > 073-libnode64-dev_10.0.0~dfsg1-3_amd64.deb (--unpack): > trying to overwrite

Re: [Pkg-javascript-devel] nodejs >= 6 for gitlab in stretch-backports

2018-05-10 9:15 GMT+02:00 Pirate Praveen <prav...@onenetbeyond.org>: > > > On Thu, May 3, 2018 at 3:19 PM, Jérémy Lal <kapo...@melix.org> wrote: > > > > 2018-05-03 11:32 GMT+02:00 Pirate Praveen <prav...@onenetbeyond.org>: > >> >> >> On

Re: [Pkg-javascript-devel] How to ship DefinitelyTyped's type definitions?

2018-05-17 6:31 GMT+02:00 Pirate Praveen : > > > On May 17, 2018 1:32:01 AM GMT+05:30, Julien Puydt < > julien.pu...@laposte.net> wrote: > >Hi, > > > >Le 16/05/2018 à 17:45, Bastien ROUCARIES a écrit : > >> Can I suggest in all the case something pragmatic ? Could I

Re: [Pkg-javascript-devel] npm 6.0.1 some progress

2018-05-23 8:26 GMT+02:00 Diane Trout : > Hi, > > I was mucking around with building npm 6.0.1 and filtering out more > things in node_modules that I can find close enough versions in Debian. > > I thought you all might be interested in I found only two source is > missing lintian

[Pkg-javascript-devel] Bug#898024: Bug#898024: trying to overwrite '/usr/include/nodejs/common.gypi', which is also in package nodejs-dev 10.0.0~dfsg-2

2018-06-10 10:26 GMT+02:00 Andreas Beckmann : > Followup-For: Bug #898024 > Control: found -1 10.3.0~dfsg-1 > Control: severity -1 serious > > The 8 -> 10 upgrade path does not work either: > > Selecting previously unselected package libnode64-dev. > Preparing to unpack

[Pkg-javascript-devel] Bug#898024: Bug#898024: Bug#898024: trying to overwrite '/usr/include/nodejs/common.gypi', which is also in package nodejs-dev 10.0.0~dfsg-2

2018-06-10 20:14 GMT+02:00 Jonas Smedegaard : > Hi Jérémy, > > Quoting Jérémy Lal (2018-06-10 16:51:14) > > 2018-06-10 10:26 GMT+02:00 Andreas Beckmann : > > > The 8 -> 10 upgrade path does not work either: > > > > > > Selecting previously unsele

[Pkg-javascript-devel] Bug#870460: Bug#870460: anyone working on npm?

2018-06-08 3:44 GMT+02:00 Pirate Praveen : > On Sat, 21 Apr 2018 01:06:57 +0200 =?UTF-8?B?SsOpcsOpbXkgTGFs?= > wrote:> I was inspecting npm's master branch and i > couldn't resist fixing some > > trivial, but also some non-trivial, things, so please make sure you stay > > up-to-date with that

[Pkg-javascript-devel] Bug#901474: Bug#901474: [nodejs][RFC] Multiarch and /usr/local search path

2018-06-13 22:09 GMT+02:00 Bastien ROUCARIÈS : > > > You could check the patch by doing require('os').constants and see > ARCH_TRIPLET: 'x86_64-linux-gnu', > GLOBAL_NODE_PATH: >'/usr/local/lib/x86_64-linux-gnu/nodejs:/usr/local/share/ >

[Pkg-javascript-devel] Bug#901474: Bug#901474: [nodejs][RFC] Multiarch and /usr/local search path

2018-06-13 22:09 GMT+02:00 Bastien ROUCARIÈS : > Package: nodejs > Version: 10.4.0~dfsg-2 > Severity: important > tags: patch > > > Hi, > > In order to get search path in multiarch path and in /usr/local I use the > following patch > > ../.. globalPaths: >[ '/home/bastien/.node_modules', >

[Pkg-javascript-devel] Bug#901474: Bug#901474: Bug#901474: [nodejs][RFC] Multiarch and /usr/local search path

2018-06-13 23:28 GMT+02:00 Bastien ROUCARIES : > On Wed, Jun 13, 2018 at 10:46 PM, Jérémy Lal wrote: > > > > > > 2018-06-13 22:09 GMT+02:00 Bastien ROUCARIÈS < > roucaries.bast...@gmail.com>: > >> > >> Package: nodejs > >> Version

[Pkg-javascript-devel] Bug#901297: Bug#901297: libnode64-dev: rename to libnode-dev

2018-06-11 8:59 GMT+02:00 Emilio Pozuelo Monfort : > Package: libnode64-dev > Version: 10.4.0~dfsg-1 > Severity: important > > Hi, > > Your shared library package is named libnode64, since it ships > libnode.so.64. > That is fine. However the development package should be named libnode-dev, > so

[Pkg-javascript-devel] Bug#900491: node-tar: version 4 breaks software written for version 2

Package: node-tar Version: 4.4.2+ds-1 Severity: important node-tar version 4 is not backward compatible (at all) with previous major versions: require('tar').Extract has moved to require('tar').extract Look if it is possible to keep backward compatibility to ensure a smoother upgrade. --

Re: [Pkg-javascript-devel] nodejs >= 6 for gitlab in stretch-backports

2018-05-02 13:44 GMT+02:00 Pirate Praveen : > Hi, > > I'd like to upload gitlab 10.6 to stretch-backports as backporting > security fixes is becoming difficult. My original idea was also > providing updates via backports, but gitlab switching to nodejs for > front end in

[Pkg-javascript-devel] nodejs 10 in experimental and soon libnode

Hi ! I just built node with --shared flag and it seems it's possible to build a libnode.so. now, with executable linked to it. This goes very well with the fact N-API is stable and supported in version 10. Also upstream pays much more attention to distributors. There are good news ! Now the bad

Re: [Pkg-javascript-devel] bundling solitary nodejs modules as components

2018-04-26 13:40 GMT+02:00 Paolo Greppi <paolo.gre...@libpf.com>: > Il 23/04/2018 14:16, Jérémy Lal ha scritto: > > After years of hesitation... i started to experiment bundling node > modules as components, > > thanks to the experiment led by pkg-components.

[Pkg-javascript-devel] nodejs: /usr/local on default global module paths ?

Hi, bug #901474 asks the question of wether having nodejs load modules found inside /usr/local (share for pure js, lib for addons) is something to be expected by default or not. Anyone can already set NODE_PATH env variable, in a somewhat compatible way with other environments, to set a

[Pkg-javascript-devel] Bug#901474: Any news ?

2018-08-01 21:55 GMT+02:00 Bastien ROUCARIES : > Hi,* > > Could be possible to merge this patch ? > > Thnkas > Yes, going to. Am busy as hell. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net

[Pkg-javascript-devel] Bug#904274: Bug#904274: nodejs: Debian nodejs is not ABI-compatible with upstream nodejs

Forwarded: https://github.com/nodejs/node/issues/21897 2018-07-22 17:37 GMT+02:00 Elana Hashman : > Package: nodejs > Version: 8.10.0~dfsg-2 > Severity: important > > This bug was initially reported downstream against Ubuntu in > https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1779863 by

[Pkg-javascript-devel] Bug#904274: Bug#904274: nodejs: Debian nodejs is not ABI-compatible with upstream nodejs

All other things being clear... 2018-07-22 20:30 GMT+02:00 Elana Hashman : > > TLDR; the pratical solution is to promote compilation of addons - which is >> *straightforward* on debian/ubuntu/fedora and derivatives >> (you just need to explain which development packages must be installed). >> > >

[Pkg-javascript-devel] Bug#904274:

2018-07-22 22:01 GMT+02:00 Nicolas Noble : > I need to voice my disagreement with the notion that compilation of addons > is straightforward, by the way, for a few reasons. > > 1) compiling code IS difficult. Planning for every single compiler, edge > case, combinations of libraries, etc is

Re: [Pkg-javascript-devel] node packages in NEW

2018-09-05 23:14 GMT+02:00 Bastien ROUCARIES : > On Wed, Sep 5, 2018 at 11:08 PM Bastien ROUCARIES > wrote: > > > > On Wed, Sep 5, 2018 at 10:50 PM Thorsten Alteholz > wrote: > > > > In order to not lose track of the installed software, providing > something > > > like debian/modules.embedded

[Pkg-javascript-devel] Bug#870460: anyone working on npm?

2018-04-19 7:57 GMT+02:00 Diane Trout : > > Sure ! You could work on a branch of npm pkg-javascript repository, > and ask me for reviewing it and merging it. If all goes well, after that > first > review, you'll work directly on master branch. > > > Hi > > I finally had time to

Re: [Pkg-javascript-devel] Re: Migrating *all* packages from alioth to salsa (Was: migrating my packages from alioth to salsa)

2018-04-19 17:24 GMT+02:00 Julien Puydt : > Hi, > > Le 18/04/2018 à 15:15, Pirate Praveen a écrit : > > > > On ബു, ഏപ്രി 18, 2018 at 12:55 വൈകു, Paolo Greppi < > paolo.gre...@libpf.com> > > wrote: > >> if there is a consensus in the js-team I can perform the mass

Re: [Pkg-javascript-devel] please finalize node-send repository migration from alioth to salsa

2018-04-24 8:53 GMT+02:00 Paolo Greppi : > > ./alioth-migration/disable-repository > ./alioth-migration/disable-repository> /git/pkg-javascript/node-send.git > /js-team/node-send > > Done -- Pkg-javascript-devel

Re: [Pkg-javascript-devel] please finalize three.js repository migration from alioth to salsa [last one !]

2018-04-24 8:59 GMT+02:00 Paolo Greppi : > > ./alioth-migration/disable-repository > ./alioth-migration/disable-repository> /git/pkg-javascript/three.js.git > /js-team/three.js > Done -- Pkg-javascript-devel mailing

Re: [Pkg-javascript-devel] please finalize node-parseurl repository migration from alioth to salsa

2018-04-24 8:49 GMT+02:00 Paolo Greppi : > > ./alioth-migration/disable-repository > ./alioth-migration/disable-repository> /git/pkg-javascript/node-parseurl.git > /js-team/node-parseurl > Done --

Re: [Pkg-javascript-devel] please finalize node-accepts repository migration from alioth to salsa

2018-04-24 8:39 GMT+02:00 Paolo Greppi : > > ./alioth-migration/disable-repository > ./alioth-migration/disable-repository> /git/pkg-javascript/node-accepts.git > /js-team/node-accepts > Done -- Pkg-javascript-devel

Re: [Pkg-javascript-devel] please finalize node-express repository migration from alioth to salsa

2018-04-24 8:45 GMT+02:00 Paolo Greppi : > ./alioth-migration/disable-repository > ./alioth-migration/disable-repository> /git/pkg-javascript/node-express.git > /js-team/node-express > Done -- Pkg-javascript-devel

Re: [Pkg-javascript-devel] please finalize node-log4js repository migration from alioth to salsa

2018-04-24 8:47 GMT+02:00 Paolo Greppi : > > ./alioth-migration/disable-repository > ./alioth-migration/disable-repository> /git/pkg-javascript/node-log4js.git > /js-team/node-log4js > Done -- Pkg-javascript-devel

Re: [Pkg-javascript-devel] please finalize node-type-is repository migration from alioth to salsa

2018-04-24 8:54 GMT+02:00 Paolo Greppi : > > ./alioth-migration/disable-repository > ./alioth-migration/disable-repository> /git/pkg-javascript/node-type-is.git > /js-team/node-type-is > Done --

Re: [Pkg-javascript-devel] bundling solitary nodejs modules as components

2018-04-24 1:20 GMT+02:00 Ben Finney <bign...@debian.org>: > Jérémy Lal <kapo...@melix.org> writes: > > > After years of hesitation... i started to experiment bundling node > > modules as components, thanks to the experiment led by pkg-components. > > I see tha

Re: [Pkg-javascript-devel] nodejs 10 in experimental and soon libnode

2018-04-26 20:57 GMT+02:00 Jonas Smedegaard : > Excerpts from Jérémy Lal's message of april 26, 2018 8:07 pm: > >> I just built node with --shared flag and it seems it's possible to build >> a libnode.so. now, with executable linked to it. >> This goes very well with the fact N-API

Re: [Pkg-javascript-devel] node-gyp install path question

Le dim. 28 oct. 2018 à 08:22, Pirate Praveen a écrit : > On 9/14/18 9:55 PM, Pirate Praveen wrote: > > > > > > On 2018, സെപ്റ്റംബർ 14 9:44:15 PM IST, "Jérémy Lal" > wrote: > >> Le ven. 14 sept. 2018 à 18:12, Pirate Praveen > >> a > >&

[Pkg-javascript-devel] Bug#912986: Bug#912986: nodejs segfaults in selinux enforcing mode

Le lun. 5 nov. 2018 à 15:03, Jade McCormick a écrit : > Source: nodejs > Severity: normal > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate > *** > >* What led up to the situation? > > try to use yarn init on a selinux system in enforcing

[Pkg-javascript-devel] Bug#913508: Bug#913508: nodejs FTBFS with ICU 63.1

Le dim. 11 nov. 2018 à 20:15, László Böszörményi a écrit : > Source: nodejs > Source-Version: 8.11.2~dfsg-1 > Severity: important > Tags: patch > Usertags: icu63 > > Dear Maintainer, > > ICU 63.1 recently released, packaged and uploaded to experimental. > Its transition is going to start soon.

[Pkg-javascript-devel] nodejs 8/10 will stay incompatible with openssl 1.1.1

As it has been the case for previous debian release and openssl 1.1.0, last version of openssl (1.1.1) will require a breaking change in nodejs, support of which is already postponed to nodejs 11. Since nodejs 8 or 10 needs to be built against openssl 1.1.0, i tried the static build. However,

[Pkg-javascript-devel] Bug#904274: nodejs: Debian nodejs is not ABI-compatible with upstream nodejs

Package: nodejs Followup-For: Bug #904274 So if i still think clear about this, the practical thing we, debian maintainers, need to do, is follow https://github.com/nodejs/node/pull/22237/commits/e47d5c6ff9426074184d508c113c85fe93629b05 TLDR "make a custom NODE_MODULE_VERSION". However the

[Pkg-javascript-devel] nodejs 10 RFH checking all modules before upload to unstable

Hi, nodejs 10.15 is in experimental and i think it is very important to upload it to unstable as soon as possible. If anyone could rebuild all node modules against it and report bugs accordingly, it'd be great ! Jérémy -- Pkg-javascript-devel mailing list

Re: [Pkg-javascript-devel] nodejs V10: buffer problem

Should that go to a node-bn.js bug report ? It's not that difficult to fix... Le mar. 1 janv. 2019 à 15:35, Bastien ROUCARIES a écrit : > Hi, > > I believe we will have a huge problem > > > https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-bn.js/1624829/log.gz > > -- >

[Pkg-javascript-devel] Bug#917961: nodejs: missing shlibs prevents build-dependencies on libnode-dev from working correctly

Package: nodejs Version: 10.15.0~dfsg-5 Severity: serious Justification: Policy 8.6 This is a reminder. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux

Re: [Pkg-javascript-devel] nodejs V10: buffer problem

> Le mar. 1 janv. 2019 à 15:35, Bastien ROUCARIES < > roucaries.bast...@gmail.com> a écrit : > Hi, >> >> I believe we will have a huge problem >> >> >> https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-bn.js/1624829/log.gz >> &g

Re: [Pkg-javascript-devel] nodejs V10: buffer problem

Le mar. 1 janv. 2019 à 18:33, Bastien ROUCARIES a écrit : > On Tue, Jan 1, 2019 at 4:25 PM Jérémy Lal wrote: > > > > > >> Le mar. 1 janv. 2019 à 15:35, Bastien ROUCARIES < > roucaries.bast...@gmail.com> a écrit : > >>> > >>&

[Pkg-javascript-devel] Bug#918388: Bug#918388: nodejs should depend or recommend npm

Yes, good idea. I did not in the first place because it was not available. Le sam. 5 janv. 2019 à 19:09, Pirate Praveen a écrit : > Package: nodejs > severity: important > > > Since upstream nodejs comes with npm, people installing nodejs in debian > expect npm to be available. > > -- >

[Pkg-javascript-devel] Bug#918388: Bug#918388: Bug#918388: nodejs should depend or recommend npm

OK, i did not upload it yet. Le sam. 5 janv. 2019 à 20:00, Jonas Smedegaard a écrit : > Quoting Jérémy Lal (2019-01-05 19:14:10) > > Yes, good idea. I did not in the first place because it was not > available. > > Please let's only suggest npm: > > Debian Policy says

[Pkg-javascript-devel] Bug#913508: nodejs FTBFS with ICU 63.1

Package: src:nodejs Followup-For: Bug #913508 I believe this is fixed however i'll let the reporter close the bug, because i'm not sure i understand perfectly the original bug report. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500,

[Pkg-javascript-devel] Bug#900653: nodejs: autopkgtest regression

Package: src:nodejs Followup-For: Bug #900653 Control: fixed -1 10.15.0~dfsg-6 Fixed in unstable. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux

[Pkg-javascript-devel] Bug#918456: nodejs: Buffer deprecation warning to stderr makes many tests fail

Package: nodejs Version: 10.15.0~dfsg-6 Severity: serious Nodejs 10.15 prints a deprecation warning to stderr when deprecated Buffer() call is made. (Correct way is now to use e.g. Buffer.from()). This makes many packages tests fail because autopkgtest fails when something is printed to stderr.

[Pkg-javascript-devel] Bug#919588: Bug#919588: nodejs: FTBFS nodejs

Le jeu. 17 janv. 2019 à 17:23, Dimitri John Ledkov a écrit : > Package: nodejs > Version: 10.15.0~dfsg-8 > Severity: important > Tags: ftbfs > > Dear Maintainer, > > When trying to rebuild nodejs in a clean sid chroot, it fails to do so. > > I've tried this on amd64 and ppc64le. Both were

Re: [Pkg-javascript-devel] Status of libv8?

Le ven. 18 janv. 2019 à 11:37, Andreas Tille a écrit : > Hi, > > I just realised that one of my packages does not migrate to testing due > to its dependency from r-cran-v8 and in turn from libv8-devel. I > realised that while libv8 has 3 security bugs which are set to > stretch-ignore (#760385,

Re: [Pkg-javascript-devel] Status of libv8?

Le ven. 18 janv. 2019 à 13:04, Andreas Tille a écrit : > Hi Jérémy, > > On Fri, Jan 18, 2019 at 11:51:38AM +0100, Jérémy Lal wrote: > > > However, when reading > > > > > >https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773671#59 > > > > >

Re: [Pkg-javascript-devel] Status of libv8?

Le ven. 18 janv. 2019 à 18:39, Andreas Tille a écrit : > On Fri, Jan 18, 2019 at 01:46:13PM +0100, Jérémy Lal wrote: > > Le ven. 18 janv. 2019 à 13:04, Andreas Tille a écrit > : > > > > > > > > Possible solutions (besides not using it at all):

Re: [Pkg-javascript-devel] Status of libv8?

Le lun. 21 janv. 2019 à 10:08, Andreas Tille a écrit : > Hi Jonas, > > On Fri, Jan 18, 2019 at 08:04:33PM +0100, Jonas Smedegaard wrote: > > Quoting Andreas Tille (2019-01-18 18:39:34) > > > I'd prefer > > > > > > - change nodejs to build its v8 as a shared lib, and provide it it > > >makes

[Pkg-javascript-devel] Bug#919585: RM: node-groove/2.5.0-4 -- RoM; FTBFS; orphaned; abandoned upstream

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm Note that groovebasin is already removed from testing. Thanks Jérémy -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'),

[Pkg-javascript-devel] Bug#905415: libnode-dev: broken symlinks: /usr/include/nodejs/deps/uv/include/{uv, uv.h} -> ../../../../{uv, uv.h}

Le dim. 20 janv. 2019 à 02:12, Andreas Beckmann a écrit : > Followup-For: Bug #905415 > Control: reopen -1 > Control: reassign -1 libnode-dev 10.15.0~dfsg-8 > Control: retitle -1 libnode-dev: broken symlinks: > /usr/include/nodejs/deps/uv/include/{uv,uv.h} -> ../../../../{uv,uv.h} > > Hi, > >

[Pkg-javascript-devel] Bug#914965: Bug#914965: nodejs: Node.js 10

Le jeu. 29 nov. 2018 à 09:15, Olaf van der Spek a écrit : > Package: nodejs > Version: 8.11.2~dfsg-1 > Severity: wishlist > > Dear Maintainer, > > Node.js 10 is available.. could it be packaged? It's waiting in NEW: https://ftp-master.debian.org/new.html Jérémy -- Pkg-javascript-devel

Re: [Pkg-javascript-devel] components without major risks

Le mar. 27 nov. 2018 à 15:22, Xavier a écrit : > Le 27/11/2018 à 15:03, Jonas Smedegaard a écrit : > > Quoting Xavier (2018-11-27 14:00:42) > >> Le 27/11/2018 à 11:55, Jonas Smedegaard a écrit : > >>> Hi Xavier and Paolo, > >>> > >>> Please allow me to highlight this security-related detail: >

Re: [Pkg-javascript-devel] script to generate debian/watch for embedding nodejs modules

Le lun. 26 nov. 2018 à 17:29, Xavier a écrit : > Xavier wrote: > >> ... > >> Looks acceptable IMO > > > > Policy update: > > - components used only during build => not used in version > >(except if they inject some code) > > - components without major risks=> not used in version > > -

[Pkg-javascript-devel] node-duplexer2 and 3 - possible to keep only one ?

Hi, is there a reason to keep both node-duplexer2 node-duplexer3 packages ? It seems it's feasible to keep only one, unless we miss a deeper issue ? Jérémy -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net

[Pkg-javascript-devel] Bug#918889: npm: LRUCache 3 breaks npm - but it's npm not calling new on constructor

Package: npm Version: 5.8.0+ds6-2 Severity: normal Pending fix. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores) Locale:

[Pkg-javascript-devel] removing node-yn ?

Hi, anyone using node-yn ? Instead of fixing it i'd rather remove it (it looks pretty useless to me). Jérémy -- 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] nodejs 10 in unstable

With which javascript maintainers can - install native js packages to /usr/share/nodejs - install addons to /usr/lib//nodejs - stop using dh_nodejs to build addons and instead Build-Depends libnode-dev (instead of nodejs-dev). In that case, depending on nodejs is not necessary (unless the addon

Re: [Pkg-javascript-devel] mocha timeout

Le ven. 11 janv. 2019 à 09:26, Xavier a écrit : > Hi all, > > for some packages, default mocha timeout (2000 ms) is too short for > autopkgtest. I patched some package to increase it but I think we could > increase this timeout directly in mocha source to avoid these failures. > It's somewhat

Re: [Pkg-javascript-devel] review node-braces 2.3.1 with pkg-component setup

Le mer. 9 janv. 2019 à 11:35, Paolo Greppi a écrit : > Il 08/01/19 17:22, Jonas Smedegaard ha scritto: > > Hi Paolo, > > > > Quoting Paolo Greppi (2019-01-08 17:11:16) > >> While updating node-braces from 2.0.2 to 2.3.1, I found that the > node-split-string version that we have in debian

Re: [Pkg-javascript-devel] yarnpkg is ready !

Le mer. 9 janv. 2019 à 22:41, Paolo Greppi a écrit : > Hi, > > packaging of yarnpkg 1.13.0 is complete. > > To embed the tiny modules that were rejected by ftp-master (and a few > more) I used the procedure: > https://wiki.debian.org/Javascript/GroupSourcesTutorial > but without tracking

Re: [Pkg-javascript-devel] GroupSourcesTutorial page to review

Hi Xavier, The example in Provides section should be written Provides: node-ta, node-tb ? 2018-09-10 23:34 GMT+02:00 Xavier : > Dear fellow maintainers, > > QA team accepted my changes, so now fakeupstream.cgi is able to handle > npmjs multiple sources. I've written a draft here: >

[Pkg-javascript-devel] Bug#909024: the fix needs nodejs 10.6

Le lun. 17 sept. 2018 à 18:39, Pirate Praveen a écrit : > Control: tags -1 help > > chownr 1.1 will now use fs.lchown if available, but we will have to wait > till nodejs 10.6 is available for the actual fix. So I will keep this > bug open. > > But chownr 1.1 tests are currently failing so help

[Pkg-javascript-devel] Bug#920538: Bug#920538: node-date-now: flaky autopkgtest as it times out sometimes

Le sam. 26 janv. 2019 à 20:15, Paul Gevers a écrit : > ../.. > ok 6 should be truthy > > 1..6 > # tests 6 > # pass 4 > # fail 2 > > autopkgtest [14:34:45]: test command1: ---] > It's not a test timeout, but the test is flaky indeed. Trying to fix it. Jérémy --

[Pkg-javascript-devel] Bug#922075: Bug#922075: npm: segfault during extract on i386

Le ven. 29 mars 2019 à 14:22, Bernhard Übelacker a écrit : > Hello Jérémy, > > Am 29.03.19 um 12:44 schrieb Jérémy Lal: > > This fails too: > > yarnpkg add electron-spellchecker@1.1.2 > > > > Are you all doing this on qemu or on real hardware ? > > On i6

[Pkg-javascript-devel] Bug#922075: Bug#922075: npm: segfault during extract on i386

Le ven. 5 avr. 2019 à 18:31, Bernhard Übelacker a écrit : > Hello Jérémy, > sorry for the delay. > > > > So if i run qemu with the first P6 cpu that comes to mind, pentiumpro, > > npm install electron-spellchecker@1.1.2 > > no longer crashes. > > > > That doesn't prove there is no crash on a

[Pkg-javascript-devel] Bug#922075: Bug#922075: npm: segfault during extract on i386

Le jeu. 28 mars 2019 à 11:58, Bernhard Übelacker a écrit : > Hello Jérémy Lal, > unfortunately yes, it still crashes. > > Attached file shows a test starting with a minimal up-to-date > Buster i386 qemu VM, and as far as I see after the crash > /usr/local/lib/node_modu

Re: [Pkg-javascript-devel] npm updating?

Le dim. 31 mars 2019 à 18:48, Danny Piper a écrit : > Hello, I wanted to ask when it is intended to release a newer npm version > via the testing source? I am currently getting an error in connection with > node. As a result, not all functions are available in npm -.- > The screenshot you sent

[Pkg-javascript-devel] Bug#922075: Bug#922075: npm: segfault during extract on i386

Control: reassign -1 nodejs This fails too: yarnpkg add electron-spellchecker@1.1.2 Are you all doing this on qemu or on real hardware ? On i686 ? I'm asking because buster does not support i586, nor does nodejs, and it seems qemu defaults to something < i686 (to be verified). Jérémy --

[Pkg-javascript-devel] v8 drops support on mips

Let's cross fingers that someone will maintain a workable fork of v8/node: https://github.com/nodejs/node/issues/26179 Jérémy -- 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] the status of JS in buster: great !

Le lun. 25 févr. 2019 à 17:32, Paolo Greppi a écrit : > Good job team ! > > We now have: > - platform: >- node 10.15.1 (current LTS) >- npm 5.8.0 (current is 6.8.0) and yarnpkg 1.13.0 (current) > - tools: buble, babel, rollup, webpack, browserify, gulp, grunt ... > - and libraries:

[Pkg-javascript-devel] Bug#921625: Bug#921625: node-gyp install fails

Le sam. 2 mars 2019 à 18:21, Paolo Greppi a écrit : > I got the same error on amd64 while running yarnpkg in root of vscode > source: > > git clone https://github.com/Microsoft/vscode > cd vscode > yarnpkg > ... > [4/4] Building fresh packages... > [1/14] ⠠ gc-signals > [2/14] ⠠ keytar > [3/14]

Re: [Pkg-javascript-devel] libnode *might* need abi bump related to openssl 1.1.1 api break... or not...

Le lun. 18 févr. 2019 à 21:16, Sebastian Andrzej Siewior a écrit : > On 2019-02-18 11:08:30 [+0100], Jérémy Lal wrote: > > hi ! > Hi, > > > It happens that that api breakage has been reverted and is merged in > > openssl 1.1.1 stable branch: > > > https

Re: [Pkg-javascript-devel] Tutorial to review/update

Cool, "Of course you need to configure salsa with a valid GitLab token." appears twice. Le mar. 19 févr. 2019 à 15:41, Xavier a écrit : > Hi all, > > I started a tutorial for js-team beginners: > https://wiki.debian.org/Javascript/Tutorial > > Please review/update it ;-) > > Cheers, > Xavier >

[Pkg-javascript-devel] Bug#919588: Bug#919588: nodejs: FTBFS nodejs

Le mer. 13 mars 2019 à 01:07, Santiago Vila a écrit : > Hi. > > Regarding eatmydata: Would "does not build with eatmydata" > be acceptable for you as "wishlist"? > > (I think around 99.98% of all packages are buildable with it) > > (If the answer is no, I will not bother, of course) > Yes, of

[Pkg-javascript-devel] Bug#919588: Bug#919588: nodejs: FTBFS nodejs

> > I am using sbuild + schroot + eatmydata. Will now try without eatmydata > to make sure eatmydata is not to blame for the failures. > > On Thu, 17 Jan 2019, Jérémy Lal wrote: > > > It's building all right - the problem you see is that there are some > tests (4) fail

[Pkg-javascript-devel] Fwd: Bits from the Release Team: Debian 10 'buster' is frozen; let's get it in shape

Anyone willing to add Node 10 and libnode to what's new in debian buster ? -- Forwarded message - From: Paul Gevers Date: mar. 12 mars 2019 à 20:53 Subject: Bits from the Release Team: Debian 10 'buster' is frozen; let's get it in shape To: -BEGIN PGP SIGNED MESSAGE-

[Pkg-javascript-devel] Bug#925211: uglifyjs conflicts with webpack which can hinder JS maintainers work

Hi, it takes some time to understand what's happening here, and since fixing it properly will require quite some work on multiple packages, i add my notes to this bug report. Nota Bene: i use "webpack" here but the sake of the example. # Situation Because uglify version 2 compiles software that

[Pkg-javascript-devel] Bug#925211: Bug#925211: uglifyjs conflicts with webpack which can hinder JS maintainers work

Le ven. 22 mars 2019 à 15:51, Jonas Smedegaard a écrit : > Quoting Jérémy Lal (2019-03-22 14:54:07) > > it takes some time to understand what's happening here, and since > > fixing it properly will require quite some work on multiple packages, > > i add my notes to this b

Re: [Pkg-javascript-devel] V8 depends from outdated and unmaintained libv8 with security issues

Le ven. 8 févr. 2019 à 10:31, Jeroen Ooms a écrit : > On Fri, Feb 8, 2019 at 9:44 AM Jérémy Lal wrote: > > > > > > > > Le ven. 8 févr. 2019 à 07:36, Jeroen Ooms a écrit > : > >> > >> For those following this discussion: there is now a versio

Re: [Pkg-javascript-devel] V8 depends from outdated and unmaintained libv8 with security issues

Le ven. 8 févr. 2019 à 13:53, Andreas Tille a écrit : > 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-javascript-devel] Bug#920329: marked as done (libnode64: Please include libv8_*.so libraries)

Le ven. 8 févr. 2019 à 15:57, Debian Bug Tracking System < ow...@bugs.debian.org> a écrit : > Your message dated Fri, 08 Feb 2019 14:55:40 + > with message-id > and subject line Bug#920329: fixed in nodejs 10.15.1~dfsg-3 > has caused the Debian Bug report #920329, > regarding libnode64:

Re: [Pkg-javascript-devel] V8 depends from outdated and unmaintained libv8 with security issues

Le ven. 8 févr. 2019 à 15:45, Dylan Aïssi a écrit : > Hi Andreas, > > Le ven. 8 févr. 2019 à 15:39, Andreas Tille a écrit : > > > > Dylan, will you find time to have a look? (I don't today and tomorrow - > later it might be to late ...) > > > > Not sure to understand what you mean. To build

[Pkg-javascript-devel] libnode *might* need abi bump related to openssl 1.1.1 api break... or not...

hi ! Nodejs c++ addons (modules) in buster are built using libnode-dev - a great improvement over previous "situation". However upstream libnode embeds its dependencies, whereas almost all debian libnode dependencies are shared. Modules authors expect a given node ABI to offer the same versions,

[Pkg-javascript-devel] Bug#922075: Bug#922075: npm: segfault during extract on i386

Le lun. 11 févr. 2019 à 20:39, Teemu Ikonen a écrit : > Package: npm > Version: 5.8.0+ds6-3 > Severity: normal > > I get a repeatable segfault from npm install by doing the following on > i386 (deleting the local .npm and node_modules dirs is not needed to > reproduce). > > -*- > > $ rm -rf

Re: [Pkg-javascript-devel] V8 depends from outdated and unmaintained libv8 with security issues

Le lun. 11 févr. 2019 à 09:11, Dominique Dumont a écrit : > Hi > > On Friday, 8 February 2019 12:10:01 CET Jérémy Lal wrote: > > > I suppose i need to ask a removal of libv8 from unstable (it's removed > > > from testing) to > > > be able to "take"

[Pkg-javascript-devel] Bug#921625: Bug#921625: node-gyp install fails

Le jeu. 7 févr. 2019 à 13:21, Teemu Ikonen a écrit : > Package: node-gyp > Version: 3.8.0-4 > Severity: normal > Tags: upstream > > I get this output from 'node-gyp install' on i386: > > -*- > > $ node-gyp install > gyp info it worked if it ends with ok > gyp info using node-gyp@3.8.0 > gyp info

[Pkg-javascript-devel] Bug#921625: Bug#921625: node-gyp install fails

Le jeu. 7 févr. 2019 à 14:28, tpikonen a écrit : > > > On Thu, Feb 7, 2019 at 3:09 PM, Jérémy Lal wrote: > > It's fair to expect this to work, however you're supposed to get your > > nodejs headers > > from libnode-dev package, not by downloading them. > > (sti

[Pkg-javascript-devel] Bug#921625: Bug#921625: node-gyp install fails

Le jeu. 7 févr. 2019 à 15:30, tpikonen a écrit : > > > On Thu, Feb 7, 2019 at 3:43 PM, Jérémy Lal wrote: > >> > I believe node on i686 is not supported and will segfault. > >> > >> Do you mean node-gyp? At least nodejs.org offers x86 downloads of >

Re: [Pkg-javascript-devel] V8 depends from outdated and unmaintained libv8 with security issues

Le mar. 29 janv. 2019 à 19:41, Jeroen Ooms a écrit : > Is there another version of libv8 available on Debian? I'm willing to > try to port it to a newer version of V8. The issue with libv8 has > always been that Google refuses to define a stable API, and they do a > new release every day (no

[Pkg-javascript-devel] Bug#921074: libnode-dev: missing dependency libssl-dev

Package: libnode-dev Version: 10.15.1~dfsg-1 Severity: important I think the dependency on libssl-dev is important to add. Isn't it ? -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture:

Re: [Pkg-javascript-devel] ?= =?utf-8?q? RFS: node-js-beautify 1.7.5+dfsg-2

Le ven. 1 févr. 2019 à 18:52, Paolo Greppi a écrit : > Il 01/02/19 16:59, Xavier ha scritto: > > Le Vendredi, Février 01, 2019 16:49 CET, Jonas Smedegaard < > jo...@jones.dk> a écrit: > > > >> Quoting Xavier (2019-02-01 16:30:01) > >>> Le 01/02/2019 à 15:34, Jonas Smedegaard a écrit : >

[Pkg-javascript-devel] Bug#888903: jsbeautifier, node-js-beautify: both ship /usr/bin/js-beautify

Package: node-js-beautify Version: 1.7.5+dfsg-1 Followup-For: Bug #888903 Hi, i find it funny that no one even tried to solve this bug: both packages (python-jsbeautifier, node-js-beautify) have the same upstream ! The solution here is to provide two dpkg-alternative to /usr/bin/js-beautify.

[Pkg-javascript-devel] Bug#888903: Bug#888903: 888903

Le jeu. 31 janv. 2019 à 09:12, Sébastien Delafond a écrit : > To me the straightforward solution here is not dpkg-alternative, but > what Ivo recommended, since it only involves modifying *one* package. > Okay, thank you for your quick reply. To me two executables with the same name and the

[Pkg-javascript-devel] Bug#888903: Bug#888903: Bug#888903: jsbeautifier, node-js-beautify: both ship /usr/bin/js-beautify

Le jeu. 31 janv. 2019 à 09:30, Paolo Greppi a écrit : > Il 31/01/19 01:15, Jérémy Lal ha scritto: > > ... > > Hi, > > > > i find it funny that no one even tried to solve this bug: > > both packages (python-jsbeautifier, node-js-beautify) > > have th

Re: [Pkg-javascript-devel] Bug#921384: Bug#921384: node-stringprep breaks node-xmpp autopkgtest

Le mar. 5 févr. 2019 à 10:40, Paolo Greppi a écrit : > Il 04/02/19 22:01, Jérémy Lal ha scritto: > > Le lun. 4 févr. 2019 à 21:51, Paul Gevers elb...@debian.org>> a écrit : > > > > ... > > With a recent upload of node-stringprep the autopkgtest of node-x

[Pkg-javascript-devel] Bug#920678: Bug#920678: nodejs: FTBFS in Buster

Le lun. 28 janv. 2019 à 10:42, Ritesh Raj Sarraf a écrit : > Source: nodejs > Version: 8.11.2~dfsg > Severity: serious > Justification: fails to build from source (but built successfully in the > past) > > Dear Maintainer, > > I have been trying to build package nodejs from Buster but it fails

  1   2   3   4   5   >