Re: [Pkg-javascript-devel] gitlab, yarn, node modules and stalled ftp NEW

[Paolo Greppi]

Il 13/04/2018 14:30, Paolo Greppi ha scritto:
> Il 13/04/2018 10:29, Pirate Praveen ha scritto:
>> Hi,
>>
>> I was hoping to be able to package all node dependencies of gitlab in main, 
>> though the sheer number of them made ftp masters to ignore them. I 
>> understand that kind of numbers are quite intimidating to deal with, so I 
>> have already moved gitlab to contrib and install these node modules directly 
>> from npm registry.
>>
>> But even that cannot move to buster because npm is not yet in buster, which 
>> is also stuck in NEW. So I'm thinking of adding yarn also to contrib, 
>> bundling all dependencies. If the node modules in NEW starts moving, 
>> hopefully when next batch of ftp assistants are on boarded, we can get it to 
>> main.
>>
>> This will also help me in backporting gitlab 10 to stretch as backporting 
>> security fixes to 8.13 is pretty challenging.
>> -- 
> 
> Why not ? We can pursue yarn packaging to contrib in parallel with the 
> mid-term task of bringing it back to main.
> This is best handled with a separate git branch (master-contrib ?)
> 
> I am ready to give it a try.
> 
> The missing dependencies can be individually npm install-ed.
> 
> Two options I can think of:
> - providing the resulting node_modules directory as a huge patch
> - running npm install xxx ... in debian/rules
> which is best ?
> 
> Paolo
> 
> P.S. yarn 1.6.0 is out, I am updating the repo just now

I had forgot there was already a (quite old) debian-contrib branch, so I used 
that.
I also used the option of running npm install xxx in debian/rules.

Note that in addition to all the missing deps I listed here:
https://bugs.debian.org/843021#157
I also had to install uuid, because of:
https://bugs.debian.org/895625

Anyway it builds fine with:
git checkout debian-contrib 
gbp buildpackage -uc -us --git-debian-branch=debian-contrib 

The resulting yarnpkg_1.6.0-1_all.deb installs, and yarnpkg can be run.
But if I use it to setup a simple project it fails:

mkdir q
cd q
yarnpkg init
yarnpkg add ci-info

yarn add v1.6.0
info No lockfile found.
[1/4] Resolving packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/ci-info: 
connect ENOENT /ci-info".
info If you think this is a bug, please open a bug report with the information 
provided in "/root/node-yarnpkg/q/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this 
command.

This looks like a network error but my network is working and I can download 
that JSON file.
Could it be one of the many out-of-date dependencies we're cheating about ?

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#895625: [node-node-uuid] please update to version 3.0.1 or higher

[Paolo Greppi]

Package: node-node-uuid
Version: 1.4.7-5
Severity: normal

--- Please enter the report below this line. ---

According to npm registry:
https://www.npmjs.com/package/node-uuid "node-uuid DEPRECATED: Use the uuid 
package instead."
https://www.npmjs.com/package/uuid points to: 
https://github.com/kelektiv/node-uuid

It appears node-uuid was a fork, then it got merged back.
There are two github projects both confusingly called "node-uuid":
- current: https://github.com/kelektiv/node-uuid is at 3.1.0
- deprecated: https://github.com/broofa/node-uuid is at 3.0.0
whereas now the module in npm registry is called "uuid".

ATM the upstream for this package is the latter.
BTW there must be something wrong with debian/watch because the tracker says "a 
new upstream version is available: 1.4.7.4.7" whereas the most recent tag is 
3.0.0.

Anyway the most recent version of the current github repo is 3.2.1 but I need 
at least 3.0.1 for yarn.

Please set the upstream to https://github.com/kelektiv/node-uuid and update the 
package to 3.0.1 or later

Thanks !

--- System information. ---
Architecture: 
Kernel:   Linux 4.15.0-2-amd64

Debian Release: buster/sid
  500 testing mi.mirror.garr.it 

--- Package information. ---
Depends  (Version) | Installed
==-+-===
nodejs | 8.9.3~dfsg-12
libjs-node-uuid| 1.4.7-5


Package's Recommends field is empty.

Package's Suggests field is empty.

-- 
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] gitlab, yarn, node modules and stalled ftp NEW

[Paolo Greppi]

Il 13/04/2018 10:29, Pirate Praveen ha scritto:
> Hi,
> 
> I was hoping to be able to package all node dependencies of gitlab in main, 
> though the sheer number of them made ftp masters to ignore them. I understand 
> that kind of numbers are quite intimidating to deal with, so I have already 
> moved gitlab to contrib and install these node modules directly from npm 
> registry.
> 
> But even that cannot move to buster because npm is not yet in buster, which 
> is also stuck in NEW. So I'm thinking of adding yarn also to contrib, 
> bundling all dependencies. If the node modules in NEW starts moving, 
> hopefully when next batch of ftp assistants are on boarded, we can get it to 
> main.
> 
> This will also help me in backporting gitlab 10 to stretch as backporting 
> security fixes to 8.13 is pretty challenging.
> -- 

Why not ? We can pursue yarn packaging to contrib in parallel with the mid-term 
task of bringing it back to main.
This is best handled with a separate git branch (master-contrib ?)

I am ready to give it a try.

The missing dependencies can be individually npm install-ed.

Two options I can think of:
- providing the resulting node_modules directory as a huge patch
- running npm install xxx ... in debian/rules
which is best ?

Paolo

P.S. yarn 1.6.0 is out, I am updating the repo just now

-- 
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#892656: even more tests fail with version 2.0.2

[Paolo Greppi]

Normally you'd expect to fix bugs with a new version, in this case while trying 
to update node-define-property 1.0.0-1 -> 2.0.2 the failing tests actually 
increased from 1 to 4.

What puzzled me was that no tests fail on upstream's CI (travis), which also 
tests nodejs version 8.

Turns out that we have upgraded node-is-descriptor to version 2.0.0, but the 
npm registry only has 1.0.2.

I have forwarded the issue upstream, and I expect upstream to answer that 
define-property correctly pins the major version of is-descriptor with ^1.0.2 
(https://docs.npmjs.com/misc/semver), stating that it won't work with 2.x.

^1.0.2 should be translated with >= 1.0.2 && < 2.0.0 but we can't encode that 
in debian/control.

So how can we check reverse dependencies for this type of issues in the future ?

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-file 1.0.0, node-resolve-dir 1.0.1 and node-flagged-respawn 1.0.0

[Paolo Greppi]

Hi, I have moved the repos to salsa and prepared the updates mentioned in the 
subject.

This is all required to update node-liftoff to 2.5.0 (hoping that fixes 
https://bugs.debian.org/853035).

Please someone allow me DM upload access for these packages or sponsor the 
uploads:
https://salsa.debian.org/js-team/node-detect-file
https://salsa.debian.org/js-team/node-node-resolve-dir
https://salsa.debian.org/js-team/node-flagged-respawn

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: WIP

[Paolo Greppi]

You can track the status here:
https://salsa.debian.org/js-team/node-liftoff/wikis/home

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#862330: unreproducible ?

[Paolo Greppi]

Hi, I just tried on a clean sid container and this is what I got:

# npm2deb depends grunt-cli
Dependencies:
NPM   Debian
grunt-cli (1.2.0) node-grunt-cli (1.2.0-3)
├─ findup-sync (~0.3.0)   node-findup-sync (0.4.3-1)
├─ grunt-known-options (~1.1.0)   node-grunt-known-options 
(1.1.0-1)
├─ nopt (~3.0.6)  node-nopt (3.0.6-3)
└─ resolve (~1.1.0)   node-resolve (1.4.0-1)

Build dependencies:
NPM   Debian
grunt (~0.4.5)grunt (1.0.1-8)
grunt-contrib-jshint (~1.0.0) None

PaulLiu and Pierre, do you think this can be closed now ?

Thanks,

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] Bug#853035: node-liftoff: Non-determistically FTBFS due to unreliable timing in tests

[Paolo Greppi]

Hi Graham and thanks for bringing this up again.

Il 07/04/2018 18:13, Graham Inggs ha scritto:
> Hi
> 
> This situation seems to get worse with each new version of nodejs.
> 
> In Ubuntu, where autopkgtests are run for every release architecture,
> node-liftoff failed on armhf [1] and arm64 [2] since the upload of
> nodejs 8.9.3.
> 
> We resorted to increasing the timeout from 5000 to 1 in
> debian/rules and debian/tests/control to allow nodejs to migrate.
> 
> Chris, you wrote "...the test would still be unreliable whatever value
> you choose", can you propose something other than increasing the
> timeout?
> 
> Regards
> Graham
> 
> [1] http://autopkgtest.ubuntu.com/packages/node-liftoff/bionic/armhf
> [2] http://autopkgtest.ubuntu.com/packages/node-liftoff/bionic/arm64

Upstream's CI does not test above node.js 6. I have raised that here:
https://github.com/js-cli/js-liftoff/issues/96

Nonetheless it may be worth updating liftoff to 2.5.0; I am going to try that.

Two new packages are required, see:
https://lists.alioth.debian.org/pipermail/pkg-javascript-devel/2018-April/025746.html
Any help with sponsoring them is welcome.

I also need to update:
- node-findup-sync 0.4.3-1 -> 2.0.0
- node-micromatch 2.3.11-1 -> 3.0.4
- node-detect-file 0.1.0-1 -> 1.0.0
- node-resolve-dir 1.0.0-1 -> 1.0.1
- node-flagged-respawn -> 0.3.2-1 -> 1.0.0

The latter in particular sounds promising for the "Liftoff launch should 
respawn if process.argv has values from v8flags in it" test failures.
flagged-respawn also has a test suite itself which can be enabled since we now 
have node-v8flags in Debian.
Maybe we catch it there !

Expect more RFSs over the next few days ...

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-make-iterator + node-object.map

[Paolo Greppi]

https://salsa.debian.org/js-team/node-make-iterator
https://salsa.debian.org/js-team/node-object.map

These are the ITPs:
https://bugs.debian.org/895323
https://bugs.debian.org/895324

Please someone sponsor the uploads.

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-yn

[Paolo Greppi]

Hi, I have packaged node-yn:
https://salsa.debian.org/js-team/node-yn

This is the ITP:
https://bugs.debian.org/886843

Please someone sponsor 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

[Pkg-javascript-devel] RFS: node-babel-plugin-transform-inline-imports-commonjs

[Paolo Greppi]

Hi, I have packaged node-babel-plugin-transform-inline-imports-commonjs:
https://salsa.debian.org/js-team/node-babel-plugin-transform-inline-imports-commonjs

This is the ITP:
https://bugs.debian.org/886844

Please someone sponsor 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] migrating my packages from alioth to salsa

[Paolo Greppi]

Il 05/04/2018 17:09, Bas Couwenberg ha scritto:
> On 2018-04-05 16:59, Paolo Greppi wrote:
>> GITLAB_TOKEN=X ./alioth-migration/migrate-repo
>> /git/pkg-javascript/node-xxx /js-team/node-xxx
> 
> There are also many node packages under collab-maint, these should also be 
> migrated to js-team on Salsa.
> 
> I did that for node-mapnik & mapnik-reference.
> 
> Kind Regards,
> 
> Bas
> 

I have looked up the current vcs_browser fields from udd (1356 packages) and 
the repos the js-team already has on salsa (217 repos).

4 packages have empty vcs_browser: node-daemon (15), node-growl (56), 
node-utilities (42) and queue-async (19)

127 have repos on salsa, 36 of those already have vcs_browser set to salsa but 
4 are incorrect (they all share the same error: the vcs_browser field should be 
without trailing .git , see https://wiki.debian.org/Salsa/Doc#Canonical_URLS):
jquery-tablesorter, less-elements.js, libjs-jquery-colorpicker and 
node-macaddress 
The remaining 127-36 = 91 have yet to update the vcs_browser field in the 
package with an upload.

We have 130 repos on collab-maint. Of these, 3 already have the salsa repo but 
have yet to update the vcs_browser field in the package with an upload: 
mapnik-reference, node-mapnik and nodejs.

There is one in a non-team repo (node-util)

The rest 1356-4-36-130-1 = 1185 are on pkg-javascript.

Paolo

P.S. How to reproduce

Get the data from udd:

ssh git.debian.org
psql -U guest -h udd.debian.org -p 5452 udd
SELECT source, vcs_browser FROM all_sources WHERE 
maintainer_email='pkg-javascript-devel@lists.alioth.debian.org' AND 
release='sid';

Get the repos that exist on salsa via the github API:
https://salsa.debian.org/api/v4/groups/js-team/projects?per_page=100=1
https://salsa.debian.org/api/v4/groups/js-team/projects?per_page=100=2
https://salsa.debian.org/api/v4/groups/js-team/projects?per_page=100=3

>From that JSON array extract the repo URLs with:
cat projects.json | jq 'map(.http_url_to_repo)'

-- 
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] migrating my packages from alioth to salsa

[Paolo Greppi]

This went rather smoothly, I post here as note to self and in case it's helpful 
to others in the team.

I sshed into moszumanska and cloned the Python script mentioned here 
https://wiki.debian.org/Salsa/AliothMigration:

ssh git.debian.org
git clone https://salsa.debian.org/anarcat/alioth-migration.git

Then for each package I "own" (sole uploader or WIP) I issued a number of 
commands similar to:

GITLAB_TOKEN=X ./alioth-migration/migrate-repo 
/git/pkg-javascript/node-xxx /js-team/node-xxx

Next for each of them in my local copy I run this (worked 95% of the time):

git checkout master
git pull
dch "Update Vcs fields for migration to https://salsa.debian.org/;
sed -i 's/Vcs-Git: 
https:\/\/anonscm.debian.org\/git\/pkg-javascript\/\(.*\).git/Vcs-Git: 
https:\/\/salsa.debian.org\/js-team\/\1.git/g' debian/control
sed -i 's/Vcs-Browser: 
https:\/\/anonscm.debian.org\/cgit\/pkg-javascript\/\(.*\).git/Vcs-Browser: 
https:\/\/salsa.debian.org\/js-team\/\1/g' debian/control
git status
git diff
git commit -am 'Update Vcs fields for migration to https://salsa.debian.org/'
sed -i 's/url = git+ssh:\/\/git.debian.org\/git\/pkg-javascript\/\(.*\).git/url 
= g...@salsa.debian.org:js-team\/\1.git/g' .git/config
git push

Finally I forked the AliothRewriter repo, and listed all the packages I 
migrated in:
https://salsa.debian.org/salsa/AliothRewriter/blob/master/definitions/pkg-javascript.conf

Note that I have not migrated the packages I team-uploaded:
/git/pkg-javascript/node-ansi-regex.git
/git/pkg-javascript/node-bl.git
/git/pkg-javascript/node-bytes.git
/git/pkg-javascript/node-htmlparser2.git
/git/pkg-javascript/node-mute-stream.git

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] How to use Debian Buster for developing with Webpack

[Paolo Greppi]

Il 21/01/2018 19:53, Paolo Greppi ha scritto:
> You have to wait a bit.
> 
> Webpack is in sid, but its migration to buster is blocked:
> https://tracker.debian.org/pkg/node-webpack
> 
> it should be unblocked as soon as nodejs 8.9.3 migrates to buster, i.e. in 3 
> days.
> 
> P.
> 
> Il 21/01/2018 19:12, Ben Finney ha scritto:
>> Pirate Praveen <prav...@onenetbeyond.org> writes:
>>
>>> On 2018, ജനുവരി 21 10:53:01 AM IST, Ben Finney <bign...@debian.org> wrote:
>>>> What do I need from Debian Buster, in order to feed a bunch of
>>>> JavaScript modules to Webpack?
>>>
>>> You just need webpack if your code is already es5.
>>
>> Which package(s) in Debian Buster? There is no ‘webpack’ package there.

Almost 1 wk has passed and nothing has happened.

According to: https://tracker.debian.org/pkg/node-webpack
webpack has "Migration status: BLOCKED: Cannot migrate due to another item, 
which is blocked (please check which dependencies are stuck)"

It also days: "webpack/armel unsatisfiable Depends: nodejs"

In fact nodejs 8.9.3~dfsg-11 is available only on:
amd64 arm64 armhf i386 mips mips64el mipsel ppc64 ppc64el s390x 

Digging in the mailing list history I found this:
https://lists.alioth.debian.org/pipermail/pkg-javascript-devel/2017-October/021369.html

Is manual action required here again ?

CC-ing Adrian...

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] How to use Debian Buster for developing with Webpack

[Paolo Greppi]

You have to wait a bit.

Webpack is in sid, but its migration to buster is blocked:
https://tracker.debian.org/pkg/node-webpack

it should be unblocked as soon as nodejs 8.9.3 migrates to buster, i.e. in 3 
days.

P.

Il 21/01/2018 19:12, Ben Finney ha scritto:
> Pirate Praveen  writes:
> 
>> On 2018, ജനുവരി 21 10:53:01 AM IST, Ben Finney  wrote:
>>> What do I need from Debian Buster, in order to feed a bunch of
>>> JavaScript modules to Webpack?
>>
>> You just need webpack if your code is already es5.
> 
> Which package(s) in Debian Buster? There is no ‘webpack’ package there.
> 


-- 
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-rollup-plugin-babel: build error unrepro but babelHelpers missing error in autopkgtest

[Paolo Greppi]

Il 17/01/2018 12:47, Pirate Praveen ha scritto:
> On 2018, ജനുവരി 17 4:54:11 PM IST, Pirate Praveen  
> wrote:
>> These warnings are gone with latest versions of base but it will break
>> snapdragon. New version of snapdragon does not depend on base, but it
>> will break braces. But braces upstream is not interested to update to
>> newer snapdragon, but he is open to pull requests.
>>
>> So the solution is to update braces to use snapdragon 0.11.
> 
> https://github.com/micromatch/braces/issues/13

OK so the developer of braces (jonschlinkert) refused to update one of braces 
dependencies (snapdragon) to a version that in turn drops a dependency on 
another one of his 1397 packages (base) ?
Ah the delights of the JS ecosystem !

But back to our issue, I follow you on 887500, but I am unsure whether 887497 
really blocks 886404 ?

I mean, only one of the 4 Critical dependency warnings seems related to 
/usr/lib/nodejs/base/utils.js (node-base)

The other 3 are related to:
/usr/lib/nodejs/babel-core/lib/transformation/file/options/option-manager.js
/usr/lib/nodejs/babel-core/lib/transformation/file/index.js

Pravi, are you sure that all the webpack "Critical dependency" warnings would 
go away with the latest version of base ?

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] bootstrapping rollup

[Paolo Greppi]

Hi team,

we are now stuck at multiple location because rollup is in contrib.

My understanding is that it is stuck in contrib because it needs itself to 
build.
It currently downloads itself with npm in the build process.

I found this piece of wisdom on circular dependencies:
https://wiki.debian.org/DebianBootstrap
"The generic way to deal with all of these is 'profile builds', where a version 
of the package
is built with lesser functionality and thus a smaller dependency tree.
This allows the depending package to then be built, then for the 'stageN' 
package to be built normally."

Pravi did the ITP and all the work (thanks!), but it is more likely we can find 
solution together.

I propose this thread as a starting point.

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-rollup-plugin-babel: build error unrepro but babelHelpers missing error in autopkgtest

[Paolo Greppi]

First the good news: I dont' get the build error on sid today. Maybe that 
problem has solved by itself ;-)

But the autopkgtest fails with the babelHelpers missing error as rollup and 
node-react:

/usr/lib/nodejs/rollup-plugin-babel/dist/rollup-plugin-babel.cjs.js:6544
var isSymbol = USE_NATIVE && babelHelpers.typeof($Symbol.iterator) == 'symbol' 
? function (it) {
 ^
ReferenceError: babelHelpers is not defined
at Object. 
(/usr/lib/nodejs/rollup-plugin-babel/dist/rollup-plugin-babel.cjs.js:6544:30)
at __webpack_require__ 
(/usr/lib/nodejs/rollup-plugin-babel/dist/rollup-plugin-babel.cjs.js:20:30)
at Object. 
(/usr/lib/nodejs/rollup-plugin-babel/dist/rollup-plugin-babel.cjs.js:18563:1)
at __webpack_require__ 
(/usr/lib/nodejs/rollup-plugin-babel/dist/rollup-plugin-babel.cjs.js:20:30)
at Object. 
(/usr/lib/nodejs/rollup-plugin-babel/dist/rollup-plugin-babel.cjs.js:6470:31)
at __webpack_require__ 
(/usr/lib/nodejs/rollup-plugin-babel/dist/rollup-plugin-babel.cjs.js:20:30)
at Object. 
(/usr/lib/nodejs/rollup-plugin-babel/dist/rollup-plugin-babel.cjs.js:1418:15)
at __webpack_require__ 
(/usr/lib/nodejs/rollup-plugin-babel/dist/rollup-plugin-babel.cjs.js:20:30)
at Object. 
(/usr/lib/nodejs/rollup-plugin-babel/dist/rollup-plugin-babel.cjs.js:2983:16)
at __webpack_require__ 
(/usr/lib/nodejs/rollup-plugin-babel/dist/rollup-plugin-babel.cjs.js:20:30)

It seems the rollup-plugin-babel cjs build with webpack has something wrong.
It is much larger than the one built by upstream with rollup:

npm install rollup-plugin-babel
ls -l node_modules/rollup-plugin-babel/dist/* 
/usr/lib/nodejs/rollup-plugin-babel/dist/*
ls -l node_modules/rollup-plugin-babel/dist/* 
/usr/lib/nodejs/rollup-plugin-babel/dist/*
-rw-r--r-- 1 root root5533 Dec 18 12:22 
node_modules/rollup-plugin-babel/dist/rollup-plugin-babel.cjs.js
-rw-r--r-- 1 root root5486 Dec 18 12:22 
node_modules/rollup-plugin-babel/dist/rollup-plugin-babel.es.js
-rw-r--r-- 1 root root 1526968 Jan  5 14:35 
/usr/lib/nodejs/rollup-plugin-babel/dist/rollup-plugin-babel.cjs.js

I noticed that these messages come up during the node-rollup-plugin-babel build 
with webpack (sorted and compacted):

WARNING in 
/usr/lib/nodejs/babel-core/lib/transformation/file/options/option-manager.js
190:19-37 Critical dependency: the request of a dependency is an expression
307:16-34 Critical dependency: the request of a dependency is an expression
WARNING in /usr/lib/nodejs/babel-core/lib/transformation/file/index.js
511:24-39 Critical dependency: the request of a dependency is an expression
WARNING in /usr/lib/nodejs/base/utils.js
3:34-41 Critical dependency: require function is used in a way in which 
dependencies cannot be statically extracted

It looks like this is by design in webpack:
https://github.com/webpack/webpack-dev-server/issues/212

SO apparently this can not be built with webpack after all ...

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] need help fixing test failure of node-svgo

[Paolo Greppi]

Il 16/01/2018 07:24, Pirate Praveen ha scritto:
> Control: tag -1 help
> 
> code is pushed to https://salsa.debian.org/js-team/node-svgo
> 
> some dependencies are still in NEW which I have added to
> https://people.debian.org/~praveen/babel/
> 
> 287 passing (1s)
>   15 failing

I am not sure if I have time to look at this today, but I'd like to mention that
for JS errors like these sometimes it's very useful to use the Chromium 
debugger.

See:
https://nodejs.org/en/docs/inspector/

Procedure tested on sid target and buster client:

1. start your nodejs app on the target with --inspect-brk, for example:
nodejs --inspect-brk /usr/lib/nodejs/mocha/bin/mocha -u tdd

it will print something like:
Debugger listening on ws://127.0.0.1:9229/c0da40fe-d906-4cfa-9bba-a38db47a37b8

then stop at the first JS line

2. open Chromium on the client and go to chrome://inspect
   click on "Open dedicated DevTools for Node" 
   and add the hostname:9229 to the list

It should connect automagically even if the client can be on a different 
machine,
unless you have picky firewalls inbetween ...

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-node-uuid

[Paolo Greppi]

Il 09/01/2018 13:33, Jérémy Lal ha scritto:
> 2018-01-09 12:53 GMT+01:00 Paolo Greppi <paolo.gre...@libpf.com 
> <mailto:paolo.gre...@libpf.com>>:
> 
> Hi, the package node-node-uuid seems broken, this fails:
> nodejs -e "require('uuid');"
> 
> Also it triggers lintian error node-package-install-in-nodejs-rootdir 
> because it installs /usr/lib/nodejs/node-uuid.js.
> 
> Next 1.4.0 is quite old and v. 3.1.0. is required for node-yarnpkg.
> 
> Finally I have some doubts on the the naming, according to policy:
> https://wiki.debian.org/Javascript/Policy 
> <https://wiki.debian.org/Javascript/Policy>
> the source should be named uuid.js, and the binaries libjs-uuid and 
> node-uuid
> 
> I would like to move its repo to salsa.d.o. and proceed to update.
> 
> Any objections / anybody else wants to do it ?
> What are your thoughts on the naming ?
> 
> Be aware that
> npm show node-uuid
> npm show uuid
> 
> both exists. Hence node-node-uuid...
> 
> Jérémy

Tanks for the lookup Jérémy !

From here:
https://www.npmjs.com/package/node-uuid
it says "node-uuid DEPRECATED: Use the uuid package instead."

It appears node-uuid was a fork, then it got merged back.
There are two github projects both confusingly called "node-uuid":
- current: https://github.com/kelektiv/node-uuid is at 3.1.0
- deprecated: https://github.com/brrofs/node-uuid is at 3.0.0

The debian node-uuid source package upstream is the "deprecated" fork.
That's why the tracker says "a new upstream version is available: 3.0.0" and 
not 3.1.0

In the light of these facts I am even more convinced that it should be renamed.
Additionally its upstream should be set to https://github.com/kelektiv/node-uuid

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-node-uuid

[Paolo Greppi]

Hi, the package node-node-uuid seems broken, this fails:
nodejs -e "require('uuid');"

Also it triggers lintian error node-package-install-in-nodejs-rootdir because 
it installs /usr/lib/nodejs/node-uuid.js.

Next 1.4.0 is quite old and v. 3.1.0. is required for node-yarnpkg.

Finally I have some doubts on the the naming, according to policy:
https://wiki.debian.org/Javascript/Policy
the source should be named uuid.js, and the binaries libjs-uuid and node-uuid

I would like to move its repo to salsa.d.o. and proceed to update.

Any objections / anybody else wants to do it ?
What are your thoughts on the naming ?

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-ms 2.1.1

[Paolo Greppi]

Hi, I have prepared the update to node-ms 2.1.1

Please someone allow me DM upload access for this package or sponsor the upload:
https://anonscm.debian.org/cgit/pkg-javascript/node-ms.git

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-inquirer 3.3.0-2

[Paolo Greppi]

Hi, I have prepared an update to node-inquirer.

It fixes the issue:
Error: Cannot find module 'rx-lite-aggregates'
that happens for example on debci:
https://ci.debian.net/packages/n/node-inquirer/unstable/amd64/

Please someone allow me DM upload access for this package or sponsor the upload:
https://anonscm.debian.org/cgit/pkg-javascript/node-inquirer.git

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-inquirer autopkgtests failing

[Paolo Greppi]

Il 08/01/2018 16:46, Paolo Greppi ha scritto:
> Hi, I have prepared an update to node-inquirer:
> https://anonscm.debian.org/cgit/pkg-javascript/node-inquirer.git
> 
> It just fixes the issue:
> Error: Cannot find module 'rx-lite-aggregates'
> 
> I get that when node-inquirer is called from node-yarnpkg.
> The same error is seen on debci as well:
> https://ci.debian.net/packages/n/node-inquirer/unstable/amd64/
> 
> But the autopkgtest is run on the source dir as-is, without applying
> the patches, so the fix will not work there.
> 
> Any ideas ?
> 
> Paolo

Sorry I must have mixed up things. The tests pass. I'll post a 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] RFS: vue.js

[Paolo Greppi]

Il 08/01/2018 11:17, Pirate Praveen ha scritto:
> On തിങ്കള്‍ 08 ജനുവരി 2018 03:36 വൈകു, Paolo Greppi wrote:
>> AFAICT upstream does not provide anything that can run in node: all files in 
>> dist run in the browser
>> https://github.com/vuejs/vue/tree/dev/dist
>> i.e. there is nothing you can run node -e "require('vue');" against
>>
>> Perhaps what you want is the "ES Module" build, which is "intended for use 
>> with modern bundlers like webpack 2 or rollup"
>>
>> The vue.esm.js file could be installed by the libjs-vue binary.
>> It's probably possible to build it with webpack too.
>> Is that acceptable ?
> 
> app/assets/javascripts/sidebar/event_hub.js (and other files) has
> 
> import Vue from 'vue';
> 
> package.json has,
> 
>   "main": "dist/vue.runtime.common.js",
>   "module": "dist/vue.runtime.esm.js",
>   "unpkg": "dist/vue.js",
>   "jsdelivr": "dist/vue.js",
> 
> If you provide the either main or module, I think that would be enough.
> Installing it in /usr/lib/nodejs makes things easier. It can just
> symlink to /usr/share/javascript/vue
> 
> See
> https://anonscm.debian.org/cgit/pkg-javascript/three.js.git/tree/debian/node-three.links

OK I'll find a way to build the ES Module (vue.runtime.esm.js) with webpack, 
then add a node-vue binary with vue.links as in:

/usr/share/javascript/vue/vue.runtime.esm.js 
usr/lib/nodejs/vue/vue.runtime.esm.js

It should also be possible to add the autopkgtest require to node-vue ...

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-inquirer autopkgtests failing

[Paolo Greppi]

Hi, I have prepared an update to node-inquirer:
https://anonscm.debian.org/cgit/pkg-javascript/node-inquirer.git

It just fixes the issue:
Error: Cannot find module 'rx-lite-aggregates'

I get that when node-inquirer is called from node-yarnpkg.
The same error is seen on debci as well:
https://ci.debian.net/packages/n/node-inquirer/unstable/amd64/

But the autopkgtest is run on the source dir as-is, without applying
the patches, so the fix will not work there.

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

Re: [Pkg-javascript-devel] RFS: vue.js

[Paolo Greppi]

Il 08/01/2018 10:53, Pirate Praveen ha scritto:
> On തിങ്കള്‍ 08 ജനുവരി 2018 02:40 വൈകു, Paolo Greppi wrote:
>> Hi, I have packaged the vue.js library:
>> https://anonscm.debian.org/git/pkg-javascript/vue.js.git
>>
>> It currently only provides the full UMD browser build, and it's built with 
>> webpack instead of rollup (that means the file is 468k rather than 279k)
>> Hopefully the package will get better with time as we get more tools in 
>> debian.
>>
>> Please someone sponsor the upload.
> 
> 
> Please provide node-vue binary as well. gitlab runs webpack for its node
> dependencies and vue is needed for gitlab.
> 
>> Paolo

AFAICT upstream does not provide anything that can run in node: all files in 
dist run in the browser
https://github.com/vuejs/vue/tree/dev/dist
i.e. there is nothing you can run node -e "require('vue');" against

Perhaps what you want is the "ES Module" build, which is "intended for use with 
modern bundlers like webpack 2 or rollup"

The vue.esm.js file could be installed by the libjs-vue binary.
It's probably possible to build it with webpack too.
Is that acceptable ?

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: vue.js

[Paolo Greppi]

Hi, I have packaged the vue.js library:
https://anonscm.debian.org/git/pkg-javascript/vue.js.git

It currently only provides the full UMD browser build, and it's built with 
webpack instead of rollup (that means the file is 468k rather than 279k)
Hopefully the package will get better with time as we get more tools in debian.

Please someone sponsor 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] rollup status: trying to build with webpack

[Paolo Greppi]

Il 07/01/2018 15:59, Pirate Praveen ha scritto:
> ...
> ERROR in ./bin/src/help.md
> Module parse failed:
> /home/pravi/forge/debian/git/pkg-javascript/node-rollup/bin/src/help.md
> Unexpected token (1:7)
> You may need an appropriate loader to handle this file type.
> | rollup version __VERSION__
> | =
> |
>  @ ./bin/src/index.js 2:0-29

it looks like you need a loader for md files (markdown)

this one comes up:
https://github.com/peerigon/markdown-loader

or just skip files of type markdown altogether:
https://github.com/cherrry/ignore-loader

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#878674: reproducible with node executable from nodejs.org

[Paolo Greppi]

It segfaults when building vue.js on sid amd64, using node executable 
downloaded from nodejs.org:

wget https://nodejs.org/dist/latest-v6.x/node-v6.12.2-linux-x64.tar.xz
xz -d node-v6.12.2-linux-x64.tar.xz
tar xf node-v6.12.2-linux-x64.tar
cd vue.js
NODE_PATH=/usr/lib/nodejs/ ../node-v6.12.2-linux-x64/bin/node 
/usr/lib/nodejs/webpack/bin/webpack.js --config debian/webpack.config.js 
Segmentation fault

Node 6.x is in LTS until end of March 2018:
https://github.com/nodejs/Release
so it should be possible to forward upstream ?

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#878674: also segfaults when building vue.js

[Paolo Greppi]

I think I reproduced this one when building vue.js on sid amd64, using node 
built in the most basic config from unchanged upstream sources:

git clone https://github.com/nodejs/node.git
cd node
git checkout v6.12.0
./configure --without-npm --prefix=/usr --openssl-use-def-ca-store && make -j8 
-C out BUILDTYPE=Debug
cd ..
git clone https://anonscm.debian.org/cgit/pkg-javascript/vue.js.git
cd vue.js
NODE_PATH=/usr/lib/nodejs/ ../node/out/Debug/node 
/usr/lib/nodejs/webpack/bin/webpack.js --config debian/webpack.config.js 
Segmentation fault

If run within gdb I get a corrip stack and no useful backtrace:

NODE_PATH=/usr/lib/nodejs/ gdb ../node/out/Debug/node
r /usr/lib/nodejs/webpack/bin/webpack.js --config debian/webpack.config.js 
(gdb) where
#0  0x15304aa3e2a8 in ?? ()
#1  0x40886800 in ?? ()
#2  0x406d8000 in ?? ()
#3  0x023b145957053b00 in ?? ()
#4  0x1209e8119e29 in ?? ()
#5  0x1209e811a2a1 in ?? ()
#6  0x0d3faf59edd1 in ?? ()
#7  0x1209e81359c9 in ?? ()
#8  0x7fff9178 in ?? ()
#9  0x15304aa06d91 in ?? ()
#10 0x002e in ?? ()
#11 0x334f3e65eb19 in ?? ()
#12 0x9140 in ?? ()
#13 0x57884360 in ?? ()
#14 0x7fff9130 in ?? ()
#15 0x566f7163 in v8::internal::(anonymous 
namespace)::ElementsAccessorBase >::GetImpl 
(holder=..., entry=3391)
at ../deps/v8/src/elements.cc:566
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Hope this helps,

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] Bug#868318: Please package latest upstream

[Paolo Greppi]

Il 12/12/2017 09:50, Pirate Praveen ha scritto:
> On Fri, 14 Jul 2017 15:28:40 +0200 Julien Puydt
>  wrote:> I can't help but notice that Debian
> has 1.20.1 while upstream is now up
>> to 3.4.2.
>>
>> Could we get a less ancient version?
>>
>> Since the package is in the Debian JavaScript Maintainers repository, I
>> might lend a help if you want to.
> 
> I tried to update it to 4.0.1 and getting this error (using webpack
> instead of browserify). Wondering why webpack is not able to find 'fs'.
> Should we add any extra path to resolve modules included with nodejs?

Does adding to the webpack config:

resolveLoader: {
modules: ['/usr/lib/nodejs'],
  },

as in here:

https://anonscm.debian.org/git/pkg-javascript/vue.js.git/tree/debian/webpack.config.js#n11

help ?

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-wrap-ansi 3.0.1

[Paolo Greppi]

Hi, I have prepared the update to node-wrap-ansi 3.0.1

With this update, I could enable the tests.
To work around the issue with the test environment mentioned here:
https://lists.alioth.debian.org/pipermail/pkg-javascript-devel/2016-November/015662.html
I had to employ the "trick" used in node-chalk tests:
https://github.com/chalk/chalk/blob/master/test/enabled.js#L4

With this "trick" in place, all tests pass except the last one
("supports unicode surrogate pairs")
Pending closer investigation on that, I just disabled it.

It has node-cliui as reverse dependency, which builds fine apart for a known 
problem (https://bugs.debian.org/880904).

Please someone allow me DM upload access for this package or sponsor the upload:
https://anonscm.debian.org/cgit/pkg-javascript/node-wrap-ansi.git

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#883553: tentative conversion to webpack/babel build

[Paolo Greppi]

cat .babelrc
{
  "presets": [
"es2015",
  ],
  "plugins": [
"babel-plugin-add-module-exports"
  ],
  "ignore": [
"dist/*.js"
  ]
}

cat webpack.config.js
'use strict';
var path = require('path');
var config = {
  target: 'web',
  entry: 'lib/es6-promise.js',
  resolve: {
modules: ['/usr/lib/nodejs', '.'],
  },
  resolveLoader: {
modules: ['/usr/lib/nodejs'],
  },
  output: {
path: path.resolve(__dirname, 'dist'),
filename: 'es6-promise.js',
libraryTarget: 'umd'
  },
  module: { rules: [ { use: [ 'babel-loader' ] } ] }
}
module.exports = config;

build with:
webpack --config webpack.config.js
uglifyjs dist/es6-promise.js > dist/es6-promise.min.js

the build succeeds and the resulting binary seems to work; I tested in the 
browser with this:

  
  
  window.Promise = null;
  
  
var promise = new Promise(function(resolve, reject) {
  var person = prompt("Please enter your name", "Harry Potter");
  if (person != null) {
resolve("Stuff worked!");
  }
  else {
reject("It broke");
  }
});
promise.then(function(result) {
  console.log(result);
}, function(err) {
  console.log(err);
});
  
  


this seems to do what upstream's es6-promise-auto does: "Automatically 
provides/replaces Promise if missing or broken"

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-locate-path

[Paolo Greppi]

Hi, I have packaged node-locate-path:
https://anonscm.debian.org/git/pkg-javascript/node-locate-path.git

This is required to update node-find-up to 2.1.0, which is required to update
node-yargs to 10.0.3, which is required for libnpx, which is needed to update
npm to 5.x (!).

Please someone sponsor 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

[Pkg-javascript-devel] Bug#881339: maybe this one is solved but let's keep finding solutions together

[Paolo Greppi]

First the actual issue of this bug may be solved because we have found 
a technical solution by cheating a little bit on dependencies:
https://lists.alioth.debian.org/pipermail/pkg-javascript-devel/2017-December/022806.html
https://anonscm.debian.org/cgit/pkg-javascript/node-babel-preset-env.git/tree/debian/patches/00-babelrc.patch

Second ATM in debian node-babel-preset-env is separate from node-babel,
but upstream moved it back into the main babel repo:
https://github.com/babel/babel-preset-env/
"Now that babel-preset-env has stabilized, it has been moved into the main Babel
mono-repo."
So in the near future node-babel-preset-env may well be one of the binaries
generated from node-babel source. And when that happens, babel will depend on
itself because:
https://github.com/babel/babel/blob/master/package.json#L15

Third considering the ephemeral nature of the boundaries between one package and
another, I propose that we consider circular references in general, be them 
within
a package or across packages.

Fourth to Don, many thanks for trying to find a clean technical solution, but 
that
won't work in this case because the babel makefile bootstrap target does:

yarn
./node_modules/.bin/lerna bootstrap
make build
cd packages/babel-runtime; node scripts/build-dist.js

and yarn and lerna are both WIP:
- yarn: https://bugs.debian.org/843021
- lerna: https://bugs.debian.org/849258

and both depend on babel:
https://wiki.debian.org/Javascript/Nodejs/Tasks/yarn
https://wiki.debian.org/Javascript/Nodejs/Tasks/lerna

so it's still a circular reference !

Now back to the issue, while it is certainly possible to bootstrap gcc,
babel, rollup or any self-compiling compiler, how much skills and time it
requires to achieve it once AND to keep it working when upstream moves on
varies a lot.

The bootstrap process of gcc for example is stable and supported by
upstream. Once you have that, there is still a lot of work to set it up in
debian, but if it works it is likely to keep working in the future.
With certain javascript packages on the other hand, given that upstream is
not in the business of systems programming and does not care about a clean,
"orthodox" bootstrap, it can be harder to get once and even harder to keep
working when upstream changes tooling, language versions ...

The javascript team has very limited resources when confronted with the
enthusiasms of upstream. The whole point of making debian or derivatives
usable by javascript folk is the hope that with more debian users among them
some may volunteer and channel some of their enthusiasm in integrating
javascript tools and products within debian !

In conclusion I think it would be nice to be able to close this bug keeping
in mind that we need to be a bit flexible with all this node-* stuff !

-- 
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] trying to build libjs-vue

[Paolo Greppi]

Il 01/12/2017 06:55, Pirate Praveen ha scritto:
> On വെള്ളി 01 ഡിസംബര്‍ 2017 12:05 രാവിലെ, Paolo Greppi wrote:
>> According to this:
>> https://medium.com/webpack/webpack-and-rollup-the-same-but-different-a41ad427058c
>> we really should use rollup over webpack.
> 
> But we don't have rollup in main, we have been working on it for quite
> some time and it is going to take quite some more time before we can use
> it in main. webpack is almost there (packaging complete), except for the
> conflict with ftp masters on node-babel-preset-env.
> 
> See node-d3-zoom or node-d3-scale for example webpack configuration.

Good tip Praveen: webpack succeded in compiling vue.js !

I install node-babel-preset-env from local build, then:
apt install webpack node-babel-loader node-babel-plugin-add-module-exports

cat .babelrc 
{
  "presets": [
"es2015",
"flow-vue"],
  "plugins": [
"syntax-dynamic-import",
"babel-plugin-add-module-exports",
  ],
  "ignore": [
"dist/*.js",
"packages/**/*.js"
  ]
}
cat webpack.config.js
'use strict';
var fs = require('fs');
var path = require('path');
var webpack = require('webpack');
var config = {
  target: 'web',
  entry: './src/platforms/web/entry-runtime-with-compiler.js',
  resolve: {
modules: ['/usr/lib/nodejs', './src', './src/platforms'],
  },
  resolveLoader: {
modules: ['/usr/lib/nodejs'],
  },
  output: {
path: path.resolve(__dirname, 'dist'),
filename: 'vue.js',
library: "Vue",
libraryTarget: 'umd',
umdNamedDefine: true
  },
  module: { rules: [ { use: [ 'babel-loader' ] } ] }
}
module.exports = config;
webpack --config webpack.config.js

I get frequent segmentation faults, probably the same as 
https://bugs.debian.org/878674
BTW, I can get rid of those with:
npm install webpack
(I then keep using the binary installed by the package, but the locally 
installed node
modules somehow cure the problem; I should probably report that to #878674 ...)

Anyway when ends I get a much larger "binary":
-rw-r--r-- 1 root root 468242 Dec  1 12:35 vue.js
and when I test that in a test application it works !

This is twice the size of the "binary" produced by upstream with rollup, but I 
still have
to experiment with dead code removal 
(https://webpack.js.org/guides/tree-shaking/#minify-the-output).

In any case we have to wait for node-babel-preset-env before I proceed with the 
RFS of this one.

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#881339: let's find a solution

[Paolo Greppi]

babel-preset-env is an essential component of babel:
https://babeljs.io/docs/plugins/preset-env

babel is a sort of "compiler" that translates from bleeding-edge javascript
to older, more widespread standard versions (such as the javascript that
runs in a browser).
It's a very successful project at the moment, see for example:
https://tomdale.net/2017/09/compilers-are-the-new-frameworks/
It is written in javascript itself so it makes sense that it must
be bootstrapped like gcc.

For sure the javascript ecosystem culture is different from debian's, and
that ecosystem is just starting to stabilize. Bur there is already a lot
of valuable open-source stuff in there.

Such as a number of server-oriented tools that it would be nice to have in
debian:
- etherpad-lite (ITP: https://bugs.debian.org/576998)
- gitlab
- gitea
- buildbot 0.9.x (if we want to keep the web client)
- ...
- 

Also if only debian were kind enough with front-end developers to provide
the tools they need, there is potential to attract quite a few new debian
(and derivatives) desktop users.

What matters most now is to get the tooling required to package stuff.

So please let's find a way to get babel-preset-env in.

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] trying to build libjs-vue

[Paolo Greppi]

Il 30/11/2017 04:59, Pirate Praveen ha scritto:
> On 2017, നവംബർ 29 3:39:51 PM IST, Paolo Greppi <paolo.gre...@libpf.com> wrote:
>> Hi all, I an trying to build from vue.js sources, see:
>> ITP: https://bugs.debian.org/871459
>> repo: https://anonscm.debian.org/git/pkg-javascript/vue.js.git
>>
>> More precisely what is wanted is the browser (UMD) build, see:
>> https://vuejs.org/v2/guide/installation.html#Explanation-of-Different-Builds
>>
>> To rebuild dist from source, upstream uses rollup (which is currently
>> stuck in contrib) plus a few rollup plugins we lack:
>> - rollup-plugin-buble
>> - rollup-plugin-alias
>> - rollup-plugin-node-resolve
>>
>> Therefore I attempted a hacky build avoiding rollup completely, and
>> using a combination of babeljs + browserify-lite.
>>
>> First I patched .babelrc as follows (apparently jsx can be used by vue
>> apps, but is not required for building vue itself):
>> -  "plugins": ["transform-vue-jsx", "syntax-dynamic-import"],
>> +  "plugins": ["syntax-dynamic-import"],
>>
>> then:
>> apt install node-browserify-lite node-babel-cli
>> node-babel-preset-es2015 node-babel-plugin-syntax-dynamic-import
>> node-babel-preset-flow-vue
>> babeljs src -d dist1
>> NODE_PATH=dist1 browserify-lite --standalone Vue ./dist1/core/index.js
>> --outfile dist/vue.js
>> uglifyjs -o dist/vue.min.js --source-map=dist/vue.min.js.map
>> dist/vue.js
>>
>> The resulting binaries are smaller/different than upstream
>> (https://github.com/vuejs/vue/tree/d4e0c3ef2444384719638a89f2a25af042b95795/dist):
>>
>> ls -l dist
>> ...
>> -rw-r--r-- 1 root root 165464 Nov 29 10:19 vue.js
>> -rw-r--r-- 1 root root 111528 Nov 29 10:19 vue.min.js
>> -rw-r--r-- 1 root root 106896 Nov 29 10:19 vue.min.js.map
>>
>> ls -l ../vue.js-2.5.9/dist
>> ...
>> -rw-r--r-- 1 paolog paolog 286869 nov 27 22:54 vue.common.js
>> -rw-r--r-- 1 paolog paolog 278610 nov 27 22:54 vue.esm.browser.js
>> -rw-r--r-- 1 paolog paolog 286852 nov 27 22:54 vue.esm.js
>> -rw-r--r-- 1 paolog paolog 284067 nov 27 22:54 vue.js
>> -rw-r--r-- 1 paolog paolog  86676 nov 27 22:54 vue.min.js
>> -rw-r--r-- 1 paolog paolog 208010 nov 27 22:54 vue.runtime.common.js
>> -rw-r--r-- 1 paolog paolog 207993 nov 27 22:54 vue.runtime.esm.js
>> -rw-r--r-- 1 paolog paolog 205957 nov 27 22:54 vue.runtime.js
>> -rw-r--r-- 1 paolog paolog  61382 nov 27 22:54 vue.runtime.min.js
>>
>> Testing them in a real-world application which works fine with upstream
>> dist files gives errors in the browser console:
>>
>> vue.js:1450 Uncaught ReferenceError: process is not defined
>>at Object.10.shared/util (vue.js:1450)
>>at req (vue.js:6)
>>at modRequire (vue.js:11)
>>at Object.4.../config (vue.js:273)
>>at req (vue.js:6)
>>at modRequire (vue.js:11)
>>at Object.1../init (vue.js:54)
>>at req (vue.js:6)
>>at modRequire (vue.js:11)
>>at Object.0../instance/index (vue.js:21)
>>
>> feeds.php:123 Uncaught ReferenceError: Vue is not defined
>>at feeds.php:123
>>
>> ...
>>
>> Has anybody here more clues than I have ?
> 
> Because browserify-lite will not handle nodejs api conversion. You can use 
> webpack (though one of its dependencies is still stuck in NEW and blocked by 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881339 it would be great if 
> more people can add their comments there).
> 
> You can enable contrib to get node-acorn-dynamic-import required for webpack.

According to this:
https://medium.com/webpack/webpack-and-rollup-the-same-but-different-a41ad427058c
we really should use rollup over webpack.

Upstream uses rollup+buble and the build/config.js confuses me.
So I gave rollup+babel a try, starting from scratch, here is my journey.

I picked:
- node-he, node-rollup-plugin-commonjs and node-babel-plugin-external-helpers 
from main, 
- node-rollup-plugin-node-resolve from the NEW queue

Installed from npm:
- rollup-plugin-babel (could be worth an ITP)
- babel-preset-es2015-rollup
the latter will not be necessary anymore with Babel>6.13, see 
https://github.com/rollup/rollup-plugin-babel#configuring-babel

.babelrc:
{ "presets": ["es2015-rollup", "flow-vue"] }

rollup.config.js:
import resolve from 'rollup-plugin-node-resolve';
import babel from 'rollup-plugin-babel';
export default {
  entry: './src/platforms/web/entry-runtime-with-compiler.js',
  moduleName: 'Vue',
  plugins: [resolve(), babel({exclude: 'node_modules/**'})],
  dest: { 'dist/vue.js' }
};

then:
rollup -

Re: [Pkg-javascript-devel] nodejs 6.12.0 build failures on mips and mipsel

[Paolo Greppi]

Il 30/11/2017 10:59, Jérémy Lal ha scritto:
> ...
> Jérémy would you only remove the --shared-zlib ?
> Since I have no access to any MIPS hardware, I am trying that on amd64, 
> on top of branch master-6.x, at least we'll see if it also breaks the build 
> there.
> 
> Anyway is only that blocking nodejs 6 out of testing ?
> Because if that's so, probably it could be OK to just skip the test and 
> postpone the investigation ... just add a TODO in the patch ?
> 
> No there's also a segfault #878674 which is not blocking right now,
> but might become again severe.
> Also #859297 the openssl 1.1 "migration" (a bad name since it requires
> heavy changes to nodejs core). On that front, hopefully nodejs 8 will fix it.
> So the goal is more or less upload nodejs 8 asap instead of coping with a
> sinking ship.
> 
> Jérémy
> 

OK so nodejs 6 while in unstable triggered the build failures on mips and 
mipsel and #878674

Testing is used by more people than unstable, so it's likely to trigger more 
trouble if it gets into testing.

On the other hand if testing were to go from nodejs 4 straight to 8 or 9 it 
would trigger yet more & all at once.
IMHO better have it introduced in degrees, so that we address the trouble from 
4 to 6 separately from that from 6 to 8/9.

So just send nodejs 6 into testing and let it rain cats & dogs (hey, it's 
called testing !).
Maybe while 6 is in testing we can move 8/9 to unstable.

In any case I agree that for buster, due to the openssl "migration" nodejs 6 is 
unacceptable.
BTW according to:
https://github.com/nodejs/Release#release-schedule
nodejs 8.x will still support OpenSSL-1.0.2.

In here ("Discussion: OpenSSL 1.1.0 planning"):
https://github.com/nodejs/node/issues/4270
it says "Taking this off the 8.0.0 milestone"
and in here ("Support both OpenSSL 1.1.0 and 1.0.2"):
https://github.com/nodejs/node/pull/16130
it says "The plan would be to land this in ~9.1.0 or thereabouts"

Back to the attempted build using embedded (latest) zlib, in fact deps/zlib is 
missing from master-6.x because it's removed by the repack.
I'll update you as soon as my attempts give some useful result.

Finally, I noticed that the zlib version embedded in nodejs has been 1.2.11 
from at least 4.8 up to current upstream master.
In sid we have zlib1g-dev 1.2.8.dfsg-5 and ubuntu has 1.2.11.dfsg-0ubuntu2.

So I just reported: https://bugs.debian.org/883180

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] nodejs 6.12.0 build failures on mips and mipsel

[Paolo Greppi]

I noticed that nodejs 6.12.0 fails to build on mips and mipsel:

https://buildd.debian.org/status/fetch.php?pkg=nodejs=mips=6.12.0%7Edfsg-2=1511795079=0
https://buildd.debian.org/status/fetch.php?pkg=nodejs=mips=6.12.0%7Edfsg-2=1510704638=0
https://buildd.debian.org/status/fetch.php?pkg=nodejs=mipsel=6.12.0%7Edfsg-2=1510706722=0

searching for "not ok", it turns out that all three tests fail here:
https://anonscm.debian.org/cgit/collab-maint/nodejs.git/tree/test/parallel/test-zlib.js?h=debian/6.12.0_dfsg-1#n153

That test is still present in upstream master branch today:
https://github.com/nodejs/node/blob/master/test/parallel/test-zlib.js#L175

I don't know why it fails, but I also noticed that currently upstream does not 
provide binaries for mips:
https://nodejs.org/dist/v8.9.1/
that perhaps indicates it's not so well tested there ?

Probably we should just skip that test ?

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] trying to build libjs-vue

[Paolo Greppi]

Hi all, I an trying to build from vue.js sources, see:
ITP: https://bugs.debian.org/871459
repo: https://anonscm.debian.org/git/pkg-javascript/vue.js.git

More precisely what is wanted is the browser (UMD) build, see:
https://vuejs.org/v2/guide/installation.html#Explanation-of-Different-Builds

To rebuild dist from source, upstream uses rollup (which is currently stuck in 
contrib) plus a few rollup plugins we lack:
- rollup-plugin-buble
- rollup-plugin-alias
- rollup-plugin-node-resolve

Therefore I attempted a hacky build avoiding rollup completely, and using a 
combination of babeljs + browserify-lite.

First I patched .babelrc as follows (apparently jsx can be used by vue apps, 
but is not required for building vue itself):
-  "plugins": ["transform-vue-jsx", "syntax-dynamic-import"],
+  "plugins": ["syntax-dynamic-import"],

then:
apt install node-browserify-lite node-babel-cli node-babel-preset-es2015 
node-babel-plugin-syntax-dynamic-import node-babel-preset-flow-vue
babeljs src -d dist1
NODE_PATH=dist1 browserify-lite --standalone Vue ./dist1/core/index.js 
--outfile dist/vue.js
uglifyjs -o dist/vue.min.js --source-map=dist/vue.min.js.map dist/vue.js

The resulting binaries are smaller/different than upstream 
(https://github.com/vuejs/vue/tree/d4e0c3ef2444384719638a89f2a25af042b95795/dist):

ls -l dist
...
-rw-r--r-- 1 root root 165464 Nov 29 10:19 vue.js
-rw-r--r-- 1 root root 111528 Nov 29 10:19 vue.min.js
-rw-r--r-- 1 root root 106896 Nov 29 10:19 vue.min.js.map

ls -l ../vue.js-2.5.9/dist
...
-rw-r--r-- 1 paolog paolog 286869 nov 27 22:54 vue.common.js
-rw-r--r-- 1 paolog paolog 278610 nov 27 22:54 vue.esm.browser.js
-rw-r--r-- 1 paolog paolog 286852 nov 27 22:54 vue.esm.js
-rw-r--r-- 1 paolog paolog 284067 nov 27 22:54 vue.js
-rw-r--r-- 1 paolog paolog  86676 nov 27 22:54 vue.min.js
-rw-r--r-- 1 paolog paolog 208010 nov 27 22:54 vue.runtime.common.js
-rw-r--r-- 1 paolog paolog 207993 nov 27 22:54 vue.runtime.esm.js
-rw-r--r-- 1 paolog paolog 205957 nov 27 22:54 vue.runtime.js
-rw-r--r-- 1 paolog paolog  61382 nov 27 22:54 vue.runtime.min.js

Testing them in a real-world application which works fine with upstream dist 
files gives errors in the browser console:

vue.js:1450 Uncaught ReferenceError: process is not defined
at Object.10.shared/util (vue.js:1450)
at req (vue.js:6)
at modRequire (vue.js:11)
at Object.4.../config (vue.js:273)
at req (vue.js:6)
at modRequire (vue.js:11)
at Object.1../init (vue.js:54)
at req (vue.js:6)
at modRequire (vue.js:11)
at Object.0../instance/index (vue.js:21)

feeds.php:123 Uncaught ReferenceError: Vue is not defined
at feeds.php:123

...

Has anybody here more clues than I have ?

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-ms in NEW

[Paolo Greppi]

Hi Ftpmasters,

there is a node-ms package in the NEW queue since some time.

It now blocks the update of node-debug to 3.1.0, see:
https://lists.alioth.debian.org/pipermail/pkg-javascript-devel/2017-November/022713.html

While all that is not urgent per se, the node-debug update in turn blocks other 
updates (such as node-snapdragon).

So please have a look at node-ms in NEW and let us know if it's fine

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-debug 3.1.0

[Paolo Greppi]

Hi, I have prepared the update to node-debug version 3.1.0

Note that this now depends on node-ms, whose upload was sponsored 3 weeks ago:
https://lists.alioth.debian.org/pipermail/pkg-javascript-devel/2017-November/022208.html
(but is still in the NEW queue)

It also produces a libjs-debug binary, see my message of Nov 3rd:
https://lists.alioth.debian.org/pipermail/pkg-javascript-devel/2017-November/00.html

I could work around the problem of browserify-lite ignoring modules in 
/usr/lib/nodejs
by using the NODE_PATH environment variable as suggested in:
https://bugs.debian.org/858940
(I don't have to resolve modules recursively so that was enough)

Please someone allow me DM upload access for this package or sponsor the upload:
https://anonscm.debian.org/cgit/pkg-javascript/node-debug.git

Paolo

P.S. as a side-effect to this update, as mentioned in the ITP for node-ms:
https://bugs.debian.org/754551
all packages that import humanize from node-debug as ms must be updated to 
depend 
on node-ms instead. On closer inspection they should be only 3, so I have filed
3 bugs:
- node-connect-timeout https://bugs.debian.org/882965
- node-send https://bugs.debian.org/882963
- node-serve-favicon https://bugs.debian.org/882964

-- 
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#882965: node-connect-timeout: should depend on node-ms

[Paolo Greppi]

Package: node-connect-timeout
Version: 1.3.0-1
Severity: important
X-Debbugs-Cc: paolo.gre...@libpf.com

Dear maintainer, this package imports humanize from node-debug as ms.
With node-debug 3.1.0 the embedded copy of the ms module will be stripped.
There is a new node-ms module for that (currently in the NEW queue).
Please update your package to remove the -use_ms_from_debug.patch and
depend on node-ms instead.
Thanks ! Paolo

-- System Information:
Debian Release: 9.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.12.0-0.bpo.1-amd64 (SMP w/2 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages node-connect-timeout depends on:
ii  node-debug   2.5.1-1
ii  node-on-headers  1.0.0-1
ii  nodejs   4.8.2~dfsg-1

node-connect-timeout recommends no packages.

node-connect-timeout suggests no packages.

-- no debconf information

-- 
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#882964: node-serve-favicon: should depend on node-ms

[Paolo Greppi]

Package: node-serve-favicon
Version: 2.1.5-1
Severity: important
X-Debbugs-Cc: paolo.gre...@libpf.com

Dear maintainer, this package imports humanize from node-debug as ms.
With node-debug 3.1.0 the embedded copy of the ms module will be stripped.
There is a new node-ms module for that (currently in the NEW queue).
Please update your package to remove the -use_ms_from_debug.patch and
depend on node-ms instead.
Thanks ! Paolo

-- System Information:
Debian Release: 9.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.12.0-0.bpo.1-amd64 (SMP w/2 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages node-serve-favicon depends on:
ii  node-debug  2.5.1-1
ii  node-etag   1.4.0-1
ii  node-fresh  0.2.0-1
ii  nodejs  4.8.2~dfsg-1

node-serve-favicon recommends no packages.

node-serve-favicon suggests no packages.

-- no debconf information

-- 
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#882963: node-send: should depend on node-ms

[Paolo Greppi]

Package: node-send
Version: 0.9.4-1
Severity: important
X-Debbugs-Cc: paolo.gre...@libpf.com

Dear maintainer, this package imports humanize from node-debug as ms.
With node-debug 3.1.0 the embedded copy of the ms module will be stripped.
There is a new node-ms module for that (currently in the NEW queue).
Please update your package to remove the 0001-use_ms_from_debug.patch and
depend instead on node-ms.
Thanks ! Paolo

-- System Information:
Debian Release: 9.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.12.0-0.bpo.1-amd64 (SMP w/2 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages node-send depends on:
ii  node-debug 2.5.1-1
ii  node-depd  1.0.0-1
ii  node-escape-html   1.0.1-1
ii  node-etag  1.4.0-1
ii  node-fresh 0.2.0-1
ii  node-mime  1.3.4-1
ii  node-on-finished   2.1.0-2
ii  node-range-parser  0.0.4+git7d1cd72a-1
ii  nodejs 4.8.2~dfsg-1

node-send recommends no packages.

node-send suggests no packages.

-- no debconf information

-- 
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-ms

[Paolo Greppi]

Hi, I had almost forgotten this one:
https://anonscm.debian.org/git/pkg-javascript/node-ms.git

It's now refreshed, please someone sponsor the upload.

With the node-debug update to 3.1.0 I am preparing we will finally unbundle ms 
from it.

Paolo

 Messaggio Inoltrato 
Oggetto: Re: [Pkg-javascript-devel] reopening the ITP for node-ms
Data: Wed, 31 May 2017 09:34:49 +0200
Mittente: Paolo Greppi <paolo.gre...@libpf.com>
Rispondi-a: paolo.gre...@libpf.com
A: pkg-javascript-devel@lists.alioth.debian.org

Il 31/05/2017 09:06, Paolo Greppi ha scritto:
> I intend to package this module, for the rationale see 
> https://bugs.debian.org/836205
> 
> A quick search on https://codesearch.debian.net shows the following 
> node/js-related packages that contain the string 'humanize', possibly 
> indicating that they import the ms copy embedded in node-debug:
> 
> libjs-sifter.js
> node-connect-timeout
> node-dot
> node-moment
> node-parse-json
> node-redis
> node-send
> node-serve-favicon
> node-utilities
> rtcninjajs
> 
> after triaging this list, when this one is packaged they should all be 
> updated to depend on it.
> 
> I would need a sponsor to upload, and I intend to maintain it within the 
> javascript maintainers team.
> 
> There is already a repo on alioth:
> https://anonscm.debian.org/git/pkg-javascript/node-ms.git
> 
> Paolo

OK that should be ready (easy, because Leo Iannacone had already done most of 
the work!)

Please someone sponsor 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

[Pkg-javascript-devel] RFS: update node-cli-cursor to 2.1.0

[Paolo Greppi]

Hi, I have prepared the update to node-cli-cursor version 2.1.0 (required for 
inquirer 3.3.0 and for node-yarnpkg).

The only reverse dependency ATM is node-inquirer, and the tests in the current 
version of node-inquirer pass.

Please someone allow me DM upload access for this package or sponsor the upload:
https://anonscm.debian.org/cgit/pkg-javascript/node-cli-cursor.git

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-commander 2.11.0 breaks node-express-generator + not sure about mocha

[Paolo Greppi]

Hi, I have prepared a team upload for node-commander to bring it to version 
2.11 (that one is required for node-yarnpkg):
https://anonscm.debian.org/git/pkg-javascript/node-commander.git

In theory it needs updating node-should 8.4.0 to 11.2.1 and node-sinon from 
1.17.6 to 2.3.5, but these are only used for testing.
So I have relaxed the min version required for them, and all tests pass with 
the versions we have in the archive.

I tested the reverse dependencies and build dependencies with 
pkg-ruby-extras/build, and then I did some manual tests after installing 
node-commander 2.11.0 from the locally built deb.

First the good news.

For node-babel I built it then installed the resulting node-babel-cli and run 
the /usr/lib/nodejs/babel-cli/bin/babel.js command trying some (not all) of the 
options. It seems to work.
BTW it should be fine because in package/babel-cli/package.json v6.26.0:
https://github.com/babel/babel/blob/cee4cde53e4f452d89229986b9368ecdb41e00da/packages/babel-cli/package.json
it requires "commander": "^2.11.0" and not > 2.4.0 as we have in debian/control.

For node-ws I built it and installed the resulting node-ws package, then run 
the wscat command trying some (not all) of the options. Everything worked.

For node-clean-css I tested running "vow" (says "OK » 271 honored") and also 
building, installing the resulting node-clean-css + cleancss packages and 
running the cleancss command trying some (not all) of the options. Everything 
worked.
This package could get a good refresh, including DEP-8 tests and moving the 
repo from collab-maint to alioth (could file a bug ?)

For node-jade: as the current master is unreleased and does not build, I have 
tried debian/1.5.0+dfsg-1; all tests pass (mocha -R spec). I also built and 
installed the resulting node-jade package, and since it does not install the 
jade binary (could file a bug ?) I run it from source with bin/jade.js, trying 
some (not all) of the options. Everything worked.

The bad news:

For node-mocha: as the current master is unreleased and does not build, I have 
tried debian/1.20.1-6, but the build time tests fail (although not the same 
errors as #872613); as such I can not determine what to do with this one.

For node-express-generator: I tested by installing and trying to run the 
express binary, it fails with:
/usr/lib/nodejs/express-generator/bin/express:62
  program.confirm('destination is not empty, continue? ', function(ok){
  ^
TypeError: program.confirm is not a function
In fact the confirm command was removed from node-commander a while ago 
(https://github.com/tj/commander.js/issues/495) so this one needs updating  
(should file a bug ?)

As it stands this update is beyond trivial. What do you suggest ?

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-commander repo

[Paolo Greppi]

Il 31/10/2017 16:11, Jérémy Lal ha scritto:
> 
> 
> 2017-10-31 16:08 GMT+01:00 Jérémy Lal <kapo...@melix.org 
> <mailto:kapo...@melix.org>>:
> 
> 
> 
>     2017-10-31 15:40 GMT+01:00 Paolo Greppi <paolo.gre...@libpf.com 
> <mailto:paolo.gre...@libpf.com>>:
> 
> Hi the node-commander repo on alioth:
> https://anonscm.debian.org/git/pkg-javascript/node-commander.git 
> <https://anonscm.debian.org/git/pkg-javascript/node-commander.git>
> is currently owned by sunweaver:collab-maint, this makes it 
> impossible for non-DD members of pkg-javascript team to push there.
> 
> Please Mike or someone else chgrp -R 
> /git/pkg-javascript/node-commander.git on git.debian.org 
> <http://git.debian.org> to scm_pkg-javascript.
> 
> Thanks
> 
> 
> Doing it.
> 
> 
> Done, please check you can push.
> 
> Jérémy

Thanks ! The push worked, but there were warnings:

remote: Migrating settings from hooks.* to multimailhook.*
remote: Traceback (most recent call last):
remote:   File "/usr/local/bin/git-commit-notice", line 30, in 
remote: environment = git_multimail.GenericEnvironment(config=config)
remote:   File "/srv/git.debian.org/bin/git_multimail.py", line 1960, in 
__init__
remote: super(ProjectdescEnvironmentMixin, self).__init__(**kw)
remote:   File "/srv/git.debian.org/bin/git_multimail.py", line 1854, in 
__init__
remote: **kw
remote:   File "/srv/git.debian.org/bin/git_multimail.py", line 1825, in 
__init__
remote: config=config, **kw
remote:   File "/srv/git.debian.org/bin/git_multimail.py", line 1914, in 
__init__
remote: config, 'refchangelist', 'mailinglist',
remote:   File "/srv/git.debian.org/bin/git_multimail.py", line 1949, in 
_get_recipients
remote: 'The list of recipients for %s is not configured.\n%s' % (names[0], 
hint)
remote: git_multimail.ConfigurationException: The list of recipients for 
refchangelist is not configured.
remote: Please set one of the following:
remote: "multimailhook.refchangelist"
remote: "multimailhook.mailinglist"

I'll RFS 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] RFS: node-bytes 3.0.0

[Paolo Greppi]

Hi, I have prepared a team upload for node-bytes to bring it to version 3 (that 
one is required for node-yarnpkg).

I tested all the reverse dependencies and build dependencies with 
pkg-ruby-extras/build, except node-raw-body which I had to  build manually 
because from pkg-ruby-extras/build it gave "no space left on device".

Please someone sponsor the upload:
https://anonscm.debian.org/cgit/pkg-javascript/node-bytes.git

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-restore-cursor 2.0.0

[Paolo Greppi]

Hi, I have updated node-restore-cursor to 2.0.0:
https://anonscm.debian.org/git/pkg-javascript/node-restore-cursor.git

This is required for updating node-cli-cursor to 2.1 and node-inquirer to 
3.3.0, the latter is necessary for node-yarnpkg.

Please someone allow me DM upload access for this package or sponsor the 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] node-yarnpkg status update

[Paolo Greppi]

I have just updated the repo:
https://anonscm.debian.org/cgit/pkg-javascript/node-yarnpkg.git
with upstream's latest release (1.2.1).

W.r.t. the previous time I looked (version 1.0.2 of 2017-09-13) the 
dependencies have not changed much:
- 2 new dependencies (strip-ansi and puka)
- node-camelcase goes from 3.0.0 to 4.0.0
- node-chalk goes from 1.1.1 to 2.1.0

I also updated the task page 
https://wiki.debian.org/Javascript/Nodejs/Tasks/yarn using the commands:

grep -v eslint-plugin-yarn-internal package.json > package1.json
./js-task-wiki-edit/js_task_edit.py -f package1.json

Let's set aside for the moment the staggering figure of 142 packages to update.

Assuming some dependencies can be skipped:
- jest, flow, flow-bin, commitizen and cz-conventional-changelog: these seem 
tools required for the upstream development workflow
- cmd-shim: should be required only on windows
- leven: node-fast-levenshtein is in debian and it should be easy to patch yarn 
to use that instead (or ask ustream, since fast-levenshtein seems more popular 
than leven)
and not counting the babel / eslint stuff and the indirect dependencies for 
direct dependencies we already have in the archive, it seems we need 15 new 
packages.

Before I file ITPs for these:
- asap
- chownr
- dnscache
- gulp-if
- gulp-watch 
- gunzip-maybe
- is-ci
- is-webpack-bundle
- mock-stdin
- node-emoji
- prettier
- puka
- tar-fs
- v8-compile-cache
- yn
do you have any comments on them ?

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#871459: vue.js

[Paolo Greppi]

Il 30/10/2017 13:20, Pirate Praveen ha scritto:
> On തിങ്കള്‍ 30 ഒക്ടോബര്‍ 2017 04:18 വൈകു, Paolo Greppi wrote:
>> BTW this is only Vue core, there are also some supporting libraries which 
>> may need packaging:
>> vue-router, vuex, vue-cli, vue-loader, vue-server-renderer, 
>> vue-class-component, vue-rx and vue-devtools.
>>
>> Any help or suggestion is welcome !
> 
> I have also been working on vue packages for gitlab
> (https://wiki.debian.org/Javascript/Nodejs/Tasks/gitlab) and some of
> them are already in NEW.
> 
> https://github.com/vuejs/vue-template-es2015-compiler/issues/10 is a
> blocker.
> 
> prettier needs chalk 2, which is in git repo, but even require test is
> failing (needs to fix it). See if you can make some progress on
> node-chalk and node-prettier in alioth.

Regarding node-chalk, if you refer to this:

$ cd node-chalk
$ node
> var test=require('./');
TypeError: Cannot read property 'close' of undefined
at Object. 
(/home/paolog/Sviluppo/debian/node-chalk/index.js:66:74)
..

it seems the ansi-styles API changed, it really must be node-ansi-styles (>= 
3.1.0).

I have put that requirement in debian/control + more cleanup and also turned on 
tests.

You can find those changes in a wip/paolog branch on alioth:

https://anonscm.debian.org/cgit/pkg-javascript/node-chalk.git/log/?h=wip/paolog

feel free to cherry-pick the commit in master if you need it.

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] vue.js

[Paolo Greppi]

As discussed (some time ago..) with Michael, I have taken over the ITP for 
vue.js.

I'll try to package it within the javascript maintainers team.

I have started work on this repo on alioth:
https://anonscm.debian.org/git/pkg-javascript/vue.js.git

It build-depends on a few packages:
https://anonscm.debian.org/git/pkg-javascript/vue.js.git/tree/package.json#n59
so it'll take some time before I can ask someone to sponsor the upload..

BTW this is only Vue core, there are also some supporting libraries which may 
need packaging:
vue-router, vuex, vue-cli, vue-loader, vue-server-renderer, 
vue-class-component, vue-rx and vue-devtools.

Any help or suggestion is welcome !

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#876435: mocha: manpage contains broken link

[Paolo Greppi]

Package: mocha
Version: 1.20.1-7
Severity: minor
X-Debbugs-Cc: paolo.gre...@libpf.com

Dear Maintainer,

when I type man mocha at the end of the manpage it states:

SEE ALSO
   More info about mocha can be found in 
/usr/share/doc/node-mocha/Readme.md.gz

But that link is broken, it should point to:
   /usr/share/doc/mocha/Readme.md.gz

Anyway the contents of that readme file are not so interesting, for example it 
would be nice
to have a list of reporters...

A more interesting piece of documentation is available from the repo for the 
mochajs website:
https://github.com/mochajs/mochajs.github.io/blob/master/index.md

-- System Information:
Debian Release: 9.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mocha depends on:
ii  libjs-mocha 1.20.1-7
ii  node-commander  2.4.0-1
ii  node-debug  2.5.1-1
ii  node-diff   1.4.0~dfsg-1
ii  node-glob   7.1.1-1
ii  node-growl  1.7.0-1
ii  node-jade   1.5.0+dfsg-1
ii  node-mkdirp 0.5.0-1
ii  nodejs  4.8.2~dfsg-1

mocha recommends no packages.

Versions of packages mocha suggests:
pn  node-jscoverage  

-- no debconf information

-- 
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-commander 2.9.0

[Paolo Greppi]

Hi

I have prepared a team upload to update node-commander from 2.4 to 2.9.
Version 2.9 is required for node-yarnpkg, see: 
https://wiki.debian.org/Javascript/Nodejs/Tasks/yarn

See: https://gitlab.com/simevo/node-commander.git
I could not push to 
https://anonscm.debian.org/git/pkg-javascript/node-commander.git because the 
dir belongs to collab-maint and I have no write access to that.

It has reverse dependencies:
- node-clean-css
- node-express-generator
- node-jade
- node-mocha
- node-ws (only this I could autopkgtest)
And it has reverse build dependencies:
- node-mocha
- node-ws 

Build of mocha fails due to #872613 which is unrelated.

I propose uploading to experimental and notifying the maintainers of these 
packages so that they can perform the manual tests.

For that purpose I have prepared a debian-experimental branch.

Please some DD sponsor this 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] RFP: node-ansi-regex and node-strip-ansi

[Paolo Greppi]

Il 19/09/2017 14:44, Paolo Greppi ha scritto:
> Hi
> 
> I have prepared team uploads for these two packages, see:
> https://anonscm.debian.org/git/pkg-javascript/node-ansi-regex.git
> https://anonscm.debian.org/git/pkg-javascript/node-strip-ansi.git
> 
> They are required to update node-string-width to 2.1.1 and node-wrap-ansi to 
> 3.0.1.
> 
> Please some DD sponsor these uploads
> 
> Thanks,
> 
> Paolo

Ooops the title should be: RFS


-- 
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] RFP: node-ansi-regex and node-strip-ansi

[Paolo Greppi]

Hi

I have prepared team uploads for these two packages, see:
https://anonscm.debian.org/git/pkg-javascript/node-ansi-regex.git
https://anonscm.debian.org/git/pkg-javascript/node-strip-ansi.git

They are required to update node-string-width to 2.1.1 and node-wrap-ansi to 
3.0.1.

Please some DD sponsor these uploads

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-ansi-regex_3.0.0-1_amd64.changes REJECTED

[Paolo Greppi]

Hi I'd like to update node-string-width and node-wrap-ansi which I maintain.

In the process of doing that I noticed that node-ansi-regex and node-strip-ansi 
are also lagging behind.

I have updated them as well.

So I happily added myself to the uploaders and tried uploading the first one to 
experimental.

This was rejected. Should this be a sponsored upload ? Or a NMU ?

Paolo

Il 19/09/2017 11:51, Debian FTP Masters ha scritto:
> 
> ACL dm: not allowed to upload source package 'node-ansi-regex'
> 
> ===
> 
> Please feel free to respond to this email if you don't understand why
> your files were rejected, or if you upload new files which address our
> concerns.


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

[Pkg-javascript-devel] Bug#870956: Bug#870956: Bug#870956: node-jsdom: should node-jsdom be removed from unstable?

[Paolo Greppi]

Il 10/09/2017 08:45, Lucas Nussbaum ha scritto:
> Hi,
> 
> On 10/08/17 at 17:38 +0530, Pirate Praveen wrote:
>> I think (from what I remember) this is a dependency of
>> node-jquery-. Though it required many other build tools also
>> packaged, so it was not touched. I will see if I can confirm this in the
>> coming days.
> 
> Ping? :)
> 
> Lucas
> 
> 
> 

Digging into the pkg-javascript-devel archives I found this message referring 
to jsdom:
http://lists.alioth.debian.org/pipermail/pkg-javascript-devel/2016-September/013791.html

It is also mentioned in the jquery and pump.io tasks:
https://wiki.debian.org/Javascript/Nodejs/Tasks/jquery?highlight=%28jsdom%29
https://wiki.debian.org/Javascript/Nodejs/Tasks/Pump.io?highlight=%28jsdom%29

All in all I think it could be useful

Paolo

-- 
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] ITP: libjs-vue -- JS library for building interactive web applications

[Paolo Greppi]

Il 08/08/2017 08:18, Michael Lustfield ha scritto:
> Package: wnpp
> Severity: wishlist
> Owner: Michael Lustfield 
> 
> * Package name: libjs-vue
>   Version : 2.4.2
>   Upstream Author : 2013-2017 Yuxi (Evan) You
> * URL : https://github.com/vuejs/vue
> * License : Expat
>   Programming Lang: Javascript
>   Description : JS library for building interactive web applications
> 
>  This Javascript library implements functions for building interactive web
>  interfaces. It provides data-reactive components with a simple and flexible
>  API.
>  .
>  Core features:
>  - Declarative rendering with a plain JS object based reactivity system
>  - Component-oriented development style with tooling support
>  - Lean and extensible core
>  - Flexible transition effect system
>  - Fast without the need for complex optimization
> 
> 
> This JS library is being packaged as a build dependency of gitea (a gogs 
> fork).
> There are a lot of build dependencies and I would love some help. If anyone is
> interested in handling this package, please feel free to contact me!

I am. I also CC the JS maint list...

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]

Hallo yes it's still on my todo list.

It's not in the npm registry so we can't easily (i.e. with the js_task_edit.py 
script) create a task page as for the other nodejs packages [1].

But it has quite a few  node dependencies.

As libjs-tinycon and node-jsonminify are in the archive we're left with 7 
direct dependencies:
- require-kernel, ITP #710057
- socket.io ITP [2]
- ueberdb
- express-session ITP #751885
- cheerio ITP #848315
- swagger-node-express
- measured

But then as Mike pointed out [3], there are recursive dependencies, so the 
count is higher.

For example there's 7 socket.io deps already listed as blocking bugs in the 
socket.io's ITP [2].

Then there is more which the last time I looked lacked IPTs:

Ueberdb2 deps:
node-cassandra-driver
node-rethinkdb
node-nano
node-elasticsearch

Cassandra-driver deps:
Node-long

rethinkdb deps:
bluebird

nano deps:
follow

And beware that I may have left out a few.

Finally one more difficulty is that it's hard to grasp what this stuff is all 
about.
For example from what I can tell there are several DB middlewares, so the 
question is: is this all really used ?

Anyway any help is welcome !

Paolo

[1] https://wiki.debian.org/Javascript/Nodejs/Tasks
[2] https://bugs.debian.org/707166
[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576998#138

Il 21/07/2017 09:39, Petter Reinholdtsen ha scritto:
> Hi.
> 
> Any progress on getting Etherpad into Debian?  I would love to add
> support for Etherpad to FreedomBox, but for that to happen there
> need to be maintainable packages in Debian.
> 
> Yesteday, the Software Freedom Conservancy announced that Etherpad
> join the Conservancy as a member, see
> https://sfconservancy.org/news/2017/jul/20/etherpad/ >.  Perhaps
> that might motivate more people to get Etherpad into Debian?
> 


-- 
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] #865892: node-proper-lockfile FTBFS

[Paolo Greppi]

Hi all,

due to FTBFS [1], node-proper-lockfile package will be removed in 5 days.

node-proper-lockfile currently has no dependents, but it will be required for 
node-yarnpkg [2] (I plan to resume work on that [3] soon).

I have pushed the fix to the git repo on alioth. My DM process [4] is still 
ongoing so please someone upload node-proper-lockfile 2.0.1-1 for me.

Thanks,

Paolo

[1] https://bugs.debian.org/865892
[2] https://github.com/yarnpkg/yarn/blob/master/package.json#L31
[3] https://bugs.debian.org/843021
[4] https://nm.debian.org/process/206

-- 
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#857986: npm: package is 3 years old (consider removal?)

[Paolo Greppi]

Il 04/07/2017 12:44, Antonio Ospite ha scritto:
> Removing npm could bring some more attention at packaging yarn[1,2],
> which seems to be better and more secure than npm (says a brief google
> search...).
> 
> Ciao,
>Antonio
> 
> [1] https://yarnpkg.com/en/
> [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843021

Yes, and if you are willing ho help please feel free to step in.

There is a lot to do:
https://wiki.debian.org/Javascript/Nodejs/Tasks/yarn

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#865892: reproducible

[Paolo Greppi]

This is easily reproducible: just apt remove node-asnyc, and try the build.

I am working on the fix while at the same time updating to 2.0.1

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-readable-stream_2.2.9-1_amd64.changes ACCEPTED into unstable, unstable

[Paolo Greppi]

Il 12/06/2017 10:00, Debian FTP Masters ha scritto:
> Accepted:
> 
> Format: 1.8
> Date: Sat, 27 May 2017 23:15:41 +0200
> Source: node-readable-stream
> Binary: node-readable-stream
> Architecture: source all
> Version: 2.2.9-1
> Distribution: unstable
> Urgency: low
> Maintainer: Debian Javascript Maintainers 
> 
> Changed-By: Bastien Roucariès 
> Description:
>  node-readable-stream - stream compatibility library for Node.js and browser
> Closes: 863510
> ...

Many modules have been patched to use nodejs' stream rather than 
readable-stream or to skip tests that require readable-stream.

Now that this is in the archive, should we pick it up ?

The involved modules (https://codesearch.debian.net/search?q=readable-stream) 
are 34:

node-are-we-there-yet
node-bl
node-cloneable-readable
node-concat-stream
node-duplexer2
node-duplexify
node-finalhandler
node-first-chunk-stream
node-from2
node-htmlparser2
node-isstream
nodejs
node-lazystream
node-lodash
node-log4js
node-memory-fs
node-merge-stream
node-mysql
node-nan
node-ordered-read-streams
node-raw-body
node-sha
node-static-module
node-stream-array
node-streamtest
node-superagent
node-tap
node-tap-parser
node-tar-pack
node-tar-stream
node-through2 
node-unpipe
node-vinyl-fs
node-ytdl-core

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] reopening the ITP for node-ms

[Paolo Greppi]

I intend to package this module, for the rationale see 
https://bugs.debian.org/836205

A quick search on https://codesearch.debian.net shows the following 
node/js-related packages that contain the string 'humanize', possibly 
indicating that they import the ms copy embedded in node-debug:

libjs-sifter.js
node-connect-timeout
node-dot
node-moment
node-parse-json
node-redis
node-send
node-serve-favicon
node-utilities
rtcninjajs

after triaging this list, when this one is packaged they should all be updated 
to depend on it.

I would need a sponsor to upload, and I intend to maintain it within the 
javascript maintainers team.

There is already a repo on alioth:
https://anonscm.debian.org/git/pkg-javascript/node-ms.git

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] is not yet fixed after all

[Paolo Greppi]

While I have been lazy in not closing this one with a Closes: line in 
debian/changes with 2.5.1-1, it turns out it was right to do so after all.

The issue has been reopened from upstream, and seems to be not really fixed in 
ms 0.7.2 as stated in the original advisory: https://github.com/zeit/ms/pull/89

I think we should:

1. create a node-ms 2.0.0 package
2. update node-debug to 2.6.8 and remove the embedded ms module

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#861515: node-grunt-contrib-copy FTBFS on armhf i386

[Paolo Greppi]

Hi all,

re. https://bugs.debian.org/861515, since we haven't got any reply from 
upstream for almost a month 
(https://github.com/gruntjs/grunt-contrib-copy/issues/291), I have updated 
node-grunt-contrib-copy to simply skip the failing test: 
https://anonscm.debian.org/git/pkg-javascript/node-grunt-contrib-copy.git/tree/debian/changelog

I have checked that the patch works when tests are run during the build 
(debian/tests/control) on i386 architecture. I have no way to test on armhf.

With autopkgtest, the patch is missing and it fails.

So if the patch is OK, please sponsor this upload else this package and its 
dependencies (node-inquirer and node-rx) will be autoremoved from testing on 
2017-06-12.
Else I am open to suggestions.

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] pump.io packaging help (from upstream)

[Paolo Greppi]

Hi Alex, nice to know that we can count on upstream for this one.

I have updated the page at 
https://wiki.debian.org/Javascript/Nodejs/Tasks/Pump.io which was stuck at 
pump.io 0.3.0.

The count of missing packages has gone up from about 40 to over 90, so it's 
going to be a long way before we can even try to package pump.io.

This is similar to what we see for Etherpad (https://bugs.debian.org/576998), 
yarn (https://bugs.debian.org/843021) and others.
The state of the nodejs ecosystem in Debian is such that we struggle to package 
the nitty-gritty dependencies, and the useful stuff remains out of reach.

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#861515: reproducibile here

[Paolo Greppi]

I have set up an i386 debci lxc testbed with:

  debci_arch=i386 debci setup

then confirmed that the lxc container has indeed been created:

  lxc-ls --fancy
  NAME  STATE   AUTOSTART GROUPS IPV4 IPV6 
  adt-sid-amd64 STOPPED 0 -  --
  adt-sid-i386  STOPPED 0 -  --

and run the test suite from the source package in the archive with:

  adt-run --user debci --output-dir /tmp/output-dir node-grunt-contrib-copy --- 
lxc --sudo adt-sid-i386

it fails with:

✖ copy - timestamp_equal

AssertionError: 1457124645257 == 1457124645000
  at Object.equal (/usr/lib/nodejs/nodeunit/lib/types.js:83:39)
  at Object.exports.copy.timestamp_equal 
(/tmp/autopkgtest-virt-lxc.shared.wv8ud5o5/downtmp/build.iwX/node-grunt-contrib-copy-1.0.0/test/copy_test.js:92:10)
  at Object. (/usr/lib/nodejs/nodeunit/lib/core.js:236:16)
  at Object. (/usr/lib/nodejs/nodeunit/lib/core.js:236:16)
  at /usr/lib/nodejs/nodeunit/lib/core.js:236:16
  at Object.exports.runTest (/usr/lib/nodejs/nodeunit/lib/core.js:70:9)
  at /usr/lib/nodejs/nodeunit/lib/core.js:118:25
  at /usr/lib/nodejs/nodeunit/deps/async.js:513:13
  at iterate (/usr/lib/nodejs/nodeunit/deps/async.js:123:13)
  at /usr/lib/nodejs/nodeunit/deps/async.js:134:25
  at /usr/lib/nodejs/nodeunit/deps/async.js:515:17
  at Immediate._onImmediate (/usr/lib/nodejs/nodeunit/lib/types.js:146:17)
  at processImmediate [as _immediateCallback] (timers.js:396:17)


AssertionError: 1457124645257 == 1457124645000
  at Object.equal (/usr/lib/nodejs/nodeunit/lib/types.js:83:39)
  at Object.exports.copy.timestamp_equal 
(/tmp/autopkgtest-virt-lxc.shared.wv8ud5o5/downtmp/build.iwX/node-grunt-contrib-copy-1.0.0/test/copy_test.js:93:10)
  at Object. (/usr/lib/nodejs/nodeunit/lib/core.js:236:16)
  at Object. (/usr/lib/nodejs/nodeunit/lib/core.js:236:16)
  at /usr/lib/nodejs/nodeunit/lib/core.js:236:16
  at Object.exports.runTest (/usr/lib/nodejs/nodeunit/lib/core.js:70:9)
  at /usr/lib/nodejs/nodeunit/lib/core.js:118:25
  at /usr/lib/nodejs/nodeunit/deps/async.js:513:13
  at iterate (/usr/lib/nodejs/nodeunit/deps/async.js:123:13)
  at /usr/lib/nodejs/nodeunit/deps/async.js:134:25
  at /usr/lib/nodejs/nodeunit/deps/async.js:515:17
  at Immediate._onImmediate (/usr/lib/nodejs/nodeunit/lib/types.js:146:17)
  at processImmediate [as _immediateCallback] (timers.js:396:17)


✔ copy - timestamp_changed

FAILURES: 2/17 assertions failed (234ms)

AFAICT this seems related to this upstream PR: 
https://github.com/gruntjs/grunt-contrib-copy/pull/268, that claims to have 
fixed a similar problem

I'll try to bring this to the attention of upstream over there.

-- 
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#860634: fix for node-grunt-contrib-copy RC bug

[Paolo Greppi]

Hi team there is a RC bug on node-grunt-contrib-copy, I have provided a fix and 
uploaded that to alioth.

I have tested with pkg-ruby-extras/build and tested the reverse deps (node-rx) 
too.

These two packages have an impressive popcon count of ... 7+5 ! But anyway 
please someone sponsor the upload

Cheers,

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#860634: reproducible here

[Paolo Greppi]

This is easy to reproduce on stretch from the root of a source package against 
the currently installed package.

Just make sure the tmp directory created during the build process is not 
present:
  make -f debian/rules clean

or just:
  rm -rf tmp

then run the tests in the local environment (that's the easiest path as per 
https://ci.debian.net/doc/file.MAINTAINERS.html):
  adt-run --output-dir /tmp/output-dir ./ --- null

The reason for the failure is that when tests are run during the build process, 
they are run via the debian/rules override_dh_clean which does:
  rm -rf tmp
  mkdir -p tmp
  grunt copy
  nodeunit

whereas when they are run by adt-run and hence by debci the tests run as 
declared in debian/tests/control per DEP-8 spec, i.e. by running nodeunit 
straight.

Interestingly this package has no Testsuite: autopkgtest or XS-Testsuite: 
autopkgtest entries in the source stanza in debian/control, but debci runs the 
tests anyway.

A fix is to make both tests run via the supplied ./debian/tests/run_tests 
script.

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

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

[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

[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-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

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

Re: [Pkg-javascript-devel] node-invariant_2.2.2-1_amd64.changes REJECTED

[Paolo Greppi]

On 26/12/2016 06:59, Pirate Praveen wrote:
> On തിങ്കള്‍ 26 ഡിസംബര്‍ 2016 04:30 രാവിലെ, Chris Lamb wrote:
>>
>> Missing attributions from Facebook.
>>
>>  -- Chris Lamb   Sun, 25 Dec 2016 22:47:24 +
> 
> 
> Fixed.

This is lost somewhere, I can not see it in the NEW queue

Could be related to this ?
https://lists.alioth.debian.org/pipermail/pkg-javascript-devel/2016-December/017050.html

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 26/12/2016 09:18, Pirate Praveen wrote:
> On ശനി 24 ഡിസംബര്‍ 2016 10:52 വൈകു, Pirate Praveen wrote:
>> This is now stuck at #849275, we need to fix lodash to proceed further
>> (babel needs this and lerna builddeps on babel). I'll try to use npm and
>> upload to contrib.
> 
> lodash is fixed.
> 
> But when I try to use the rollup built as /usr/bin/rollup, I get this error
> 
> $ /usr/bin/rollup -c
> [TypeError: Cannot read property 'id' of undefined]
> 
> You can reproduce this by cloning node-rollup,
> 
> npm install -g rollup
> gbp buildpackage
> dpkg -i ../rollup*.deb
> /usr/bin/rollup -c

I can reproduce this, tried to debug by spinkling console.log
statements, and got lost somewhere when it loads the rollup.config.js

Sorry I can't help more

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 10:54, Paolo Greppi wrote:
> On 23/12/2016 10:38, Paolo Greppi wrote:
>> 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
>>
> 
> for sync-exec it should be possible to patch it to use
> child_process.execSync so I'll skip the ITP
> 
> P

There you go !

With the 3 RFS I posted today, you should have everything you need for lerna

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-object-assign-sorted 1.0.0

[Paolo Greppi]

Hi,

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

This depends on node-sorted-object which is currently in the NEW queue.

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-inquirer 2.0.0

[Paolo Greppi]

Hi,

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

This depends on node-rx and on node-cli-cursor which are currently in
the NEW queue.

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-command-join 1.1.1

[Paolo Greppi]

Hi,

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

I managed to get away with the build-dep on babel ... by just copying
the file as-is (!). The build-time tests run fine. The autopkgtests
currently fail because the tests only work in the source dir if the
build (which puts the command-join.js in the dist subdir) has run.

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

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