Re: [Pkg-javascript-devel] Packages ready to review

[Pirate Praveen]

On തി, മേയ് 7, 2018 at 8:10 വൈകു, Xavier 
 wrote:

Updated list of packages to review:

 - node-mongodb
   - node-mongodb-core
   - node-require-optional


Try to enable tests. See 
https://wiki.debian.org/Javascript/Nodejs/Npm2Deb#Run_tests_if_available



   - bson.js


bson.js: I suggest you keep node-bson as source package name, remove 
nodejs depndency from node-bson binary package, remove libjs-bson 
binary package and just provide libjs-bson.


Also rebuild browser_build/bson.js using the provided webpack 
configuration. See 
https://wiki.debian.org/Javascript/Nodejs#Using_build_tools_like_grunt



 - node-nodedbi
 - node-file-cache-simple
   - node-fs-jetpack
 - node-inireader
 - node-q
 - node-syslog-client

Regards,
Xavier

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

Re: [Pkg-javascript-devel] NEW queue

[Pirate Praveen]

On തി, മേയ് 7, 2018 at 11:58 രാവിലെ, Paolo 
Greppi  wrote:
And for many the vcs_git/browser fields are set to anonscm (118) 
rather

than salsa (51).
BTW of those 118, only 31 have been migrated to salsa.


Because the migration happened only recently and some packages are in 
NEW for 6 months. Also techwolf/Daniel Ring wanted all packages in one 
place so he created new packages also in alioth before the migration to 
salsa.


So the backlog could also be due to something that we could improve 
from

our end.

Any ideas ?


I think it is just the numbers. I think many of are already trying to 
reduce the number of packages, but for existing queue, I think the 
feasible option is only more volunteers in ftp team (redoing the work 
of reducing packages is extra work I think).


A radical option could be to bundle all modules per main package and 
ask them to reject the individual packages.
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] NEW queue

[Pirate Praveen]

On ചൊ, മേയ് 8, 2018 at 3:25 വൈകു, Paolo Greppi 
<paolo.gre...@libpf.com> wrote:

Il 08/05/2018 10:11, Pirate Praveen ha scritto:
 On തി, മേയ് 7, 2018 at 11:58 രാവിലെ, Paolo 
Greppi <paolo.gre...@libpf.com> wrote:
 And for many the vcs_git/browser fields are set to anonscm (118) 
rather than salsa (51). BTW of those 118, only 31 have been 
migrated to salsa.


 Because the migration happened only recently and some packages are 
in NEW for 6 months. Also techwolf/Daniel Ring wanted all packages 
in one place so he created new packages also in alioth before the 
migration to salsa.


To address this, I volunteer to migrate to salsa the 118-31=87, using 
the procedure here:

https://alioth-lists.debian.net/pipermail/pkg-javascript-devel/2018-April/025717.html



Thanks!

I'd skip the AliothRewriter step because those repo were never really 
"public".

But I'd fix the Vcs-* fields in d/control for all 118.

So new uploads would then be required.
Would we increase the debian version ?
Would those be team uploads ?


Yes for both, just like updating a package already in the archive.
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] NEW queue

[Pirate Praveen]

On April 27, 2018 11:18:22 PM GMT+05:30, Paolo Greppi  
wrote:
>Of 340 packages that sit in the NEW queue, 161 start with "node-"
>
>The average age of the 161 node-* is 120 days, for the others it is 40.
>
>What can we do to ease the job on the ftp-masters ?
>

I think more people joining ftp master team is an option.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

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

Re: [Pkg-javascript-devel] Bug#886849: RFS: node-puka

[Pirate Praveen]

On വെ, ഏപ്രി 27, 2018 at 8:45 വൈകു, Paolo Greppi 
 wrote:

I have rebuilt the repo on salsa from scratch.

BTW can you delete the node-puka.old repo ?
https://salsa.debian.org/js-team/node-puka.old
I think I haven't got enough powers to do that


removed old repo and uploaded.
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] RFS: node-peek-stream

[Pirate Praveen]

On വെ, ഏപ്രി 27, 2018 at 9:06 വൈകു, Paolo Greppi 
 wrote:

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

I am Cc-ing the ITP.

Please someone sponsor the upload.

Paolo


Uploaded, thanks!
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] RFS: node-gunzip-maybe

[Pirate Praveen]

On വെ, ഏപ്രി 27, 2018 at 9:33 വൈകു, Paolo Greppi 
 wrote:

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

It requires node-peek-stream see RFS:
https://alioth-lists.debian.net/pipermail/pkg-javascript-devel/2018-April/025955.html
I have tested the build with sbuild --extra-package

I am Cc-ing the ITP.

Please someone sponsor the upload.

Paolo


Uploaded, thanks!
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] Problems to recreate minimized JS in r-cran-jsonld

[Pirate Praveen]

On Wed, May 9, 2018 at 3:05 PM, Andreas Tille  
wrote:

Hi,

I was stumbling upon an issue with some minimized JS in the package
r-cran-jsonld (ITPed in #898224).  I tried to recreate jsonld.min.js 
and

have written a script[1] which calls webpack in a clone of the Github
reporsitory.  Unfortunately the webpack call ends in:



webpack-merge@4.1.2 node_modules/webpack-merge
└── lodash@4.17.10
Hash: eaf5c95c94821ab4944c9f696b4a89040915c26b
Version: webpack 3.5.6
Child
Hash: eaf5c95c94821ab4944c
Time: 140ms
Asset Size  Chunks Chunk Names
jsonld.js  3.61 kB   0  [emitted]  jsonld
   [0] multi regenerator-runtime/runtime 
core-js/fn/array/includes core-js/fn/object/assign core-js/fn/promise 
core-js/fn/string/starts-with core-js/fn/symbol ./lib/index.js 100 
bytes {0} [built]


ERROR in multi regenerator-runtime/runtime 
core-js/fn/array/includes core-js/fn/object/assign core-js/fn/promise 
core-js/fn/string/starts-with core-js/fn/symbol ./lib/index.js
Module not found: Error: Can't resolve 'babel-loader' in 
'/home/andreas/debian-maintain/salsa/r-pkg-team/0_prospective/r-cran-jsonld/debian/JS/jsonld.js'
 @ multi regenerator-runtime/runtime core-js/fn/array/includes 
core-js/fn/object/assign core-js/fn/promise 
core-js/fn/string/starts-with core-js/fn/symbol ./lib/index.js





You'll need to update webpack.config.js with system path for it to find 
apt installed modules.


jsonld.js does not work.  The file size of this uncompressed file is 
way
smaller than the minimazion result and doese not work together with 
the

R code.  Thus I really need to undergo the process to create the
minimized JS.

Any idea how to approach this?


https://wiki.debian.org/Javascript/#Using_build_tools_like_grunt has 
examples.




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

Re: [Pkg-javascript-devel] Problems to recreate minimized JS in r-cran-jsonld

[Pirate Praveen]

On Thu, May 10, 2018 at 2:31 PM, Andreas Tille  wrote:


 > jsonld.js does not work.  The file size of this uncompressed file 
is way
 > smaller than the minimazion result and doese not work together 
with the

 > R code.  Thus I really need to undergo the process to create the
 > minimized JS.

 https://wiki.debian.org/Javascript/#Using_build_tools_like_grunt has
 examples.


Is there any actual package example?  The anchor does not exist (any
more) on that wiki page (which should be updated to Salsa anyway ;-) 
).



https://wiki.debian.org/Javascript/Nodejs#Using_build_tools_like_grunt 
last link seems a mistake in copy-paste, this is the correct link.
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Pirate Praveen]

On Thu, May 10, 2018 at 1:22 PM, Jérémy Lal  wrote:


Yes the server is setup by the tests. Anyway if local interface was 
not setup,

you would have seen more test failures, so that was a bad suggestion.
A better idea: this test might be depending on some libc-ares2 recent 
release.


Jérémy




Thanks! That worked. I have bumbed minimum version of c-ares in master 
as well. I will upload this version to stretch-backports once the 
dependencies are accepted there.
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Pirate Praveen]

On Thu, May 3, 2018 at 3:19 PM, Jérémy Lal <kapo...@melix.org> wrote:



2018-05-03 11:32 GMT+02:00 Pirate Praveen <prav...@onenetbeyond.org>:



On ബു, മേയ് 2, 2018 at 9:04 വൈകു, Jérémy Lal 
<kapo...@melix.org> wrote:
Correction: nodejs 8.11 supports both openssl 1.0.1 or openssl >= 
1.1.0g.

So if you build it using libss1.0-dev it should be all right.
I prefer option 2...


Thanks. I tried with libss1.0-dev and build passed, but tests failed 
(tried with lxc and also in sbuild chroot).


5 tests failed in lxc, but only test failed in sbuild (this test 
failed in both). Any idea?


not ok 400 parallel/test-dns-resolveany
  ---
  duration_ms: 0.911
  severity: fail
  stack: |-
assert.js:669
assert.ifError = function ifError(err) { if (err) throw err; };
  ^

Error: queryAny EBADRESP example.org
at errnoException (dns.js:50:10)
at QueryReqWrap.onresolve [as oncomplete] (dns.js:238:19)



This test runs a server on 127.0.0.1:, so your 
build env needs

to have local interface up.

Jérémy



I suspected some issues with my local setup and rerun it on another 
machine, but got the same error. Shouldn't setting up of the server be 
part of package? May be it needs some libraries to be backported? Can 
you try it?


https://people.debian.org/~praveen/gitlab/ has both libuv1 and 
http-parser backported.
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] NEW queue

[Pirate Praveen]

On വെള്ളി 11 മേയ് 2018 11:49 വൈകു, Paolo Greppi wrote:
> OK I just finished updating the Vcs-* fields in debian/control for the 115
> packages from js-team that:
> - are in the NEW queue
> - have vcs_git matching regex /anonscm/ (118)
> - the repo on alioth actually exists (3 haven't got one)

Thanks for your work!

> In doing this, I found a few minor issues:
> 1. node-fast-diff: missing debian/... tag (I added it)
> 2. node-postcss-reduce-initial: the debian/1.0.1-1 tag seems wrong:
>https://salsa.debian.org/js-team/node-postcss-reduce-initial/issues/1
> 3. two have an associated bug of type RFP:
>   - https://salsa.debian.org/js-team/node-is-utf8/issues/1
>   - https://salsa.debian.org/js-team/node-md5-hex/issues/1
>   to prevent the ITPs being automatically turned to RFP by the BTS, I have
>   sent an update mail to all ITP bugs associated with the other 113 packages,
>   similar to this one: https://bugs.debian.org/887493#10
> 
> And 2 major issues:
> - node-clone-response claims to close 989766, it should be 890080:
>   https://salsa.debian.org/js-team/node-clone-response/issues/1
> - node-keyv claims to close 989766, it should be 892663:
>   https://salsa.debian.org/js-team/node-keyv/issues/1
> I notified ftp-master on these two.
> 
> For all 115 of them, with the help of gitlab-cli I have created an issue on 
> the
> current_itps kanban:
> https://salsa.debian.org/js-team/current_itps/boards
> They are now in the backlog column, to make them easy to spot I tagged them 
> all
> with the label NEW-alioth.
> 
> Finally, I still haven't got a reply for the 3 packages for which we lost the
> repo (node-insert-module-globals, node-mimelib and node-postcss-merge-idents).
> If there's no reply for another couple of weeks, I think we can request
> ftp-master to reject them.

I have pushed repo for node-postcss-merge-idents. I don't think a git
repo is mandatory as per policy and if required we can just import the
dsc after the package is accepted. So I don't think we should request a
rejection just because the repo is missing.



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] alioth is down: what to do with those 119 packages ?

[Pirate Praveen]

On Friday 01 June 2018 11:08 AM, Paolo Greppi wrote:
> Hi as you know, since yesterday alioth is dead.

I think there will be a read only mirror.

> There's still quite a few packages from the js-team sitting in the
> new queue with the vcs* fields in debian/control set to:
> https://anonscm.debian.org/cgit/pkg-javascript/...
> 
> To find out which they are, try the "Debian NEW Packages fancy view" at:
> http://212.237.56.209/
> check the "Only show active packages" checkbox then type this as search 
> string:
> "https://anonscm.debian.org/cgit/pkg-javascript/; 
> 
> They are 119 ATM.
> 
> As mentioned here:
> https://alioth-lists.debian.net/pipermail/pkg-javascript-devel/2018-May/026296.html
> this work has been planned for a while.
> 
> Unfortunately most of the ITP owners failed to even register on salsa, nor 
> have 
> we prepared team uploads.
> You can track the WIP here:
> https://salsa.debian.org/js-team/current_itps/boards?label_name[]=NEW-alioth
> (BTW, they are 114 there so 5 are missing)
> 
> Currently only node-ansicolors and node-classnames are in the RFC (request
> for comments) column i.e. almost ready for sponsoring.
> 
> My proposal is to ask ftp-master to reject them all.
> This is fair to them and will clean up the queue.

I don't think changing vcs url is worth a reject.

> After that, we have all the time in the universe to reassign ITPs,
> prepare team uploads etc.
> 
> Paolo
> 




signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] RFS: node-bl 1.1.2-2 to address #894927 and debci test failures

[Pirate Praveen]

On Thursday 07 June 2018 02:39 PM, Paolo Greppi wrote:
> We do need node-bl which is required for tar-stream and therefore for yarnpkg.
> 
> So I have prepared a minor update that includes (besides the usual bumps) the 
> patch suggested by Graham.
> 
> We have no stringent need to upgrade it as tar-stream requires >= 1.0.0:
> https://github.com/mafintosh/tar-stream/blob/master/package.json#L10
> 
> Please someone allow me DM upload access for this package or sponsor the 
> upload:
> https://salsa.debian.org/js-team/node-bl

Granted DM access.



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#902178: node-turbolinks: Does not work as intended

[Pirate Praveen]

On Wed, 27 Jun 2018 04:43:43 -0700 njos...@riseup.net wrote:
> I think the issue is with coffeescript compilation. I tried compiling it
> using the coffee command. The index.js produced has no imports at all.
> Hence, the output that is finally produced using webpack and uglifyjs is
> just the index.js file. The dist file is literally the index.js file
> with some webpack cruft added at the top.
> 
> I don't recognize the import syntax in the coffeescript files. Is this a
> new require syntax introduced in coffeescript 2.0 ? But why put them in
> comments with #= symbols? I hope it isn't a syntax that can only be
> compiled by their "blade" gem.

I think this is the syntax used by sprokets. We may be able to patch it
to use the regular commonjs require syntax.



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#902178: node-turbolinks: Does not work as intended

[Pirate Praveen]

On Wed, 27 Jun 2018 18:10:55 +0530 Pirate Praveen 
wrote:
> I think this is the syntax used by sprokets. We may be able to patch it
> to use the regular commonjs require syntax.
> 

I have pushed a patch to salsa. Can you build and test?



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Pirate Praveen]

On June 23, 2018 8:32:22 PM GMT+05:30, Bastien ROUCARIES 
 wrote:
>On Thu, Jun 21, 2018 at 7:06 AM, Pirate Praveen
> wrote:
>>
>> Can't this be node-types-foo? Then it follows the existing node-
>> standard and node-types can be used to filter types packages. This
>also
>> makes it easier for npm2deb, which won't require any special handling
>> for this case (when types is a separate package). node-types will be
>> only used for types packages, so I don't see any conflict.
>
>No because and unfortunatly some pure node package are named type-is
>(debian name node-type-is).

But that is clearly different, node-type != node-types.

Is there any module that starts with types-?

>Therefore it is a dead end. Better to add logic in npm
>
>> @types/jquery -> node-types-jquery
>> @std/esd - node-std-esm
>> @ava/abc -> node-ava-abc
>>

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

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

[Pkg-javascript-devel] Bug#902178: node-turbolinks: Does not work as intended

[Pirate Praveen]

On Sat, 23 Jun 2018 13:03:24 +0530 Joseph Nuthalapati
 wrote:> The turbolinks package installed through
Debian doesn't seem to have all the
> code from upstream.
> 
> The minified Javascript from the Debian package has 1448 characters while the
> dist packaged obtained from source has 36927 characters, measured using `wc`.
> This might be why the package does nothing when used in the browser.

We used webpack because the upstream build system is not packaged.

> Please fix the build mechanism of this package.

Any ideas? May be we missed some options for webpack.



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#902178: node-turbolinks: Does not work as intended

[Pirate Praveen]

On Sat, 23 Jun 2018 18:44:53 +0530 Pirate Praveen 
wrote:
> Any ideas? May be we missed some options for webpack.

If we cannot emulate the build with webpack, we will have to package
blade (written in ruby).



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#801468: Fixed in node-jquery 2.24+dfsg-1

[Pirate Praveen]

Control: fixed -1 2.24+dfsg-1
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Pirate Praveen]

On Saturday 19 May 2018 08:08 PM, Bastien ROUCARIES wrote:
> On Thu, May 17, 2018 at 6:31 AM, Pirate Praveen
>  wrote:
>>
>>
>> On May 17, 2018 1:32:01 AM GMT+05:30, Julien Puydt 
>>  wrote:
>>> Hi,
>>>
>>> Le 16/05/2018 à 17:45, Bastien ROUCARIES a écrit :
>>>> Can I suggest in all the case something pragmatic ? Could I suggest
>>>> that package providing types for node-foo should be named
>>>> nodetypes-foo (without hyphen in order to avoid conflict with node
>>>> package)
>>>>
>>>> If node-foo include type it is only needed to add "Provides:
>>>> nodetypes-foo (= ${Source:Version})" in node-foo.
>>>>
>>>> Can someone suggest a policy file change ?
>>>>
>>>> The same tips could be used for libjs-foo lib BTW. I have done that
>>>> for node-normalize.css for instance. It avoid small package and is
>>>> ftpmaster friendly
>>>
>>>
>>> Good idea, but the question of how to actually provide nodetypes-foo if
>>> it's only available in DefinitelyTyped's big repository is still open,
>>> if I don't err?
>>>
>>> Snark on #debian-js
>>
>> I think just adding it as debian/types, installing it to 
>> /usr/lib/nodejs/foo/types and provides nodetypes-foo.
> 
> Please provides: nodetypes-foo (= ${source:Version})

Can't this be node-types-foo? Then it follows the existing node-
standard and node-types can be used to filter types packages. This also
makes it easier for npm2deb, which won't require any special handling
for this case (when types is a separate package). node-types will be
only used for types packages, so I don't see any conflict.

@types/jquery -> node-types-jquery
@std/esd - node-std-esm
@ava/abc -> node-ava-abc



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#701583: Generated files are removed from orig.tar

[Pirate Praveen]

Control: fixed -1 2.24+dfsg-1
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] Packages ready to review

[Pirate Praveen]

On ബു, മേയ് 2, 2018 at 10:44 രാവിലെ, Xavier 
 wrote:

Hi all,

these packages are ready for review (with dependencies):
 - node-fastcgi
   - node-fastcgi-stream
   - node-bufferlist
 - node-mongodb
   - node-mongodb-core
   - node-require-optional
   - bson.js
 - node-nodedbi
 - file-cache-simple.js
   - fs-jetpack.js


This seems to be a node module, so it is better to keep node- 
as the source package name (the default by npm2deb).



 - inireader.js
 - node-q

Best regards,
Xavier

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

Re: [Pkg-javascript-devel] RFS: node-is-builtin-module 2.0.0

[Pirate Praveen]

On ബു, മേയ് 2, 2018 at 2:01 രാവിലെ, Paolo 
Greppi  wrote:
Hi, I have prepared an update to node-is-builtin-module from 1.0.0 to 
2.0.0


It is required for yarnpkg, see:
https://salsa.debian.org/js-team/node-yarnpkg/wikis/home

It has only one few reverse dependency (node-normalize-package-data) 
and according to meta/build the new version does not break it.


Please someone allow me DM upload access for this package or sponsor 
the upload:

https://salsa.debian.org/js-team/node-extend-shallow


Done!

dcut dm --uid F0D93601375202CC4E22626C3BA38591B2BF98D5 --allow 
node-is-builtin-modules


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

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

[Pirate Praveen]

Hi,

I'd like to upload gitlab 10.6 to stretch-backports as backporting
security fixes is becoming difficult. My original idea was also
providing updates via backports, but gitlab switching to nodejs for
front end in gitlab 9 made that impossible.

Now with all nodejs modules stuck in NEW for about 5-7 months, I'm
focusing on gitlab in contrib with nodejs modules installed via npm/yarn.

To get this moving, I have backported all required ruby gems and they
are available here https://people.debian.org/~praveen/gitlab/

Since npm is not in stretch, I hope to upload npm 1.4 to
stretch-backports now and update it when 5.8 is available (which should
be soon).

Now one of the node modules punycode@2.1.0 needs nodejs >= 6. So I'm
trying to rebuild nodejs for stretch. With help from Jeremy on IRC I was
able to skip nghttp2 support but got stuck with openssl issue. nodejs
supports only openssl 1.1.0g and stretch only has 1.1.0f.

So I tried to build nodejs 6.12 and that worked.

Please suggest/help in proceeding further.

1. Can I just proceed with nodejs 6.12? (stretch-backports-6 branch on
salsa)
2. I need help with building nodejs 8.11 on stretch. (stretch-backports
branch on salsa)



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] Packages ready to review

[Pirate Praveen]

On ബുധന്‍ 02 മേയ് 2018 02:21 വൈകു, Xavier wrote:
> Done for node-fs-jetpack, node-file-cache-simple and node-inireader.
> List is now:
>  - node-fastcgi
>- node-fastcgi-stream
>- node-bufferlist

Uploaded. Next time you can use compat 11 and also remove unnecessary
dh-buildinfo build dependency (not required for debhelper >= 10).

Also check the LICENSE* file and update debian/copyright. See my changes
in node-fastcgi.

>  - node-mongodb
>- node-mongodb-core
>- node-require-optional
>- bson.js
>  - node-nodedbi
>  - node-file-cache-simple
>- node-fs-jetpack
>  - node-inireader
>  - node-q
> 
> Thanks!
> 



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] RFS: node-puka

[Pirate Praveen]

On വ്യാ, ഏപ്രി 26, 2018 at 7:54 വൈകു, Paolo 
Greppi  wrote:

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

This requires node-rollup-plugin-babel which is already in the NEW 
queue.


The ITP is in CC.

Please someone sponsor the upload.


pristine-tar branch is missing the dfsg tarball and uscan is not 
working. Please fix these two issues.
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] proposal: phase out Task pages on wiki.d.o in favor of gitlab repo wikis

[Pirate Praveen]

On വ്യാ, ഏപ്രി 26, 2018 at 3:03 വൈകു, Paolo 
Greppi  wrote:

Hi,

with the switch from alioth to salsa there is a bunch of gitlab 
features we

can exploit - one is the built-in wiki associated with each repo.

I have been experimenting with those wikis, as in:

https://salsa.debian.org/js-team/node-liftoff/wikis/home
https://salsa.debian.org/js-team/node-micromatch/wikis/home
https://salsa.debian.org/js-team/node-yarnpkg/wikis/home
https://salsa.debian.org/js-team/node-execa/wikis/home

then I realized that this overlaps with the Task pages on wiki.d.o:
https://wiki.debian.org/Javascript/Nodejs/Tasks

My proposal is that we keep the wiki.d.o for general stuff (policies,
procedures...) and move all package-specific stuff to salsa: if a 
package is
WIP, it should have a repo on salsa (this encourages the would-be 
maintainer
to share her work early with the team), so we may just use the gitlab 
wiki.


It should be possible to tweak this script:
https://anonscm.debian.org/cgit/pkg-javascript/js-task-wiki-edit.git
to output the task page in the gitlab markdown dialect ...
(BTW this repo should be migrated to salsa)

The js-task output could go to a separate wiki page:
https://salsa.debian.org/js-team/node-yarnpkg/wikis/task
and the home:
https://salsa.debian.org/js-team/node-yarnpkg/wikis/home
could be used as a notepad by the maintainer.

What are your thoughts ?


I think this is a good idea. As you already noted, it needs somoene to 
update the task generation script.
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] RFS: node-ret

[Pirate Praveen]

On ചൊ, ഏപ്രി 24, 2018 at 2:39 വൈകു, Paolo Greppi 
 wrote:

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

I am Cc-ing the ITP.

Please someone sponsor the upload.


Updated copyright year to match LICENSE file and uploaded.


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

[Pkg-javascript-devel] Bug#892742: rollup FTBFS with node-rollup-plugin-commonjs 9.0

[Pirate Praveen]

On Mon, 12 Mar 2018 18:41:36 +0530 Pirate Praveen 
wrote:
> Package: src:node-rollup
> Version: 0.50.0-1

Latest version of rollup is 0.60.7 and it has already moved to
rollup-plugin-commonjs 9.x

https://github.com/rollup/rollup/blob/6e004184ede79832e658c22983de439aa5c30462/package.json



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#905943: Should create Vcs-* fields pointing to salsa

[Pirate Praveen]

On 12/08/18 10:17 AM, Julien Puydt wrote:
> I was surprised this morning that npm2deb created a package with Vcs-*
> fields pointing to anonscm.debian.org... they should point to salsa
> instead.

It is already fixed in upstream master, we are waiting for a new release
(needs review of one pull request before we release).



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#907195: RM: gmod -- RoM; obsolete; unmaintained upstream;

[Pirate Praveen]

Source: node-tar-pack
Severity: wishlist
User: debian...@lists.debian.org
Usertags: proposed-removal

node-tar-pack is affected by rc bug #906451 (it is compatible with
version of node-tar in unstable). The only reverse dependency,
node-pre-gyp no longer depends on it. node-pre-gyp which no longer
depends on node-tar-pack already entered testing.



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] Comments regarding node-csv-spectrum_1.0.0-1_amd64.changes

[Pirate Praveen]

On 2018, ഓഗസ്റ്റ് 25 1:50:34 AM IST, Chris Lamb 
 wrote:
>Are you looking at Lintian? There are some glaring issues like:
>
> https://anonscm.debian.org/git/pkg-javascript/node-csv-spectrum.git
>^^^

This package was uploaded when it was still a valid URL. Anyway, I'll update it.

> -- Chris Lamb   Fri, 24 Aug 2018 20:20:32 +

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

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

[Pkg-javascript-devel] Bug#906451: tar-pack seems an unmaintained module

[Pirate Praveen]

The only package that depends on node-tar-pack is node-pre-gyp, which
has a newer upstream release that no longer depends on tar-pack.



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#906451: tar-pack seems an unmaintained module

[Pirate Praveen]

On Sun, 19 Aug 2018 21:54:11 +0530 Pirate Praveen
 wrote:
> The only package that depends on node-tar-pack is node-pre-gyp, which
> has a newer upstream release that no longer depends on tar-pack.
> 

I have uploaded a new upstream version of node-pre-gyp (0.6.32-1 ->
0.10.2-1)  to experimental. node-mapnik, node-sqlite3 and node-zipfile
are its reverse dependencies.

Lazslo, Sebastian, Jeremy, can you confirm if this version is compatible
with your package? I'd like to upload this to unstable soon. Since it is
still in 0.x I assume it can have breaking changes, so just giving a
heads up to be extra careful here.



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#906451: tar-pack seems an unmaintained module

[Pirate Praveen]

On 2018, ഓഗസ്റ്റ് 20 1:17:52 AM IST, Sebastiaan Couwenberg  
wrote:
>I don't know, you should do a round of rebuilds to find out.

Rebuilds won't be enough I think because these are runtime dependencies. As 
they don't have functional autopkgtests enabled, we have to use upstream test 
suite to confirm.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

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

[Pkg-javascript-devel] Bug#906451: Bug#906451: tar-pack seems an unmaintained module

[Pirate Praveen]

On 20/08/18 10:58 AM, Pirate Praveen wrote:
> 
> 
> On 2018, ഓഗസ്റ്റ് 20 1:17:52 AM IST, Sebastiaan Couwenberg 
>  wrote:
>> I don't know, you should do a round of rebuilds to find out.
> 
> Rebuilds won't be enough I think because these are runtime dependencies. As 
> they don't have functional autopkgtests enabled, we have to use upstream test 
> suite to confirm.
> 

On a second thought, since their builds also use node-pre-gyp, may be
rebuilds are enough. Anyway, I have updated node-zipfile to latest
upstream releases which supports this version of node-pre-gyp.



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#906451: Bug#906451: Bug#906451: Bug#906451: tar-pack seems an unmaintained module

[Pirate Praveen]

On 20/08/18 1:24 PM, Pirate Praveen wrote:
> On 20/08/18 12:54 PM, Pirate Praveen wrote:
>> On a second thought, since their builds also use node-pre-gyp, may be
>> rebuilds are enough. Anyway, I have updated node-zipfile to latest
>> upstream releases which supports this version of node-pre-gyp.
>>
>>
> 
> node-sqlite3 also updated. node-mapnik also has a new upstream release
> that supports the new pre-gyp. I will try to update this one too.
> 
> 

I'm getting this error building 4.0.1 (available in git).

../src/utils.hpp:16:10: fatal error: mapnik/value/types.hpp: No such
file or directory
 #include 



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#906451: Bug#906451: Bug#906451: tar-pack seems an unmaintained module

[Pirate Praveen]

On 20/08/18 12:54 PM, Pirate Praveen wrote:
> On a second thought, since their builds also use node-pre-gyp, may be
> rebuilds are enough. Anyway, I have updated node-zipfile to latest
> upstream releases which supports this version of node-pre-gyp.
> 
> 

node-sqlite3 also updated. node-mapnik also has a new upstream release
that supports the new pre-gyp. I will try to update this one too.



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#844075: Bug#844075: Bug#844075: leaflet: Please provide the latest Leaflet package including a node module

[Pirate Praveen]

On 2018, ഓഗസ്റ്റ് 23 1:15:17 PM IST, Andreas Tille  wrote:
>Any news here?  I need to package r-cran-leaflet which has a code copy
>of leaflet 1.3.1.  I guess the recent upstream version 1.3.4 will be
>fine as well. 
>
>I gave the packaging a naive try imported the new version into leaflet
>Git[1] but ended up with:
>
> debian/rules build
>test -x debian/rules
>mkdir -p "."
>jake build
>jake aborted.
>Error: No Jakefile. Specify a valid path with -f/--jakefile, or place
>one in the current directory.
>at api.fail (/usr/lib/nodejs/jake/api.js:326:18)
>   at EventEmitter.utils.mixin.run (/usr/lib/nodejs/jake/jake.js:317:9)
>(See full trace by running task with --trace)
>make: *** [debian/rules:32: build/libjs-leaflet] Error 1
>dpkg-buildpackage: error: debian/rules build gave error exit status 2
>I: copying local configuration
>E: Failed autobuilding of package
>
>
>Thus I will not push my poor naive changes (which was basically
>importing the new version and removing the patch which was trying to
>fix
>a not existing Jakefile).  I have no experience with JS and thus will
>not be of any help at all.

They moved their build system to rollup (it is already packaged). The new build 
command is,

rollup -c build/rollup-config.js

From, package.json  -> scripts -> build

I can help if you want to learn JS packaging. My plate is full with gitlab node 
dependencies, so can't take more.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

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

[Pkg-javascript-devel] Bug#764614: this is still failing

[Pirate Praveen]

Control: forcemerge 904071 -1

pravi@andhaka:/tmp/lirc$ npm install --production lirc
npm WARN deprecated coffee-script@1.12.7: CoffeeScript on NPM has moved
to "coffeescript" (no hyphen)
npm WARN deprecated coffee-script@1.6.3: CoffeeScript on NPM has moved
to "coffeescript" (no hyphen)
npm WARN deprecated coffee-script@1.5.0: CoffeeScript on NPM has moved
to "coffeescript" (no hyphen)
npm WARN deprecated graceful-fs@1.1.14: please upgrade to graceful-fs 4
for compatibility with current and future versions of Node.js
npm WARN notice [SECURITY] lactate has the following vulnerability: 1
high. Go here for more details:
https://nodesecurity.io/advisories?search=lactate=0.13.12 - Run
`npm i npm@latest -g` to upgrade your npm version, and then `npm audit`
to get more info.
npm ERR! write after end
npm WARN notice [SECURITY] ws has the following vulnerabilities: 2 high,
1 low. Go here for more details:
https://nodesecurity.io/advisories?search=ws=0.4.32 - Run `npm i
npm@latest -g` to upgrade your npm version, and then `npm audit` to get
more info.
npm ERR! write after end
npm WARN notice [SECURITY] uglify-js has the following vulnerability: 2
low. Go here for more details:
https://nodesecurity.io/advisories?search=uglify-js=2.2.5 - Run
`npm i npm@latest -g` to upgrade your npm version, and then `npm audit`
to get more info.
npm ERR! write after end
npm ERR! write after end

npm ERR! A complete log of this run can be found in:
npm ERR! /home/pravi/.npm/_logs/2018-07-19T06_34_47_019Z-debug.log



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#904071: npm install fails to install development dependencies

[Pirate Praveen]

package: npm
version: 5.8.0-1
severity: important

pravi@andhaka:/tmp/node_modules/pretty-ms$ npm install --production
npm notice created a lockfile as package-lock.json. You should commit
this file.
added 1 package from 1 contributor in 6.715s


   ╭─╮
   │ │
   │   Update available 5.8.0 → 6.2.0│
   │   Run npm i npm to update   │
   │ │
   ╰─╯

pravi@andhaka:/tmp/node_modules/pretty-ms$ npm install
npm ERR! write after end
npm ERR! write after end
npm ERR! write after end
^C



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#763040: npm: "npm help " is broken

[Pirate Praveen]

Control: fixed -1 5.8.0+ds-1

On Sat, 27 Sep 2014 15:06:02 +0200 Tobias Hoffmann
 wrote:
> npm help  is supposed to show the man page npm-,
> but it only shows the list of more-or-less matching commands
> (which basically says: type "npm help " to get more help).

It works with the last uploaded version.



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] Bug#764614: this is still failing

[Pirate Praveen]

On 19/07/18 12:16 PM, Pirate Praveen wrote:

> pravi@andhaka:/tmp/lirc$ npm install --production lirc

npm i lactate
npm WARN notice [SECURITY] lactate has the following vulnerability: 1
high. Go here for more details:
https://nodesecurity.io/advisories?search=lactate=0.13.12 - Run
`npm i npm@latest -g` to upgrade your npm version, and then `npm audit`
to get more info.
npm ERR! write after end

Though, each of its dependencies can be installed successfully. lactate
is a dependency of lirc.



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#780789: fixed in last upload

[Pirate Praveen]

Control: fixed -1 5.8.0+ds-1

Works with last upload of npm 5.8.0



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] npm_1.4.21+ds-2~bpo9+1_amd64.changes REJECTED

[Pirate Praveen]

On 2018, ഓഗസ്റ്റ് 31 6:30:17 PM IST, Alexander Wirt 
 wrote:
>
>Where is that version from? Testing has 5.8.0?

This version was in Debian for about 3+ years. It was removed before the 
stretch release because it could not be updated in time for stretch. But now 
new version is available in buster.

This would be helpful to get gitlab to stretch-backports. gitlab in contrib 
uses this version of npm to install yarn and then uses yarn to install the 
dependencies.

Getting npm 5.8 to stretch-backports is going to be much more work. Many new 
dependencies and core packages like babel will need to be back ported.
>
>
>
>===
>
>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.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

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

Re: [Pkg-javascript-devel] npm_1.4.21+ds-2~bpo9+1_amd64.changes REJECTED

[Pirate Praveen]

[Resending from another id]

On 2018, സെപ്റ്റംബർ 1 8:32:08 AM IST, Pirate Praveen  wrote:
>
>
>On 2018, ഓഗസ്റ്റ് 31 6:30:17 PM IST, Alexander Wirt
> wrote:
>>
>>Where is that version from? Testing has 5.8.0?
>
>This version was in Debian for about 3+ years. It was removed before
>the stretch release because it could not be updated in time for
>stretch. But now new version is available in buster.
>
>This would be helpful to get gitlab to stretch-backports. gitlab in
>contrib uses this version of npm to install yarn and then uses yarn to
>install the dependencies.
>
>Getting npm 5.8 to stretch-backports is going to be much more work.
>Many new dependencies and core packages like babel will need to be back
>ported.
>>
>>
>>
>>===
>>
>>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.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

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

Re: [Pkg-javascript-devel] Thank you for ‘npm’ in Debian!

[Pirate Praveen]

On 2018, സെപ്റ്റംബർ 5 9:29:37 PM IST, Ross Gammon  
wrote:
>I can try and help out with a few node-* backports. But work is keeping
>me busy, so progress would be slow. If it is a team effort, we probably
>need a list. Or use the ITP tracker on Gitlab?

Thanks! I think we can use the salsa wiki for npm package. If someone with 
python knowledge can modify the task tracker script, that would be better.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

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

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

[Pirate Praveen]

On 06/09/18 10:15 AM, Pirate Praveen wrote:
> I suggest we categorize the packages in NEW and process accordingly. I can 
> help with categorizing it.
> 
> I propose the following,
> 
> 1. Simple modules that could be embedded - REJECT.
> 2. Modules that includes a build step, for example that needs babel, webpack 
> etc. (Modules that will produce a source is missing lintian error). I think 
> those packages would be better in their own package as it will make embedding 
> more complicated to maintain - ACCEPT
> 3. A module that is a dependency or build dependency of more than 3 packages 
> (arbitrary, could be 5 as well) - ACCEPT
> 

I have started this categorization here,

https://wiki.debian.org/Javascript/Nodejs/NEW



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Pirate Praveen]

On April 13, 2018 10:02:25 PM GMT+05:30, Paolo Greppi  
wrote:
>> 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 was thinking of yarn-installer as a separate package, because I want it in 
stretch as well.

>> I am ready to give it a try.
>> 
>> The missing dependencies can be individually npm install-ed.

But we have no npm in stretch...

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

I think we will have to just wget the dist tarballs, extract and copy it to 
node_modules, as we can't depend on npm in stretch.

node_modules will have to be in /var/lib and a symlink can be in 
/usr/lib/nodejs/yarn.

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

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

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

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

[Pirate Praveen]

On ബു, ഏപ്രി 18, 2018 at 12:55 വൈകു, Paolo Greppi 
 wrote:
if there is a consensus in the js-team I can perform the mass 
migration.




Thanks! I think you can go ahead, unless someone object to it.


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

Re: [Pkg-javascript-devel] RFS: node-make-iterator + node-object.map

[Pirate Praveen]

On ചൊവ്വ 10 ഏപ്രിൽ 2018 03:11 രാവിലെ, Paolo Greppi wrote:
> 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.

Uploaded. For debhelper > 10, we can remove dh-buildinfo build dep (I
made this change to both).




signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] RFS: node-detect-file 1.0.0, node-resolve-dir 1.0.1 and node-flagged-respawn 1.0.0

[Pirate Praveen]

On ബുധന്‍ 11 ഏപ്രിൽ 2018 04:08 വൈകു, Paolo Greppi wrote:
> 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

Granted you DM access for all 3.



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Pirate Praveen]

On വെള്ളി 06 ഏപ്രിൽ 2018 10:43 വൈകു, Paolo Greppi wrote:
> 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.

Uploaded, thanks!



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] RFS: node-yn

[Pirate Praveen]

On വെള്ളി 06 ഏപ്രിൽ 2018 10:51 വൈകു, Paolo Greppi wrote:
> 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.

Uploaded, thanks!



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#909753: fails to find binary package

[Pirate Praveen]

On Thu, 27 Sep 2018 12:51:58 -0400 =?utf-8?Q?Antoine_Beaupr=C3=A9?=
 wrote: > FWIW, I've also submitted this as a merge
request in salsa.

Thanks for the patch. As this is not a native debian package, can you
send the pull request to https://github.com/LeoIannacone/npm2deb or
modify the existing merge request as a quilt patch (in case you don't
like to use github)?

> The "-S" does not help here: it would show binary packages if we
> somehow magically found the right source package, but not the
> reverse.

For the majority of packages created by npm2deb, the source package name
is always node-, but as you found out, not all packages
follow this scheme and there is the case of babel, where one source
package creates a lot of binary packages. We were simple not aware of a
better solution and thanks for figuring out the correct solution.



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] node-axios_0.16.2+dfsg-1_amd64.changes REJECTED

[Pirate Praveen]

On 10/12/18 1:31 AM, Thorsten Alteholz wrote:
> 
> this package depends on software that needs to be embedded and has some 
> lintian E:

Fixed and reuploaded



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] node-autoprefixer_7.2.5-1_amd64.changes REJECTED

[Pirate Praveen]

On 10/14/18 2:30 AM, Thorsten Alteholz wrote:
> 
> Hi,
> 
> package depends on software (node-num2fraction) that should be embedded.

Fixed and reuploaded.

>   Thorsten
> 
> 
> 
> ===
> 
> 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.
> 
> 



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#911338: Bug#911338: node-webpack: new upstream version 4.21.0 available

[Pirate Praveen]

On 2018, ഒക്‌ടോബർ 19 1:00:05 AM IST, Daniel Kahn Gillmor 
 wrote:
>Source: node-webpack
>Version: 3.5.6-3
>Severity: wishlist
>Control: affects -1 src:gpgme1.0
>Control: block 911189 by -1
>
>https://github.com/webpack/webpack/archive/v4.21.0.tar.gz is available
>upstream.
>
>The debian package for webpack has not been updated since 2018-03-08.
>
>I'm trying to use webpack to build the GPGME javascript bindings (see
>https://bugs.debian.org/911189), and that package uses webpack to
>bundle its javascript.
>
>but when i try to build it using the "webpack" binary in unstable, i
>see errors like so:
>
>---
>0 dkg@sid:~/src/gpgme/gpgme/lang/js$ npx webpack --config
>webpack.conf_unittests.js 
>Invalid configuration object. Webpack has been initialised using a
>configuration object that does not match the API schema.
>- configuration has an unknown property 'mode'. These properties are
>valid:
>object { amd?, bail?, cache?, context?, dependencies?, devServer?,
>devtool?, entry, externals?, loader?, module?, name?, node?, output?,
>parallelism?, performance?, plugins?, profile?, recordsInputPath?,
>recordsOutputPath?, recordsPath?, resolve?, resolveLoader?, stats?,
>target?, watch?, watchOptions? }
>   For typos: please correct them.
>For loader options: webpack 2 no longer allows custom properties in
>configuration.
>Loaders should be updated to allow passing options via loader options
>in module.rules.
>Until loaders are updated one can use the LoaderOptionsPlugin to pass
>these options to the loader:
> plugins: [
>   new webpack.LoaderOptionsPlugin({
> // test: /\.xxx$/, // may apply this only for some modules
> options: {
>   mode: ...
> }
>   })
> ]
>1 dkg@sid:~/src/gpgme/gpgme/lang/js$ 
>---
>
>I suspect this is due to webpack being out of date in debian unstable.
>
>(I can comment out the offending "mode: 'production'" lines from
>webpack.conf.js as a workaround, but it looks like upstream expects a
>modern version of webpack)
>
>Thanks for maintaining webpack in debian!

The easiest option would be to adapt configuration for webpack 3. I briefly 
looked into updating webpack to 4 and it will require updating babel to 7 as 
well. If there is more people interested in helping I can join them else I will 
wait till more packages need webpack 4.

My main motivation in packaging webpack was gitlab. Even though it wants 
webpack 4, I have to package a lot more dependencies before I can use packaged 
versions (currently gitlab is in contrib as I pull the dependencies from 
npmjs.com in postinst). So my webpack 4 need is not urgent, but if more people 
join I can work on it.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

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

Re: [Pkg-javascript-devel] Comments regarding node-caniuse-api_2.0.0-1_amd64.changes

[Pirate Praveen]

On 10/12/18 1:33 AM, Thorsten Alteholz wrote:
> Hi,
> 
> can you please tell me where I can find the build-dependency: bablejs?

node-babel-cli provides babeljs
https://salsa.debian.org/js-team/node-babel/blob/master/debian/control#L57

$ apt-cache search babeljs
node-babel-cli - Babel command line

> Thanks!
>  Thorsten
> 
> 



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] node-knockout_3.4.2-1_amd64.changes REJECTED

[Pirate Praveen]

On 10/12/18 2:30 AM, Thorsten Alteholz wrote:
> 
> Hi Daniel,
> 
> please also mention at least the BSD license in your debian/copyright,

Fixed and reuploaded



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] node-libnpx_9.7.1-1_amd64.changes REJECTED

[Pirate Praveen]

On 10/12/18 1:31 AM, Thorsten Alteholz wrote:
> 
> this package depends on software that needs to be embedded 

Fixed and reuploaded.



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] babel 6 -> 7 transition - call for help

[Pirate Praveen]

Hi team,

Webpack 3 -> 4 update was requested recently which needs babel 7. In
addition to it, esm needs (which will allow us to skip rollup for ES
modules to help fix many circular dependencies) babel 7, gitlab also
needs babel 7.

I started working on the update and just looked at the devDependencies,
it needs browserify, webpack, rollup and gulp to build! This is new
record even by node's own standard!

Luckily we have a recent enough nodejs in unstable and we can skip most
of the transpilation steps (tested with acorn) but it requires a manual
conversion of ES modules to CJS. It is sad to see native support for ES
modules remaining experimental for ever in nodejs.

Let me know if anyone feel brave enough to join this effort.

Thanks
Praveen




signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] babel 6 -> 7 transition - call for help

[Pirate Praveen]

On 10/23/18 7:06 PM, Pirate Praveen wrote:
> I started working on the update and just looked at the devDependencies,
> it needs browserify, webpack, rollup and gulp to build! This is new
> record even by node's own standard!

It seems webpack is used only for babel-standalone so I have patched out
its usage for now.

I have embedded all new build dependencies and got this far,

/<>/Gulpfile.js:121
gulp.task("default", gulp.series("build"));
  ^

TypeError: gulp.series is not a function
at Object. (/<>/Gulpfile.js:121:27)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at Liftoff.handleArguments (/usr/lib/nodejs/gulp/bin/gulp.js:119:3)
at Liftoff. (/usr/lib/nodejs/liftoff/index.js:198:16)
make[3]: *** [Makefile:13: build] Error 1

Looks like I need to update gulp to 4.x So another transition to go with
this.



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] node-react_16.2.0-2_amd64.changes REJECTED

[Pirate Praveen]

On 10/25/18 1:42 AM, Bastian Blank wrote:
> 
> node-react is split in two binary packages: node-react and node-react-dom.
> Both binary packages have the same dependencies, nor are they large, so there
> is no reason to split them.

I have combined the two and reuploaded.
> 
> 
> 
> ===
> 
> 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.
> 
> 




signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] node-react_16.2.0-2_amd64.changes REJECTED

[Pirate Praveen]

On 2018, ഒക്‌ടോബർ 26 5:12:06 PM IST, Pirate Praveen  
wrote:
>On 10/25/18 1:42 AM, Bastian Blank wrote:
>> 
>> node-react is split in two binary packages: node-react and
>node-react-dom.
>> Both binary packages have the same dependencies, nor are they large,
>so there
>> is no reason to split them.
>
>I have combined the two and reuploaded.

This upload was rejected. Please reject 16.2.0-1 as well so I can upload it 
again.
>> 
>> 
>> 
>> ===
>> 
>> 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.
>> 
>> 

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

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

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

[Pirate Praveen]

On 10/28/18 2:22 PM, Jérémy Lal wrote:
> Try
> require('gyp')

But gyp and node-gyp are two different modules.

/usr/share/node-gyp/package.json says name is node-gyp, so
require('node-gyp') is expected to work.



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] node-react_16.2.0-2_amd64.changes REJECTED

[Pirate Praveen]

On 10/26/18 6:53 PM, Bastian Blank wrote:
> On Fri, Oct 26, 2018 at 06:43:38PM +0530, Pirate Praveen wrote:
>>> I have combined the two and reuploaded.
>> This upload was rejected. Please reject 16.2.0-1 as well so I can upload it 
>> again.
> 
> Please upload -3

Uploaded.

> Bastian
> 




signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] Thank you for ‘npm’ in Debian!

[Pirate Praveen]

On 9/16/18 5:10 PM, Ross Gammon wrote:
> Hi Praveen,
> 
> Hmm. No ideas for bluebird here really, other than bundling a pre-built
> acorn npm node_module style.

I just uploaded node-bluebird and acorn to stretch-backports. As
mentioned earlier, acorn source was converted to CJS modules with a
patch from Ashutosh instead of using rollup to convert them.

> What is the hold up with rollup? I was looking into rollup/acorn in
> Ubuntu, and things have got very messy there. None of them will build
> without the right version of each other. It looks like a messed up
> transition in Debian. We should probably sort things out in Debian first!

rollup conversion to cjs is also in progress, most of the work is
completed by Ashutosh and it needs fixing some issues that popped up
when building other packages (rollup command itself works).



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] New javascript packages for taliesin

[Pirate Praveen]

On 2018, നവംബർ 11 7:13:47 PM IST, Nicolas Mora  wrote:
>Hello,
>
>I'm working on packaging Taliesin, an audio streaming server with a
>front-end written in react [1].

Welcome to javascript  team.

>To build the front-end, I need some new node packages. I've already
>starting packaging some of them, but I prefer asking the javascript
>team
>about it first, to make sure I'm making it right.

That is a good approach. We have some very recent changes in policy which is 
yet to be documented clearly.

>Among the required new packages, there are
>i18next-browser-languagedetector and i18next-xhr-backend that require
>the packages serialize-javascript [2] and jest-worker.

If a module is simple (no build steps) then it should be embedded.

>I've already packaged those last 2 and uploaded them to mentors.d.n.
>But
>then I saw that a package node-jest is already in preparation so I can
>offer my help to package node-jest instead.

Just have a look at the repo in salsa.

>I also made a new package for node-i18next. There's already a package
>libjs-i18next but the version is quite old (1.7.1) when the current
>version is 12.0.0.

We should try to update the existing package.

>Another package in mentors.d.n is react-audio-player [3], a wrapper for
>the html  tag binded with react.
>
>Among the other packages I need, there are some that are easy, like
>react-i18next, but some others will probably be difficult to build,
>considering their dependencies. I'm thinking about react-bootstrap and
>redux especially. I've started to package them and their dependencies.

Embed the simple one.

>I'm also willing to help the javascript with other packages than the
>ones I need if you want.

Yes, that would be good. Getting jest and ava would be good.

>Thanks in advance for your help and advises.

Happy to help. You can come to our irc channel as well for real time help.

>/Nicolas
>
>[1] - https://salsa.debian.org/babelouest-guest/taliesin
>[2] - https://mentors.debian.net/package/node-serialize-javascript
>[3] - https://mentors.debian.net/package/node-react-audio-player
>
>-- 
>Pkg-javascript-devel mailing list
>Pkg-javascript-devel@alioth-lists.debian.net
>https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

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

Re: [Pkg-javascript-devel] New javascript packages for taliesin

[Pirate Praveen]

On 2018, നവംബർ 11 11:07:04 PM IST, Bastien ROUCARIES 
 wrote:
>On Sun, Nov 11, 2018 at 5:15 PM Pirate Praveen
> wrote:
>Not embded use group source feature of git uscan please.
>

I don't think grouping unrelated packages is a good idea. If there is a 
circular dependency or related projects, then its OK. It is making things 
unnecessarily complex.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

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

[Pkg-javascript-devel] Bug#913813: Bug#913813: node-tar : Depends: node-yallist (>= 3.0.2~) but 2.0.0-1 is to be installed

[Pirate Praveen]

On 2018, നവംബർ 15 9:01:15 PM IST, Mathieu Malaterre  wrote:
>The following information may help to resolve the situation:
>
>The following packages have unmet dependencies:
>node-tar : Depends: node-yallist (>= 3.0.2~) but 2.0.0-1 is to be
>installed
>E: Unable to correct problems, you have held broken packages.

It in NEW for last 2 weeks.

https://ftp-master.debian.org/new/node-yallist_3.0.2-1~bpo9+1.html


-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

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

[Pkg-javascript-devel] Bug#913812: Bug#913812: node-boxen : Depends: node-camelcase (>= 4.0.0) but 3.0.0-1 is to be installed

[Pirate Praveen]

On 2018, നവംബർ 15 8:54:58 PM IST, Mathieu Malaterre  wrote:
>The following information may help to resolve the situation:
>
>The following packages have unmet dependencies:
>node-boxen : Depends: node-camelcase (>= 4.0.0) but 3.0.0-1 is to be
>installed
>E: Unable to correct problems, you have held broken packages.

It is in NEW for last 2 weeks

https://ftp-master.debian.org/new/node-camelcase_4.1.0-1~bpo9+1.html
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

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

Re: [Pkg-javascript-devel] New javascript packages for taliesin

[Pirate Praveen]

On 2018, നവംബർ 14 12:08:30 AM IST, Nicolas Mora  wrote:
>I don't think either that making a group package for such small 
>dependencies is a good idea to build other javascript packages.
>
>Concerning jest, I've created a merge request in the current salsa repo
>
>to complete the node-jest package. [1]
>The package now builds with success with all jest packages included.

I'll check it soon.

>Lintian complains about the script jest-cli/jest.js that is not 
>executable and I haven't figured out why yet.

You can chmod +x it in override_dh_fixperms target in rules.

>But the remaining problem in order to complete node-jest is to package 
>some of its dependencies.
>
>I'm currently making a package for istanbuljs that is a meta package 
>like jest and some of its modules are required for node-jest-cli.

I think Istanbul is already in NEW.

>Another issue with jest is the package node-babel-code-frame which is 
>required for node-jest-message-util. Currently the package node-babel
>in 
>unstable is 6.26 but I see in salsa that node-babel 7 is in progress to
>
>be packaged. I also can ask upstream if babel 6.26 is enough for this 
>module to work.

babel 7 needs a lot of work, it needs gulp 4 and probably more. If it can work 
with babel 6, that would be best. If not we should complete babel 7. Help is 
always welcome. Gulp 4 needs updating many of its dependencies.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

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

Re: [Pkg-javascript-devel] New javascript packages for taliesin

[Pirate Praveen]

On 2018, നവംബർ 14 8:11:39 PM IST, Bastien ROUCARIES 
 wrote:
>On Wed, Nov 14, 2018 at 3:09 PM Pirate Praveen
> wrote:

>No it is nyc. So we need to package nyc

Can't we just patch and skip these? Style checks can be skipped for Debian 
package I think.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

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

Re: [Pkg-javascript-devel] Thank you for ‘npm’ in Debian!

[Pirate Praveen]

On 2018, സെപ്റ്റംബർ 16 5:10:00 PM IST, Ross Gammon  
wrote:
>What is the hold up with rollup? I was looking into rollup/acorn in
>Ubuntu, and things have got very messy there. None of them will build
>without the right version of each other. It looks like a messed up
>transition in Debian. We should probably sort things out in Debian
>first!

Just uploaded rollup with cjs patch by Ashutosh. This fixes both rc bugs and 
clears way for getting rollup to enter testing after a long stay in unstable 
only state. This does not depend on itself making bootstrapping easier.

And npm itself is in backports  NEW.

Thanks also to Gitlab Inc for sponsoring Ashutosh's work which made both of 
these possible.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

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

Re: [Pkg-javascript-devel] New javascript packages for taliesin

[Pirate Praveen]

On 2018, നവംബർ 14 7:23:24 PM IST, Nicolas Mora  wrote:
>Le 2018-11-14 05:43, Pirate Praveen a écrit :
>Also, I just realized that the script jest/bin/jest.js contains this 
>simple code:
>
>require('jest-cli/bin/jest');
>
>So I think we should remove the file debian/links and add a file 
>debian/node-jest-cli.links instead that will contain the following:
>
>usr/lib/nodejs/jest-cli/bin/jest.js usr/bin/jest
>
>What do you think?

Test it and see if it is working. Also we may need to move all jest modules to 
a single binary package and add Provides for others.

>>> I'm currently making a package for istanbuljs that is a meta package
>>> like jest and some of its modules are required for node-jest-cli.
>> 
>> I think Istanbul is already in NEW.
>> 
>Yes, I saw that, but that the package node-istanbul in NEW comes from 
>github.com/gotwarlost/istanbul [1], and the one required by jest are 
>node-istanbul-lib-coverage, node-istanbul-lib-instrument and 
>node-istanbul-lib-source-maps, which are in 
>github.com/istanbuljs/istanbul
>
>I think they are not the same...
>
>I shall call my new package node-istanbuljs to avoid confusion.

OK.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

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

[Pkg-javascript-devel] Bug#876618: Bug#876618: science.js build-depends on removed nodejs-legacy

[Pirate Praveen]

On 2018, സെപ്റ്റംബർ 28 10:52:24 AM IST, Petter Reinholdtsen  
wrote:
>
>vows test/env-assert.js test/\*/\*-test.js
>module.js:549
>throw err;
>^
>
>Error: Cannot find module 'glob'

Just add node-glob as build dependency.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

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

[Pkg-javascript-devel] Bug#907686: npm2deb: chokes on parsing mocha when locale is C

[Pirate Praveen]

On 2018, ഓഗസ്റ്റ് 31 4:57:54 PM IST, Jonas Smedegaard  wrote:
>Package: npm2deb
>Version: 0.2.8-1
>Severity: normal
>
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA512
>
>Attempting to follow https://wiki.debian.org/Javascript/Nodejs/Tasks to
>resolve dependencies of node-server, in a limited environment (a
>cowbuilder chroot) with "C" a locale, caused the following failure:
>
>Traceback (most recent call last):
>  File "js_task_edit.py", line 230, in 
>main()
>  File "js_task_edit.py", line 213, in main
>build_deps = get_builddeps(module_name)
>  File "js_task_edit.py", line 161, in get_builddeps
>debian = get_debian(dep)
>  File "js_task_edit.py", line 80, in get_debian
>npm2deb_instance = _Npm2Deb(module_name)
>File "/usr/lib/python3/dist-packages/npm2deb/__init__.py", line 57, in
>__init__
>self.read_package_info()
>File "/usr/lib/python3/dist-packages/npm2deb/__init__.py", line 363, in
>read_package_info
>(self.name, self.version))
>  File "/usr/lib/python3.6/subprocess.py", line 517, in getstatusoutput
>data = check_output(cmd, shell=True, universal_newlines=True,
>stderr=STDOUT)
>  File "/usr/lib/python3.6/subprocess.py", line 336, in check_output
>**kwargs).stdout
>  File "/usr/lib/python3.6/subprocess.py", line 405, in run
>stdout, stderr = process.communicate(input, timeout=timeout)
>  File "/usr/lib/python3.6/subprocess.py", line 830, in communicate
>stdout = self.stdout.read()
>  File "/usr/lib/python3.6/encodings/ascii.py", line 26, in decode
>return codecs.ascii_decode(input, self.errors)[0]
>UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position
>26639: ordinal not in range(128)

See if setting LANG=C.UTF-8 fixes it. If not try LC_ALL=UTF-8.

Some node modules have metadata in Unicode and the locale should have UTF-8 
support.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

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

Re: [Pkg-javascript-devel] Remove package node-uuid? (Was: Update package node-uuid?)

[Pirate Praveen]

On 9/21/18 12:29 PM, W. Martin Borgert wrote:
> Hi,
> 
> in fact, uuid is already in Debian, even the relatively recent
> version 3.2.1, but embedded in the npm package. #895625 can just
> be closed, I assume.

It is embedded because node-uuid is not available. It should be dropped
when uuid 3.2.1 is available in the archive.

> Only the depends in node-request and the build depends in
> node-http-signature need to be changed from node-node-uuid to npm.
> Also, yarnpkg and libjs-jingle-session would need to depend on
> npm.

It is not a good idea for those packages to depend on npm for just uuid,
and moreover uuid is not exposed in usual path by npm.

> Or shall we instead remove uuid from npm and let it depend on
> node-uuid? npm is 275 times larger than node-node-uuid.

yes, once node-uuid is updated, npm can drop the embedded copy. Same for
node-request.

> Minor points:
> 
>  - node-request has the latest and freshest uuid release 3.3.2
>included in it's source package

Because node-node-uuid is still old and since you were already on it, I
did not want to update uuid first. It was in my plan to drop the
embedded copy once you update node-uuid.

>  - npm contains uuids README.md, which should be build from its
>source README_js.md using runmd (no ITP/RFP yet)

This should be handled by node-uuid.

>  - `require('uuid')` is deprecated and should be replaced with
>`require('uuid/[v1|v3|v4|v5]')` in node-request

I can see it is using the correct api.
lib/multipart.js:var uuid = require('uuid/v4')

>  - who needs libjs-node-uuid? can we drop the binary package?

I think it should be dropped.



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] Re: Shipping DefinitelyTyped definitions : one binary package per definition?

[Pirate Praveen]

On 2018, സെപ്റ്റംബർ 23 8:26:25 PM IST, Bastien ROUCARIES 
 wrote:
>types node should go to parent package. i means node-types-acorn
>should go to package node-acorn using fakeuptstream multiple tar
>improvement if needed
>

I think it is over engineering and making things unnecessarily complex. This 
can be a fallback option if a separate version of type definition is required 
instead of the centrally shipped version.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

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

Re: [Pkg-javascript-devel] Re: Shipping DefinitelyTyped definitions : one binary package per definition?

[Pirate Praveen]

On 9/24/18 2:09 PM, Bastien ROUCARIES wrote:
>> I think it is over engineering and making things unnecessarily complex. This 
>> can be a fallback option if a separate version of type definition is 
>> required instead of the centrally shipped version.
> And how to you keep version in sync ?

You always ship the latest in node-typescript-types package and ship
separate definitions only in case something don't work. I don't think we
have to keep it strictly in sync with the node modules. For example, we
have nodejs 8.11.2 but @types/node only has 8.10.x.



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] Re: Re: Shipping DefinitelyTyped definitions : one binary package per definition?

[Pirate Praveen]

On 2018, സെപ്റ്റംബർ 24 6:24:50 AM IST, Julien Puydt  
wrote:
>Hi,
>
>Le 23/09/2018 à 16:44, Pirate Praveen a écrit :
>> On 9/23/18 5:13 PM, Julien Puydt wrote:
>>> What do you think of the attached script? It assumes the upstream
>>> DefinitelyTyped tree is in "DefinitelyTyped.upstream" as it's the
>layout
>>> I use for my experiment, and generates a "control" file and a bunch
>of
>>> "node-types-*.install" files.
>> 
>> Did you check node-typescript-types source? It just downloads the
>> tarballs from npm registry. I think that is a better approach (only
>ship
>> the definitions we want instead of all) and instead of creating many
>> more binary packages, a provides should be sufficient (if at all
>required).
>> 
>
>Did you see the script was detecting which packages are in Debian, and 
>only then shipped them? Here I have:
>
>jpuydt@nox:~/Debian/DefinitelyTyped$ python3 build_control.py
>Reading package lists... Done
>Building dependency tree
>Reading state information... Done
>490 node-types-* generated and 4266 not considered

It'd add 490 new binary packages, which I don't think will make ftp masters 
happy.

Even this much is unnecessary I think. Instead of looking at a node package 
being in Debian as a criteria, I think we can add them only if a package 
actually build depend on it.

>so yes, the source tree has everything, but it's only packaging as 
>binary the necessary files...
>
>In my first mail I think proposed to ship what is really often a
>*single 
>file* within each package separately ; that sounds the least complex
>(no 
>need for fancy features in a fakeupstream, no need for a complex script
>
>to build thousands of packages...).

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

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

Re: [Pkg-javascript-devel] Re: Shipping DefinitelyTyped definitions : one binary package per definition?

[Pirate Praveen]

On 9/24/18 4:05 PM, Bastien ROUCARIES wrote:
> No it is quite easy with newer fakeupstream support. It a joy, Did you try ?

1. Well, we don't always use the fakeupstream. Most of the time it is
github tarballs.
2. It still involve manual effort in multiple packages rather than do it
once for all (and manual work only when necessary).



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] Re: Shipping DefinitelyTyped definitions : one binary package per definition?

[Pirate Praveen]

On 2018, സെപ്റ്റംബർ 24 2:28:00 PM IST, Bastien ROUCARIES 
 wrote:
>On Mon, Sep 24, 2018 at 10:43 AM Pirate Praveen
> wrote:
>>
>> On 9/24/18 2:09 PM, Bastien ROUCARIES wrote:
>> >> I think it is over engineering and making things unnecessarily
>complex. This can be a fallback option if a separate version of type
>definition is required instead of the centrally shipped version.
>> > And how to you keep version in sync ?
>>
>> You always ship the latest in node-typescript-types package and ship
>> separate definitions only in case something don't work. I don't think
>we
>> have to keep it strictly in sync with the node modules. For example,
>we
>> have nodejs 8.11.2 but @types/node only has 8.10.x.
>
>I believe it is quite fragile compared to
>https://wiki.debian.org/Javascript/GroupSourcesTutorial

I think the type definitions don't change for every js code change so its not 
as fragile. If it really change to breaking builds, then only we need to do the 
extra work of adding it to corresponding node package. Adding multiple tarballs 
is real pain and that has to be the last resort I think.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

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

Re: [Pkg-javascript-devel] status of acorn git repo - build is failing

[Pirate Praveen]

On 9/23/18 8:28 PM, Bastien ROUCARIES wrote:
> On Fri, Sep 21, 2018 at 4:53 PM Pirate Praveen  
> wrote:
>>
>> Hi,
>>
>> Can someone confirm if you can build acorn from git repo? I tried master
>> and debian/5.5.3+ds3-1 both failed.
> 
> Did you see it is a multiple tar ?

No. It did not have any README.Source and watch file had only a single
entry.



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] Shipping DefinitelyTyped definitions : one binary package per definition?

[Pirate Praveen]

On 8/10/18 2:58 AM, Bastien ROUCARIES wrote:
> 
> - just one node-types-definitelytyped real package would provide all
> necessary node-types-foo ones, so if a package needs the @types/foo, it
> can depend on node-types-foo and the right one is pulled in ;
> 
> 
> No

There is already such a package,
https://tracker.debian.org/pkg/typescript-types

What is the current status and how to proceed here?

I think one source package is perfect as it is only a build dependency
anyway.



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] Thank you for ‘npm’ in Debian!

[Pirate Praveen]

On 2018, സെപ്റ്റംബർ 16 5:16:39 PM IST, Pirate Praveen 
 wrote:
>On 16/09/18 5:10 PM, Ross Gammon wrote:
>> Hmm. No ideas for bluebird here really, other than bundling a
>pre-built
>> acorn npm node_module style.
>
>Ashutosh (https://github.com/juggernaut451) is trying to replace
>bluebird with ES6 native promise (though it will be slower).
>
>> What is the hold up with rollup? I was looking into rollup/acorn in
>> Ubuntu, and things have got very messy there. None of them will build
>> without the right version of each other. It looks like a messed up
>> transition in Debian. We should probably sort things out in Debian
>first!
>
>I think Julien is trying to update rollup to latest version (the
>current
>version can't build itself) but stuck with Definitely Typed situation
>(rollup moved to typescript).
>
>Julien, any update on the situation?

May be with this patch, we can drop the circular build dependency between acorn 
and rollup.

https://salsa.debian.org/juggernaut451-guest/acorn/blob/cjs/debian/patches/cjs.patch

May be with this version of acorn we can fix #892133

But we will need to include a prebuilt version of node-rollup-plugin-commonjs 8 
for #892742

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

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

Re: [Pkg-javascript-devel] Thank you for ‘npm’ in Debian!

[Pirate Praveen]

On 2018, സെപ്റ്റംബർ 22 8:24:47 PM IST, Ross Gammon  
wrote:
>I have merged all the previous stretch-backports commits, and rebased
>the backport onto the latest version in testing.
>
>Unfortunately, I get the same issue as before, and it won't build for
>me. Firstly, you have to use "--git-no-pristine-tar" as pristine tar
>doesn't seem to play well with pkg-components. Then, the build fails
>with (tail of buildlog):

I think you forgot to run uscan-components. 
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

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

[Pkg-javascript-devel] Bug#909424: update node-xterm to 3.x

[Pirate Praveen]

Package: node-xterm
version: 2.7.0+ds1-1
severity: wishlist

I'd like to get node-xterm >= 3.5 for gitlab. I have started working on
the update, but it requires updating node-typescript-types with more
type definitions or simple embed it inside the package directly.



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] Shipping DefinitelyTyped definitions : one binary package per definition?

[Pirate Praveen]

On 9/22/18 5:17 PM, Bastien ROUCARIES wrote:
> No because it is source included. How do you take care of version hell

If a package needs a different version of type definition that shipped
in node-typescript-types, the module should be updated or type
definition should be embedded.



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] Re: Shipping DefinitelyTyped definitions : one binary package per definition?

[Pirate Praveen]

On 9/23/18 5:13 PM, Julien Puydt wrote:
> What do you think of the attached script? It assumes the upstream
> DefinitelyTyped tree is in "DefinitelyTyped.upstream" as it's the layout
> I use for my experiment, and generates a "control" file and a bunch of
> "node-types-*.install" files.

Did you check node-typescript-types source? It just downloads the
tarballs from npm registry. I think that is a better approach (only ship
the definitions we want instead of all) and instead of creating many
more binary packages, a provides should be sufficient (if at all required).



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] acorn porting to es5

[Pirate Praveen]

On 2018, സെപ്റ്റംബർ 25 3:14:55 PM IST, ashutosh singh  
wrote:
>Hello
>
>I am porting acorn to es5 as currently it's using rollup to convert
>from
>es6 to es5. As next step would be compiling bluebird with this es5
>version.
>I am able to build the bluebird with it.

Basic idea is,
If we convert es6 import/export to commonjs  require syntax, we could skip 
rollup and use the rest of es6 syntax directly in nodejs.

Once rollup is removed from the situation, we can build bluebird in 
stretch-backports easily.

> Need little help to verify
>that i
>am doing the correct way as i am new to debian family.

Push it to salsa so we can check.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

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

Re: [Pkg-javascript-devel] Feasibility of GitLab as a Debian package (was: Heads up: Likely scaling back on my involvement in JavaScript team)

[Pirate Praveen]

On 12/28/18 10:58 AM, Ben Finney wrote:
> Pirate Praveen  writes:
> 
>> I started getting involved in JavaScript team to keep diaspora and
>> gitlab packages in main.
> 
> (I am very grateful to your work, not only in package maintenance but
> also in providing a focus for the work of many others in the JavaScript
> team.)

Thanks.

>> Gitlab was included in stretch but it is proposed to be removed from
>> buster. [1]
> 
> An exchange from that bug report discussion:
> 
> Pirate Praveen:
> > [I am trying to find] other ways to accommodate fast changing
> > software like gitlab. Broadening the definition of backports is
> > one possible option I see. Another option could be to have
> > personal package archive for gitlab.
> 
> Thorsten Glaser:
> > Find a way to pick stable, slow changing versions of it and
> > improve their packaging in testing/unstable so you can backport
> > it.
> >
> > Work with upstream towards that goal. Some upstreams are receptive
> > of stabilising certain versions in order to get packaged.
> >
> > If [the ‘gitlab’ package] upstreams aren’t, they’re probably not
> > worth the effort using the software.
> 
> Pirate, to what extent do you agree with Thorsten's assessment?

I think that is just living in denial. I think it was pointed out by
many how silly that argument is because debian itself is using gitlab as
a core component of its development infrastructure. So I don't think the
pace of development has nothing to do with whether a software is useful
or not.

> How broadly does this apply to JavaScript software, or how narrowly is
> this applicable to only GitLab? Or some other extent?

This is specific to gitlab. It uses a large number of node/javascript
modules and if there is no official gitlab package in debian, then there
is no motivation to keep packaging them. If gitlab itself need to be
obtained from an unofficial repo, then it should be fine to get these
node modules from npmjs.com as well.

>> I proposed a redefined volatile archive that can accommodate packages
>> like gitlab. I hope it gets accepted.
> 
> Dominik George mentions (also in that bug report discussion) he hopes to
> bring a propsed redefinition also. I hope that this can be a help to
> package maintainers.

I hope too, this proposal can go through.

> My concern, though, is that GitLab is just one example of the JavaScript
> developer community being particularly hostile – more than merely
> uninterested, but actively working to fight against – long-term stable
> releases with ongoing maintenance. GitLab is an example of this, and I
> wonder to what extent this is true for *most* JavaScript software that
> we would like available as Debian packages.

There is a difficulty in packaging javascript/node packages in general,
but this particular situation is specific to gitlab as a single project.
Each of those node modules could be included in stable and hence in
backports.

> If that is true, I think moving such software into a special
> low-stability, short-term-maintenance section is not part of a solution,
> only covering up a problem that needs to be fixed by working with
> upstream to improve release and maintenance practices.
> 

I think its too naive to think only our development model is right and
we can convert everyone else.



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] Thank you for ‘npm’ in Debian!

[Pirate Praveen]

On 11/9/18 7:00 PM, Pirate Praveen wrote:
> And npm itself is in backports  NEW.
> 
> Thanks also to Gitlab Inc for sponsoring Ashutosh's work which made both of 
> these possible.
> 

npm is now available in stretch-backports!



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Re: [Pkg-javascript-devel] Update policy for Buster

[Pirate Praveen]

On 2018, ഡിസംബർ 30 1:56:54 PM IST, Xavier  wrote:
>Hi all,
>
>while buster freeze comes,
>https://udd.debian.org/dmd/?pkg-javascript-devel%40lists.alioth.debian.org
>shows that:
> - more than 60 RC bugs have to be fixed
> - the majority of our packages are outdated or obsolete
>
>I think we should - at least until buster freeze - have a "salvage"
>policy.
>Some ways:
> - declare JS team as "Low Threshold Nmu" [1]
> - organize some online hacking parties to release "team uploads"
>   regardless uploader name
>

I think that is how it already is for team maintained packages.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

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

Re: [Pkg-javascript-devel] Bug#917750: node-redis: FTBFS: tests failed

[Pirate Praveen]

On 2018, ഡിസംബർ 30 1:32:47 PM IST, Xavier  wrote:
>Hello,
>
>node-redis seems also out-of-date. Would you accept co-maintenance on
>this package ?
>

It is already listed as team maintained. I don't think we need to ask every 
uploader separately.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

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

Re: [Pkg-javascript-devel] RFS: node-extend-shallow 3.0.2

[Pirate Praveen]

On 1/3/19 3:49 AM, Paolo Greppi wrote:
> Hi, I have refreshed the update to node-extend-shallow from 3.0.1 to 3.0.2 
> for which I RFS some months ago:
> https://alioth-lists.debian.net/pipermail/pkg-javascript-devel/2018-April/025963.html
> 
> It is required to update node-micromatch to 3.1.10, see:
> https://salsa.debian.org/js-team/node-micromatch/wikis/home
> which in turn is required to update node-findup-sync to 2.0.0 and 
> node-liftoff to 2.5.0 see:
> https://salsa.debian.org/js-team/node-liftoff/wikis/home
> 
> Please someone allow me DM upload access for this package or sponsor the 
> upload:
> https://salsa.debian.org/js-team/node-extend-shallow

DM access granted.



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

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

[Pirate Praveen]

Package: nodejs
severity: important


Since upstream nodejs comes with npm, people installing nodejs in debian
expect npm to be available.



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Bug#918388: fixed in nodejs 10.15.0~dfsg-8

[Pirate Praveen]

[asking -release]

On 1/6/19 5:31 PM, Pirate Praveen wrote:
> Control: reopen -1
> 
> On Sun, 06 Jan 2019 10:34:48 + =?utf-8?b?SsOpcsOpbXkgTGFs?=
>  wrote:
>>* Suggests npm - because nodejs must not be blocked by it.
>>  Closes: #918388.
> 
> I don't think this reasoning is correct. gitlab recommends gitaly with
> the expectation that gitaly andd gitlab could be on different machines.
> ruby-rails currently recommends packages not even in the archive
> currently and it is not marked for auto removals for that.
> 
> I'd be happy to be proven wrong.
> 

Hi Release team,

Can you confirm if an rc bug in a packaged listed in recommends will
block testing migration of a package? (in this specific case, the fear
is that rc bug in npm will block nodejs testing migration).

Thanks
Praveen



signature.asc
Description: OpenPGP digital signature
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel