[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