[Pkg-javascript-devel] Bug#836205: should be fixed by 2.5.1-1

[Paolo Greppi]

Please note that version 2.5.1-1 should fix this issue since we updated the 
patch that bundles ms to ms version 0.7.2.

https://tracker.debian.org/media/packages/n/node-debug/changelog-2.5.1-1
https://sources.debian.net/src/node-debug/2.5.1-1/debian/patches/00-bundle_ms.diff/#L288

Paolo

-- 
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#853035: mmmh

[Paolo Greppi]

In the log you attached this line:

  [0m Error: timeout of 5000ms exceeded

looks different from what you report in the bug:

  [0m Error: timeout of 1ms exceeded

The test suite is run by upstream (and by us) with this command:

  mocha -t 5000 -b -R spec test/index

this is where the timeout of 5 s comes from.

Not sure if we should worry about this one.
And above all: I'm clueless at why it should fail.

Where did it fail ?
What is special with your test environment ?

Paolo

-- 
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] pre-spring cleaning, please advise

[Paolo Greppi]

This is a good idea ! There is a lot of cruft, especially packages created for 
some obscure reason 2-3 years ago and since then abandoned both by the 
maintainer and by upstream, and superseded by the next cool thing in the nodejs 
ecosystem.

I propose to extract from UDD a list of candidate packages to be removed: those 
not fulfilling the criteria proposed by Jérémy, plus some more like:

- popcon > 20
..

The list would be published for scrutiny here in this mailing list or on the 
wiki for say 2 weeks.

To address the point raised by Ben (i.e. to make sure we don't remove a library 
needed at some point in the future for some other package not yet uploaded), I 
would leave it to the owner of the high-level package IPTs: for each of those 
there is a Task in the wiki or a non-disclosed WIP list - in any case the ITP 
owner knows best and she should manually remove from the list the packages she 
thinks she'll need, providing a rationale (i.e. "needed for yarnpkg").

Once the 2 weeks are over we can proceed mass filing those "candidate for 
removal" bugreports.

Once the additional 2 weeks are over the bugreports can be reassigned to 
ftpmaster.

Paolo

On 28/01/2017 10:17, Jonas Smedegaard wrote:
> Quoting Ben Finney (2017-01-28 03:07:01)
>> Jérémy Lal  writes:
>>
>>> - or having a reverse (build-)dependency, or what's the point ?
>>
>> I am very much in favour of this: node libraries should be in Debian 
>> to provide a library that is needed for some actual program of benefit 
>> to Debian users.
> 
> Agreed.
> 
> 
>> But my eagerness to remove useless packages makes me worry that some 
>> useful ones could be swept up also.
>>
>> One use case I don't see addressed: How will we ensure that a library 
>> is not needed for some other package not yet uploaded to Debian?
> 
> Removal from testing involves filing a bugreport to ftpmaster.  I guess 
> it makes sense if at all uncertain to first file bugreport against the 
> package and cc this list - of not-to-high severity - suggesting the 
> intent (removal from stretch or removal from Debian completely) some 
> time (2 weeks?) before reasigning to ftpmaster.
> 
> Discussing only here is not adequate: Being part of this team and 
> subscribing to this mailinglist is voluntary.
> 
> 
>  - Jonas


-- 
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] Fwd: Bug#768073: [pkg-go] Bug#768073: LXC team take over ITP?

[Paolo Greppi]

This is interesting.

Should we also keep those useless node-* packages out of stretch ?

Note: useless until the actual package we need is packaged (be it browserify, 
yarnpkg ...).

Paolo

 Messaggio Inoltrato 
Oggetto: Bug#768073: [pkg-go] Bug#768073: LXC team take over ITP?
Rispedito-Data: Fri, 17 Feb 2017 16:12:02 +
Rispedito-Da: Jonathan Dowland 
Rispedito-A: debian-bugs-d...@lists.debian.org
Rispedito-CC: w...@debian.org, ad...@hodzic.org
Data: Fri, 17 Feb 2017 16:08:18 +
Mittente: Jonathan Dowland 
Rispondi-a: Jonathan Dowland , 768...@bugs.debian.org
A: 768...@bugs.debian.org, Debian Go Packaging Team 


Hi folks,

We didn't manage to get LXD into the archive in time for the freeze.

We packaged the following specifically as LXD dependencies which did go in:

 * https://tracker.debian.org/pkg/golang-gopkg-flosch-pongo2.v3
 * https://tracker.debian.org/pkg/golang-petname
 (possibly others, hit-list was at https://wiki.debian.org/LXD)

IMHO, and at least for the ones I did, I think we should file RC bugs to
prevent these packages from going into stretch. They should stay in the
archive/sid, for continued work on LXD, but I don't think that they are
valuable on their own in the next release: it's just stuff that people
might try to use that isn't being looked after properly (since the reason
for them being there does not exist), taking up archive space and apt
metadata space, etc.

Thoughts?

-- 
Jonathan Dowland


-- 
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] 2 NMUs for node-findup-sync

[Paolo Greppi]

Hi there today I pushed to mentors.d.n. two NMUs for the
node-findup-sync package.
The first one (0.1.3-1.1) fixes the debian/watch file and a couple of
minor issues.
The second one (0.4.3-0.1) picks up the latest release from upstream.

Here they are:
https://mentors.debian.net/package/node-findup-sync

Getting this package up to date is necessary to unblock node-grunt-cli
(https://tracker.debian.org/pkg/node-grunt-cli) from moving to testing,
which is in turn required on the (long) road to atom
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747824)

Paolo

-- 
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] 2 NMUs for node-findup-sync

[Paolo Greppi]

On 28/10/2016 15:24, Mattia Rizzolo wrote:
> IMHO, you could join the team if you haven't, commit your changes, and

OK, I have sent a couple of commits to
https://anonscm.debian.org/cgit/pkg-javascript/node-findup-sync.git,
they are the changes with higher priority (0.1.3-2).

As I am not 100% sure I get the team upload process right, let's get
this through first; for the next one I'll pull the new upstream version.

> do a team upload instead; while on it also do some random QA, like:
>  * https in Vcs-*

Done

>  * debhelper compat 10
>  * bump std-ver

These I'd keep on hold until we do 0.4.3-1.

> Feel free to ask here for sponsorship, I'll happily review your package
> and upload it.

Mattia please review the first batch of changes, and sponsor the upload
if it's OK.

> Also I'm keeping you in Cc, but please tell me if you're subscribed to
> the list, so I'll drop you from the explicit recipients.

I joined the list !

Paolo



signature.asc
Description: OpenPGP digital signature
-- 
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-findup-sync is marked for autoremoval from testing

[Paolo Greppi]

On 30/10/2016 05:39, Debian testing autoremoval watch wrote:
> node-findup-sync 0.1.3-1 is marked for autoremoval from testing on 2016-12-05
> 
> It (build-)depends on packages with these RC bugs:
> 841698: node-lodash: FTBFS with bash as /bin/sh

The issue with node-lodash can be easily fixed (the patch is provided by
the submitter) but note that the dependency on lodash has been dropped
from the current version of findup-sync:
https://github.com/js-cli/node-findup-sync/compare/v0.1.3...v0.4.3

I plan to update the node-findup-sync package to 0.4.3 soon

Paolo


-- 
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 update the Npm2Deb database about is-fullwidth-code-point

[Paolo Greppi]

The approach of patching away the dependency on is-fullwidth-code-point
with node-wcwidth.js has worked with node-string-width.

For this reason we have closed the ITP for node-is-fullwidth-code-point
https://bugs.debian.org/842191

I believe the Npm2Deb database at
https://wiki.debian.org/Javascript/Nodejs/Database should be updated so
that is-fullwidth-code-point has "error" as readable-stream, and should
point to node-string-width as an example how to patch.

In this way whoever starts to package any one of the 6 other reverse
dependencies of is-fullwidth-code-point other than string-width
(generator-arc, nodeshot, @rstacruz/pnpm, web-component-tester-bundle,
break-string, readline2) is aware.

Thanks,

Paolo



signature.asc
Description: OpenPGP digital signature
-- 
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] RFS: node-wrap-ansi 2.0.0

[Paolo Greppi]

Hi,

I packaged node-wrap-ansi as per this ITP
https://bugs.debian.org/845262, this is the repo:
https://anonscm.debian.org/git/pkg-javascript/node-wrap-ansi.git
it's set up for git-buildpackage and pristine-tar.

Please someone more experienced than me review it and if it's OK sponsor
its upload.

Thanks,

Paolo



signature.asc
Description: OpenPGP digital signature
-- 
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#794890: npm: new upstream version

[Paolo Greppi]

Jonas,

I beg to slightly differ on the point below.

I think of npm or yarn/yarnpkg as the equivalent for the nodejs
ecosystem of python virtualenv. There are workflows where you'd want to
maintain a certain configuration of a webapp, phonegap app or website
using a local set of modules / pinned versions.

Getting npm / yarn into Debian is a high priority task to expand the
Debian user base.
If we have those, from there on all the web developers of the world can
run npm without the -g option and maintain their projects as they like,
possibly using a mixture of globally installed binaries and locally
installed modules.

Paolo

On 23/11/2016 14:57, Jonas Smedegaard wrote:
> Npm is an *alternative* to using Debian packaged nodejs code.
> 
> Users of Debian cannot tell anything about how same or similar tasks 
> could be solved using Debian, because they evidently stopped trying.




signature.asc
Description: OpenPGP digital signature
-- 
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#794890: npm: new upstream version

[Paolo Greppi]

OK whereas if you have no locally installed soso, it will pick the
system node-soso.

I don't know much of the ruby world.

But that looks like the same as you get in python, when you pass the
--system-site-packages option to virtualenv.

By default virtualenv is completely isolated from the global site-packages.

Paolo

On 23/11/2016 15:52, Jérémy Lal wrote:
> 2016-11-23 15:45 GMT+01:00 Paolo Greppi <paolo.gre...@libpf.com>:
>> On 23/11/2016 14:57, Jonas Smedegaard wrote:
>>> Npm is an *alternative* to using Debian packaged nodejs code.
>>>
>>> Users of Debian cannot tell anything about how same or similar tasks
>>> could be solved using Debian, because they evidently stopped trying.
>> Jonas,
>>
>> I beg to slightly differ on the point below.
>>
>> I think of npm or yarn/yarnpkg as the equivalent for the nodejs
>> ecosystem of python virtualenv. There are workflows where you'd want to
>> maintain a certain configuration of a webapp, phonegap app or website
>> using a local set of modules / pinned versions.
>>
>> Getting npm / yarn into Debian is a high priority task to expand the
>> Debian user base.
>> If we have those, from there on all the web developers of the world can
>> run npm without the -g option and maintain their projects as they like,
>> possibly using a mixture of globally installed binaries and locally
>> installed modules.
>>
>> Paolo
> 
> Ha right, about that:
> currently (for fear we would make a big mess) if you install
> debian package node-soso and then in a project you do
> `npm install soso`
> it *will* pull soso module from npmjs repository.
> 
> Any other behavior should be provided by a package
> npm-integration (like rubygems-integration).
> 
> Jérémy
> 
> 




signature.asc
Description: OpenPGP digital signature
-- 
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] enabling tests in node-chalk package

[Paolo Greppi]

Hi,

While working on node-wrap-ansi (which will depend on node-chalk) I
noticed that two of the missing build deps for node-chalk
(require-uncached and resolve-from) are required precisely for testing,
that's why the mocha line in debian/rules is commented ATM.

BUT they are only required for testing on Windows ! so the dependency
can be easy to get rid of by simply patching test.js.

I have tried that, and the tests run and pass from the command line
(just type "mocha"). That's fine, except that if I enable the tests
during the build process, uncommenting the line above in debian/rules,
they fail like this:

  

  6 passing (32ms)
  14 failing

  1) chalk should style string:

  AssertionError: 'foo' == '\u001b[4mfoo\u001b[24m'
  + expected - actual

  -foo
  +foo

  at Context.
(/root/debian/node-chalk/node--chalk/test.js:10:10)

  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:223:21)

  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:216:7)

  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:373:10)

  at /usr/lib/nodejs/mocha/lib/runner.js:451:12

  at next (/usr/lib/nodejs/mocha/lib/runner.js:298:14)

  at /usr/lib/nodejs/mocha/lib/runner.js:308:7

  at next (/usr/lib/nodejs/mocha/lib/runner.js:246:23)

  at Immediate._onImmediate
(/usr/lib/nodejs/mocha/lib/runner.js:275:5)
  at processImmediate [as _immediateCallback] (timers.js:383:17)


  2) chalk should support applying multiple styles at once:

  AssertionError: 'foo' ==
'\u001b[31m\u001b[42m\u001b[4mfoo\u001b[24m\u001b[49m\u001b[39m'
  + expected - actual

  -foo
  +foo

  at Context.
(/root/debian/node-chalk/node-chalk/test.js:16:10)

  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:223:21)

  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:216:7)

  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:373:10)

  at /usr/lib/nodejs/mocha/lib/runner.js:451:12

  at next (/usr/lib/nodejs/mocha/lib/runner.js:298:14)

  at /usr/lib/nodejs/mocha/lib/runner.js:308:7

  at next (/usr/lib/nodejs/mocha/lib/runner.js:246:23)

  at Immediate._onImmediate
(/usr/lib/nodejs/mocha/lib/runner.js:275:5)
  at processImmediate [as _immediateCallback] (timers.js:383:17)


  3) chalk should support nesting styles:

  AssertionError: 'foobar!' ==
'\u001b[31mfoo\u001b[4m\u001b[44mbar\u001b[49m\u001b[24m!\u001b[39m'
  + expected - actual

  -foobar!
  +foobar!

  at Context.
(/root/debian/node-chalk/node-chalk/test.js:21:10)

  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:223:21)

  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:216:7)

  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:373:10)

  at /usr/lib/nodejs/mocha/lib/runner.js:451:12

  at next (/usr/lib/nodejs/mocha/lib/runner.js:298:14)

  at /usr/lib/nodejs/mocha/lib/runner.js:308:7

  at next (/usr/lib/nodejs/mocha/lib/runner.js:246:23)

  at Immediate._onImmediate
(/usr/lib/nodejs/mocha/lib/runner.js:275:5)
  at processImmediate [as _immediateCallback] (timers.js:383:17)


  4) chalk should support nesting styles of the same type (color,
underline, bg):

  AssertionError: 'abcbc' ==
'\u001b[31ma\u001b[33mb\u001b[32mc\u001b[33mb\u001b[31mc\u001b[39m'
  + expected - actual

  -abcbc
  +abcbc

  at Context.
(/root/debian/node-chalk/node-chalk/test.js:28:10)

  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:223:21)

  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:216:7)

  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:373:10)

  at /usr/lib/nodejs/mocha/lib/runner.js:451:12

  at next (/usr/lib/nodejs/mocha/lib/runner.js:298:14)

  at /usr/lib/nodejs/mocha/lib/runner.js:308:7

  at next (/usr/lib/nodejs/mocha/lib/runner.js:246:23)

  at Immediate._onImmediate
(/usr/lib/nodejs/mocha/lib/runner.js:275:5)
  at processImmediate [as _immediateCallback] (timers.js:383:17)


  5) chalk should reset all styles with `.reset()`:

  AssertionError: 'foofoo' ==
'\u001b[0m\u001b[31m\u001b[42m\u001b[4mfoo\u001b[24m\u001b[49m\u001b[39mfoo\u001b[0m'


  + expected - actual

  -foofoo
  +foofoo

  at Context.
(/root/debian/node-chalk/node-chalk/test.js:35:10)

  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:223:21)

  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:216:7)

  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:373:10)

  at /usr/lib/nodejs/mocha/lib/runner.js:451:12

  at next (/usr/lib/nodejs/mocha/lib/runner.js:298:14)

  at /usr/lib/nodejs/mocha/lib/runner.js:308:7

  at next (/usr/lib/nodejs/mocha/lib/runner.js:246:23)

  at Immediate._onImmediate
(/usr/lib/nodejs/mocha/lib/runner.js:275:5)
  at processImmediate [as _immediateCallback] (timers.js:383:17)


  6) chalk should be able to cache multiple styles:

[Pkg-javascript-devel] RFS: node-string-width 2.0.0

[Paolo Greppi]

Hi,

I packaged node-string-width as per this ITP
https://bugs.debian.org/845240, this is the repo:
https://anonscm.debian.org/git/pkg-javascript/node-string-width.git
it's set up for git-buildpackage.

Please someone more experienced than me review it and if it's OK sponsor
its upload.

Thanks,

Paolo



signature.asc
Description: OpenPGP digital signature
-- 
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] Using clean build scripts from pkg-ruby-extras repo

[Paolo Greppi]

Hi this is opinionated but very useful. I have a couple of newbie questions.

Did you try these scripts on Debian stable as host ?

Why do we need two virtualization systems (schroot for sbuild & lxc for
autopkgtest) ?

Would it be possible to use only one (for example lxc) ?

Paolo

On 28/11/2016 08:27, Pirate Praveen wrote:
> Hi,
> 
> I find these scripts very useful so I thought of sharing it more widely.
> I use it for ruby, go and nodejs packages.
> 
> Scripts are here
> https://anonscm.debian.org/cgit/pkg-ruby-extras/pkg-ruby-extras.git
> 
> 1. git clone
> 2. add cloned location to PATH,
> 3. and run `setup`, (this will create sbuild chroot and lxc-container)
> 4. then run `build` when you want to build a package from its source
> tree (those who have upload access can use build-and-upload).
> 
> Features:
> 1. It will build in a clean chroot using sbuild,
> 2. it will run autopkgtest in an lxc container,
> 3. it will offer to run autopkgtest of any or all reverse dependencies,
> 4. it will also offer to rebuild all or any reverse build dependencies.
> 
> It is very convenient when updating packages, especially for major
> updates that may break reverse dependencies.
> 
> It could end up in a package some time in the future when it is made
> more generic https://lists.debian.org/debian-ruby/2016/11/msg00011.html
> 
> Thanks
> Praveen




signature.asc
Description: OpenPGP digital signature
-- 
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#794890: work required to update the npm package to 3.10.9

[Paolo Greppi]

Issuing the command:

  npm2deb depends -b -r npm > list

on sid returns the attached list of node-* dependencies.

Filtering the list with:

  cat list | grep None | sed 's/│//g' | sed 's/├//g' | sed 's/─//g' |
sed 's/└//g' | sed 's/^ *//g' | awk '{print $1}' | sort | uniq | wc

gives the estimate that more than 50 new npm modules must be packaged
before npm can be updated to 3.10.9.

For comparison, bringing the npm "competitor" yarn into Debian (see RFP
https://bugs.debian.org/843021) would require 19 modules. But some of
the latter are really tough !
npm2deb depends -b -r npm

Dependencies:
NPM   Debian
npm (3.10.9)  None
├─ abbrev (~1.0.9)node-abbrev (1.0.9-1)
├─ ansi-regex (*) node-ansi-regex (2.0.0-1)
├─ ansicolors (~0.3.2)None
├─ ansistyles (~0.1.3)None
├─ aproba (~1.0.4)None
├─ archy (~1.0.0) node-archy (0.0.2-1)
├─ asap (~2.0.5)  None
├─ chownr (~1.0.1)None
├─ cmd-shim (~2.0.2)  None
│  ├─ graceful-fs (^4.1.2)node-graceful-fs (4.1.10-1)
│  └─ mkdirp (~0.5.0) node-mkdirp (0.5.0-1)
├─ columnify (~1.5.4) None
│  ├─ strip-ansi (^3.0.0) node-strip-ansi (3.0.1-1)
│  └─ wcwidth (^1.0.0)None
│ └─ defaults (^1.0.3)node-defaults (1.0.3-1)
├─ config-chain (~1.1.11) None
│  ├─ ini (^1.3.4)node-ini (1.1.0-1)
│  └─ proto-list (~1.2.1) None
├─ debuglog (*)   None
├─ dezalgo (~1.0.3)   None
│  ├─ asap (^2.0.0)   None
│  └─ wrappy (1)  node-wrappy (1.0.2-1)
├─ editor (~1.0.0)None
├─ fs-vacuum (~1.2.9) None
│  ├─ graceful-fs (^4.1.2)node-graceful-fs (4.1.10-1)
│  ├─ path-is-inside (^1.0.1) None
│  └─ rimraf (^2.5.2) node-rimraf (2.2.8-1)
├─ fs-write-stream-atomic (~1.0.8)None
│  ├─ graceful-fs (^4.1.2)node-graceful-fs (4.1.10-1)
│  ├─ iferr (^0.1.5)  None
│  ├─ imurmurhash (^0.1.4)None
│  └─ readable-stream (1 || 2)None
│ ├─ buffer-shims (^1.0.0)None
│ ├─ core-util-is (~1.0.0)node-core-util-is (1.0.2-1)
│ ├─ inherits (~2.0.1)node-inherits (2.0.1-3)
│ ├─ isarray (~1.0.0) node-isarray (1.0.0-1)
│ ├─ process-nextick-args (~1.0.6)node-process-nextick-args 
(1.0.8-1)
│ ├─ string_decoder (~0.10.x) node-string-decoder 
(0.10.25-1)
│ └─ util-deprecate (~1.0.1)  node-util-deprecate (1.0.2-1)
├─ fstream (~1.0.10)  node-fstream (0.1.24-1)
├─ fstream-npm (~1.2.0)   None
│  ├─ fstream-ignore (^1.0.0) node-fstream-ignore (0.0.6-2)
│  └─ inherits (2)node-inherits (2.0.1-3)
├─ glob (~7.1.0)  node-glob (7.1.1-1)
├─ graceful-fs (~4.1.9)   node-graceful-fs (4.1.10-1)
├─ has-unicode (~2.0.1)   None
├─ hosted-git-info (~2.1.5)   node-hosted-git-info (2.1.5-1)
├─ iferr (~0.1.5) None
├─ imurmurhash (*)None
├─ inflight (~1.0.5)  node-inflight (1.0.6-1)
├─ inherits (~2.0.3)  node-inherits (2.0.1-3)
├─ ini (~1.3.4)   node-ini (1.1.0-1)
├─ init-package-json (~1.9.4) None
│  ├─ glob (^6.0.0)   node-glob (7.1.1-1)
│  ├─ npm-package-arg (^4.0.0)None
│  │  ├─ hosted-git-info (^2.1.5) node-hosted-git-info (2.1.5-1)
│  │  └─ semver (^5.1.0)  node-semver (5.3.0-1)
│  ├─ promzard (^0.3.0)   None
│  │  └─ read (1) node-read (1.0.5-1)
│  ├─ read (~1.0.1)   node-read (1.0.5-1)
│  ├─ read-package-json (1 || 2)  node-read-package-json 
(1.2.4-1)
│  ├─ semver (2.x || 3.x || 4 || 5)   node-semver (5.3.0-1)
│  ├─ validate-npm-package-license (^3.0.1)   
node-validate-npm-package-license (3.0.1-1)
│  └─ validate-npm-package-name (^2.0.1)  None
│ └─ builtins (0.0.7)  

Re: [Pkg-javascript-devel] 2 NMUs for node-findup-sync

[Paolo Greppi]

That's a very helpful overview, and it makes it clear that it's quite a
lot of work.

Going through the latest news and the WNPP queue I can see that:
- node-detect-file has been ACCEPTED into unstable this morning
- node-cache-base has been ACCEPTED into unstable yesterday
- node-os-homedir has an ITP bug http://bugs.debian.org/841196

Several other node modules have no ITP yet, but a repo is present in
https://anonscm.debian.org/git/pkg-javascript indicating that work is
underway

It would be helpful to (programmatically) cross-link the info about the
existing packages' trackers, the ITPs and the alioth repos in the task
page. I could hack a python script to poll the UDD API and a crude grep
of the directory listing

But I don't how that script would fit in the current infrastructure ...

P

On 30/10/2016 12:02, Pirate Praveen wrote:
> We are also waiting to update node-findup-sync for grunt, but it needs a
> few more dependencies to be packaged (they are waiting for packages in NEW)
> 
> See https://wiki.debian.org/Javascript/Nodejs/Tasks/grunt




signature.asc
Description: OpenPGP digital signature
-- 
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] 2 NMUs for node-findup-sync

[Paolo Greppi]

On 30/10/2016 11:40, Mattia Rizzolo wrote:
> also Vcs-Git please.

OK

>>>  * debhelper compat 10
>>>  * bump std-ver
>>
>> These I'd keep on hold until we do 0.4.3-1.
> 
> ok, but I find weird that you bumped std-ver 3.9.5 → 3.9.6 then…
> You could have gone all the way to 3.9.8, since no changes are needed
> for this package anyway.
> https://www.debian.org/doc/debian-policy/upgrading-checklist

The reason is that 3.9.6 is the current one on jessie. But will 0.1.3-2
ever get to jessie ?

> Other things::
>  * you changed d/watch to point to somebody else's repo in github,
>writing "Fix d/watch".  You're not saying what that fixes; it
>should really work both ways, since there is a redirect.
>Also please use more descriptive messagges in changelog

OK

The old watch faile is currently failing on
https://packages.qa.debian.org/n/node-findup-sync.html
whereas the redirect works on:
https://tracker.debian.org/pkg/node-findup-sync

Probably we're all on the bleeding edge (tracker.d.o) but people who
click on the Developer Information (PTS) link on packages.d.o still land
on packages.qa.d.o

>  * you can remove the '[ Paolo Greppi ]' from the changelog, since
>everything is from you anyway.

OK



signature.asc
Description: OpenPGP digital signature
-- 
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] how to address node-lodash 841698

[Paolo Greppi]

On 02/11/2016 14:36, Pirate Praveen wrote:
> On Wednesday 02 November 2016 04:11 PM, Paolo Greppi wrote:
>> Fine, can you review what I have done so far and if it's OK sponsor it ?
>>
>> https://anonscm.debian.org/git/pkg-javascript/node-lodash.git/log/?h=debian/master-2.4
> 
> I have uploaded it even though there are other possible improvements
> (like fixing a lintian error, updating standards version etc), which we
> can target for next upload.

Thanks.

I'll go through the lintian warnings to see if there is any that still
need to be applied on master.

>> It should be possible to apply commit
>> fe688dba75a85e4e06824262a7fcf4bd58538415 to master.
> 
> Please apply and push.

Done, I have also pushed a couple of tags (upstream/2.4.1+dfsg and
upstream/4.3.0+dfsg) which are required if one builds it using gbp
buildpackage -uc -us

Those upstream/x.y.z+dfsg I have re-created starting from the
corresponding debian/x.y.z+dfsg-w, simply deleting the debian directory.



signature.asc
Description: OpenPGP digital signature
-- 
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] how to address node-lodash 841698

[Paolo Greppi]

On 02/11/2016 10:42, Pirate Praveen wrote:
> On Wednesday 02 November 2016 01:46 PM, Paolo Greppi wrote:
>> For this one it seems the master branch has some commits targeting
>> experimental (4.3.0+dfsg-1 and 3.9.3+dfsg-1) that have not made it to to
>> sid yet:
>> https://anonscm.debian.org/git/pkg-javascript/node-lodash.git/tree/debian/changelog
>>
>> My intention was to apply the patch and close
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841698 with the most
>> limited changes possible, i.e. 2.4.1+dfsg-3 -> 2.4.1+dfsg-4
>>
>> This guarantees that it does not get kicked out of testing on
>> 2016-12-05, whether we manage to do the maneuver you describe by that
>> date, or not.
>>
>> The patch can be also applied to the master branch so that it's there
>> when work on 4.3.0+dfsg-x resumes.
>>
>> Please let me know if this has any value.
> 
> Ok, then you can make a branch from current version in sid and upload
> the package. I suggest master-2.4 as the branch name. Apply the change
> to master branch as well so we are not hit again.

Fine, can you review what I have done so far and if it's OK sponsor it ?

https://anonscm.debian.org/git/pkg-javascript/node-lodash.git/log/?h=debian/master-2.4

It should be possible to apply commit
fe688dba75a85e4e06824262a7fcf4bd58538415 to master.

Paolo




signature.asc
Description: OpenPGP digital signature
-- 
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] alternatives for node.js dependency management

[Paolo Greppi]

Post by the python-flask author on "Micropackages and Open Source Trust
Scaling" (2016-03-24)
http://lucumr.pocoo.org/2016/3/24/open-source-trust-scaling/

node-isarray installed size on sid: 16 kB
https://packages.debian.org/sid/node-isarray

RFP for yarn: a fast, reliable, and secure package manager for Node.js
https://bugs.debian.org/843021



signature.asc
Description: OpenPGP digital signature
-- 
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] dependencies for complex Node.js modules: findup-sync

[Paolo Greppi]

Starting a separate thread from
https://lists.alioth.debian.org/pipermail/pkg-javascript-devel/2016-November/014868.html
...

On 01/11/2016 10:56, Pirate Praveen wrote:
> On Tuesday 01 November 2016 03:09 PM, Paolo Greppi wrote:
>> ...
>> It would be helpful to (programmatically) cross-link the info about the
>> existing packages' trackers, the ITPs and the alioth repos in the task
>> page. I could hack a python script to poll the UDD API and a crude grep
>> of the directory listing
>>
>> But I don't how that script would fit in the current infrastructure ...
> 
> This info is already available as npm2deb search .
> 
> https://wiki.debian.org/Javascript/Nodejs/Npm2Deb has more tips like this.

Thanks, very interesting. It's python and definitely a good starting
point for a hack. For example if upstream is interested, there could be
a new CLI option to generate the hierarchical dependencies tree as HTML
with all the links and color-coded fancy:

npm2deb depends-html findup-sync

I'll think about it ... but first I need to understand exactly what
we're doing here.

As it stands now the tree that can be seen for example in the Node.js
grunt task:
https://wiki.debian.org/Javascript/Nodejs/Tasks/grunt
looks much more complete than what 'npm2deb depends grunt' returns.

To generate the tree programmatically, I tried
https://www.npmjs.com/package/npm-remote-ls on findup-sync.

With node 4.6.1 on unstable 'npm-remote-ls findup-sync@0.4.3' spits out
about 240 modules, see list0.

It reports a (recursive) dependency on grunt (can we actually package
node-findup-sync without grunt ?), if I remove that we're down to 90
modules.

Many of them are repeated: filtering (sed 's/[ └─│├]//g' | sort | uniq)
reduces to 71 (excluding findup-sync itself), see list2.

Still a few are repeated with different version numbers, yanking away
the version info (sed 's/\(.*\)@.*/\1/g' | sort | uniq) reduces the
count to 68, see list3.

Do you reckon this info is relevant to the packaging of node-findup-sync
and to the grunt task ?
└─ findup-sync@0.4.3
   ├─ fs-exists-sync@0.1.0
   ├─ resolve-dir@0.1.1
   │  ├─ global-modules@0.2.3
   │  │  ├─ is-windows@0.2.0
   │  │  └─ global-prefix@0.1.4
   │  │ ├─ ini@1.3.4
   │  │ ├─ is-windows@0.2.0
   │  │ ├─ osenv@0.1.3
   │  │ │  ├─ os-homedir@1.0.2
   │  │ │  └─ os-tmpdir@1.0.2
   │  │ └─ which@1.2.11
   │  └─ expand-tilde@1.2.2
   │ └─ os-homedir@1.0.2
   ├─ is-absolute@0.2.6
   │  ├─ is-relative@0.2.1
   │  │  └─ is-unc-path@0.1.1
   │  │ └─ unc-path-regex@0.1.2
   │  └─ is-windows@0.2.0
   ├─ minimist@1.2.0
   ├─ grunt@1.0.1
   │  ├─ coffee-script@1.10.0
   │  ├─ dateformat@1.0.12
   │  │  ├─ get-stdin@4.0.1
   │  │  └─ meow@3.7.0
   │  │ ├─ camelcase-keys@2.1.0
   │  │ │  ├─ map-obj@1.0.1
   │  │ │  └─ camelcase@2.1.1
   │  │ ├─ loud-rejection@1.6.0
   │  │ │  ├─ currently-unhandled@0.4.1
   │  │ │  │  └─ array-find-index@1.0.2
   │  │ │  └─ signal-exit@3.0.1
   │  │ ├─ map-obj@1.0.1
   │  │ ├─ decamelize@1.2.0
   │  │ ├─ minimist@1.2.0
   │  │ ├─ object-assign@4.1.0
   │  │ ├─ normalize-package-data@2.3.5
   │  │ │  ├─ hosted-git-info@2.1.5
   │  │ │  ├─ is-builtin-module@1.0.0
   │  │ │  │  └─ builtin-modules@1.1.1
   │  │ │  ├─ validate-npm-package-license@3.0.1
   │  │ │  │  ├─ spdx-correct@1.0.2
   │  │ │  │  │  └─ spdx-license-ids@1.2.2
   │  │ │  │  └─ spdx-expression-parse@1.0.4
   │  │ │  └─ semver@5.3.0
   │  │ ├─ read-pkg-up@1.0.1
   │  │ │  ├─ read-pkg@1.1.0
   │  │ │  │  ├─ load-json-file@1.1.0
   │  │ │  │  │  ├─ parse-json@2.2.0
   │  │ │  │  │  │  └─ error-ex@1.3.0
   │  │ │  │  │  │ └─ is-arrayish@0.2.1
   │  │ │  │  │  ├─ graceful-fs@4.1.9
   │  │ │  │  │  ├─ strip-bom@2.0.0
   │  │ │  │  │  │  └─ is-utf8@0.2.1
   │  │ │  │  │  ├─ pinkie-promise@2.0.1
   │  │ │  │  │  └─ pify@2.3.0
   │  │ │  │  ├─ path-type@1.1.0
   │  │ │  │  │  ├─ pify@2.3.0
   │  │ │  │  │  ├─ pinkie-promise@2.0.1
   │  │ │  │  │  └─ graceful-fs@4.1.9
   │  │ │  │  └─ normalize-package-data@2.3.5
   │  │ │  └─ find-up@1.1.2
   │  │ │ ├─ pinkie-promise@2.0.1
   │  │ │ │  └─ pinkie@2.0.4
   │  │ │ └─ path-exists@2.1.0
   │  │ │└─ pinkie-promise@2.0.1
   │  │ ├─ trim-newlines@1.0.0
   │  │ └─ redent@1.0.0
   │  │├─ indent-string@2.1.0
   │  ││  └─ repeating@2.0.1
   │  ││ └─ is-finite@1.0.2
   │  ││└─ number-is-nan@1.0.1
   │  │└─ strip-indent@1.0.1
   │  │   └─ get-stdin@4.0.1
   │  ├─ eventemitter2@0.4.14
   │  ├─ exit@0.1.2
   │  ├─ findup-sync@0.3.0
   │  │  └─ glob@5.0.15
   │  │ ├─ inflight@1.0.6
   │  │ ├─ once@1.4.0
   │  │ ├─ path-is-absolute@1.0.1
   │  │ ├─ minimatch@3.0.3
   │  │ └─ inherits@2.0.3
   │  ├─ grunt-known-options@1.1

[Pkg-javascript-devel] dependencies for complex Node.js modules: findup-sync

[Paolo Greppi]

Starting a separate thread from
https://lists.alioth.debian.org/pipermail/pkg-javascript-devel/2016-November/014868.html
...

On 01/11/2016 10:56, Pirate Praveen wrote:
> On Tuesday 01 November 2016 03:09 PM, Paolo Greppi wrote:
>> ...
>> It would be helpful to (programmatically) cross-link the info about the
>> existing packages' trackers, the ITPs and the alioth repos in the task
>> page. I could hack a python script to poll the UDD API and a crude grep
>> of the directory listing
>>
>> But I don't how that script would fit in the current infrastructure ...
> 
> This info is already available as npm2deb search .
> 
> https://wiki.debian.org/Javascript/Nodejs/Npm2Deb has more tips like this.

Thanks, very interesting. It's python and definitely a good starting
point for a hack. For example if upstream is interested, there could be
a new CLI option to generate the hierarchical dependencies tree as HTML
with all the links and color-coded fancy:

npm2deb depends-html findup-sync

I'll think about it ... but first I need to understand exactly what
we're doing here.

As it stands now the tree that can be seen for example in the Node.js
grunt task:
https://wiki.debian.org/Javascript/Nodejs/Tasks/grunt
looks much more complete than what 'npm2deb depends grunt' returns.

To generate the tree programmatically, I tried
https://www.npmjs.com/package/npm-remote-ls on findup-sync.

With node 4.6.1 on unstable 'npm-remote-ls findup-sync@0.4.3' spits out
about 240 modules, see list0.

It reports a (recursive) dependency on grunt (can we actually package
node-findup-sync without grunt ?), if I remove that we're down to 90
modules.

Many of them are repeated: filtering (sed 's/[ └─│├]//g' | sort | uniq)
reduces to 71 (excluding findup-sync itself), see list2.

Still a few are repeated with different version numbers, yanking away
the version info (sed 's/\(.*\)@.*/\1/g' | sort | uniq) reduces the
count to 68, see list3.

Do you reckon this info is relevant to the packaging of node-findup-sync
and to the grunt task ?
└─ findup-sync@0.4.3
   ├─ fs-exists-sync@0.1.0
   ├─ resolve-dir@0.1.1
   │  ├─ global-modules@0.2.3
   │  │  ├─ is-windows@0.2.0
   │  │  └─ global-prefix@0.1.4
   │  │ ├─ ini@1.3.4
   │  │ ├─ is-windows@0.2.0
   │  │ ├─ osenv@0.1.3
   │  │ │  ├─ os-homedir@1.0.2
   │  │ │  └─ os-tmpdir@1.0.2
   │  │ └─ which@1.2.11
   │  └─ expand-tilde@1.2.2
   │ └─ os-homedir@1.0.2
   ├─ is-absolute@0.2.6
   │  ├─ is-relative@0.2.1
   │  │  └─ is-unc-path@0.1.1
   │  │ └─ unc-path-regex@0.1.2
   │  └─ is-windows@0.2.0
   ├─ minimist@1.2.0
   ├─ grunt@1.0.1
   │  ├─ coffee-script@1.10.0
   │  ├─ dateformat@1.0.12
   │  │  ├─ get-stdin@4.0.1
   │  │  └─ meow@3.7.0
   │  │ ├─ camelcase-keys@2.1.0
   │  │ │  ├─ map-obj@1.0.1
   │  │ │  └─ camelcase@2.1.1
   │  │ ├─ loud-rejection@1.6.0
   │  │ │  ├─ currently-unhandled@0.4.1
   │  │ │  │  └─ array-find-index@1.0.2
   │  │ │  └─ signal-exit@3.0.1
   │  │ ├─ map-obj@1.0.1
   │  │ ├─ decamelize@1.2.0
   │  │ ├─ minimist@1.2.0
   │  │ ├─ object-assign@4.1.0
   │  │ ├─ normalize-package-data@2.3.5
   │  │ │  ├─ hosted-git-info@2.1.5
   │  │ │  ├─ is-builtin-module@1.0.0
   │  │ │  │  └─ builtin-modules@1.1.1
   │  │ │  ├─ validate-npm-package-license@3.0.1
   │  │ │  │  ├─ spdx-correct@1.0.2
   │  │ │  │  │  └─ spdx-license-ids@1.2.2
   │  │ │  │  └─ spdx-expression-parse@1.0.4
   │  │ │  └─ semver@5.3.0
   │  │ ├─ read-pkg-up@1.0.1
   │  │ │  ├─ read-pkg@1.1.0
   │  │ │  │  ├─ load-json-file@1.1.0
   │  │ │  │  │  ├─ parse-json@2.2.0
   │  │ │  │  │  │  └─ error-ex@1.3.0
   │  │ │  │  │  │ └─ is-arrayish@0.2.1
   │  │ │  │  │  ├─ graceful-fs@4.1.9
   │  │ │  │  │  ├─ strip-bom@2.0.0
   │  │ │  │  │  │  └─ is-utf8@0.2.1
   │  │ │  │  │  ├─ pinkie-promise@2.0.1
   │  │ │  │  │  └─ pify@2.3.0
   │  │ │  │  ├─ path-type@1.1.0
   │  │ │  │  │  ├─ pify@2.3.0
   │  │ │  │  │  ├─ pinkie-promise@2.0.1
   │  │ │  │  │  └─ graceful-fs@4.1.9
   │  │ │  │  └─ normalize-package-data@2.3.5
   │  │ │  └─ find-up@1.1.2
   │  │ │ ├─ pinkie-promise@2.0.1
   │  │ │ │  └─ pinkie@2.0.4
   │  │ │ └─ path-exists@2.1.0
   │  │ │└─ pinkie-promise@2.0.1
   │  │ ├─ trim-newlines@1.0.0
   │  │ └─ redent@1.0.0
   │  │├─ indent-string@2.1.0
   │  ││  └─ repeating@2.0.1
   │  ││ └─ is-finite@1.0.2
   │  ││└─ number-is-nan@1.0.1
   │  │└─ strip-indent@1.0.1
   │  │   └─ get-stdin@4.0.1
   │  ├─ eventemitter2@0.4.14
   │  ├─ exit@0.1.2
   │  ├─ findup-sync@0.3.0
   │  │  └─ glob@5.0.15
   │  │ ├─ inflight@1.0.6
   │  │ ├─ once@1.4.0
   │  │ ├─ path-is-absolute@1.0.1
   │  │ ├─ minimatch@3.0.3
   │  │ └─ inherits@2.0.3
   │  ├─ grunt-known-options@1.1

[Pkg-javascript-devel] how to address node-lodash 841698

[Paolo Greppi]

Hi I would like to contribute to this bug.

The current package version in unstable is 2.4.1+dfsg-3.

If I understand correctly
https://wiki.debian.org/DebianMentorsFaq#What_does_.2BIBw-dfsg.2BIB0_in_the_version_string_mean.3F,
we would issue the 2.4.1+dfsg-4 version.

I have cloned the repo
git://anonscm.debian.org/pkg-javascript/node-lodash.git

I see this commit: abcc478dad9eb33aaed9a92aa7b55d3f5f9cbafe matches the
released version 2.4.1+dfsg-3 so I'd tag it (as git-buildpackage would
do) as "debian/2.4.1+dfsg-3"

Next I'd create branch from there with branch name "debian/sid" and work
on that that branch to avoid interfering with the master branch.

Any comments ?



signature.asc
Description: OpenPGP digital signature
-- 
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] how to address node-lodash 841698

[Paolo Greppi]

On 02/11/2016 08:45, Pirate Praveen wrote:
> On Wednesday 02 November 2016 01:09 AM, Paolo Greppi wrote:
>> Any comments ?
> 
> You can just work on the master branch. We do all the work targeting sid
> on master branch.

For this one it seems the master branch has some commits targeting
experimental (4.3.0+dfsg-1 and 3.9.3+dfsg-1) that have not made it to to
sid yet:
https://anonscm.debian.org/git/pkg-javascript/node-lodash.git/tree/debian/changelog

My intention was to apply the patch and close
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841698 with the most
limited changes possible, i.e. 2.4.1+dfsg-3 -> 2.4.1+dfsg-4

This guarantees that it does not get kicked out of testing on
2016-12-05, whether we manage to do the maneuver you describe by that
date, or not.

The patch can be also applied to the master branch so that it's there
when work on 4.3.0+dfsg-x resumes.

Please let me know if this has any value.

> But we cannot update lodash yet because it has two reverse dependencies.
> You have to make sure both works with the new version of lodash.
> 
> $ apt-cache rdepends node-lodash
> node-lodash
> Reverse Depends:
>   node-findup-sync
>   node-globule
> 
> New version of findup-sync does not depend on lodash, so you have to
> wait till a new version of findup-sync is uploaded or test the current
> version of findup-sync with new version of lodash.
> 
> $ apt-cache rdepends node-globule
> node-globule
> Reverse Depends:
> 
> So you'll have to check if the current version of globule works with the
> new version of lodash or update globule along with lodash.
> 
> But I suggest you try packaging a few new packages to get experience
> before trying to update existing packages.
> 
> You could take any from https://wiki.debian.org/Javascript/Nodejs/Tasks/gulp

OK thanks for the suggestion and the patience.

BTW it all stated when I wanted to scratch my itch (getting apt-get
install atom to work in stretch, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747824#98) we'll see
where this takes me !



signature.asc
Description: OpenPGP digital signature
-- 
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] node-loose-envify: source-is-missing

[Paolo Greppi]

Hi, while packaging node-loose-envify (https://bugs.debian.org/846206) I
get this lintian error:

E: node-loose-envify source: source-is-missing
test/react/react-with-addons-with-node_env.js line length is 845
characters (>512)

See the repo on alioth.

Since the tests require browserify, I guess they'll have to wait a bit
anyway.

What do you suggest ?

Thanks

Paolo



signature.asc
Description: OpenPGP digital signature
-- 
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] RFS: node-loose-envify 1.3.0

[Paolo Greppi]

On 05/12/2016 11:41, Pirate Praveen wrote:
> On തിങ്കള്‍ 05 ഡിസംബര്‍ 2016 03:45 വൈകു, Paolo Greppi wrote:
>> It does the trick because the lintian error is gone.
> 
> But its bad for long term maintenance, any time that file changes,
> you'll have to refresh the patch.
>> I'd rather avoid dfsg rightnow because :
>> - the specific file is part of the javascript corpus the test suite runs
>> on (which we can't run at the moment anyway since it requires browserify)
>> - I don't think that makes the package "non-DFSG clean" as a whole
> 
> but the removal is for dfsg.
> 
>> - sheer ignorance: the dfsg_clean workflow being new for me
> 
> See node-levn for an example.
> 
> 1. Add Files-Excluded to copyright
> 2. Add repack options to watch
> 3. Rename to +dfsg.orig and edit the orig.tar, remove the file (I use
> graphical tools like file-roller)
> 4. Edit changelog
> 5. Import the +dfsg.orig (gbp import-orig)
> 
> If you get it working, may be add it to a wiki page.
> 
>> There are about 6 dependencies left to go plus babel + gulp as build
>> deps. The latter is the same short-term focus as
>> https://www.generosity.com/community-fundraising/debian-browserify-2 so
>> yes maybe it can be done !
> 
> This campaign did not receive much support (only 7% of the target). But
> we are still working on it. We need to complete about 30 modules to
> finish gulp. Any help in finishing that list would be awesome.
> 
> All babel modules are in a single repo, Shanavas is trying to automate
> it. But we still need to package non babel dependencies from here.
> 
> https://wiki.debian.org/Javascript/Nodejs/Tasks/babel-cli
> 
> https://wiki.debian.org/Javascript/Nodejs/Tasks/gulp needs tiny
> submodules of lodash but we need help for that
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845227 can you try it?

Hi this one should be ready, please review & upload.

I have applied Jérémy's recipy with success: uscan is able to produce
the dfsg tarball automatically ! No need to manually edit the tarball.

BTW Pirate, what do you mean with "If you get it working, may be add it
to a wiki page." ?

P.

-- 
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] RFS: node-loose-envify 1.3.0

[Paolo Greppi]

On 05/12/2016 11:46, Pirate Praveen wrote:
> On തിങ്കള്‍ 05 ഡിസംബര്‍ 2016 04:07 വൈകു, Jérémy Lal wrote:
>> Add this to debian/watch params:
>> repacksuffix=~dfsg
> 
> I think +dfsg is better here, else any module depending on it has to add
> a ~ at the end to its version. May be we make npm2deb do it
> automatically https://github.com/LeoIannacone/npm2deb/issues/40

BTW2, can you elaborate on the difference between ~dfsg and +dfsg ?

I could not find any policy / standard on that.

What I found is:
https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version
which states that:
version = [epoch:]upstream_version[-debian_revision]
epoch=unsigned integer or 0 if missing
upstream_version=A-Za-z0-9.+-:~
debian_revision=A-Za-z0-9+.~ or 0 if missing

Empirical research shows that people add dfsg, ds or debian in many
different ways to the upstream_version.

Looking at the packages in sid with architecture and64, they are added
resp. 71, 16 and 9 times without separator, for example:

4.8.0dfsg
1.06.dfsg
0.2.dfsg1
6.02.dfsg.1
0.62.dfsg2
0.12.10dfsg2
...
0.5.ds
1.45.ds2
2002.04.10ds1
3.0.19.ds1
...
0.4.2.debian1
1.2debian
5.6.debian.1
0.10.32.debian

The most popular suffix separator for dfsg is + (694 times), last comes
~dfsg (79 times) and finally -dfsg (15 times).

?

-- 
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] RFS: node-tar-stream 1.5.2

[Paolo Greppi]

On 04/12/2016 10:06, Pirate Praveen wrote:
> On ഞായര്‍ 04 ഡിസംബര്‍ 2016 02:18 വൈകു, Paolo Greppi wrote:
>> It should be low risk to upgrade because the command:
>>   apt-cache rdepends node-bl
>>
>> returns:
>>
>> node-bl
>> Reverse Depends:
>>   node-yawl
>>
>> The latter has a FTBFS big open for about a year, git repo is basically
>> stuck in 2014, and npm registry showns 96 downloads in the last month.
> 
> If it is easy to fix and tests pass with new node-bl, update both.
> 
> 
> 
> 

node-bl has been updated so node-tar-stream should be OK now !

Paolo

-- 
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] Processing of node-bl_1.1.2-1_amd64.changes

[Paolo Greppi]

On 09/12/2016 09:19, Pirate Praveen wrote:
> On വെള്ളി 09 ഡിസംബര്‍ 2016 01:29 വൈകു, Jérémy Lal wrote:
>> Nothing !
>> My key has expired, i renewed it as explained here:
>> https://keyring.debian.org/
>> but it's not updated immediately by "ftp masters" - i don't think it has to
>> be available in the debian-keyring package to work again, but some update
>> must be done somewhere and has not yet been done.
> 
> I think they push the changes every month. keyring git repo on alioth
> will get a new tag when they push changes live.
> 
>> Let's ask someone else to upload node-bl - the gbp repo is ready to be 
>> uploaded.
> 
> Uploaded.

Thanks! It was a mystery because no error was being returned, nor could
I find any place where to check the status

P.




signature.asc
Description: OpenPGP digital signature
-- 
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] Processing of node-bl_1.1.2-1_amd64.changes

[Paolo Greppi]

Hi all this does not seem to get through.

The new version does not come up here:
https://tracker.debian.org/pkg/node-bl

What did I do wrong ?

Paolo

On 08/12/2016 18:19, Debian FTP Masters wrote:
> node-bl_1.1.2-1_amd64.changes uploaded successfully to localhost
> along with the files:
>   node-bl_1.1.2-1.dsc
>   node-bl_1.1.2.orig.tar.gz
>   node-bl_1.1.2-1.debian.tar.xz
>   node-bl_1.1.2-1_all.deb
>   node-bl_1.1.2-1_amd64.buildinfo
> 
> Greetings,
> 
>   Your Debian queue daemon (running on host usper.debian.org)
> 


-- 
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] RFS: node-object-path 0.11.3

[Paolo Greppi]

Hi

I packaged node-object-path as per this ITP:
https://bugs.debian.org/846215, this is the repo:
https://anonscm.debian.org/git/pkg-javascript/node-object-path.git

Please someone more experienced than me review it and if it's OK sponsor
its upload.

Thanks,

Paolo

-- 
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] Removing myself from Uploaders: field...

[Paolo Greppi]

On 14/12/2016 16:26, Mike Gabriel wrote:
> Hi all,
> 
> some time ago, I had the initiative of getting etherpad-lite into
> Debian. This goal is still not easily reachable. For now, I'd rather
> remove myself as uploader from the various JS packages I uploaded. Some
> have already been taken by others, some not.
> 
> I will provide a list of packages that remain with Uploaders: empty
> after my name has been removed and then I'd be happy to get feedback
> from the team, if someone in the team wants to continue maintenance or
> if the package should rather be removed or orphaned for now.
> 
> It's not that I am not interested in JS development, but I really need
> to focus on less things in Debian and do those properly.
> 
> Expect my Git commits during the next couple of days...
> 
> light+love,
> Mike

BTW do you have git repo somewhere about the work done on the etherpad
ITP https://bugs.debian.org/576998 ?

Thanks,

Paolo

-- 
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] RFS: node-dom{handler,utils,-serializer}

[Paolo Greppi]

Hi

I packed for upload:

- node-domhandler https://bugs.debian.org/848322
- node-domutils https://bugs.debian.org/848324
- node-dom-serializer https://bugs.debian.org/848325

They are all related to: https://bugs.debian.org/794988

Please someone more experienced than me review them and if they're OK
sponsor their upload.

Thanks,

Paolo


-- 
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] RFS: node-has-binary 0.1.7

[Paolo Greppi]

Hi

based on the work of Bas Couwenberg (2015) I prepared for upload
node-has-binary as per this ITP:
https://bugs.debian.org/781486, this is the repo:
https://anonscm.debian.org/git/pkg-javascript/node-has-binary.git/

It is required for node-socket.io-client, which in turn
is required for node-socket.io which in turn is one of the bits required
by etherpad-lite.

Please someone more experienced than me review it and if it's OK sponsor
its upload.

Thanks,

Paolo

-- 
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] RFS: node-emoji 1.4.1

[Paolo Greppi]

On 03/12/2016 16:49, Paolo Greppi wrote:
> On 03/12/2016 06:57, Pirate Praveen wrote:
>> On ശനി 03 ഡിസംബര്‍ 2016 06:46 രാവിലെ, Jérémy Lal wrote:
>>> Bad move :)
>>> What if a module is named "emoji" ? Then you'll have node-emoji
>>> conflict with it.
>>> node-node-emoji is the right name here.
>>
>> I think this is over engineering. We add node- prefix so we can have the
>> same library in other languages like ruby-emoji, python-emoji etc.
>>
>> As for having an unlikely node-emoji and emoji modules, we can choose to
>> support the better one and patch its reverse dependencies in most cases.
>> If that option is not working, I think node-node- should be a last resort.
> 
> Actually there is already a module in the npm registry called "emoji"
> https://www.npmjs.com/package/emoji
> but it seems less popular (963 downloads in the last month against
> 1.856.808 downloads in the same period for node-emoji). The github repo
> is also stuck at 2014-07-05 whereas node-emoji is more active.
> 
> The policy within Debian is whoever gets there first can get hold of a
> package name but I'd prefer to reach a consensus among us.
> 
> Paolo

Can someone push this through ? The more I think about it the more I am
convinced that node-emoji is OK

Paolo

-- 
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] RFS: node-path-root 0.1.1

[Paolo Greppi]

Hi

I packaged node-path-root as per this ITP:
https://bugs.debian.org/847910, this is the repo:
https://anonscm.debian.org/git/pkg-javascript/node-path-root.git/

The debian/watch file is using fakeupstream at the moment, but I've
asked upstream to tag the release:
https://github.com/jonschlinkert/path-root/issues/1

There is a test.js file on the github repo, which is absent from the
tarball (because fakeupstream pulls from npmjs). I have run

 mocha -R spec

on that file and they all pass. If we manage to point debian/watch to
github, we can easily turn on tests.

Please someone more experienced than me review it and if it's OK sponsor
its upload.

Thanks,

Paolo

-- 
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] RFS: node-roadrunner 1.1.0

[Paolo Greppi]

Hi

I packaged node-object-path as per this ITP:
https://bugs.debian.org/846218, this is the repo:
https://anonscm.debian.org/git/pkg-javascript/node-roadrunner.git/

Please someone more experienced than me review it and if it's OK sponsor
its upload.

Thanks,

Paolo

-- 
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] RFS: node-path-root 0.1.1

[Paolo Greppi]

On 12/12/2016 15:00, Pirate Praveen wrote:
> On തിങ്കള്‍ 12 ഡിസംബര്‍ 2016 06:05 വൈകു, Paolo Greppi wrote:
>> on that file and they all pass. If we manage to point debian/watch to
>> github, we can easily turn on tests.
> 
> You can include the test as a patch. When they add tags (jonschlinkert
> is pretty quick to add tags), we can switch tarballs and remove the patch.

Upstream was quicker than imaginable !

I have recreated from scratch the repo on alioth. Now it points to
github and tests are enabled.

P.

P.S. Clone again and dump the build area (rm -rf
~/build-area/node-path-root*) if you already used pkg-ruby-extras/build



-- 
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] RFS: node-parse-filepath 1.0.1

[Paolo Greppi]

On 13/12/2016 18:02, Pirate Praveen wrote:
> On ചൊവ്വ 13 ഡിസംബര്‍ 2016 10:01 വൈകു, Paolo Greppi wrote:
>> Hi
>>
>> I packaged node-parse-filepath as per this ITP:
>> https://bugs.debian.org/847911, this is the repo:
>> https://anonscm.debian.org/git/pkg-javascript/node-parse-filepath.git/
>>
>> I patched away the dependency on is-absolute with node-path-is-absolute.
>>
>> Please someone more experienced than me review it and if it's OK sponsor
>> its upload.
> 
> Uploaded, thanks!

My next one is node-fined. It's ready on alioth, I can test here if I
install node-parse-filepath and node-lodash-packages with dpkg -i (and
everything seems fine).

I cant' test yet with pkg-ruby-extras/build because those are still in
the NEW queue ...

Paolo


-- 
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] RFS: node-parse-filepath 1.0.1

[Paolo Greppi]

Hi

I packaged node-parse-filepath as per this ITP:
https://bugs.debian.org/847911, this is the repo:
https://anonscm.debian.org/git/pkg-javascript/node-parse-filepath.git/

I patched away the dependency on is-absolute with node-path-is-absolute.

Please someone more experienced than me review it and if it's OK sponsor
its upload.

Thanks,

Paolo


-- 
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] RFS: node-parse-filepath 1.0.1

[Paolo Greppi]

On 13/12/2016 19:14, Pirate Praveen wrote:
> On ചൊവ്വ 13 ഡിസംബര്‍ 2016 10:57 വൈകു, Paolo Greppi wrote:
>> My next one is node-fined. It's ready on alioth, I can test here if I
>> install node-parse-filepath and node-lodash-packages with dpkg -i (and
>> everything seems fine).
>>
>> I cant' test yet with pkg-ruby-extras/build because those are still in
>> the NEW queue ...
> 
> autopkgtest is failing (you can use 'adt-run ./ --- null' from package
> source directory) because require('expect') fails, it should be
> require('expect.js').
> 
> I'm not sure what is the best solution here, to patch or to fix
> node-expect.js. For now, please patch and make autopkgtest pass.

There's expect and there's expect.js

In debian we already have the latter so I patch it to use what we have
https://anonscm.debian.org/git/pkg-javascript/node-fined.git/tree/debian/patches/00-expect.diff

P

-- 
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#847091: Bug#847091: Bug#847091: update node-extend to latest upstream release

[Paolo Greppi]

On 14/12/2016 10:55, Pirate Praveen wrote:
> 
> 
> On 2016, ഡിസംബർ 14 2:16:46 PM IST, Paolo Greppi <paolo.gre...@libpf.com> 
> wrote:
>> That's because also node-liftoff (which is my ITP pipeline after
>> node-fixed) depends on node-extend >= 3.0.0
>>
> I think easier option would be to see if liftoff tests pass with node-extend 
> 2.0 and relax dependencies in debian/control.
> 

Actually they pass ...

Paolo

-- 
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#847091: Bug#847091: update node-extend to latest upstream release

[Paolo Greppi]

On 14/12/2016 10:53, Pirate Praveen wrote:
> 
> 
> On 2016, ഡിസംബർ 14 2:16:46 PM IST, Paolo Greppi <paolo.gre...@libpf.com> 
> wrote:
>>
>> Assuming we want to keep node-xtend and node-extend separate, I have
>> prepared the update for this one in the alioth repo.
>>
>> That's because also node-liftoff (which is my ITP pipeline after
>> node-fixed) depends on node-extend >= 3.0.0
>>
>> I also activated tests and tested reverse dependencies (only
>> node-superagent) with pkg-ruby-extras/build. RFS !
> 
> I think node-superagent only has require tests. We may need to enable tests 
> or run those tests manually after updating package.json and using npm.
> 

Not easy.

Testing current node-superagent 0.20.0 requires patching the tests like
this:

--- a/test/node/agency.js
+++ b/test/node/agency.js
@@ -4,8 +4,10 @@ var express = require('express')
   , assert = require('assert')
   , should = require('should');

-app.use(express.cookieParser());
-app.use(express.session({ secret: 'secret' }));
+var cookieParser = require('cookie-parser')
+var session = require('express-session')
+app.use(cookieParser());
+app.use(session({ secret: 'secret' }));

 app.post('/signin', function(req, res) {

but while we have node-cookie-session, express-session is missing.

I tried updating node-superagent to current 3.3.0 but to run the tests
there we would require should-http ...

How would I test with express-session or should-http from npm ?

And BTW should I push the work I have done on node-superagent 3.3.0 ti
alioth ?

P

-- 
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] why not

[Paolo Greppi]

I'd like to give this one a try, in the framework of the Debian
Javascript Maintainers team.

The new repo will be here (many thanks to Mike Gabriel for sharing his
previous work):
https://anonscm.debian.org/git/pkg-javascript/etherpad-lite.git

My current count of missing node-* packages is 9:
- require-kernel
- socket.io
- ueberdb
- express-session
- cheerio
- tinycon
- swagger-node-express
- jsonminify
- measured

Paolo

-- 
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] node-retry 0.10.1

[Paolo Greppi]

Hi

once I had upstream tag it, I updated node-retry to 0.10.1.

node-retry > 0.10.0 is required for node-proper-lockfile which I have in
my ITP pipeline because in turn it's required for node-yarnpkg

Since I do not have access to collab-maint I used this repo:
https://anonscm.debian.org/git/pkg-javascript/node-retry.git/

This package has as reverse dependency ... npm ! Not sure how to test that.

Any ideas ?

Paolo

-- 
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] RFS: node-node-uid-safe 2.1.3

[Paolo Greppi]

Hi

based on the work of Leo Iannacone (2014) I updated & packaged
node-path-root as per this ITP:
https://bugs.debian.org/754574, this is the repo:
https://anonscm.debian.org/git/pkg-javascript/node-uid-safe.git/

This is a dependency of node-express-session which is required for
etherpad-lite and is necessary to run tests on current node-superagent
0.20.0, a reverse dependency of node-extent that we might want to test
(see #847091).

Please someone more experienced than me review it and if it's OK sponsor
its upload.

Thanks,

Paolo

-- 
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] RFS: node-node-uid-safe 2.1.3

[Paolo Greppi]

On 15/12/2016 14:10, Paolo Greppi wrote:
> Hi
> 
> based on the work of Leo Iannacone (2014) I updated & packaged
> node-path-root as per this ITP:
> https://bugs.debian.org/754574, this is the repo:
> https://anonscm.debian.org/git/pkg-javascript/node-uid-safe.git/
> 
> This is a dependency of node-express-session which is required for
> etherpad-lite and is necessary to run tests on current node-superagent
> 0.20.0, a reverse dependency of node-extent that we might want to test
> (see #847091).
> 
> Please someone more experienced than me review it and if it's OK sponsor
> its upload.
> 
> Thanks,
> 
> Paolo

baah it's node-uid-safe, trust me !

Paolo

-- 
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] why not

[Paolo Greppi]

On 15/12/2016 11:59, Mike Gabriel wrote:
> Hi Paolo,
> 
> On  Mi 14 Dez 2016 23:01:16 CET, Paolo Greppi wrote:
> 
>> I'd like to give this one a try, in the framework of the Debian
>> Javascript Maintainers team.
>>
>> The new repo will be here (many thanks to Mike Gabriel for sharing his
>> previous work):
>> https://anonscm.debian.org/git/pkg-javascript/etherpad-lite.git
>>
>> My current count of missing node-* packages is 9:
>> - require-kernel
>> - socket.io
>> - ueberdb
>> - express-session
>> - cheerio
>> - tinycon
>> - swagger-node-express
>> - jsonminify
>> - measured
>>
>> Paolo
> 
> Have you checked dependencies of dependencies? I'd be delighted if you
> could dive into this. Please note that I pushed work on
> require-kernel.js and socket.io to pkg-javscript Git just now. Not
> up-to-date, but something to start from, at least.
> 
> Mike

Yes, there is more than I initially thought. I'm doing a
breadth-first-search !

I found your old repos, and I am starting from those.. we'll see

Paolo

-- 
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] RFS: node-blob 0.0.4

[Paolo Greppi]

Hi

based on the work of Bas Couwenberg (2015) I prepared for upload
node-blob as per this ITP:
https://bugs.debian.org/781478, this is the repo:
https://anonscm.debian.org/git/pkg-javascript/node-blob.git/

node-blob is required for node-engine.io-parser (#781458), which in turn
is required for node-socket.io (#707166) which in turn is one of
the bits required by etherpad-lite.

Please someone more experienced than me review it and if it's OK sponsor
its upload.

Thanks,

Paolo

-- 
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] advice needed on node module rx

[Paolo Greppi]

https://www.npmjs.com/package/rx

its description reads "Library for composing asynchronous and
event-based operations in JavaScript"

should the source package be named rx.js or node-rx ?

could one source provide binaries libjs-rx and node-rx ?

Paolo

P.S. it's a dependency of node-inquirer https://bugs.debian.org/848364

-- 
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] node-retry 0.10.0

[Paolo Greppi]

According to npm registry node-retry should be at version 0.10.0:
https://www.npmjs.com/package/retry#changelog
whereas we're at 0.6.0

uscan fails but there is no tag anyway for 0.10.0 in github:
https://github.com/tim-kos/node-retry/tags

I've notified upstream of the missing tag:
https://github.com/tim-kos/node-retry/issues/44

Once we get that, I can update the debian/watch and try to upgrade; I'm
interested in this one because proper-lockfile which I am preparing
depends on node-retry 0.10.0

Paolo

-- 
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] ITPs related to gulp

[Paolo Greppi]

Hi team

just to make you aware that to help with gulp packaging I just filed the
ITPs for node-liftoff and some of its dependencies:

http://bugs.debian.org/847910
ITP: node-path-root -- Get the root of a posix or windows filepath

http://bugs.debian.org/847911
ITP: node-parse-filepath -- parses a filepath into an object.

http://bugs.debian.org/847913
ITP: node-fined -- Find a file given a declaration of locations

http://bugs.debian.org/847916
ITP: node-liftoff -- Launch your command line tool with ease

Paolo

-- 
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] RFS: node-loose-envify 1.3.0

[Paolo Greppi]

On 10/12/2016 08:39, Pirate Praveen wrote:
> On ശനി 10 ഡിസംബര്‍ 2016 11:55 രാവിലെ, Paolo Greppi wrote:
>> BTW Pirate, what do you mean with "If you get it working, may be add it
>> to a wiki page." ?
> 
> Document steps to create a dfsg version in wiki,debian.org so we can
> just link to it when someone else asks the same question.

Here it is:

https://wiki.debian.org/Javascript/Repacking

It's currently not linked from https://wiki.debian.org/Javascript so
kind of hidden.

P.

-- 
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] RFS: node-htmlparser2 3.9.2

[Paolo Greppi]

On 11/01/2017 15:54, Pirate Praveen wrote:
> On ചൊവ്വ 03 ജനുവരി 2017 07:26 വൈകു, Paolo Greppi wrote:
>> On 28/12/2016 18:15, Paolo Greppi wrote:
>>> Hi,
>>>
>>> since node-cheerio (https://bugs.debian.org/848315) which is a requirement 
>>> of etherpad-lite (https://bugs.debian.org/576998) needs htmlparser2 
>>> "^3.9.1", I have updated node-htmlparser2 from version 3.7.3 to the current 
>>> version 3.9.2.
>>>
>>> And since we now have node-dom{elementtype,handler,utils} in the archive, I 
>>> have unbundled them.
>>>
>>> Also I have turned on tests, and they pass so that also 
>>> https://bugs.debian.org/794988 is fixed.
>>>
>>> node-htmlparser2 has a single reverse dependency: node-jsdom.
>>> But node-jsdom currently fails to pass autopkgtests anyway 
>>> (https://ci.debian.net/packages/n/node-jsdom/)
>>> nor does it have a proper test suite.
>>>
>>> I noticed that the repo on alioth has not the usual branch layout, so I 
>>> have set it up in a separate repo:
>>> https://anonscm.debian.org/git/pkg-javascript/node-htmlparser2_new.git
>>>
>>> Please someone more experienced than me review it and if it's OK sponsor 
>>> its upload.
>>>
>>> Paolo
>>
>> bump ?
> 
> I see only master branch in this repo. Can you push the other branches?

I think you are looking at the old repo here:
https://anonscm.debian.org/git/pkg-javascript/node-htmlparser2.git

The repo I created has all the branches / tags:
https://anonscm.debian.org/git/pkg-javascript/node-htmlparser2_new.git

I have created a new repo because the old one has this weird branch layout and 
a lot of tags, but I was shy of deleting it.

We can of course do a:

ssh git.debian.org
cd /git/pkg-javascript
rm -rf node-htmlparser2.git/
mv node-htmlparser2._new.git/ node-htmlparser2.git/

but then we'd have to update it in debian/control since that currently points 
to node-htmlparser2_new

Paolo

-- 
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] RFS: node-htmlparser2 3.9.2

[Paolo Greppi]

On 11/01/2017 17:30, Pirate Praveen wrote:
> Paolo Greppi wrote:
>> I think you are looking at the old repo here:
>> https://anonscm.debian.org/git/pkg-javascript/node-htmlparser2.git
>>
>> The repo I created has all the branches / tags:
>> https://anonscm.debian.org/git/pkg-javascript/node-htmlparser2_new.git
>>
>> I have created a new repo because the old one has this weird branch layout 
>> and a lot of tags, but I was shy of deleting it.
>>
>> We can of course do a:
>>
>> ssh git.debian.org
>> cd /git/pkg-javascript
>> rm -rf node-htmlparser2.git/
>> mv node-htmlparser2._new.git/ node-htmlparser2.git/
>>
>> but then we'd have to update it in debian/control since that currently 
>> points to node-htmlparser2_new
> 
> since this is going to be the main repo, I suggest you rename the other repo 
> as _old.
> 
> 


OK I've done that, and updated the debian/control accordingly

P.

-- 
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] RFS: node-end-of-stream 1.1.0

[Paolo Greppi]

On 02/12/2016 17:51, Pirate Praveen wrote:
> On വെള്ളി 02 ഡിസംബര്‍ 2016 04:26 വൈകു, Paolo Greppi wrote:
>> oops !
>>
>> git push --all && git push --tags
>>
> 
> Its failing to build on a clean chroot.
> 
> Error: Cannot find module 'once'
> 
> node-once should be added as a build dependency as well.
> 
> You can use build scripts from pkg-ruby-extras repo as per steps given
> in
> http://lists.alioth.debian.org/pipermail/pkg-javascript-devel/2016-November/015893.html
> so it will build on a clean system and run autopkgtests also on a clean
> system.

Repetita juvant: at last you convinced me. I was resisting because I
have jessie on my main workstation, but worked around that by using a
separate VM.

The build script from pkg-ruby-extras is great indeed. It also made me
aware of a couple of additional minor issues (lintian wishlist warnings)

Paolo




-- 
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] RFS: node-detect-indent 5.0.0

[Paolo Greppi]

Hi,

I packaged node-detect-indent as per this ITP:
https://bugs.debian.org/846204, this is the repo:
https://anonscm.debian.org/git/pkg-javascript/node-detect-indent.git

Please someone more experienced than me review it and if it's OK sponsor
its upload.

Thanks,

Paolo

-- 
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] RFS: node-loose-envify 1.3.0

[Paolo Greppi]

Hi,

I packaged node-loose-envify as per this ITP:
https://bugs.debian.org/846206, this is the repo:
https://anonscm.debian.org/git/pkg-javascript/node-loose-envify.git

Two notes
- regarding the source-is-missing error mentioned here
https://lists.alioth.debian.org/pipermail/pkg-javascript-devel/2016-November/015929.html,
I choose to delete the file with a patch
- I could not get rid of the binary-without-manpage lintian warning, as
the supplied CLI does not support --help I could not use help2man ...

Please someone more experienced than me review it and if it's OK sponsor
its upload.

Thanks,

Paolo



-- 
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] RFS: node-emoji 1.4.1

[Paolo Greppi]

On 03/12/2016 06:57, Pirate Praveen wrote:
> On ശനി 03 ഡിസംബര്‍ 2016 06:46 രാവിലെ, Jérémy Lal wrote:
>> Bad move :)
>> What if a module is named "emoji" ? Then you'll have node-emoji
>> conflict with it.
>> node-node-emoji is the right name here.
> 
> I think this is over engineering. We add node- prefix so we can have the
> same library in other languages like ruby-emoji, python-emoji etc.
> 
> As for having an unlikely node-emoji and emoji modules, we can choose to
> support the better one and patch its reverse dependencies in most cases.
> If that option is not working, I think node-node- should be a last resort.

Actually there is already a module in the npm registry called "emoji"
https://www.npmjs.com/package/emoji
but it seems less popular (963 downloads in the last month against
1.856.808 downloads in the same period for node-emoji). The github repo
is also stuck at 2014-07-05 whereas node-emoji is more active.

The policy within Debian is whoever gets there first can get hold of a
package name but I'd prefer to reach a consensus among us.

Paolo



signature.asc
Description: OpenPGP digital signature
-- 
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] enabling tests on node-cliui

[Paolo Greppi]

On 02/12/2016 10:13, Jérémy Lal wrote:
> Please don't top-post.
> 
>> On 29/11/2016 13:59, Jérémy Lal wrote:
>>> 2016-11-29 13:24 GMT+01:00 Paolo Greppi <paolo.gre...@libpf.com>:
>>>> Since chai is in Debian I have re-enabled the original tests in
>>>> node-cliui, there is one failing and 23 passing:
>>>>
>>>>   1) cliui layoutDSL ignores ansi escape codes when measuring padding:
>>>>
>>>>   AssertionError: expected [ Array(5) ] to deeply equal [ Array(5) ]
>>>>   + expected - actual
>>>>
>>>>  "  |",
>>>>  "  __|   __|  |   |   _ \\",
>>>>  "  || |   |   __/",
>>>>  " \\__| _|\\__,_| \\___|",
>>>>   -  ""
>>>>   +  " "
>>>>]
>>>>
>>>>   at Context.
>>>> (/root/debian/node-cliui/node-cliui/test/cliui.js:441:17)
>>>>   at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:223:21)
>>>>   at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:216:7)
>>>>   at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:373:10)
>>>>   at /usr/lib/nodejs/mocha/lib/runner.js:451:12
>>>>   at next (/usr/lib/nodejs/mocha/lib/runner.js:298:14)
>>>>   at /usr/lib/nodejs/mocha/lib/runner.js:308:7
>>>>   at next (/usr/lib/nodejs/mocha/lib/runner.js:246:23)
>>>>   at Immediate._onImmediate (/usr/lib/nodejs/mocha/lib/runner.js:275:5)
>>>>   at processImmediate [as _immediateCallback] (timers.js:383:17)
>>>>
>>>> Has anybody an idea why ?
>>>
>>> (please push commits so that we can sbuild easily).
>>>
>>> It works locally, but not in a clean sbuild chroot.
>>> No idea why. Something with how much console features are supported.
>>> I'm interested to find out why !
>>>
>>>> Or should I just skip the failing test using the mocha skip
>>>> chain-function (http://mochajs.org/#inclusive-tests) ?
>>>
>>> Good idea - it's better than a patch !
>>>
>>> Jérémy
> 
> 2016-12-02 10:02 GMT+01:00 Paolo Greppi <paolo.gre...@libpf.com>:
>> I have investigated and found that the same fix for node-chalk
>> (https://lists.alioth.debian.org/pipermail/pkg-javascript-devel/2016-November/015905.html)
>> fixes the issue here.
>>
>> No need to path to skip tests.
>>
>> This package is basically ready for release with the tests enabled.
>> Would Jérémy sponsor its upload ?
> 
> Sure, please fix
> I: node-cliui source: quilt-patch-missing-description 00-enable_chalk.diff
> 
> Jérémy
> 
> 

I have fixed the warning !

Paolo

[& sorry for the top post]

-- 
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] RFS: node-end-of-stream 1.1.0

[Paolo Greppi]

Hi,

I resumed work on node-end-of-stream as per this old ITP (which I
unarchived, reopened and reassigned): https://bugs.debian.org/753250,
This is the repo:
https://anonscm.debian.org/git/pkg-javascript/node-end-of-stream.git

Please someone more experienced than me review it and if it's OK sponsor
its upload.

This is required for node-yarnpkg (https://bugs.debian.org/843021).

Thanks,

Paolo

-- 
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] RFS: node-end-of-stream 1.1.0

[Paolo Greppi]

On 02/12/2016 11:54, Pirate Praveen wrote:
> On വെള്ളി 02 ഡിസംബര്‍ 2016 03:28 വൈകു, Paolo Greppi wrote:
>> Hi,
>>
>> I resumed work on node-end-of-stream as per this old ITP (which I
>> unarchived, reopened and reassigned): https://bugs.debian.org/753250,
>> This is the repo:
>> https://anonscm.debian.org/git/pkg-javascript/node-end-of-stream.git
>>
>> Please someone more experienced than me review it and if it's OK sponsor
>> its upload.
> 
> Seems you forgot to push all branches and tags. Tag and pristine-tar
> data for current version is missing.
> 
> 
> 
> 
oops !

git push --all && git push --tags


-- 
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] RFS: node-string.prototype.codepointat 0.2.0

[Paolo Greppi]

I've done that. The tests are silent, when run with:

  nodejs test/test.js

when run with:

  mocha test/test.js

it says "0 passing" probably because upstream did not use the
describe... it ... syntax

Paolo

On 02/12/2016 07:08, Pirate Praveen wrote:
> On ചൊവ്വ 29 നവംബര്‍ 2016 06:37 വൈകു, Paolo Greppi wrote:
>> Please someone more experienced than me review it and if it's OK sponsor
>> its upload.
> 
> Can you enable tests? The tests don't give any output when it runs, but
> if I move codepointat.js to another directory, it fails.




signature.asc
Description: OpenPGP digital signature
-- 
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] RFS: node-tar-stream 1.5.2

[Paolo Greppi]

On 02/12/2016 10:12, Pirate Praveen wrote:
> 
> 
> On 2016, ഡിസംബർ 2 2:36:04 PM IST, Paolo Greppi <paolo.gre...@libpf.com> wrote:
>> OK BTW on this one when I tried to reopen the ITP #753287 the BTS
>> replied "nope, the bug is archived!"
>>
>> So what is best here ? To unarchive it or to open a new one ?
>>
> 
> I see the main purpose of ITP as way for avoiding duplication and giving a 
> chance for wider community to review suitability of a proposed package. Both 
> are met with the current ITP. So I think it is fine to just keep the same ITP.
> 
OK I have unarchived, reopened and reassigned the existing ITP. I have
also set out to enable build tests + autopkgtests in this one, and in
doing so I noticed that I need end-of-stream first, see the other RFS ..

I guess we can put this one on hold and wait for node-end-of-stream so
that tests can be enabled as well.

Paolo

-- 
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] RFS: node-tar-stream 1.5.2

[Paolo Greppi]

On 03/12/2016 17:59, Pirate Praveen wrote:
> On വെള്ളി 02 ഡിസംബര്‍ 2016 03:30 വൈകു, Paolo Greppi wrote:
>> I guess we can put this one on hold and wait for node-end-of-stream so
>> that tests can be enabled as well.
> 
> node-end-of-stream is in the archive, but pristine-tar data is missing.
> Please push pristine-tar branch.

Hi I have done that and proceeded launch build from pkg-ruby-extras
which failed the autopkgtest because of some issues with dependencies.

I fixed most, but now I am stuck here: package.json declares a
dependency on bl ^1.0.0 whereas ATM we have
https://tracker.debian.org/pkg/node-bl 0.9.3 while 1.1.2 is out; should
I update that first ?

node-bl seems to be a quite relevant package with 9.823.459 downloads in
the last month.

It should be low risk to upgrade because the command:
  apt-cache rdepends node-bl

returns:

node-bl
Reverse Depends:
  node-yawl

The latter has a FTBFS big open for about a year, git repo is basically
stuck in 2014, and npm registry showns 96 downloads in the last month.

Paolo



signature.asc
Description: OpenPGP digital signature
-- 
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] enabling tests on node-cliui

[Paolo Greppi]

Since chai is in Debian I have re-enabled the original tests in
node-cliui, there is one failing and 23 passing:

  1) cliui layoutDSL ignores ansi escape codes when measuring padding:

  AssertionError: expected [ Array(5) ] to deeply equal [ Array(5) ]
  + expected - actual

 "  |",
 "  __|   __|  |   |   _ \\",
 "  || |   |   __/",
 " \\__| _|\\__,_| \\___|",
  -  ""
  +  " "
   ]

  at Context.
(/root/debian/node-cliui/node-cliui/test/cliui.js:441:17)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:223:21)
  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:216:7)
  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:373:10)
  at /usr/lib/nodejs/mocha/lib/runner.js:451:12
  at next (/usr/lib/nodejs/mocha/lib/runner.js:298:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:308:7
  at next (/usr/lib/nodejs/mocha/lib/runner.js:246:23)
  at Immediate._onImmediate (/usr/lib/nodejs/mocha/lib/runner.js:275:5)
  at processImmediate [as _immediateCallback] (timers.js:383:17)

Has anybody an idea why ?

Or should I just skip the failing test using the mocha skip
chain-function (http://mochajs.org/#inclusive-tests) ?

Paolo



signature.asc
Description: OpenPGP digital signature
-- 
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] RFS: node-death 1.0.0

[Paolo Greppi]

Hi,

I packaged node-death as per this ITP:
https://bugs.debian.org/846202, this is the repo:
https://anonscm.debian.org/git/pkg-javascript/node-death.git

Please someone more experienced than me review it and if it's OK sponsor
its upload.

Thanks,

Paolo



signature.asc
Description: OpenPGP digital signature
-- 
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] RFS: node-tar-stream 1.5.2

[Paolo Greppi]

Hi,

I resumed work on node-tar-stream as per this ITP:
https://bugs.debian.org/753287, this is the repo:
https://anonscm.debian.org/git/pkg-javascript/node-tar-stream.git

Please someone more experienced than me review it and if it's OK sponsor
its upload.

This is required for node-yarnpkg (https://bugs.debian.org/843021).

Thanks,

Paolo



signature.asc
Description: OpenPGP digital signature
-- 
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] RFS: node-string.prototype.codepointat 0.2.0

[Paolo Greppi]

Hi,

I packaged node-string.prototype.codepointat as per this ITP:
https://bugs.debian.org/846213, this is the repo:
https://anonscm.debian.org/git/pkg-javascript/node-string.prototype.codepointat.git

Please someone more experienced than me review it and if it's OK sponsor
its upload.

Thanks,

Paolo



signature.asc
Description: OpenPGP digital signature
-- 
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] RFS: node-bl 1.1.2

[Paolo Greppi]

Hi,

I updated node-bl from version 0.9.3 to 1.1.2 on alioth:
https://anonscm.debian.org/git/pkg-javascript/node-bl.git/

This version is required for node-tar-stream (which depends on bl
^1.0.0); node-tar-stream is in turn required for node-yarnpkg
(https://bugs.debian.org/843021).

Please someone more experienced than me review it and if it's OK sponsor
its upload.

Thanks,

Paolo



signature.asc
Description: OpenPGP digital signature
-- 
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] RFS: node-loose-envify 1.3.0

[Paolo Greppi]

On 03/12/2016 01:33, Jérémy Lal wrote:
> 2016-12-03 1:02 GMT+01:00 Paolo Greppi <paolo.gre...@libpf.com>:
>> Hi,
>>
>> I packaged node-loose-envify as per this ITP:
>> https://bugs.debian.org/846206, this is the repo:
>> https://anonscm.debian.org/git/pkg-javascript/node-loose-envify.git
>>
>> Two notes
>> - regarding the source-is-missing error mentioned here
>> https://lists.alioth.debian.org/pipermail/pkg-javascript-devel/2016-November/015929.html,
>> I choose to delete the file with a patch
> 
> I'm not sure it does the trick.
> A better IMO approach is to use Files-Exclude in debian/copyright, and
> make a proper debian/watch. Then uscan will automatically dfsg-repack
> the orig tarball. See how some other dfsg/ds packages do that.

It does the trick because the lintian error is gone.

I'd rather avoid dfsg rightnow because :
- the specific file is part of the javascript corpus the test suite runs
on (which we can't run at the moment anyway since it requires browserify)
- I don't think that makes the package "non-DFSG clean" as a whole
- sheer ignorance: the dfsg_clean workflow being new for me

> 
>> - I could not get rid of the binary-without-manpage lintian warning, as
>> the supplied CLI does not support --help I could not use help2man ...
> 
> Then you need to build a manpage...
> A very easy way to do so is with marked-man (convert .md to .1).
> Leave the envify.md file in debian/ dir and build the .1 during build.

Nice tool, I have created a basic manpage.

> Side note:
> override_dh_fixperms:
>   dh_fixperms -X debian/node-loose-envify/usr/lib/nodejs/loose-envify/cli.js
> 
> isn't right because it makes the build non-reproducible, see
> https://bugs.debian.org/845745
> about why.

Done

> Also the description isn't really clear. Maybe a short sentence about
> what it's about in a more general way. Is it useful for some build tool ?

I gave it a try, let me know if it makes more sense.

It's difficult for me to imagine the use cases of some of the modules we
are packaging. This one I'm trying to get in because it's a dependency
of node-invariant - and all this is to get node-yarnpkg into Stretch as
a new package.

I wonder if we can do it < 2017-01-05 ?

There are about 6 dependencies left to go plus babel + gulp as build
deps. The latter is the same short-term focus as
https://www.generosity.com/community-fundraising/debian-browserify-2 so
yes maybe it can be done !

> 
> Jérémy.
> 
> 


-- 
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] RFS: node-loose-envify 1.3.0

[Paolo Greppi]

On 05/12/2016 11:41, Pirate Praveen wrote:
> On തിങ്കള്‍ 05 ഡിസംബര്‍ 2016 03:45 വൈകു, Paolo Greppi wrote:
>> It does the trick because the lintian error is gone.
> 
> But its bad for long term maintenance, any time that file changes,
> you'll have to refresh the patch.
>> I'd rather avoid dfsg rightnow because :
>> - the specific file is part of the javascript corpus the test suite runs
>> on (which we can't run at the moment anyway since it requires browserify)
>> - I don't think that makes the package "non-DFSG clean" as a whole
> 
> but the removal is for dfsg.
> 
>> - sheer ignorance: the dfsg_clean workflow being new for me
> 
> See node-levn for an example.
> 
> 1. Add Files-Excluded to copyright
> 2. Add repack options to watch
> 3. Rename to +dfsg.orig and edit the orig.tar, remove the file (I use
> graphical tools like file-roller)
> 4. Edit changelog
> 5. Import the +dfsg.orig (gbp import-orig)
> 
> If you get it working, may be add it to a wiki page.

Thanks Jérémy & Pirate for all the suggestions, I'll give it a try. But
I have to pause my debian activities for a couple of days first ...

>> There are about 6 dependencies left to go plus babel + gulp as build
>> deps. The latter is the same short-term focus as
>> https://www.generosity.com/community-fundraising/debian-browserify-2 so
>> yes maybe it can be done !
> 
> This campaign did not receive much support (only 7% of the target). But
> we are still working on it. We need to complete about 30 modules to
> finish gulp. Any help in finishing that list would be awesome.

I'll have a look after Thursday !

> All babel modules are in a single repo, Shanavas is trying to automate
> it. But we still need to package non babel dependencies from here.
> 
> https://wiki.debian.org/Javascript/Nodejs/Tasks/babel-cli

Quite some fun here as well, again I'll have a look after Thursday.

> https://wiki.debian.org/Javascript/Nodejs/Tasks/gulp needs tiny
> submodules of lodash but we need help for that
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845227 can you try it?

Why they not using a good old makefile ? Anyway I have added a comment
to the bug, just my shot in the dark ...

Paolo




signature.asc
Description: OpenPGP digital signature
-- 
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#845227: trying my JS skills

[Paolo Greppi]

I am not sure what you want to achieve (and I ignore the intent of
upstream) but I noticed that the build-modules.js script looks at the
last argument in the command line to select the target it should copy
the files to

so for example if I create a directory:

  mkdir dist/q

then passing this as last argument to the command line:

  nodejs lib/main/build-modules.js dist/q

will not cause the error

-- 
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] RFS: node-bl 1.1.2

[Paolo Greppi]

On 04/12/2016 18:39, Jérémy Lal wrote:
> 2016-12-04 15:27 GMT+01:00 Paolo Greppi <paolo.gre...@libpf.com>:
>> Hi,
>>
>> I updated node-bl from version 0.9.3 to 1.1.2 on alioth:
>> https://anonscm.debian.org/git/pkg-javascript/node-bl.git/
>>
>> This version is required for node-tar-stream (which depends on bl
>> ^1.0.0); node-tar-stream is in turn required for node-yarnpkg
>> (https://bugs.debian.org/843021).
>>
>> Please someone more experienced than me review it and if it's OK sponsor
>> its upload.
> 
> I fixed copyright author, and added a patch to be able to run tests
> with node-tap.
> Please have a look, change last things, and i'll upload.
> 
> Jérémy

Thanks !

I have enabled the same tests in autopkgtest.

I would call this release 1.1.2-1 since it's the 1st upload.

Finally, making it a team upload avoids the
source-nmu-has-incorrect-version-number lintian warning.

It should be ready now.

Paolo


-- 
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#848749: disable build-time tests

[Paolo Greppi]

Il looks like node-expand-tilde returns a directory which does not exist
(sbuild-nonexistent) at this line in
node-fined/test/utils/get-userhome-file.js:
var userHomeDir = expandTilde('~');

This in turn triggers the exception in the next line:
var userHomeFiles = fs.readdirSync(userHomeDir);

Google tells me that in an sbuild chroot HOME is indeed set to
/sbuild-nonexistent.

Node-expand-tilde has build and autopkgtests turned on, but they pass
because they do not check that the returned dir exist, only that they
are consistent !

I guess we have no choice but to disable build tests. I have done so in
the repo on alioth, autopkgtests are still on (although I had to disable
a few also related to tilde expansion).

Paolo

-- 
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] RFS: tinycon.js 0.6.5

[Paolo Greppi]

Hi,

I have packaged tinycon.js, see the ITP I am CC-ing and
the repo:
https://anonscm.debian.org/git/pkg-javascript/tinycon.js.git

This is a requirement of etherpad-lite (https://bugs.debian.org/576998).

Please someone more experienced than me review it and if it's OK sponsor
its upload.

Thanks,

Paolo

-- 
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] grunt-contrib-uglify and grunt-contrib-copy

[Paolo Greppi]

On 21/12/2016 08:19, Paolo Greppi wrote:
> On 20/12/2016 03:41, Pirate Praveen wrote:
>> On ചൊവ്വ 20 ഡിസംബര്‍ 2016 12:15 രാവിലെ, Paolo Greppi wrote:
>>> Hi,
>>>
>>> while packaging node-rx and trying to build it with grunt, I noticed
>>> that apart from a number of non-relevant grunt add-ons related to
>>> linting (grunt-jscs and grunt-contrib-jshint), testing (grunt-saucelabs,
>>> grunt-contrib-connect, grunt-contrib-qunit) and stuff
>>> (grunt-contrib-watch) it depends on grunt-contrib-uglify and
>>> grunt-contrib-copy
>>>
>>> From what I can tell, these I'll really need.
>>
>> grunt-contrib-copy should be easy. grunt-contrib-uglify has many
>> dependencies still to be packaged last time I checked. You can just call
>> uglifyjs from commandline in debian/rules. See node-jquery-textchange
>> for an example. We can package grunt-contrib-uglify in parallel to avoid
>> the manual steps.
> 
> I filed ITPs for both.
> 
> For node-grunt-contrib-uglify I found I can patch away maxmin by
> providing a down-to-earth one-liner, this gets rid of a few recursive
> dependencies. I just sent the RFS.
> 
> Node-grunt-contrib-copy is also ready but awaits for node-file-sync-cmp

Now I have provisional node-grunt-contrib-uglify and
node-grunt-contrib-copy installed on the test machine, I patched the
Gruntfile.js to run only the relevant tasks, but when I issue:

quilt push -a
grunt --force

I got these errors:

Local Npm module "grunt-contrib-copy" not found. Is it installed?
Local Npm module "grunt-contrib-uglify" not found. Is it installed?
Local Npm module "grunt-contrib-concat" not found. Is it installed?
Warning: Task "concat:core" not found. Used --force, continuing.

Any idea ?

Paolo

P.S. The repo is here:
https://anonscm.debian.org/git/pkg-javascript/node-rx.git

-- 
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] RFS: node-grunt-contrib-uglify 2.0.0

[Paolo Greppi]

Hi,

I have packaged node-grunt-contrib-uglify, see the ITP I am CC-ing and
the repo:
https://anonscm.debian.org/git/pkg-javascript/node-grunt-contrib-uglify.git

I had to repackage to get rid of uglyfied files part of the test suite.
Therefore I can not not run tests during build or autopkgtests ...

Please someone more experienced than me review it and if it's OK sponsor
its upload.

Thanks,

Paolo

-- 
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] grunt-contrib-uglify and grunt-contrib-copy

[Paolo Greppi]

On 20/12/2016 03:41, Pirate Praveen wrote:
> On ചൊവ്വ 20 ഡിസംബര്‍ 2016 12:15 രാവിലെ, Paolo Greppi wrote:
>> Hi,
>>
>> while packaging node-rx and trying to build it with grunt, I noticed
>> that apart from a number of non-relevant grunt add-ons related to
>> linting (grunt-jscs and grunt-contrib-jshint), testing (grunt-saucelabs,
>> grunt-contrib-connect, grunt-contrib-qunit) and stuff
>> (grunt-contrib-watch) it depends on grunt-contrib-uglify and
>> grunt-contrib-copy
>>
>> From what I can tell, these I'll really need.
> 
> grunt-contrib-copy should be easy. grunt-contrib-uglify has many
> dependencies still to be packaged last time I checked. You can just call
> uglifyjs from commandline in debian/rules. See node-jquery-textchange
> for an example. We can package grunt-contrib-uglify in parallel to avoid
> the manual steps.

I filed ITPs for both.

For node-grunt-contrib-uglify I found I can patch away maxmin by
providing a down-to-earth one-liner, this gets rid of a few recursive
dependencies. I just sent the RFS.

Node-grunt-contrib-copy is also ready but awaits for node-file-sync-cmp

>> Has anybody experience with these ? Should I just package them as ?
>>
>> The current state of node-rx is here:
>>
>> https://anonscm.debian.org/git/pkg-javascript/node-rx.git
>>


-- 
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] RFS: node-jsonminify 0.4.1

[Paolo Greppi]

Hi,

I have packaged node-jsonminify, see the ITP I am CC-ing and
the repo:
https://anonscm.debian.org/git/pkg-javascript/node-jsonminify.git

Please someone more experienced than me review it and if it's OK sponsor
its upload.

Thanks,

Paolo

-- 
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] RFS: node-proper-lockfile 2.0.0

[Paolo Greppi]

On 18/12/2016 12:01, Pirate Praveen wrote:
> On വെള്ളി 16 ഡിസംബര്‍ 2016 09:28 വൈകു, Paolo Greppi wrote:
>> The repo on alioth is ready:
>> https://anonscm.debian.org/git/pkg-javascript/node-proper-lockfile.git
>>
>> For the version dependency on node-retry >= 0.10.0, discussed here:
>> -
>> https://lists.alioth.debian.org/pipermail/pkg-javascript-devel/2016-December/016454.html
>> -
>> https://lists.alioth.debian.org/pipermail/pkg-javascript-devel/2016-December/016559.html
>> I have found that after relaxing it the tests still pass. So this could
>> be a feasible workaround while we decide what to do with node-retry.
>>
>> Please someone more experienced than me review it and if it's OK sponsor
>> its upload.
> 
> I relaxed dependency on node-retry (you relaxed only builddeps, if you
> had used build-and-upload script from pkg-ruby-extras, you'd have found
> it) and uploaded.

oops ! I do use those scripts but now this time apparently !

Paolo



-- 
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] RFS: node-external-editor 2.0.1

[Paolo Greppi]

Hi,

I have packaged node-external-editor, see the ITP I am CC-ing and the repo:
https://anonscm.debian.org/git/pkg-javascript/node-external-editor.git/

I had to cheat on the dependency on node-tmp: the package.json requests
0.0.31 but with 0.0.28 that we have in debian the tests pass ..

Please someone more experienced than me review it and if it's OK sponsor
its upload.

Thanks,

Paolo

-- 
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] RFS: node-is-promise 2.1.0

[Paolo Greppi]

Hi,

I have packaged node-is-promise, see the ITP I am CC-ing and the repo:
https://anonscm.debian.org/git/pkg-javascript/node-is-promise.git/

Please someone more experienced than me review it and if it's OK sponsor
its upload.

Thanks,

Paolo

-- 
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#848749: set a different $HOME for build-time tests

[Paolo Greppi]

As per this comment in the Pkg-javascript-devel mailing list:
https://lists.alioth.debian.org/pipermail/pkg-javascript-devel/2016-December/016725.html

I have changed the approach to set a different $HOME for build-time
tests. This should fix the build-time tests.

Paolo

-- 
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#848749: disable build-time tests

[Paolo Greppi]

On 20/12/2016 07:41, Pirate Praveen wrote:
> On ചൊവ്വ 20 ഡിസംബര്‍ 2016 12:03 വൈകു, Paolo Greppi wrote:
>> Il looks like node-expand-tilde returns a directory which does not exist
>> (sbuild-nonexistent) at this line in
>> node-fined/test/utils/get-userhome-file.js:
>> var userHomeDir = expandTilde('~');
>>
>> This in turn triggers the exception in the next line:
>> var userHomeFiles = fs.readdirSync(userHomeDir);
>>
>> Google tells me that in an sbuild chroot HOME is indeed set to
>> /sbuild-nonexistent.
> 
> ... because debian policy prevents writing to $HOME during build and
> sbuild enforces it by setting it to a non existing directory.
> 
>> Node-expand-tilde has build and autopkgtests turned on, but they pass
>> because they do not check that the returned dir exist, only that they
>> are consistent !
>>
>> I guess we have no choice but to disable build tests. I have done so in
>> the repo on alioth, autopkgtests are still on (although I had to disable
>> a few also related to tilde expansion).
> 
> See node-v8flags for setting a different $HOME for tests


Thanks for the trick !

I have re-instated the build-ime tests, see:
https://bugs.debian.org/848749#15

RFS !

Paolo

-- 
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] Re: Help needed on rollup

[Paolo Greppi]

On 23/12/2016 07:16, Pirate Praveen wrote:
> On ചൊവ്വ 20 ഡിസംബര്‍ 2016 03:33 വൈകു, Pirate Praveen wrote:
>> yes, in theory. In practice, babel-cli has a long chain of dependencies.
>> https://wiki.debian.org/Javascript/Nodejs/Tasks/babel-cli
> 
> babel-cli is mostly complete, but it needs lerna too
> https://wiki.debian.org/Javascript/Nodejs/Tasks/lerna

Looking at that:
- cmd-shim and read-cmd-shim you only need on windows
- inquirer I'm rushing for that too (it's required for node-yarnpkg)

So we're left with three simple packages:
- pad (*)
- progress (*)
- sync-exec (*)
two with just 1 dependency:
- command-join
- object-assign-sorted
and their dependencies which should be packaged first:
- array-from (*)
- sorted-object (*)

I am going to file the ITPs for the 5 marked with (*)

Paolo

-- 
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] RFS: node-read 1.0.7

[Paolo Greppi]

Hi,

I have updated node-read from 1.0.5 to 1.0.7.

Version 1.0.7 is required for node-yarnpkg 0.18

I also added build-time / autopkg tests, and the license changed from
BSD to Expat.

There is 1 reverse dependency: npm (!), without tests.

It proved impossible to run the supplied test suite during the
autopkgtests, see the message in the last commit

Paolo

-- 
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] RFS: node-bytes 2.4.0

[Paolo Greppi]

Hi,

I have updated node-bytes from 2.1.0 to 2.4.0 and moved its repo from
collab-maint to pkg-javascript.

Version 2.4.0 is required for node-yarnpkg 0.18

There are 3 reverse dependencies:
- node-body-parser
- node-compression
- node-raw-body

I have launched the autopkgtests for those and their dependencies with
pkg-ruby-extras/build and everything seems fine.

Paolo

-- 
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] RFSx4

[Paolo Greppi]

- node-array-from https://bugs.debian.org/849178
  pkg-javascript/node-array-from.git

- node-pad https://bugs.debian.org/849182
  pkg-javascript/node-pad.git

- node-progress https://bugs.debian.org/849181
  pkg-javascript/node-progress.git

- node-sorted-object https://bugs.debian.org/849179
  pkg-javascript/node-sorted-object.git

Ciao

-- 
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] RFS: node-mute-stream 0.0.7

[Paolo Greppi]

On 23/12/2016 17:11, Pirate Praveen wrote:
> On വെള്ളി 23 ഡിസംബര്‍ 2016 06:25 വൈകു, Paolo Greppi wrote:
>> Hi,
>>
>> I have updated node-mute-stream from 0.0.4 to 0.0.7.
>>
>> Version 0.0.6 is required to install node-inquirer.
>>
>> I also added build-time / autopkg tests, and the license changed from
>> BSD to Expat.
>>
>> There is 1 reverse dependency: node-read, without autopkgtests.
>>
>> So I test this one against read 1.0.7, and the tests pass.
> 
> How did you test it? I think its better if Jeremy Lal takes it as
> node-read has npm as reverse dependency.

Fine with me !

I run build-tests in node-read while updating the latter to 1.0.7, see
my other RFS about that

P


-- 
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] RFS: node-cli-cursor 1.0.2

[Paolo Greppi]

Hi,

I have packaged node-cli-cursor, see the ITP I am CC-ing and
the repo:
https://anonscm.debian.org/git/pkg-javascript/node-cli-cursor.git

Please someone more experienced than me review it and if it's OK sponsor
its upload.

Thanks,

Paolo

-- 
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-sorted-object_2.0.1-1_amd64.changes REJECTED

[Paolo Greppi]

On 24/12/2016 00:00, Thorsten Alteholz wrote:
> Hi Paolo,
> 
> please mention the double license of this software in your debian/copyright.
> 
> Thanks!
>  Thorsten

So I have added the WTFPL-2 too, a quite popular license:
https://codesearch.debian.net/search?q=path%3Adebian%2Fcopyright+WTFPL

Fixed without increasing the version + tag deleted.

Please sponsor again the upload.

Paolo


-- 
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-rx_4.1.0+dfsg1-1_amd64.changes REJECTED

[Paolo Greppi]

On 24/12/2016 00:00, Thorsten Alteholz wrote:
> Hi Paolo,
> 
> Microsoft claims copyright for some files ...
> 
>   Thorsten

I have attributed the copyright to Microsoft Corporation.

Fixed without increasing the version + tag deleted.

Please sponsor again the upload.

Paolo

-- 
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#794988: the domhandler dependency

[Paolo Greppi]

On 16/12/2016 11:29, Paolo Greppi wrote:
> I got the same while testing node-cheerio (ITP:
> https://bugs.debian.org/848315).
> 
> The domhandler dependency is indeed listed in the current upstream's
> package.json.
> 
> Upgrading node-htmlparser2 from 3.7.3 to 3.9.2 would force us to package
> domhandler and domutils, and the latter's dependency node-dom-serializer.
> 
> And I assume this bug would be fixed.
> 
> BTW while updating we could also add debian/watch to this one ...
> 
> Paolo

Now that we have those tiny packages is, and because node-cheerio
(https://bugs.debian.org/848315) requires htmlparser2 ^3.9.1, I tried
packaging the current version of node-htmlparser2 (3.9.2).

Since the existing git repo on alioth does not conform to
git-buildpackage, I created a brand new one:
https://anonscm.debian.org/cgit/pkg-javascript/node-htmlparser2_new.git

In there I moved the control and changelog from the old repo, but most
of what npm2dep generated I left untouched. So we get the watch file,
and of course no patches to bundle node-dom{elementtype,handler,utils}.

It works here: all build/DEP8 tests pass.
The DEP8 test of the only reverse dependency node-jsdom fail with the
same error as on ci.d.n:
https://ci.debian.net/data/packages/unstable/amd64/n/node-jsdom/latest-autopkgtest/log.gz

Any comment ?

Paolo



-- 
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#849557: Bug#849557: switch to node-uglify instead of yui-compressor

[Paolo Greppi]

On 28/12/2016 17:30, Pirate Praveen wrote:
> 2016-12-28 21:32 या दिवशी Pirate Praveen ने लिहीले :
>> yui-compressor pulls in jre. Since nodejs is already a build dep, its
>> better to use node-uglify.
> 
> On a closer look, yui-compressor is used only for minifying css. To replace 
> it, we should package uglifycss. There are no dependencies for uglifycss.
> 

According to npm registry data, they are both seldom used modules. clean-css is 
more popular, and is already in the archive as node-clean-css.

Why not use that ?

P.

-- 
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] RFS: node-htmlparser2 3.9.2

[Paolo Greppi]

Hi,

since node-cheerio (https://bugs.debian.org/848315) which is a requirement of 
etherpad-lite (https://bugs.debian.org/576998) needs htmlparser2 "^3.9.1", I 
have updated node-htmlparser2 from version 3.7.3 to the current version 3.9.2.

And since we now have node-dom{elementtype,handler,utils} in the archive, I 
have unbundled them.

Also I have turned on tests, and they pass so that also 
https://bugs.debian.org/794988 is fixed.

node-htmlparser2 has a single reverse dependency: node-jsdom.
But node-jsdom currently fails to pass autopkgtests anyway 
(https://ci.debian.net/packages/n/node-jsdom/)
nor does it have a proper test suite.

I noticed that the repo on alioth has not the usual branch layout, so I have 
set it up in a separate repo:
https://anonscm.debian.org/git/pkg-javascript/node-htmlparser2_new.git

Please someone more experienced than me review it and if it's OK sponsor its 
upload.

Paolo

-- 
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] RFS: node-socket.io-parser 2.3.1

[Paolo Greppi]

Hi,

building on the work by Bas Couwenberg back in 2015 I have packaged 
node-socket.io-parser, see the ITP I am CC-ing and
the repo:
https://anonscm.debian.org/git/pkg-javascript/node-socket.io-parser.git

Besides node-socket.io and closure-util mentioned above in the ITP, this is 
also a requirement for
packaging etherpad-lite (https://bugs.debian.org/576998).

Please someone more experienced than me review it and if it's OK sponsor its 
upload.

Thanks,

Paolo

-- 
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] RFS: node-graceful-readlink 1.0.1

[Paolo Greppi]

Hi,

I have packaged node-graceful-readlink, see the ITP I am CC-ing and
the repo:
https://anonscm.debian.org/git/pkg-javascript/node-graceful-readlink.git

Please someone more experienced than me review it and if it's OK sponsor its 
upload.

Thanks,

Paolo

-- 
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-uid-safe_2.1.3-1_amd64.changes REJECTED

[Paolo Greppi]

On 22/12/2016 17:00, Thorsten Alteholz wrote:
> 
> Hi Paolo,
> 
> there seem to be some copyright holder missing in your debian/copyright.
> 
> Thanks!
>  Thorsten

I fixed this (scan-copyrights!) without increasing the version since
it's unreleased.
I deleted the remote tag as well with

  git tag -d debian/2.1.3-1
  git push origin :refs/tags/debian/2.1.3-1

Please sponsor again the upload.

Paolo


-- 
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-loose-envify_1.3.0+dfsg-1_amd64.changes REJECTED

[Paolo Greppi]

On 22/12/2016 17:00, Thorsten Alteholz wrote:
> 
> Hi Paolo,
> 
> you wrote that you removed the bad react code, but 
>  test/pkg/node_modules/invariant/index.js
>  test/pkg/node_modules/warning/index.js
> is still there...
> 
>   Thorsten

I have removed those files as well with dfsg1 repack.

I should make the https://wiki.debian.org/CopyrightReviewTools part of
my workflow ...

Please sponsor again the upload.

Paolo


-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel