Re: [Pkg-javascript-devel] Javascript team policy and rejection of node-three binary package [and 1 more messages]
On Mon, Mar 12, 2018 at 7:52 AM, Pirate Praveen wrote: > > > On March 12, 2018 3:34:26 AM GMT+05:30, Bastien ROUCARIES > wrote: >>Done for node-has using node-function-bind but it break uscan for >>node-has >> >>Bill could you get a glimpse, I will like to create something more >>robust > > I think it is better to create a native Debian package (so no need for uscan > or repackaging) node-tiny-modules instead of adding to random modules. Yes I concours but we could also improve uscan in order to get something easier. It is orthogonal Bastien > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] Javascript team policy and rejection of node-three binary package [and 1 more messages]
On Sun, Mar 11, 2018 at 9:15 PM, Bill Allombert wrote: > On Sun, Mar 11, 2018 at 02:48:40PM +0530, Pirate Praveen wrote: >> > * Some Javascript modules are very small, resulting in lots of small >> > packages >> >> I think we need to balance the small packages concern with number of >> times such small packages are used. >> >> node-has was rejected recently because it was "too small". I agree if >> only one, two or even three modules depend on it embedding it is okay (I >> have been doing that already). But when more than three modules need a >> tiny module? Is it really better to embed it that many times? > > You should not embed them. Instead you can merge several tiny > modules together and ship them as a single .deb, which eventually > Provides: node-mod1, node-mod2 etc. So package can still Depends on the > individual names. Done for node-has using node-function-bind but it break uscan for node-has Bill could you get a glimpse, I will like to create something more robust > Cheers, > -- > Bill. > > Imagine a large red swirl here. > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] node-has_1.0.1-1_amd64.changes REJECTED
Hi, I will do some homework, not yet uploaded, but I think that it is more in line for ftpmaster I have uploaded to mentors for comments: The respective dsc file can be found at: https://mentors.debian.net/debian/pool/main/n/node-function-bind/node-function-bind_1.1.1+ds-1.dsc If you do not yet have a sponsor for your package you may want to go to https://mentors.debian.net/sponsors/rfs-howto/node-function-bind I have not yet uploaded, but here is a tar.xz On Fri, Mar 2, 2018 at 9:46 AM, Joerg Jaspert wrote: > On 14959 March 1977, Pirate Praveen wrote: > 8 node modules (all of them dependencies of gitlab) depend on this > module (colormin, cssnano, eslint-import-resolver-webpack, > eslint-plugin-import, postcss-merge-idents, postcss-minify-selectors, > postcss-reduce-transforms, postcss-zindex). Do you think duplicating > this code 8 times or maintaining 8 patches are better approach than this? >>> For one line code: yes. You can never change this one line anyway. >> I'd like to ask other ftp masters if they agree with this assessment. >> How do we know for sure we will never have to change this line? Even if >> I agree this need not be changed, is having duplicated work 8 times >> still better compromise? > > Duplicate of one line? Yes. > > Leaving out the insanity of ways that node goes with its design of > idiotically small modules for things, lets consider what it means in > Debian terms: > > A one line, no matter if its 20 or 1000 characters long, needs a > package. Upstream with license, readme, maybe tests, in Debian then with > all the stuff in debian/, most files larger than the actual code. > Then you end up with the .deb. Now that and the source get onto mirrors. > And into all packages files, blowing them up. And needing to be > processed in all the various locations all over. > > So we have 114 bytes of code and 50 to a hundred times that size of > metadata, on every mirror. And one more stanza in the packages file to > parse for every tool, yet more data and time at totally unrelated > places. > > Thats why we ended up long ago to deny small packages. Yes, most of node > is small, so we really dislike it, but if its at least a bit more than a > line, we grudgingly accepted it. (Also, actually most of node is unfit > for packaging, neither is the nodejs system made to be packaged, nor is > Debian made to handle this stuff). > > > I think reject faq needs to make it more clear on size, currently its > included in "Package split". I'm unsure what a good value is for minimum > size. It can't be one value. But 114bytes of source? I'm with > Bastian/Chris here. > > -- > bye, Joerg > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#889048: [node-source-map] FTBFS: lib/mappings.wasm
Please next time upload to experimental. It is a good idea to upload now newer version to experimental. BTW bug in reverse depends should be now important not serious -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#878006: moreinformation about node-constants-browserify
control: tags -1 + moreinfo I need more info How can I reproduce and so on -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] Bug#877212: node-d3-color: B-D npm not available in testing
Le 29 septembre 2017 19:34:24 GMT+02:00, "Jérémy Lal" a écrit : >2017-09-29 19:24 GMT+02:00 Andreas Beckmann : > >> Package: node-d3-color >> Version: 1.0.3-1 >> Severity: serious >> Justification: Build-Depends not satisfiable in testing >> Control: block -1 with 857986 >> Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9 -10 >> Control: reassign -2 node-d3-format 1.2.0-1 >> Control: retitle -2 node-d3-format: B-D npm not available in testing >> Control: block -2 with 857986 >> Control: reassign -3 node-d3-queue 3.0.7-1 >> Control: retitle -3 node-d3-queue: B-D npm not available in testing >> Control: block -3 with 857986 >> Control: reassign -4 node-d3-selection 1.1.0-1 >> Control: retitle -4 node-d3-selection: B-D npm not available in >testing >> Control: block -4 with 857986 >> Control: reassign -5 d3-timer 1.0.7-1 >> Control: retitle -5 d3-timer: B-D npm not available in testing >> Control: block -5 with 857986 >> Control: reassign -6 node-filesize 3.5.10+dfsg-1 >> Control: retitle -6 node-filesize: B-D npm not available in testing >> Control: block -6 with 857986 >> Control: reassign -7 node-gulp-babel 7.0.0-1 >> Control: retitle -7 node-gulp-babel: B-D npm not available in testing >> Control: block -7 with 857986 >> Control: reassign -8 node-babel-plugin-transform-define 1.3.0-1 >> Control: retitle -8 node-babel-plugin-transform-define: B-D npm not >> available in testing >> Control: block -8 with 857986 >> Control: reassign -9 node-babel 6.25.0+dfsg-8 >> Control: retitle -9 node-babel: B-D npm not available in testing >> Control: block -9 with 857986 >> Control: reassign -10 node-babylon 6.18.0-1 >> Control: retitle -10 node-babylon: B-D npm not available in testing >> Control: block -10 with 857986 >> >> >> Hi, >> >> with npm not available in testing (and according to #857986 this will >> not change in the near future), these node-* packages must be kept >> out of testing, since they cannot be rebuilt in testing (regardless >of >> any external resources they might need additionally). >> > >Build-Depending on npm is a sign something very wrong, policy-breaking, >is happening, like downloading a npm module during build. > >An example of how wrong the problem is: >``` >override_dh_auto_build: > npm install rollup >``` > >ouch > >I cc-ed everyone to make sure this doesn't happen again. Please fill a lintian bug > >Jérémy -- Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#870956: Bug#870956: Bug#870956: Bug#870956: node-jsdom: should node-jsdom be removed from unstable?
Le 10 septembre 2017 14:46:17 GMT+02:00, Paolo Greppi a écrit : >Il 10/09/2017 08:45, Lucas Nussbaum ha scritto: >> Hi, >> >> On 10/08/17 at 17:38 +0530, Pirate Praveen wrote: >>> I think (from what I remember) this is a dependency of >>> node-jquery-. Though it required many other build tools >also >>> packaged, so it was not touched. I will see if I can confirm this in >the >>> coming days. >> >> Ping? :) >> >> Lucas >> >> >> > >Digging into the pkg-javascript-devel archives I found this message >referring to jsdom: >http://lists.alioth.debian.org/pipermail/pkg-javascript-devel/2016-September/013791.html > >It is also mentioned in the jquery and pump.io tasks: >https://wiki.debian.org/Javascript/Nodejs/Tasks/jquery?highlight=%28jsdom%29 >https://wiki.debian.org/Javascript/Nodejs/Tasks/Pump.io?highlight=%28jsdom%29 > >All in all I think it could be useful > >Paolo Will get a glimpse -- Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#754462: Bug#754462: Bug#754462: Bug#862051: nodejs (6.11.2~dfsg-1) experimental; urgency=medium
Le 1 septembre 2017 14:16:14 GMT+02:00, Mattia Rizzolo a écrit : >On Fri, Sep 01, 2017 at 11:41:36AM +0100, Ian Jackson wrote: >> One thing you I would consider is that it would be nice if scripts in >> Debian packages were made more portable to other distros. So Debian >> packages should gradually change to use /usr/bin/node. I am very >> conservative about these things because I like to keep backporting >> (within Debian) as easy as possible. So if I were the maintainer of >a >> node.js package which had scripts mentioning /usr/bin/nodejs, I would >> probably make that change in buster+1 rather than in buster. > >It's enough to depend on >nodejs (>= 6.11.2~dfsg-1) | nodejs-legacy >And then you can backport it to whatever debian release you like the >most. > >> In buster+1 you should probably consider asking for a lintian warning >> about references to /usr/bin/nodejs. Not because you intend to drop >> /usr/bin/nodejs ever (why do that - see previous emails) but because >> it would be better, as I've just discussed, for Debian packages to >> contain fewer hurdles to adoption elsewhere. > >That's already done. >https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=4ea7bdf953e1fb23bfc85830ad743efaf0ad0373 >https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=7d0c0732e792cf0a0cadeb583c9878463813e24a >(will be in the next lintian release) Please also parse autopkgtest like require ans dix npm2deb -- Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#873148: Fails to properly escape the ; , {, }, <, and > characters
Package: node-shell-quote severity: serious forwarded: https://github.com/substack/node-shell-quote/issues/31 couple of open issues that seem reasonably serious for a package that appears to be intended for sanitising user input before passing it on to the shell: -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#873098: Bug#873098: Use node instead of nodejs
It need in this cas a depend on nodejs (>= 6) On Thu, Aug 24, 2017 at 4:50 PM, Julien Puydt wrote: > Package: npm2deb > Version: 0.2.7-2 > Severity: wishlist > > Now nodejs provides /usr/bin/node -- so the tests (like the require one) > should use node and not nodejs. > > Snark on #debian-js > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#872899: Bug#872899: node-tap: autopkgtests fail with nodejs 6
Le 22 août 2017 11:48:46 GMT+02:00, Jonas Smedegaard a écrit : >Quoting Graham Inggs (2017-08-22 11:35:11) >> Source: node-tap >> Version: 8.0.0-4 >> User: ubuntu-de...@lists.ubuntu.com >> Usertags: origin-ubuntu artful autopkgtest >> >> Hi Maintainer >> >> Since the upload of nodejs 6, node-tap's autopkgtests have been >failing >> [1] with the following error: >> >> # failed 3 of 47 tests >> # skip: 7 >> # time=113059.894ms >> autopkgtest [11:52:27]: test command1: ---] >> autopkgtest [11:52:27]: test command1: - - - - - - - - - - results - >- >> - - - - - - - - >> command1 FAIL non-zero exit status 1 >> >> The tests have been flaky in the past, but now they seem to be >failing >> consistently. > >Perhaps solved in a newer upstream release: Upstream is at version >10.7.2. I am trying to do that. Wainting for ftpmaster for deps > > - Jonas -- Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#872898: Bug#872898: node-browserify-sign: autopkgtests fail with nodejs 6
Le 22 août 2017 11:27:05 GMT+02:00, Graham Inggs a écrit : > >Source: node-browserify-sign >Version: 4.0.4-1 >User: ubuntu-de...@lists.ubuntu.com >Usertags: origin-ubuntu artful autopkgtest > >Hi Maintainer > >Since the upload of nodejs 6, node-browserify-sign's autopkgtests have >been failing [1] with the following error: > >autopkgtest [00:53:25]: summary >require PASS >command1 FAIL stderr: (node:1192) DeprecationWarning: >crypto.pbkdf2 without specifying a digest is deprecated. Please specify > >a digest > >I think the patch below is a reasonable workaround until upstream is >updated. > >--- a/debian/tests/control >+++ b/debian/tests/control >@@ -3,3 +3,4 @@ > > Test-Command: tape test/*.js > Depends: @, node-tape >+Restrictions: allow-stderr I will do it but i prefer another approach > >Regards >Graham > > >[1] >https://ci.debian.net/packages/n/node-browserify-sign/unstable/amd64/ -- Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#872438: Bug#872438: Bug#872438: Bug#872438: src:nodejs: FTBFS on mips64el: Can't determine the arch of ./node
On Fri, Aug 18, 2017 at 7:42 PM, Jérémy Lal wrote: > James Cowgill replied this to my give back request on mip64el: > >> My guess is this GCC-7 bug which is breaking lots of stuff on mips64el >> at the moment: >> https://bugs.debian.org/871514 > >> Thanks, >> James > > Cheers, > > Jérémy Thanks BTW why node has no debug symbols ? Bastien > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#872438: Bug#872438: src:nodejs: FTBFS on mips64el: Can't determine the arch of ./node
Starting program: /home/rouca/nodejs-6.11.2~dfsg/node warning: GDB can't find the start of the function at 0xfff7fcd0c4. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/mips64el-linux-gnuabi64/libthread_db.so.1". warning: GDB can't find the start of the function at 0xfff7fcddc8. [New Thread 0xfff59db1e0 (LWP 516)] [New Thread 0xfff59bb1e0 (LWP 517)] [New Thread 0xfff51bb1e0 (LWP 518)] [New Thread 0xfff49bb1e0 (LWP 521)] [New Thread 0xfff41bb1e0 (LWP 522)] Thread 1 "node" received signal SIGBUS, Bus error. 0x0001 in ?? () (gdb) info register zero at v0 v1 R0 00ffda68 4500d051 53731e19 a0 a1 a2 a3 R4 0001 00ffda98 000120f81220 2ee04241 a4 a5 a6 a7 R8 2ee63501 2ee41019 0003 0003 t0 t1 t2 t3 R12 35436b00 84080018 811372e0 0009 s0 s1 s2 s3 R16 0001 00ffda98 0001 s4 s5 s6 s7 R20 2ee635c8 beeddead 000120f81258 2ee3ed41 t8 t9 k0 k1 R24 000120f82cc8 0001 0015 gp sp s8 ra R28 000120f424b0 00ffda60 00ffda88 3540610c status lo hi badvaddr 04109cf3 604189374cdec514 00ebe2a5 0001 cause pc 00800010 0001 fcsr fir restart dc64 00739600 (gdb) bt warning: GDB can't find the start of the function at 0x3540610b. #0 0x0001 in ?? () #1 0x3540610c in ?? () (gdb) frame #0 0x0001 in ?? () (gdb) -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#872438: Bug#872438: src:nodejs: FTBFS on mips64el: Can't determine the arch of ./node
On Thu, Aug 17, 2017 at 3:54 PM, Felipe Sateler wrote: > Package: src:nodejs > Version: 6.11.2~dfsg-2 > Severity: serious > > nodejs failed to build with this error: > > make[1]: Entering directory '/<>' > # Clean up any leftover processes but don't error if found. > ps awwx | grep Release/node | grep -v grep | cat > /usr/bin/python tools/test.py -p tap \ > --mode=release --flaky-tests=dontcare \ > --arch=mips64el --timeout=3000 message parallel sequential > Can't determine the arch of: './node' > > Can't determine the arch of: './node' > > Can't determine the arch of: './node' The line are : vm = context.GetVm(arch, mode) if not exists(vm): print "Can't find shell executable: '%s'" % vm continue archEngineContext = Execute([vm, "-p", "process.arch"], context) vmArch = archEngineContext.stdout.rstrip() if archEngineContext.exit_code is not 0 or vmArch == "undefined": print "Can't determine the arch of: '%s'" % vm print archEngineContext.stderr.rstrip() continue env = { 'mode': mode, 'system': utils.GuessOS(), 'arch': vmArch, } > > No tests to run. > Makefile:220: recipe for target 'test-ci-js' failed > make[1]: *** [test-ci-js] Error 1 > make[1]: Leaving directory '/<>' > > > Full log at > https://buildd.debian.org/status/fetch.php?pkg=nodejs&arch=mips64el&ver=6.11.2~dfsg-2&stamp=1502862893&raw=0 > > > -- System Information: > Debian Release: buster/sid > APT prefers unstable > APT policy: (500, 'unstable'), (1, 'experimental') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.9.0-3-amd64 (SMP w/2 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), > LANGUAGE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#872433: Bug#872433: Bug#872433: [with solution] Doesn't find modules installed in Debian directories
On Thu, Aug 17, 2017 at 2:49 PM, Julien Puydt wrote: > Hi, > > Le 17/08/2017 à 14:23, Bastien ROUCARIES a écrit : >> Could you get a glimpse at node-minimatch debian/test/runtestsuite ? > > Won't work, since we don't have all the test deps in Debian (lacking > object-keys -- beware we have object-key but that's not what it wants). Could you open a bug or point me to ITP bug ? > >> For the NMIU one lintian warning you are member of team javascript add >> a * team upload at the beginning of changelog. If not you should add a >> * NMU > > I know, but since I had a look at the package yesterday and only filled > the report today, I don't think it would be correct to push anything or > plan an upload (NMU or team, whatever) before I left Thorsten ample time > to answer. > > Cheers, > > Snark > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#872433: Bug#872433: [with solution] Doesn't find modules installed in Debian directories
Could you get a glimpse at node-minimatch debian/test/runtestsuite ? For the NMIU one lintian warning you are member of team javascript add a * team upload at the beginning of changelog. If not you should add a * NMU On Thu, Aug 17, 2017 at 2:19 PM, Julien Puydt wrote: > Hi, > > Le 17/08/2017 à 14:04, Bastien ROUCARIES a écrit : >> Could you also modernize this package ? policy bump, autopkg-test (see >> node-tape) > > I bumped std-ver and dh compat if that's what you mean by policy bump. > There was already an autopkg-test directory and I added a test for my > patch (which has a DEP3 header). > > Here is what my git-log has to say on the changes since debian/1.1.7-2 > was released ; lintian only complains about unreleased-changes, > changelog-should-mention-nmu and source-nmu-has-incorrect-version-number > because I created a 1.4.0-1 and I'm not an uploader : > > commit 706643f1cc5c6a6d72b0fa092379ed6f029b6540 (HEAD -> master) > Author: Julien Puydt > Date: Thu Aug 17 13:54:36 2017 +0200 > > Remove useless build-dep on dh-buildinfo > > commit c5cf00738e9a7c597a86406ddb9ae1c7a8e086a3 > Author: Julien Puydt > Date: Thu Aug 17 13:52:23 2017 +0200 > > Add an autopkgtest for the patch to enable Debian paths > > commit 5303fa0df9bc3d0f223963a5af33da5f511cf245 > Author: Julien Puydt > Date: Thu Aug 17 13:46:31 2017 +0200 > > Add a patch so node_modules isn't always added to searched paths > > commit 92349b284cad11524a4a6f7acb1b979794a1d818 > Author: Julien Puydt > Date: Thu Aug 17 13:42:52 2017 +0200 > > Bump std-ver to 4.0.0 > > commit 9bce40b53ef272e9c1035bbd1ad6c8299b55b654 > Author: Julien Puydt > Date: Thu Aug 17 13:41:45 2017 +0200 > > Bump dh compat to 10 > > commit 16f46e9d3789232de1c2d41471851fbb20490014 > Author: Julien Puydt > Date: Wed Aug 16 19:36:15 2017 +0200 > > Package upstream 1.4.0 > > commit 2ad252931b6710dab0a6d708c11e4cbe30ead326 > Merge: febbf48 68dce8d > Author: Julien Puydt > Date: Wed Aug 16 19:35:45 2017 +0200 > > Updated version 1.4.0 from 'upstream/1.4.0' > > with Debian dir 641fcf33ab138af6a27661a439a7b435ac210f03 > > commit 68dce8d4a97fd679c5214be9dc2e16658a7b7cf3 (tag: upstream/1.4.0, > upstream) > Author: Julien Puydt > Date: Wed Aug 16 19:35:39 2017 +0200 > > New upstream version 1.4.0 > > commit febbf4801383e0b650432dda8eceeeb1f6275248 (origin/master, origin/HEAD) > Author: Mike Gabriel > Date: Thu Dec 15 11:21:37 2016 +0100 > > debian/control: Drop myself from Uploaders: field. > > commit b2e880ef277e4f2ebf7d20386066efc6ffc029fe (tag: debian/1.1.7-2) > Author: Thorsten Alteholz > Date: Fri Jun 17 19:56:34 2016 +0200 > > fix typo > > > > And here is what my d/ch entry looks like: > node-resolve (1.4.0-1) UNRELEASED; urgency=medium > > * New upstream release. > * Bump dh compat to 10. > * Bump std-ver to 4.0.0. > * Add a patch so node_modules isn't always added to search paths. > * Add an autopkgtest to check the patch mentioned above works. > * Remove build-dep on dh-buildinfo. > > -- Julien Puydt Wed, 16 Aug 2017 19:35:50 +0200 > > I think it doesn't look bad, but I'd rather have the uploader (Thorsten > Alteholz) tell me he's ok with me pushing those changes (or part of > them) and doing the upload. > > Cheers, > > Snark on #debian-js -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#872433: Bug#872433: [with solution] Doesn't find modules installed in Debian directories
Let ping me at ro...@debian.org if needed Could you also modernize this package ? policy bump, autopkg-test (see node-tape) On Thu, Aug 17, 2017 at 1:40 PM, Julien Puydt wrote: > Package: node-resolve > Version: 1.1.7-2 > Severity: grave > > Hi, > > I'm surprised nobody reported it yet since it basically makes the > package useless as far as I see, but the current node resolve doesn't > find modules installed in Debian directories : while working on another > package, I was surprised that nothing was found. When investigating > using strace, I saw that resolve.sync was always adding "node_modules" > to the paths it tried, so of course it didn't find anything. > > I got things to work by editing node-modules-paths.js from: > > module.exports = function nodeModulesPaths(start, opts) { > var modules = opts && opts.moduleDirectory > ? [].concat(opts.moduleDirectory) > : ['node_modules']; > > to: > > module.exports = function nodeModulesPaths(start, opts) { > var modules = opts && opts.moduleDirectory > ? [].concat(opts.moduleDirectory) > : ['node_modules', '']; > > ie: I added '' to the list of things to add when generating paths to check. > > The following two lines fail with the unpatched node-resolve, and work > with the patched one: > resolve=require('resolve') > resolve.sync('resolve/lib/core.js', {basedir: '/usr/lib/nodejs'}) > (it should be added in debian/tests/) > > I'm part of the Debian Javascript maintainers team so I can add the > necessary patch (with the right header) and test [and probably push > higher upstream version, std-ver and dh] to the git repository to help > if you want -- but I'm no DD so can't upload myself. > > Cheers, > > Snark on #debian-js > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#861172: Bug#861172: node-jsonstream FTBFS in stretch: Build dependency node-tape is not available
control: owner -1 ro...@debian.org On Tue, Apr 25, 2017 at 2:10 PM, Adrian Bunk wrote: > Source: node-jsonstream > Version: 1.0.3-3 > Severity: serious > > node-jsonstream build-depends on node-tape, which is not in stretch. > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#860382: Install in wrong dir useless
Package: node-jsonstream Version: 1.0.3-1 Severity: grave This package install files under jsonstream instead of JSONStream... Thus it is useless -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] thought replaced by thought2 !!! API are different
Hi, How can I replace thought by tought2 ? API are differents for instance queue method does not exist... I am not against changing it, but I believe a small compatibilty layer in though2 will greatly help or example how to do Bastien -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#847715: Bug#847715: Plan to do a NMU
Here the diff, quite trivial diff --git a/debian/changelog b/debian/changelog index 8d6a8ec..25d57f9 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +node-resumer (0.0.0-2) unstable; urgency=medium + + * Team upload. + * Bug fix: "node-resumer depends on node-through2 (>= 2.3.4), but +only 2.0.3-1 is in unstable", thanks to Adrian Bunk (Closes: #847715). + + -- Bastien Roucariès Tue, 04 Apr 2017 00:12:33 +0200 + node-resumer (0.0.0-1) unstable; urgency=low * Initial release (Closes: #814286) diff --git a/debian/control b/debian/control index a06010f..9f4222e 100644 --- a/debian/control +++ b/debian/control @@ -15,7 +15,7 @@ Package: node-resumer Architecture: all Depends: ${misc:Depends}, nodejs, - node-through2 (>= 2.3.4) + node-through2 (>= 2.0) Description: through stream that starts paused and resumes on the next tick Return a through stream that starts out paused and resumes on the next tick, unless somebody called .pause(). On Tue, Apr 4, 2017 at 12:03 AM, Bastien ROUCARIES wrote: > Hi, > > I plan to do a NMU on this one. > > Do you want the diff ?. > > Bastien > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#847715: Plan to do a NMU
Hi, I plan to do a NMU on this one. Do you want the diff ?. Bastien -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#859098: New upstream version
Package: node-convert-source-map Version: 1.2.0-1 Severity: wishlist Hi, Could you package the new upstream version? It will be nice for browserify -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#858593: reopen
Control: reopen 858593 Control: found 1.20.1-6 -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#850419: Bug#850419: Bug#850419: Local installation seems needed
On Fri, Jan 6, 2017 at 5:41 PM, Jonas Smedegaard wrote: > Quoting Pirate Praveen (2017-01-06 17:12:29) >> Control: severity -1 important >> >> On വെള്ളി 06 ജനുവരി 2017 04:07 വൈകു, Bastien ROUCARIES wrote: >> > Using grunt for node-sprintf-js I get >> > >> > Fatal error: Unable to find local grunt. >> > >> > If you're seeing this message, grunt hasn't been installed locally to >> > your project. For more information about installing and configuring grunt, >> > please see the Getting Started guide: >> > >> > http://gruntjs.com/getting-started >> > >> > Thus it unusable >> > >> >> This is the default behavior of grunt and the upstream is unwilling to >> change this behaviour. To use it for building packages in debian, you >> have to patch Gruntfile.js. >> >> Patches welcome to make grunt look for global tasks by default. You can >> see packages like node-fuzzaldrin-plus for the patch. >> >> https://anonscm.debian.org/cgit/pkg-javascript/node-fuzzaldrin-plus.git/tree/debian/patches/use-global-tasks.patch > > How about patching the error message, as an intermediary step? How about adding an option --global to make grunt global > > - Jonas > > -- > * Jonas Smedegaard - idealist & Internet-arkitekt > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ > > [x] quote me freely [ ] ask before reusing [ ] keep private > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#850419: Bug#850419: Bug#850419: Local installation seems needed
On Fri, Jan 6, 2017 at 6:39 PM, Bastien ROUCARIES wrote: > On Fri, Jan 6, 2017 at 5:41 PM, Jonas Smedegaard wrote: >> Quoting Pirate Praveen (2017-01-06 17:12:29) >>> Control: severity -1 important >>> >>> On വെള്ളി 06 ജനുവരി 2017 04:07 വൈകു, Bastien ROUCARIES wrote: >>> > Using grunt for node-sprintf-js I get >>> > >>> > Fatal error: Unable to find local grunt. >>> > >>> > If you're seeing this message, grunt hasn't been installed locally to >>> > your project. For more information about installing and configuring grunt, >>> > please see the Getting Started guide: >>> > >>> > http://gruntjs.com/getting-started >>> > >>> > Thus it unusable >>> > >>> >>> This is the default behavior of grunt and the upstream is unwilling to >>> change this behaviour. To use it for building packages in debian, you >>> have to patch Gruntfile.js. >>> >>> Patches welcome to make grunt look for global tasks by default. You can >>> see packages like node-fuzzaldrin-plus for the patch. >>> >>> https://anonscm.debian.org/cgit/pkg-javascript/node-fuzzaldrin-plus.git/tree/debian/patches/use-global-tasks.patch >> >> How about patching the error message, as an intermediary step? > > How about adding an option --global to make grunt global And even better add a environment variable GRUNT_FLAGS to pass flag to grunt > > > >> >> - Jonas >> >> -- >> * Jonas Smedegaard - idealist & Internet-arkitekt >> * Tlf.: +45 40843136 Website: http://dr.jones.dk/ >> >> [x] quote me freely [ ] ask before reusing [ ] keep private >> >> -- >> Pkg-javascript-devel mailing list >> Pkg-javascript-devel@lists.alioth.debian.org >> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#850420: Please install bash and zsh completion files
Package: node-grunt-cli Version: 1.2.0-3 Severity: minor Hi Please install completion files -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#850419: Local installation seems needed
Package: node-grunt-cli Version: 1.2.0-3 Severity: serious Using grunt for node-sprintf-js I get Fatal error: Unable to find local grunt. If you're seeing this message, grunt hasn't been installed locally to your project. For more information about installing and configuring grunt, please see the Getting Started guide: http://gruntjs.com/getting-started Thus it unusable -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#850418: Lack of documentation (manpage, offline doc)
Package: node-grunt-cli Version: 1.2.0-3 Severity: important I wish to use grunt-cli for node-sprintf-js but due to lack of documentation I could not go futher. They are no man page and moreover running grunt give me: grunt-cli: The grunt command line interface (v1.2.0) Fatal error: Unable to find local grunt. If you're seeing this message, grunt hasn't been installed locally to your project. For more information about installing and configuring grunt, please see the Getting Started guide: http://gruntjs.com/getting-started -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#772023: Bug#772023: nodejs v4.0.0 released
Le 15 septembre 2015 23:44:25 GMT+02:00, Edmund Grimley Evans a écrit : >> Sorry guys: >> >> ifeq (armel, $(DEB_HOST_ARCH)) >> CC = gcc -march=armv6 >> CXX = g++ -march=armv6 >> export CC >> export CXX >> endif >> >> That's actually not going to work for "armel" hardware... "armel" is >> currently built as "armv4t", so "-march=armv6" is going to cause >> invalid instruction faults on devices running armel.. > >That's deliberate. The V8 library requires ARMv6 + VFP2, and some >armel systems will have that hardware, so the idea is to get nodejs >working on those systems. (Raspberry Pi?) > >The next step would be to get it to fail gracefully, rather than just >crash, on other armel systems, presumably by checking the auxiliary >vector (getauxval). Could we get information why they nees this ? And what is the porting effort needed? Btw openning upstream bug for a pure c ans slow implémentation will ne worthwhile. Un case of problems with compile chain we could fallback to slow but debuggable code. > >By the way, the patch above modified configure and debian/rules. I >think the change to debian/rules makes the change to configure >redundant: you only need to add those 6 lines to debian/rules; if you >use an ARMv6 compiler, the rest works. I'll get back to you if the >latest build fails. > >___ >Pkg-javascript-devel mailing list >Pkg-javascript-devel@lists.alioth.debian.org >http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté. ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Please add me to git
Hi, I plan to add node-esprima. Could you please add me to git ? My alioth login is broucaries-guest. Thanks Bastien ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] Have opened too many RC bugs => I morally should join
On Mon, Apr 21, 2014 at 11:41 PM, valentin OVD wrote: > How do you want to help ? Close RC bug. Try to improvejquery packaging > What are the RC Bugs ? > Did You have already do a contribution for Debian ? Yes imagemagick, lintian, autoconf-archive, kbibtex, cfortran > > Regards. > -- > ovd > ____ > De : Bastien ROUCARIES > Envoyé : 21/04/2014 19:43 > À : pkg-javascript-devel@lists.alioth.debian.org > Objet : [Pkg-javascript-devel] Have opened too many RC bugs => I morally > should join > > Hi, > > I have opened too many RC bug. > > May I join in order to improve the teams? > > I suppose you need to get versionned jquery soon. I can help here. > > Bastien > > ___ > Pkg-javascript-devel mailing list > Pkg-javascript-devel@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Have opened too many RC bugs => I morally should join
Hi, I have opened too many RC bug. May I join in order to improve the teams? I suppose you need to get versionned jquery soon. I can help here. Bastien ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#736779: [src:nodejs] Sourceless file
Package: src:nodejs Version: 0.10.25~dfsg1-1 Severity: serious User: debian...@lists.debian.org Usertags: source-contains-prebuilt-javascript-object X-Debbugs-CC: ftpmas...@debian.org control: found -1 0.10.24~dfsg1-1 I could not find the source of: nodejs 0.10.24~dfsg1-1 (source) doc/sh_javascript.min.js Bastien ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel