[Pkg-javascript-devel] Bug#892022: ITP: node-catty -- source file concatenator for Mapshaper

[Ross Gammon]

Package: wnpp
Severity: wishlist
Owner: Ross Gammon 
X-Debbugs-CC: debian-de...@lists.debian.org
X-Debbugs-CC: pkg-javascript-devel@lists.alioth.debian.org

* Package name    : node-catty
  Version : 0.0.8
  Upstream Author : Matthew Bloch 
* URL : https://github.com/mbloch/catty
* License : Expat
  Programming Lang: JavaScript
  Description : source file concatenator for Mapshaper

 Catty is the source file concatenator for Mapshaper.
 .
 Some features:
 .
 * Each source file lists its dependencies in a formatted comment. There
   is no manifest, unlike some other tools.
 * Concatenated files are (optionally) wrapped in a self-executing
   function, to protect the global namespace.
 * Catty can monitor source files and regenerate output files when a
   required source file changes.
 .
 Node.js is an event-based server-side JavaScript engine.

This package is a required dependency of node-chroma.js, which is a
new dependency of the latest version of node-carto.

This package will be maintained within the Debian JavaScript maintainers
team.

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

[Pkg-javascript-devel] Bug#826560: Nearly there with node-carto dependencies

[Ross Gammon]

Hi All interested,

Sorry - I am extremely busy at the moment.

I am nearly ready with chroma-js, which is the only remaining missing
dependency from what I can see.

I just need to package catty to make for a smooth build process for
chroma-js. Help with than one package would be good, as I probably won't
get back onto chroma-js for a few weeks.

Ross



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

Re: [Pkg-javascript-devel] Bug#870460: anyone working on npm?

[Ross Gammon]

Hi Diane,

https://wiki.debian.org/Javascript/Nodejs/Tasks/npm

As far as I know, people have been working on trying to get all the
missing packages packaged, and update the old ones. Unfortunately, I
have not had the time to help myself.

I am not sure if anyone else has tried building npm yet, but it is good
to know we are getting close.

I will let the other more active team members comment on how best to
incorporate your work.

Ross

On 01/24/2018 08:14 AM, Diane Trout wrote:
> Hello,
>
> I was looking to update zotero, which needs a newer npm.
>
> I was curious, so I tried building a npm using upstream's 5.6.0, and I
> have something that almost installs & runs.
>
> Several dependencies are out of date in Debian, and there's still a
> fair number of node_modules that don't seem to have a corresponding
> Debian package.
>
> Would it be worth sharing these changes? How would you prefer to
> receive / review them? There's a few issues I avoided that need some
> discussion. (Like they embed a copy of node-gyp, and several scripts
> hard code relative paths to that copy)
>
> I wanted to get in touch with people in the javascript team before
> slogging through updating the copyright file.
>
> Diane
> detrout on Debian IRC
> Debian Developer



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

Re: [Pkg-javascript-devel] node-postgres with pkg-components ?

[Ross Gammon]

Hi Jeremy,

On 12/30/2017 04:57 PM, Jérémy Lal wrote:
> Hi,
>
> i'd like to update node-postgres, however it relies upon many modules
> that are:
> - not already packaged
> - heavily used by only node-postgres, almost never by other packages
> - node-postgres rely upon specific version of them
>
> I wonder if current pkg-components is avanced enough to cover the
> "let's bundle some node_modules as multiple upstream tarballs" case.
>
> Do anyone has some experience with that ?
>

Sorry - I had not heard of it until just now. But reading the README, it
looks definitely worth playing with. I will probably give it a try on a
few packages where I have more "debatable" reasons for bundling (e.g.
proof of a working package before I try patching it to hell to work with
what modules/versions of modules we have in Debian).

Regards,

Ross

Ross

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

Re: [Pkg-javascript-devel] Grunt plugins not found by Grunt

[Ross Gammon]

Hi Ben,

This tripped me up too when packaging something that needed the
system-wide installed Tasks.

See if this helps:
https://wiki.debian.org/grunt

Ross
On 12/01/2017 05:18 AM, Ben Finney wrote:
> Howdy all,
>
> I am attempting to satisfy the build dependencies for a package using
> Grunt as its build system. The Grunt task is not finding the plug-ins
> installed by the Debian packages for those plug-ins.
>
> The ‘Gruntfile.js’ (attached to this message)
>
>
>  declares these plug-in
> dependencies with:
>
> grunt.loadNpmTasks('grunt-contrib-concat');
> grunt.loadNpmTasks('grunt-contrib-uglify');
>
> which are then referenced in the task definition:
>
> grunt.registerTask('default', ['connect', 'watch']);
> grunt.registerTask('build', ['concat', 'uglify']);
>
> So, I have these build dependencies in ‘debian/control’ (attached to
> this message) 
>
>
> :
>
> Build-Depends:
> grunt,
> node-grunt-contrib-concat,
> node-grunt-contrib-uglify,
> debhelper (>= 10~)
>
> and those packages are installed:
>
> $ aptitude search 'grunt-contrib' | grep '^i'
> i A node-grunt-contrib-concat - Concatenate files
> i A node-grunt-contrib-uglify - Minify JavaScript files with UglifyJS
>
> Yet, with those packages installed, Grunt complains the libraries are
> not installed:
>
> $ grunt build
> >> Local Npm module "grunt-contrib-concat" not found. Is it installed?
> >> Local Npm module "grunt-contrib-uglify" not found. Is it installed?
> Warning: Task "concat" not found. Use --force to continue.
>
> Aborted due to warnings.
>
> What have I done wrong? How is the Debian ‘grunt’ package not finding
> Grunt libraries installed by other Debian packages?
>
>
>

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

[Pkg-javascript-devel] Fwd: Request to Join Project Debian JavaScript Maintainers from Sebastien Badia (sbadia)

[Ross Gammon]

Hi Sebastien,

Welcome to the team.

If you haven't already, please read the team policy:

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

Cheers,

Ross



 Forwarded Message 
Subject:Request to Join Project Debian JavaScript Maintainers from
Sebastien Badia (sbadia)
Date:   Wed, 22 Nov 2017 13:10:23 +
From:   nore...@alioth.debian.org
To: deb...@the-gammons.net



Sebastien Badia (sbadia) has requested to join your project. 
You can approve this request here: 
https://alioth.debian.org/project/admin/users.php?group_id=100128 

Comments by the user:
Hello!

I'm trying to re-introduce rspamd inside Debian, the new version have new 
dependency on javascript library.

https://github.com/moisseev/D3Evolution
https://github.com/benkeen/d3pie
https://github.com/fooplugins/FooTable
https://github.com/HubSpot/humanize
https://github.com/ai/visibilityjs

I think that pkg-javascript is a better place than collab-maint to maintain 
theses libs, so here is my request to join the team :-)

Cheers,

Sebastien

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

[Pkg-javascript-devel] Bug#876937: missing build dependency

[Ross Gammon]

Control: tags -1 pending

Hi Petter,

I have just tested, and yes - adding node-mkdirp as a build dependency
fixes it.

Unfortunately I have to go out, but expect a team upload with the fix
from me later today.

Regards,

Ross



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

[Pkg-javascript-devel] Fwd: Request to Join Project Debian JavaScript Maintainers from Akhil Varkey (akhilvarkey-guest)

[Ross Gammon]

Hi Akhil,

Welcome to the team! I am sure Praveen pointed it out to you (and more),
but if you haven't already, please read the team policy:

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

Ross

 Forwarded Message 
Subject:Request to Join Project Debian JavaScript Maintainers from
Akhil Varkey (akhilvarkey-guest)
Date:   Fri, 27 Oct 2017 13:55:52 +
From:   nore...@alioth.debian.org
To: deb...@the-gammons.net



Akhil Varkey (akhilvarkey-guest) has requested to join your project. 
You can approve this request here: 
https://alioth.debian.org/project/admin/users.php?group_id=100128 

Comments by the user:
Hi Team,

I have packaged two node modules as part of satisfying npm(5.5.1) dependencies 
which were sponsored by Praveen and uploaded.

node-ssri (https://git.fosscommunity.in/akhilvarkey/node-ssri)
node-mutate-fs (https://git.fosscommunity.in/akhilvarkey/node-mutate-fs)

I request access to package more and continue to maintain the same.

Best Regards,
Akhil

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

Re: [Pkg-javascript-devel] Bug#877212: Bug#877212: node-d3-color: B-D npm not available in testing

[Ross Gammon]

On 10/04/2017 05:50 AM, Sean Whitton wrote:
> Hello Jérémy,
>
> On Tue, Oct 03 2017, Jérémy Lal wrote:
>
>> It might be a good idea to make policy more explicit about downloads
>> during build.
> I'm not sure how it could be more explicit:
>
> For packages in the main archive, no required targets may attempt
> network access.
>
>

Some people could read "in the main archive" as not applying to contrib
& non-free?
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Fwd: Request to Join Project Debian JavaScript Maintainers from Preyass Chandran (preyassc-guest)

[Ross Gammon]

Welcome to the team. If you haven't already, please read the Team Policy
& linked pages on Nodejs:

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



 Forwarded Message 
Subject:Request to Join Project Debian JavaScript Maintainers from
Preyass Chandran (preyassc-guest)
Date:   Mon, 02 Oct 2017 06:28:32 +
From:   nore...@alioth.debian.org
To: deb...@the-gammons.net



Preyass Chandran (preyassc-guest) has requested to join your project. 
You can approve this request here: 
https://alioth.debian.org/project/admin/users.php?group_id=100128 

Comments by the user:
Hi,
I would like to join Debian javaScript maintainers team. I have already 
completed these,
https://git.fosscommunity.in/preyassc/node-decompress-response.git
https://git.fosscommunity.in/preyassc/node-parallel-transform.git
https://git.fosscommunity.in/preyassc/node-thenify.git

Thank you

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

[Pkg-javascript-devel] Bug#875279: node-coffeeify: Please enable upstream Testsuite

[Ross Gammon]

Package: node-coffeeify
Version: 1.0.0-1
Severity: normal

Dear Maintainer,

The upstream testsuite is not run during the building of the package. This is
due to node-browserify not yet being available in Debian (see TODO file).

Please remember to enable the tests once browserify is packaged.

Ross



-- System Information:
Debian Release: stretch/sid
  APT prefers zesty-updates
  APT policy: (500, 'zesty-updates'), (500, 'zesty-security'), (500, 
'zesty-proposed'), (500, 'zesty'), (100, 'zesty-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.10.0-33-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

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

[Pkg-javascript-devel] Fwd: Request to Join Project Debian JavaScript Maintainers from KARTIK KULKARNI (kartik-karz-guest)

[Ross Gammon]

Welcome to the team!

If you haven't already, please read the Team Policy:
https://wiki.debian.org/Javascript/Policy

 Forwarded Message 
Subject:Request to Join Project Debian JavaScript Maintainers from
KARTIK KULKARNI (kartik-karz-guest)
Date:   Sat, 02 Sep 2017 15:03:49 +
From:   nore...@alioth.debian.org
To: deb...@the-gammons.net



KARTIK KULKARNI (kartik-karz-guest) has requested to join your project. 
You can approve this request here: 
https://alioth.debian.org/project/admin/users.php?group_id=100128 

Comments by the user:
I have packaged the following Debian Nodejs packages

https://git.fosscommunity.in/kartik-karz/node-immediate
https://git.fosscommunity.in/kartik-karz/node-statuses
https://git.fosscommunity.in/kartik-karz/node-encodeurl
https://git.fosscommunity.in/kartik-karz/node-setprototypeof

and would like to join the group for Debian JavaScript Maintainers.

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

Re: [Pkg-javascript-devel] parallel installation

[Ross Gammon]

On 08/18/2017 08:53 PM, Jonas Smedegaard wrote:
> Quoting Ross Gammon (2017-08-18 19:54:50)
>> On 08/18/2017 06:09 PM, Jonas Smedegaard wrote:
>>> Quoting Ross Gammon (2017-08-18 16:47:10)
>>>> On 08/18/2017 04:50 AM, Hubert Chathi wrote:
>>>>> On Wed, 16 Aug 2017 09:27:49 +0200, Ross Gammon 
>>>>>  said:
>>>>>
>>>>>> For node-* stuff however, upstream handle this by bundling a 
>>>>>> particular version of a module in node_modules. If it is "really 
>>>>>> difficult" to patch a node module/app to use the Debian version 
>>>>>> of a library (because the versions have changed too much), then 
>>>>>> shouldn't we bundle the node_module and install it as upstream do 
>>>>>> it (avoiding all the relative path issues)? It could be followed 
>>>>>> up with a bug (severity wishlist/normal?) to remove the bundled 
>>>>>> module once Debian and upstream are more aligned.
>>>>> Embedding copies of libraries should be highly discouraged.  For 
>>>>> one thing, it is agaist policy[1], but it also it makes security 
>>>>> support much harder, you may end up with multiple buggy versions 
>>>>> of a library on your system, and have a bunch of duplication.  It 
>>>>> may make initial packaging easier, but it usually makes 
>>>>> maintenance harder.
>>>>>
>>>>> [1] 
>>>>> https://www.debian.org/doc/debian-policy/ch-source.html#s-embeddedfiles
>>>> The title of this section of policy is actually "Convenience copies 
>>>> of code". It is definitely not a convenience to heavily patch a 
>>>> package just to use a "way out of date" dependency, when it is out 
>>>> of date because many other packages still require that old 
>>>> dependency.
>>> It is an _upstream_ antipattern, and is indeed a convenience for 
>>> them.
>>>
>>>
>>>> I agree that it should be discouraged though, except in rare cases. 
>>>> It is just a normal transition (like in C/C++) after all.
>>> Not sure if you agree with policy or try argue against it.
>>>
>>>
>>>> Whether it is bundled, or several versions of the same upstream are 
>>>> packaged separately, you still have the issue of code duplication,
>>> No, several versions of a library is not convenience code copies.
>>>
>>>
>>>> and the possibility that a security update might be required in 
>>>> several places at the same time.
>>> It is certainly _possible_ for a security bug to exist in multiple 
>>> upstream releases of a code project, but when tracked on its own it 
>>> is easier to hunt down such bugs, and when each version exist only 
>>> at one place in Debian then each version needs only be fixed once 
>>> for a security bug to get squashed.
>>>
>>>
>>>> Of course, bundled copies are harder to find. But we can manage 
>>>> that in the team (via a transition bug, and/or a list on the wiki?) 
>>>> while we push all the unwilling upstreams to align on the same 
>>>> version (and nodejs upstreams are REALLY unwilling on this - 
>>>> believe me). I still think it is better to manage multiple copies 
>>>> in the same way that upstream do. It will give a lot less friction 
>>>> upstream.
>>> It is not adequate to agree in this team about bundling code: As an 
>>> example, the security team tracks security bugs and will also need 
>>> to agree on such deviation from Debian Policy.
>>>
>>> Personally I do *not* find bundling easier manageable than 
>>> separately tracking each true upstream project.  You are welcome to 
>>> explore argue for that, but you will need to convince not only this 
>>> team but Debian in general.
>>>
>>>
>>>  - Jonas
>>>
>> From the policy: "Debian packages should not make use of these 
>> convenience copies unless the included package is explicitly intended 
>> to be used in this way.".
>>
>> "Should" does not equal "must", it means something closer to "maybe". 
>> This gave me some trouble in my Danish language classes :-)
> And also from policy: "Non-conformance with guidelines denoted by should 
> (or recommended) will generally be considered a bug, but will not 
> necessarily render a package unsuitable for distribution.".
&g

Re: [Pkg-javascript-devel] parallel installation

[Ross Gammon]

On 08/18/2017 06:09 PM, Jonas Smedegaard wrote:
> Quoting Ross Gammon (2017-08-18 16:47:10)
>> On 08/18/2017 04:50 AM, Hubert Chathi wrote:
>>> [meant to reply to the list, so sending again]
>>>
>>> On Wed, 16 Aug 2017 09:27:49 +0200, Ross Gammon 
>>>  said:
>>>
>>>> For node-* stuff however, upstream handle this by bundling a
>>>> particular version of a module in node_modules. If it is "really
>>>> difficult" to patch a node module/app to use the Debian version of a
>>>> library (because the versions have changed too much), then shouldn't
>>>> we bundle the node_module and install it as upstream do it (avoiding
>>>> all the relative path issues)? It could be followed up with a bug
>>>> (severity wishlist/normal?) to remove the bundled module once Debian
>>>> and upstream are more aligned.
>>> Embedding copies of libraries should be highly discouraged.  For one
>>> thing, it is agaist policy[1], but it also it makes security support
>>> much harder, you may end up with multiple buggy versions of a library on
>>> your system, and have a bunch of duplication.  It may make initial
>>> packaging easier, but it usually makes maintenance harder.
>>>
>>> [1] https://www.debian.org/doc/debian-policy/ch-source.html#s-embeddedfiles
>> The title of this section of policy is actually "Convenience copies of 
>> code". It is definitely not a convenience to heavily patch a package 
>> just to use a "way out of date" dependency, when it is out of date 
>> because many other packages still require that old dependency.
> It is an _upstream_ antipattern, and is indeed a convenience for them.
>
>
>> I agree that it should be discouraged though, except in rare cases. It 
>> is just a normal transition (like in C/C++) after all.
> Not sure if you agree with policy or try argue against it.
>
>
>> Whether it is bundled, or several versions of the same upstream are 
>> packaged separately, you still have the issue of code duplication,
> No, several versions of a library is not convenience code copies.
>
>
>> and the possibility that a security update might be required in 
>> several places at the same time.
> It is certainly _possible_ for a security bug to exist in multiple 
> upstream releases of a code project, but when tracked on its own it is 
> easier to hunt down such bugs, and when each version exist only at one 
> place in Debian then each version needs only be fixed once for a 
> security bug to get squashed.
>
>
>> Of course, bundled copies are harder to find. But we can manage that 
>> in the team (via a transition bug, and/or a list on the wiki?) while 
>> we push all the unwilling upstreams to align on the same version (and 
>> nodejs upstreams are REALLY unwilling on this - believe me). I still 
>> think it is better to manage multiple copies in the same way that 
>> upstream do. It will give a lot less friction upstream.
> It is not adequate to agree in this team about bundling code: As an 
> example, the security team tracks security bugs and will also need to 
> agree on such deviation from Debian Policy.
>
> Personally I do *not* find bundling easier manageable than separately 
> tracking each true upstream project.  You are welcome to explore argue 
> for that, but you will need to convince not only this team but Debian in 
> general.
>
>
>  - Jonas
>
>From the policy: "Debian packages should not make use of these
convenience copies unless the included package is explicitly intended to
be used in this way.".

"Should" does not equal "must", it means something closer to "maybe".
This gave me some trouble in my Danish language classes :-)

I believe upstream "intended to be used in this way".

But I don't really want to argue about it any more, and I am happy to go
with what the team agrees.

Ross


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

Re: [Pkg-javascript-devel] parallel installation

[Ross Gammon]

On 08/18/2017 04:50 AM, Hubert Chathi wrote:
> [meant to reply to the list, so sending again]
>
> On Wed, 16 Aug 2017 09:27:49 +0200, Ross Gammon  
> said:
>
>> For node-* stuff however, upstream handle this by bundling a
>> particular version of a module in node_modules. If it is "really
>> difficult" to patch a node module/app to use the Debian version of a
>> library (because the versions have changed too much), then shouldn't
>> we bundle the node_module and install it as upstream do it (avoiding
>> all the relative path issues)? It could be followed up with a bug
>> (severity wishlist/normal?) to remove the bundled module once Debian
>> and upstream are more aligned.
> Embedding copies of libraries should be highly discouraged.  For one
> thing, it is agaist policy[1], but it also it makes security support
> much harder, you may end up with multiple buggy versions of a library on
> your system, and have a bunch of duplication.  It may make initial
> packaging easier, but it usually makes maintenance harder.
>
> [1] https://www.debian.org/doc/debian-policy/ch-source.html#s-embeddedfiles

The title of this section of policy is actually "Convenience copies of
code". It is definitely not a convenience to heavily patch a package
just to use a "way out of date" dependency, when it is out of date
because many other packages still require that old dependency.

I agree that it should be discouraged though, except in rare cases. It
is just a normal transition (like in C/C++) after all.

Whether it is bundled, or several versions of the same upstream are
packaged separately, you still have the issue of code duplication, and
the possibility that a security update might be required in several
places at the same time. Of course, bundled copies are harder to find.
But we can manage that in the team (via a transition bug, and/or a list
on the wiki?) while we push all the unwilling upstreams to align on the
same version (and nodejs upstreams are REALLY unwilling on this -
believe me). I still think it is better to manage multiple copies in the
same way that upstream do. It will give a lot less friction upstream.



Cheers,

Ross

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

Re: [Pkg-javascript-devel] CTTE decision on nodejs (bug #862051)

[Ross Gammon]

On 16/08/17 15:06, Jérémy Lal wrote:
>
>
> 2017-08-16 14:30 GMT+02:00 Ross Gammon  <mailto:javascr...@the-gammons.net>>:
>
>
>
> On 16/08/17 10:22, Jérémy Lal wrote:
>>
>>
>> 2017-08-16 9:08 GMT+02:00 Ross Gammon > <mailto:javascr...@the-gammons.net>>:
>>
>> On 08/01/2017 09:14 AM, Jérémy Lal wrote:
>>>
>>>
>>> 2017-08-01 7:59 GMT+02:00 Ross Gammon
>>> >> <mailto:javascr...@the-gammons.net>>:
>>>
>>> On 07/31/2017 08:05 PM, Jérémy Lal wrote:
>>>> Hi team,
>>>>
>>>> 2017-07-31 19:17 GMT+02:00 Tollef Fog Heen
>>>> mailto:tfh...@debian.org>>:
>>>>
>>>>
>>>> The technical committee was asked in bug #862051 to
>>>> revisit the decision in
>>>> bug #614907 (conflict between the ax25-node package
>>>> and the nodejs package).
>>>>
>>>> === Resolution ===
>>>>
>>>> The Technical Committee recognises that
>>>> circumstances change in ways
>>>> that make previous resolutions no longer
>>>> appropriate.  In 2012, it was
>>>> resolved that the nodejs package should not provide
>>>> /usr/bin/node due to
>>>> the historical conflict with the ax25-node
>>>> package.  Node.js is still
>>>> quite popular and the ax25-node package is no
>>>> longer in stable, testing
>>>> or unstable so the requirement for nodejs to not
>>>> provide /usr/bin/node
>>>> no longer applies.
>>>>
>>>> The Committee therefore resolves that:
>>>>
>>>> 1. The CTTE decision from 2012-07-12 in bug #614907
>>>> is repealed.
>>>>
>>>> This means Debian's normal policies and practices
>>>> take over and the
>>>> nodejs package is free to provide /usr/bin/node. 
>>>> The migration should
>>>> be managed according to Debian's usual
>>>> backwards-compatibility
>>>> arrangements.
>>>>
>>>> === End Resolution ===
>>>>
>>>> Please see http://bugs.debian.org/862051 for
>>>> discussion of this bug.
>>>>
>>>>
>>>> Next time i'll upload nodejs, it will be with
>>>> /usr/bin/node and /usr/bin/nodejs.
>>>> After that, please stop patching modules shebangs.
>>>> I suspect it is a bad idea to keep /usr/bin/nodejs
>>>> forever, so hopefully it will
>>>> be possible to remove it before buster.
>>>>
>>>> Regards,
>>>> Jérémy.
>>>>
>>>>
>>>>
>>>
>>> Once that is done, I will tweak
>>> https://wiki.debian.org/Javascript/Nodejs/Manual
>>> <https://wiki.debian.org/Javascript/Nodejs/Manual> and
>>> https://wiki.debian.org/Javascript/Nodejs
>>> <https://wiki.debian.org/Javascript/Nodejs> for new team
>>> members if you like.
>>>
>>> Should we eventually add something to the buster release
>>> notes to warn those users/developers that might have
>>> been unaware of nodejs-legacy, and developed their own
>>> stuff using /usr/bin/nodejs? Or is that likely to be a
>>> rare situation?
>>>
>>>
>>> I suppose it's important enough to, yes.
>>>
>>> Jérémy
>>
>>
>> What's "done" exactly ? The wiki changes ?
>
> Sorry - yes, just the wiki changes.
>
>> Done - please double check someone!
>>
>> Where are we with npm2deb. Should I submit a bug, or has it
>> already been fixed? Sorry - I am suck on Stretch on my laptop
>> (waiting for more

Re: [Pkg-javascript-devel] CTTE decision on nodejs (bug #862051)

[Ross Gammon]

On 16/08/17 10:22, Jérémy Lal wrote:
>
>
> 2017-08-16 9:08 GMT+02:00 Ross Gammon  <mailto:javascr...@the-gammons.net>>:
>
> On 08/01/2017 09:14 AM, Jérémy Lal wrote:
>>
>>
>> 2017-08-01 7:59 GMT+02:00 Ross Gammon > <mailto:javascr...@the-gammons.net>>:
>>
>> On 07/31/2017 08:05 PM, Jérémy Lal wrote:
>>> Hi team,
>>>
>>> 2017-07-31 19:17 GMT+02:00 Tollef Fog Heen
>>> mailto:tfh...@debian.org>>:
>>>
>>>
>>> The technical committee was asked in bug #862051 to
>>> revisit the decision in
>>> bug #614907 (conflict between the ax25-node package and
>>> the nodejs package).
>>>
>>> === Resolution ===
>>>
>>> The Technical Committee recognises that circumstances
>>> change in ways
>>> that make previous resolutions no longer appropriate. 
>>> In 2012, it was
>>> resolved that the nodejs package should not provide
>>> /usr/bin/node due to
>>> the historical conflict with the ax25-node package. 
>>> Node.js is still
>>> quite popular and the ax25-node package is no longer in
>>> stable, testing
>>> or unstable so the requirement for nodejs to not provide
>>> /usr/bin/node
>>> no longer applies.
>>>
>>> The Committee therefore resolves that:
>>>
>>> 1. The CTTE decision from 2012-07-12 in bug #614907 is
>>> repealed.
>>>
>>> This means Debian's normal policies and practices take
>>> over and the
>>> nodejs package is free to provide /usr/bin/node.  The
>>> migration should
>>> be managed according to Debian's usual
>>> backwards-compatibility
>>> arrangements.
>>>
>>> === End Resolution ===
>>>
>>> Please see http://bugs.debian.org/862051 for discussion
>>> of this bug.
>>>
>>>
>>> Next time i'll upload nodejs, it will be with /usr/bin/node
>>> and /usr/bin/nodejs.
>>> After that, please stop patching modules shebangs.
>>> I suspect it is a bad idea to keep /usr/bin/nodejs forever,
>>> so hopefully it will
>>> be possible to remove it before buster.
>>>
>>> Regards,
>>> Jérémy.
>>>
>>>
>>>
>>
>> Once that is done, I will tweak
>> https://wiki.debian.org/Javascript/Nodejs/Manual
>> <https://wiki.debian.org/Javascript/Nodejs/Manual> and
>> https://wiki.debian.org/Javascript/Nodejs
>> <https://wiki.debian.org/Javascript/Nodejs> for new team
>> members if you like.
>>
>> Should we eventually add something to the buster release
>> notes to warn those users/developers that might have been
>> unaware of nodejs-legacy, and developed their own stuff using
>> /usr/bin/nodejs? Or is that likely to be a rare situation?
>>
>>
>> I suppose it's important enough to, yes.
>>
>> Jérémy
>
>
> What's "done" exactly ? The wiki changes ?

Sorry - yes, just the wiki changes.

> Done - please double check someone!
>
> Where are we with npm2deb. Should I submit a bug, or has it
> already been fixed? Sorry - I am suck on Stretch on my laptop
> (waiting for more time), so I do lots of manual fixing when
> working on a new package ATM.
>
> Was npm2deb rewriting shebang ?

No. But maybe I went too far with the wiki update, as I also renamed the
library install paths (as well as the binary path), and npm2deb would
also need to update the paths in the debian/install files. I can drop
that part of the change. In any case  I think npm2deb would need to
adjust the path to the binary in debian/dirs and debian/install (and/or
links?).

> There is no particular urge in dropping /usr/bin/nodejs, though it
> would be nice to get there for Buster.
>
> Backports - It struck me when doing the updates to the wiki that
> we might need a versioned depends on nodejs [Build-Depends: nodejs
> (>= 4.8.3~dfsg-1~) to make it clear for people (like Andreas
> Tille) that might want to 

Re: [Pkg-javascript-devel] parallel installation

[Ross Gammon]

Hi,

On 08/15/2017 09:20 PM, Paul Gevers wrote:
> Hi,
>
> On 14-08-17 20:38, Hubert Chathi wrote:
>> At the BoF at DebConf, we were talking about parallel installation of
>> different versions of JS libraries.  In order to do parallel
>> installation, we'd need differently named packages for different
>> versions, and it seems like the obvious way to do that is to have
>> packages called something like libjs-fooVER and node-fooVER, where VER
>> some sort of the API version, similar to the way that C/C++ library
>> packages are named after the library SONAME.  If upstream follows semver
>> properly, then VER would be the major version number.
> This sounds like a reasonable approach, but what I am missing is a
> recommendation on what to do to keep the number of packages limited. I
> think it is not such a great idea to replace one problem (not the right
> version) with another one (too many packages to support).
>
> One approach could be for example the following. Try to have only two
> versions per release, but really limit the number to a maximum of 3.
>
>> For libjs-fooVER, the JavaScript files would probably go in
>> /usr/share/javascript/fooVER/ rather than /usr/share/javascript/foo.
>> Obviously everything that previously pointed to the old place would have
>> to now point to the new place, but we could create a libjs-foo
>> transitional package libjs-foo that symlinks /usr/share/javascript/foo
>> to /usr/share/javascript/fooVER so that existing packages don't break.

For libjs stuff, this is generally aligned with how things are managed
upstream. I have seen many apps looking for a particular version of js
stuff on an online CDN anyway.

>> For node-fooVER, the logical analogue would be to put the files in
>> /usr/lib/nodejs/fooVER.  However, anything that uses the library does
>> "require("foo")", and so would not be able to find it there.  There are
>> a couple possible options for fixing that I can think of.  The first is
>> to change all "require("foo")" to "require("fooVER")", but that sounds
>> painful to do.  The second option is to add a symlink from
>> node_modules/foo to /usr/lib/nodejs/fooVER in the root directory of the
>> thing that requires foo.  I think the second option is the best,
>> especially since Node upstream seems to prefer searching for things in
>> node_modules rather than in /usr/lib/nodejs.  And again, we may want to
>> create a transitional package node-foo that symlinks /usr/lib/nodejs/foo
>> to /usr/lib/nodejs/fooVER.
>>
>> What are peoples' thoughts on this?
> For packages that are somewhat forgiving and/or want to migrate when
> required, it may make sense to not think about the *-foo packages as
> transitional packages, but as the default, which will always point to
> the latest version. Honestly, I rather depend on such a package and fix
> bugs as they come than having to keep an eye out for updates and update
> the dependency to the latest version.
>
> Paul
>
>
>

For node-* stuff however, upstream handle this by bundling a particular
version of a module in node_modules. If it is "really difficult" to
patch a node module/app to use the Debian version of a library (because
the versions have changed too much), then shouldn't we bundle the
node_module and install it as upstream do it (avoiding all the relative
path issues)? It could be followed up with a bug (severity
wishlist/normal?) to remove the bundled module once Debian and upstream
are more aligned.

Cheers,

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

Re: [Pkg-javascript-devel] CTTE decision on nodejs (bug #862051)

[Ross Gammon]

On 08/01/2017 09:14 AM, Jérémy Lal wrote:
>
>
> 2017-08-01 7:59 GMT+02:00 Ross Gammon  <mailto:javascr...@the-gammons.net>>:
>
> On 07/31/2017 08:05 PM, Jérémy Lal wrote:
>> Hi team,
>>
>> 2017-07-31 19:17 GMT+02:00 Tollef Fog Heen > <mailto:tfh...@debian.org>>:
>>
>>
>> The technical committee was asked in bug #862051 to revisit
>> the decision in
>> bug #614907 (conflict between the ax25-node package and the
>> nodejs package).
>>
>> === Resolution ===
>>
>> The Technical Committee recognises that circumstances change
>> in ways
>> that make previous resolutions no longer appropriate.  In
>> 2012, it was
>> resolved that the nodejs package should not provide
>> /usr/bin/node due to
>> the historical conflict with the ax25-node package.  Node.js
>> is still
>> quite popular and the ax25-node package is no longer in
>> stable, testing
>> or unstable so the requirement for nodejs to not provide
>> /usr/bin/node
>> no longer applies.
>>
>> The Committee therefore resolves that:
>>
>> 1. The CTTE decision from 2012-07-12 in bug #614907 is repealed.
>>
>> This means Debian's normal policies and practices take over
>> and the
>> nodejs package is free to provide /usr/bin/node.  The
>> migration should
>> be managed according to Debian's usual backwards-compatibility
>> arrangements.
>>
>> === End Resolution ===
>>
>> Please see http://bugs.debian.org/862051 for discussion of
>> this bug.
>>
>>
>> Next time i'll upload nodejs, it will be with /usr/bin/node and
>> /usr/bin/nodejs.
>> After that, please stop patching modules shebangs.
>> I suspect it is a bad idea to keep /usr/bin/nodejs forever, so
>> hopefully it will
>> be possible to remove it before buster.
>>
>> Regards,
>> Jérémy.
>>
>>
>>
>
> Once that is done, I will tweak
> https://wiki.debian.org/Javascript/Nodejs/Manual
> <https://wiki.debian.org/Javascript/Nodejs/Manual> and
> https://wiki.debian.org/Javascript/Nodejs
> <https://wiki.debian.org/Javascript/Nodejs> for new team members
> if you like.
>
> Should we eventually add something to the buster release notes to
> warn those users/developers that might have been unaware of
> nodejs-legacy, and developed their own stuff using
> /usr/bin/nodejs? Or is that likely to be a rare situation?
>
>
> I suppose it's important enough to, yes.
>
> Jérémy

Done - please double check someone!

Where are we with npm2deb. Should I submit a bug, or has it already been
fixed? Sorry - I am suck on Stretch on my laptop (waiting for more
time), so I do lots of manual fixing when working on a new package ATM.

Backports - It struck me when doing the updates to the wiki that we
might need a versioned depends on nodejs [Build-Depends: nodejs (>=
4.8.3~dfsg-1~) to make it clear for people (like Andreas Tille) that
might want to start backporting node stuff to stretch. Otherwise they
will need to add back the patches to make things work.

Also I note on the wiki that the "nodejs-abi" might become a mandatory
goal for Stretch! Where did we get with that? Should we make it
mandatory for Buster?

Cheers,

Ross

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

Re: [Pkg-javascript-devel] CTTE decision on nodejs (bug #862051)

[Ross Gammon]

On 07/31/2017 08:05 PM, Jérémy Lal wrote:
> Hi team,
>
> 2017-07-31 19:17 GMT+02:00 Tollef Fog Heen  >:
>
>
> The technical committee was asked in bug #862051 to revisit the
> decision in
> bug #614907 (conflict between the ax25-node package and the nodejs
> package).
>
> === Resolution ===
>
> The Technical Committee recognises that circumstances change in ways
> that make previous resolutions no longer appropriate.  In 2012, it was
> resolved that the nodejs package should not provide /usr/bin/node
> due to
> the historical conflict with the ax25-node package.  Node.js is still
> quite popular and the ax25-node package is no longer in stable,
> testing
> or unstable so the requirement for nodejs to not provide /usr/bin/node
> no longer applies.
>
> The Committee therefore resolves that:
>
> 1. The CTTE decision from 2012-07-12 in bug #614907 is repealed.
>
> This means Debian's normal policies and practices take over and the
> nodejs package is free to provide /usr/bin/node.  The migration should
> be managed according to Debian's usual backwards-compatibility
> arrangements.
>
> === End Resolution ===
>
> Please see http://bugs.debian.org/862051 for discussion of this bug.
>
>
> Next time i'll upload nodejs, it will be with /usr/bin/node and
> /usr/bin/nodejs.
> After that, please stop patching modules shebangs.
> I suspect it is a bad idea to keep /usr/bin/nodejs forever, so
> hopefully it will
> be possible to remove it before buster.
>
> Regards,
> Jérémy.
>
>
>

Once that is done, I will tweak
https://wiki.debian.org/Javascript/Nodejs/Manual and
https://wiki.debian.org/Javascript/Nodejs for new team members if you like.

Should we eventually add something to the buster release notes to warn
those users/developers that might have been unaware of nodejs-legacy,
and developed their own stuff using /usr/bin/nodejs? Or is that likely
to be a rare situation?

Cheers,

Ross

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

[Pkg-javascript-devel] Fwd: Request to Join Project Debian JavaScript Maintainers from Rejah Rehim (rejah-guest)

[Ross Gammon]

Welcome Rejah,

If you haven't already, please read the Team Policy
(https://wiki.debian.org/Javascript/Policy)

Regards,

Ross


 Forwarded Message 
Subject:Request to Join Project Debian JavaScript Maintainers from
Rejah Rehim (rejah-guest)
Date:   Sat, 29 Jul 2017 10:10:44 +
From:   nore...@alioth.debian.org
To: deb...@the-gammons.net



Rejah Rehim (rejah-guest) has requested to join your project. 
You can approve this request here: 
https://alioth.debian.org/project/admin/users.php?group_id=100128 

Comments by the user:
Contributed to Debian ruby team before. Would like to contribute to Debian 
Javascript packages. 

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

[Pkg-javascript-devel] coffeescript & node-coffeeify

[Ross Gammon]

Hi Jonas,

The last package I had sitting in experimental because of the Stretch
freeze is node-coffeeify.

I looked at moving it to unstable yesterday, but realised that it needs
the version of coffeescript that is also sitting in experimental.

Is there anything holding up the latest coffeescript from moving to
unstable (other than time)? It is not urgent for anything as far as I
know - just a gentle prompt.

Cheers,

Ross

PS: I can see there are a few reverse dependencies now. Let me know if I
can help check any of those.



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

Re: [Pkg-javascript-devel] node-readable-stream_2.2.9-1_amd64.changes ACCEPTED into unstable, unstable

[Ross Gammon]

I looked at packaging readable-stream a while back. It seemed to provide
"stream" fixed at a particular version.

If the packages work with stream in our nodejs package, why bother to
change? It is probably easier to use the node-readable-stream package
now that it exists for new packages (instead of patching).


On 12/06/17 10:15, Paolo Greppi wrote:
> Il 12/06/2017 10:00, Debian FTP Masters ha scritto:
>> Accepted:
>>
>> Format: 1.8
>> Date: Sat, 27 May 2017 23:15:41 +0200
>> Source: node-readable-stream
>> Binary: node-readable-stream
>> Architecture: source all
>> Version: 2.2.9-1
>> Distribution: unstable
>> Urgency: low
>> Maintainer: Debian Javascript Maintainers 
>> 
>> Changed-By: Bastien Roucariès 
>> Description:
>>  node-readable-stream - stream compatibility library for Node.js and browser
>> Closes: 863510
>> ...
> Many modules have been patched to use nodejs' stream rather than 
> readable-stream or to skip tests that require readable-stream.
>
> Now that this is in the archive, should we pick it up ?
>
> The involved modules (https://codesearch.debian.net/search?q=readable-stream) 
> are 34:
>
> node-are-we-there-yet
> node-bl
> node-cloneable-readable
> node-concat-stream
> node-duplexer2
> node-duplexify
> node-finalhandler
> node-first-chunk-stream
> node-from2
> node-htmlparser2
> node-isstream
> nodejs
> node-lazystream
> node-lodash
> node-log4js
> node-memory-fs
> node-merge-stream
> node-mysql
> node-nan
> node-ordered-read-streams
> node-raw-body
> node-sha
> node-static-module
> node-stream-array
> node-streamtest
> node-superagent
> node-tap
> node-tap-parser
> node-tar-pack
> node-tar-stream
> node-through2 
> node-unpipe
> node-vinyl-fs
> node-ytdl-core
>
> P.
>



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

[Pkg-javascript-devel] Bug#863575: unblock: node-concat-stream/1.5.1-2

[Ross Gammon]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package node-concat-stream

Node-concat-stream is vunerable to Uninitialized Memory Exposure (CWE-201).
This was reported in bug https://bugs.debian.org/cgi-
bin/bugreport.cgi?archive=no&bug=863481. This was fixed upstream, and a version
of the fixing commit is included in this version as a patch. The patch has been
tested with the upstream testsuite, which unfortunately has to be disabled as
the testing framework (node-tape) does not exist in testing.

More information can be found in the attached debdiff (between tesing &
unstable), in the patch description.

unblock node-concat-stream/1.5.1-2

-- System Information:
Debian Release: stretch/sid
  APT prefers yakkety-updates
  APT policy: (500, 'yakkety-updates'), (500, 'yakkety-security'), (500,
'yakkety'), (100, 'yakkety-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-24-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
diff -Nru node-concat-stream-1.5.1/debian/changelog node-concat-stream-1.5.1/debian/changelog
--- node-concat-stream-1.5.1/debian/changelog	2015-11-08 17:03:58.0 +0100
+++ node-concat-stream-1.5.1/debian/changelog	2017-05-28 16:19:49.0 +0200
@@ -1,3 +1,12 @@
+node-concat-stream (1.5.1-2) unstable; urgency=high
+
+  * Apply upstream fix for Uninitialized Memory Exposure weakness CWE-201
+(Closes: #863481)
+  * Use stretch git branch
+  * Use Ubuntu email address
+
+ -- Ross Gammon   Sun, 28 May 2017 16:19:49 +0200
+
 node-concat-stream (1.5.1-1) unstable; urgency=low
 
   * Initial release (Closes: #796351)
diff -Nru node-concat-stream-1.5.1/debian/control node-concat-stream-1.5.1/debian/control
--- node-concat-stream-1.5.1/debian/control	2015-11-08 17:03:58.0 +0100
+++ node-concat-stream-1.5.1/debian/control	2017-05-28 16:19:49.0 +0200
@@ -2,13 +2,13 @@
 Section: web
 Priority: optional
 Maintainer: Debian Javascript Maintainers 
-Uploaders: Ross Gammon 
+Uploaders: Ross Gammon 
 Build-Depends: debhelper (>= 9),
dh-buildinfo,
nodejs
 Standards-Version: 3.9.6
 Homepage: https://github.com/maxogden/concat-stream#readme
-Vcs-Git: git://anonscm.debian.org/pkg-javascript/node-concat-stream.git
+Vcs-Git: git://anonscm.debian.org/pkg-javascript/node-concat-stream.git -b stretch
 Vcs-Browser: https://anonscm.debian.org/cgit/pkg-javascript/node-concat-stream.git
 
 Package: node-concat-stream
diff -Nru node-concat-stream-1.5.1/debian/gbp.conf node-concat-stream-1.5.1/debian/gbp.conf
--- node-concat-stream-1.5.1/debian/gbp.conf	2015-11-08 17:03:58.0 +0100
+++ node-concat-stream-1.5.1/debian/gbp.conf	2017-05-28 16:19:49.0 +0200
@@ -6,7 +6,7 @@
 
 # The default name for the Debian branch is "master".
 # Change it if the name is different (for instance, "debian/unstable").
-debian-branch = master
+debian-branch = stretch
 
 # git-import-orig uses the following names for the upstream tags.
 # Change the value if you are not using git-import-orig
diff -Nru node-concat-stream-1.5.1/debian/patches/series node-concat-stream-1.5.1/debian/patches/series
--- node-concat-stream-1.5.1/debian/patches/series	2015-11-08 17:03:58.0 +0100
+++ node-concat-stream-1.5.1/debian/patches/series	2017-05-28 16:19:49.0 +0200
@@ -1 +1,2 @@
 readable-stream.patch
+to-string_numbers.patch
diff -Nru node-concat-stream-1.5.1/debian/patches/to-string_numbers.patch node-concat-stream-1.5.1/debian/patches/to-string_numbers.patch
--- node-concat-stream-1.5.1/debian/patches/to-string_numbers.patch	1970-01-01 01:00:00.0 +0100
+++ node-concat-stream-1.5.1/debian/patches/to-string_numbers.patch	2017-05-28 16:19:49.0 +0200
@@ -0,0 +1,81 @@
+Description: to-string numbers written to the stream
+ Node-concat-stream is vulnerable to Uninitialized Memory Exposure. This
+ possible memory disclosure vulnerability exists when a value of type number
+ is provided to the stringConcat() method and results in concatination of
+ uninitialized memory to the stream collection.
+ This is a result of unobstructed use of the Buffer constructor, whose
+ insecure default constructor increases the odds of memory leakage.
+ See https://snyk.io/vuln/npm:concat-stream:20160901 for further details.
+Origin: upstream, https://github.com/maxogden/concat-stream/
+Bug: https://github.com/maxogden/concat-stream/issues/55
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863481
+Applied-Upstream: https://github.com/maxogden/concat-stream/pull/47/commits/3e285ba5e5b10b7c98552217f5c1023829efe69e
+Last-Update: 2017-05-28
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- node-concat-stream.orig/index.js
 node-concat-stream/index.js
+@@ -73,6 +73,10 @@
+   return /Array\]$/.test(Object.proto

Re: [Pkg-javascript-devel] Bug#863481: Bug#863481: [node-concat-stream] Uninitialized Memory Exposure

[Ross Gammon]

Hi Bastien,

On 05/27/2017 09:47 PM, roucaries bastien wrote:
> I can do it but I do not know that is the best:
> - let 1.6 go to unstable
> - patch old version
>
> Could you ask release team.
>
> The debdiff between the two version is so small that I have doubt
>

I had almost finished the email to the release team, when I did some
final checks. And whilst I agree the unrelated changes upstream are very
small, I unfortunately enabled the testsuite in 1.6 (in experimental)
now that node-tape is available in unstable. As node-tape is not
available in testing (stretch), I would have to disable the tests when
moving to unstable.

All in all, I think it will be easier to create a stretch branch in git
& add a patch which will also make the unblocking process easier.

I will work on that today. But if I run out of time, please feel free to
take it forward.

Regards,

Ross

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

[Pkg-javascript-devel] My status in Debian

[Ross Gammon]

Hi Team,

I know I am not a guru like most of you in the team, and that and my busy life 
means I am a little slow sometimes. I also spread myself around Debian a bit 
(Multimedia, GIS & Python teams), and I also work on Ubuntu Studio.

Anyway, one of my other sponsors has stated a few times when I have
asked for DM rights for something, that maybe it was time to step up to
DD status.

I am in no hurry (probably would aim to take the plunge towards the
middle of the year). And I wouldn't do it until there was wider support
for that. So any words of encouragement, or any suggestions of things
that you would like to see from me before you would endorse me are
welcome (here or in private).

Regards,

Ross


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

[Pkg-javascript-devel] Ghislain Vaillant joins the team

[Ross Gammon]

Hi Ghis,

Welcome to the Team. If you haven't already, please read the team policy:

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

Cheers,

Ross


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

[Pkg-javascript-devel] Bug#822251: Tried testing with Mocha instead

[Ross Gammon]

Hi,

As node-espresso is unmaintained upstream, I tried testing with mocha 
instead. But mocha fails to find 'seq'. Actually, this is also the case 
with espresso included as a node_module.


The test cases might need some work, or alternatively run as autopkgtest 
(installed) instead.


Regards,

Ross

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

[Pkg-javascript-devel] Bug#855471: RFP: node-bin-version-check -- Check whether a version satisfies a semver range

[Ross Gammon]

Package: wnpp
Severity: wishlist
X-Debbugs-CC: pkg-javascript-devel@lists.alioth.debian.org

* Package name: node-bin-version-check
  Version : 3.0.0
  Upstream Author : Sindre Sorhus  
(sindresorhus.com)

* URL : https://github.com/sindresorhus/bin-version-check
* License : Expat
  Programming Lang: JavaScript
  Description : Check whether a binary version satisfies a semver range

 Node-bin-version-check checks whether a binary version satisfies a semver
 range. This is useful when you have a thing that only works with specific
 versions of a binary.
 .
 Node.js is an event-based server-side JavaScript engine.

Node-bin-version-check is a dependency of grunt-contrib-compass and 
should probably be packaged within the Debian Javascript Team.


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

[Pkg-javascript-devel] Bug#855469: RFP: node-dargs -- Convert options into an array of arguments

[Ross Gammon]

Package: wnpp
Severity: wishlist
X-Debbugs-CC: pkg-javascript-devel@lists.alioth.debian.org

* Package name: node-dargs
  Version : 5.1.0
  Upstream Author : Sindre Sorhus  
(sindresorhus.com)

* URL : https://github.com/sindresorhus/dargs#readme
* License : Expat
  Programming Lang: JavaScript
  Description : Convert options into an array of arguments
 Node-dargs can be considered a reverse of minimist. It converts an object
 of options into an array of command-line arguments. This is useful when
 spawning command-line tools.
 .
 Node.js is an event-based server-side JavaScript engine.

Node-dargs is a dependency of node-grunt-contrib-compass and should 
probably be packaged in the Debian Javascript Team.


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

[Pkg-javascript-devel] Bug#855466: RFP: node-grunt-contrib-compass -- Compile Sass to CSS using Compass

[Ross Gammon]

Package: wnpp
Severity: wishlist
X-Debbugs-CC: pkg-javascript-devel@lists.alioth.debian.org

* Package name: node-grunt-contrib-compass
  Version : 1.1.1
  Upstream Author : Grunt Team (http://gruntjs.com/)
* URL : https://github.com/gruntjs/grunt-contrib-compass#readme
* License : Expat
  Programming Lang: JavaScript
  Description : Compile Sass to CSS using Compass

 Compass is an open-source authoring framework for the Sass css
 preprocessor. It helps you build stylesheets faster with a huge library
 of Sass mixins and functions, advanced tools for spriting, and workflow
 improvements including file based Sass configuration and a simple pattern
 for building and using Compass extensions.
 .
 Node.js is an event-based server-side JavaScript engine.

Node-grunt-contrib-compass is a dependency of 
kodi-addon-webinterface-chorus2 and is a good fit for the Debian 
Javascript Team.


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

[Pkg-javascript-devel] Fwd: Request to Join Project Debian JavaScript Maintainers from Nikhil Gawande (nikhilgawande-guest)

[Ross Gammon]

Welcome Nikhil!

If you have not already, please read the Debian Javascript Team policy:
pkg-javascript-devel@lists.alioth.debian.org

 Forwarded Message 
Subject: Request to Join Project Debian JavaScript Maintainers from 
Nikhil Gawande (nikhilgawande-guest)

Date: Tue, 14 Feb 2017 10:57:34 +
From: nore...@alioth.debian.org
To: deb...@the-gammons.net

Nikhil Gawande (nikhilgawande-guest) has requested to join your project. 
You can approve this request here: 
https://alioth.debian.org/project/admin/users.php?group_id=100128

Comments by the user:
I'm doing packaging of node packages . I already done one . and working 
on some more Please grant me access .


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

Re: [Pkg-javascript-devel] RFS : node-tty-browserify

[Ross Gammon]

On 03/02/17 11:55, Pirate Praveen wrote:

On ചൊവ്വ 31 ജനുവരി 2017 10:13 വൈകു, Akash Sarda wrote:

I have packaged, lintian cleaned, and ran sbuild.
Please upload! :)

Uploaded, thanks! Please request access to alioth and import your
package to pkg-javascript team repo.


Welcome to the team Akash!

Make sure you have read the team policy:

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

Cheers,

Ross

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

Re: [Pkg-javascript-devel] lots of requests to join pkg-javascript

[Ross Gammon]

On 28/01/17 18:44, Pirate Praveen wrote:

On ശനി 28 ജനുവരി 2017 10:21 വൈകു, Ross Gammon wrote:

I was disappointed with this too. I think we should be encouraging
newcomers to place their packaging in the standard place, so we can help
them when required. The last thing we want is node-*/js packaging being
done in a different way, in a different place.

If I had a list of Alioth logins, I would be happy to help adding them
to the team. We need more help here!

Tushar Agey (tush-guest) requested membership today, you can start with
him. I'll ask each of them to apply again when they are ready to upload
a second package. For now, someone needs to import all the packages
accepted by ftp masters (filter mail by ACCEPTED) so the duplication can
be avoided until npm2deb is fixed to look in experimental too.


Somebody had already added Tushar to the team. Welcome Tushar!

I have pushed all the recent packages uploaded to experimental to 
alioth. I did notice some of them did not have a complete set of tags, 
and I did not check if the repository URI matches the link in 
debian/control. This should be checked before the next upload. But at 
least npm2deb should find the repositories & help avoid duplicated effort.


Cheers,

Ross

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

Re: [Pkg-javascript-devel] lots of requests to join pkg-javascript

[Ross Gammon]

Hi Pirate,

On 01/27/2017 10:02 AM, Pirate Praveen wrote:
> Thanks to a bug in npm2deb search which does not look in experimental
> and our excellent on boarding practices which prefers keeping new git
> repos out of team repo in alioth, people are duplicating work, packaging
> already packaged node modules (node-timed-out and node-cli-spinners
> already, I expect more duplication). I don't see the same level of
> enthusiasm to import those repos to alioth (I'm not going to do it as I
> strongly disagree with the unilateral decision of rejecting their alioth
> requests based on one person's prejudice, it is also unnecessary extra
> work for the team, those who advocated this setup should be willing to
> take the extra work).
>
>

I was disappointed with this too. I think we should be encouraging
newcomers to place their packaging in the standard place, so we can help
them when required. The last thing we want is node-*/js packaging being
done in a different way, in a different place.

If I had a list of Alioth logins, I would be happy to help adding them
to the team. We need more help here!

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

Re: [Pkg-javascript-devel] pre-spring cleaning, please advise

[Ross Gammon]

On 01/28/2017 10:52 AM, Paolo Greppi wrote:
> This is a good idea ! There is a lot of cruft, especially packages created 
> for some obscure reason 2-3 years ago and since then abandoned both by the 
> maintainer and by upstream, and superseded by the next cool thing in the 
> nodejs ecosystem.
>
> I propose to extract from UDD a list of candidate packages to be removed: 
> those not fulfilling the criteria proposed by Jérémy, plus some more like:
>
> - popcon > 20
> ..
>
> The list would be published for scrutiny here in this mailing list or on the 
> wiki for say 2 weeks.
>
> To address the point raised by Ben (i.e. to make sure we don't remove a 
> library needed at some point in the future for some other package not yet 
> uploaded), I would leave it to the owner of the high-level package IPTs: for 
> each of those there is a Task in the wiki or a non-disclosed WIP list - in 
> any case the ITP owner knows best and she should manually remove from the 
> list the packages she thinks she'll need, providing a rationale (i.e. "needed 
> for yarnpkg").
>
> Once the 2 weeks are over we can proceed mass filing those "candidate for 
> removal" bugreports.
>
> Once the additional 2 weeks are over the bugreports can be reassigned to 
> ftpmaster.
>
> Paolo
>
> On 28/01/2017 10:17, Jonas Smedegaard wrote:
>> Quoting Ben Finney (2017-01-28 03:07:01)
>>> Jérémy Lal  writes:
>>>
 - or having a reverse (build-)dependency, or what's the point ?
>>> I am very much in favour of this: node libraries should be in Debian 
>>> to provide a library that is needed for some actual program of benefit 
>>> to Debian users.
>> Agreed.
>>
>>
>>> But my eagerness to remove useless packages makes me worry that some 
>>> useful ones could be swept up also.
>>>
>>> One use case I don't see addressed: How will we ensure that a library 
>>> is not needed for some other package not yet uploaded to Debian?
>> Removal from testing involves filing a bugreport to ftpmaster.  I guess 
>> it makes sense if at all uncertain to first file bugreport against the 
>> package and cc this list - of not-to-high severity - suggesting the 
>> intent (removal from stretch or removal from Debian completely) some 
>> time (2 weeks?) before reasigning to ftpmaster.
>>
>> Discussing only here is not adequate: Being part of this team and 
>> subscribing to this mailinglist is voluntary.
>>
>>
>>  - Jonas
>

I agree. But...

It might be a good idea to keep the alioth repo for a while though.
Upstreams can sometimes get going again when some need is identified and
someone willing steps up to maintain it. Then we can at least quickly
resurrect the package if required.

Can we be a little less aggressive on the timescales? It should be a
Buster goal. It can take me most of a release cycle to get all the other
dependencies in shape in order for the final reverse dependency to get
uploaded (I failed with several things this release cycle). Trying to
re-remember what package I don't want to get "dropped out" (which could
be maintained by someone else) and then adjusting bug severities does
take up valuable time which could be spent getting the other
dependencies ready.

Also, as we enable more and more autopkgtests & buildtime testsuites,
packages in bad shape will naturally fall out of testing anyway -
without us doing any work. Periodically looking at the packages that
have not been in testing for a long time could be another metric to use.
I know I have a couple of those that weren't worth working on until a
series of other dependencies were ready.

Cheers,

Ross


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

Re: [Pkg-javascript-devel] lots of requests to join pkg-javascript

[Ross Gammon]

Hi All,

Sorry - I am a bit late to this. I have had problems with my javascript
email address, and I am now using a new one here.

On 01/06/2017 07:21 AM, Pirate Praveen wrote:
> I have asked them to push their work to git.fosscommunity.in and send
> RFS mails to this list. Those who institute such bureaucracy should also
> volunteer to import these repos to alioth. I do not want to be forced to
> do extra work.
>
> Other option would have been using mentors.debian.net, but we lose the
> ability to incorporate their git history (or like now depend on external
> services).
>
> I will also look at possibility of using personal alioth repositories.

I really like to encourage the use of mentors.debian.net to new-comers.
There are a lot of experienced developers there who can answer general
packaging questions and queries about Debian policy etc. I have had
requests for help from people that would prefer to be mentored
privately. But I prefer that we all share our learning experiences on a
public list, so that others can learn at the same time. Mentors.net also
has the advantage that the package is known to have been successfully
built, in order for the *.changes file to get uploaded. It also gives
experience in debsign & dput.

But this thread points out that we are missing a parallel "mentors"
git/svn repository where people can learn about packaging within a
repository as well. The work can be pushed to the official place later
(whenever the sponsor suggests the mentee joins a team).

As for whether we should let "anyone" have access to the Javascript
alioth repository (ie. join the team), my opinion is that the repository
is not the archive. We can always reconstruct the repo from the archive
(although losing some history) after discovering someone from the team
has misbehaved, or made a mistake. Commitment to continued maintenance
is something the sponsor should check before uploading to the archive. I
am sure there are a few sponsors that have been left "holding a baby"
when someone just wanted to get a package into Debian, but was lying
about their commitment. And this is not even after a "packaging
tutorial" or whatever event. The package will be orphaned and hopefully
picked up by someone else if it is an important enough package.

Other teams I am a member of, expect the "joining request" to include a
statement that they have read the team policy. Maybe we should add a
"Joining the Team" line on https://wiki.debian.org/Javascript that
"softly" states that it is recommended to read the team policy before
applying to join? If the request to join is a little short on
information, you can always recommend they read the information (on the
list) after the request to join is accepted by someone in the team. I
have seen Jonas do this many times.

Regards,

Ross

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

Re: [Pkg-javascript-devel] Using clean build scripts from pkg-ruby-extras repo

[Ross Gammon]

Hi all,

On 29/11/16 12:20, Antonio Terceiro wrote:
> On Mon, Nov 28, 2016 at 10:44:08PM +0530, Pirate Praveen wrote:
>> On 2016, നവംബർ 28 10:27:15 PM IST, Paolo Greppi  
>> wrote:
>>> Hi this is opinionated but very useful. I have a couple of newbie
>>> questions.
>>>
>>> Did you try these scripts on Debian stable as host ?
>> No, I have not tried.
> Neither did I, but I will be happy to merge patches if anything does not
> work.

I run Jessie on my laptop, and thought I would give pkg-ruby-extras a
go. I ran into problems running the setup script due to a lack of space
under /root (too many chroots & containers!). This is my fault and a
problem I had been meaning to fix for a while.

So after fixing that, the next problem is that you run into #843137 with
sbuild (there have been a lot of changes in unstable/stretch with apt &
gpg). You have to install sbuild from jessie-backports to fix that.

Then the build command works fine up until the debci bit:
Run the test suite now? [Y/n]y
adt-run [16:44:30]: version 3.6jessie1
Error: container adt-sid-amd64 is not defined
: failure: ['sudo', 'lxc-clone', '--new',
'adt-virt-lxc-tbsmsn', '--orig', 'adt-sid-amd64'] failed (exit status 1)
adt-run [16:44:30]: ERROR: testbed failed: cannot send to testbed:
['BrokenPipeError: [Errno 32] Broken pipe\n']

WARNING: Test suite failed! Please verify before uploading

Now edit /home/ross/.chdist/unstable/etc/apt/sources.list
Run chdist apt-get unstable update
And enjoy.

I suppose I will have to create the adt-sid-amd64 manually, and then run
into the same gpg/apt issue. But it is Christmas Eve now, and that will
have to wait.

All the best!

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

Re: [Pkg-javascript-devel] Bug#848912: RFS: node-file-sync-cmp/0.1.1-1 [ITP]

[Ross Gammon]

Thank Pirate. Once I have managed to get ruby-extras set up (on Jessie),
I will start enabling the upstream testsuites for debci for my other
packages as well.

Ross

On 22/12/16 06:57, Pirate Praveen wrote:
> On ബുധന്‍ 21 ഡിസംബര്‍ 2016 12:14 രാവിലെ, Ross Gammon wrote:
>> Alternatively, one can download the package with dget using this command:
>>
>> dget -x https://mentors.debian.net/debian/pool/main/n/node-file-sync-cmp
>> /node-file-sync-cmp_0.1.1-1.dsc
>>
> I have used alioth repo to build the package. I have enabled
> autopkgtests and uploaded. Thanks!
>
>
>
>

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

[Pkg-javascript-devel] Bug#848912: RFS: node-file-sync-cmp/0.1.1-1 [ITP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist
Tags: l10n

Dear mentors,

I am looking for a sponsor for my package "node-file-sync-cmp"

* Package name: node-file-sync-cmp
  Version : 0.1.1-1
  Upstream Author : Martin Geisler  (http://geisler.net/)
* URL : https://github.com/mgeisler/file-sync-cmp/
* License : Expat
  Section : web

It builds this binary package:

node-file-sync-cmp - Synchronous file comparison

To access further information about this package, please visit the following
URL:

  https://mentors.debian.net/package/node-file-sync-cmp


Alternatively, one can download the package with dget using this command:

dget -x https://mentors.debian.net/debian/pool/main/n/node-file-sync-cmp
/node-file-sync-cmp_0.1.1-1.dsc

Debian packaging can be found here:
https://anonscm.debian.org/cgit/pkg-javascript/node-file-sync-cmp.git

Changes since the last upload:

  * Initial release (Closes: #845025)


Regards,
Ross Gammon



-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-24-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

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

[Pkg-javascript-devel] Bug#848507: node-acorn: Acorn does not build walk

[Ross Gammon]

Package: node-acorn
Version: 4.0.3-2
Severity: normal

Dear Maintainer,

I am trying to package node-bluebird, and I was very glad to see your work on
acorn, and to see it make it into the archive. Acorn is needed to build
bluebird.

Unfortunately, bluebird cannot find "walk" which is part of acorn.

According to acorn's package.json, walk is built with "rollup -c
rollup/config.walk.js" and ends up in "dist/walk.js".

Unfortunately, rollup is not yet packaged for Debian, although some packaging
has been started:
https://anonscm.debian.org/cgit/pkg-javascript/node-rollup.git/

I hope that once rollup makes it into Debian, that you will build walk for me
in acorn.

Regards,

Ross



-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-24-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

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

Re: [Pkg-javascript-devel] RFS: node-loose-envify 1.3.0

[Ross Gammon]

On 12/10/2016 07:26 AM, Paolo Greppi wrote:
> The most popular suffix separator for dfsg is + (694 times), last comes
> ~dfsg (79 times) and finally -dfsg (15 times).
> 
> ?

~ sorts before [a-z], + sorts after [a-z]

I have used 1.2.3-1~exp1 sometimes, because then I can use 1.2.3-1 for
the next upload to unstable once I know that it worked in experimental.

If you exclude something from the upstream tarball because it is not
allowed in Debian, then to stop repacking the tarball you need a new
fixed version (without the offending file in the tarball) to be released
upstream. Then 1.2.3+dfsg-1 makes a lot of sense, because if upstream
fix it, the next version will always be higher than 1.2.3 (e.g 1.2.4).

The only advantage to using ~ that I can think of, is if we change the
rules and the offending file was now "free", you could just drop the
~dfsg. Unless others can think of another use case?

Cheers,

Ross

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

Re: [Pkg-javascript-devel] Bug#798278: Node-tape depends on node-has which is very small

[Ross Gammon]

Aah, thanks. I has been a long time since I started on node-tape. Time enough 
to pick up new dependencies :-) 

For the record, here is the latest list (although I am using an older npm2deb, 
and it does not pick up some that have already been packaged.):

$ npm2deb depends -r tape
Dependencies:
NPM   Debian
tape (4.6.3)  None
├─ deep-equal (~1.0.1)node-deep-equal (1.0.1-1)
├─ defined (~1.0.0)   node-defined (1.0.0-1)
├─ for-each (~0.3.2)  None
│  └─ is-function (~1.0.0)None
├─ function-bind (~1.1.0) None
├─ glob (~7.1.1)  node-glob (4.0.5-1)
├─ has (~1.0.1)   None
│  └─ function-bind (^1.0.2)  None
├─ inherits (~2.0.3)  node-inherits (2.0.1-3)
├─ minimist (~1.2.0)  node-minimist (1.2.0-1)
├─ object-inspect (~1.2.1)None
├─ resolve (~1.1.7)   node-resolve (0.3.1-1)
├─ resumer (~0.0.0)   None
│  └─ through (~2.3.4)node-through2 (1.1.1-1)
├─ string.prototype.trim (~1.1.2) None
│  ├─ define-properties (^1.1.2)  None
│  │  ├─ foreach (^2.0.5) None
│  │  └─ object-keys (^1.0.8) None
│  ├─ es-abstract (^1.5.0)None
│  │  ├─ es-to-primitive (^1.1.1) None
│  │  │  ├─ is-callable (^1.1.1)  None
│  │  │  ├─ is-date-object (^1.0.1)   None
│  │  │  └─ is-symbol (^1.0.1)None
│  │  ├─ function-bind (^1.1.0)   None
│  │  ├─ is-callable (^1.1.3) None
│  │  └─ is-regex (^1.0.3)None
│  └─ function-bind (^1.0.2)  None
└─ through (~2.3.8)   node-through2 (1.1.1-1)

Build dependencies:
NPM   Debian
concat-stream (~1.5.2)node-concat-stream (1.5.1-1)
falafel (~2.0.0)  None
js-yaml (~3.7.0)  None
tap (~7.1.1)  node-tap (0.7.1-1.1)
tap-parser (~3.0.4)   None

Regards,

Ross

On 12/04/2016 02:55 PM, Lucas Castro wrote:
> I'm not sure about that,
> 
> npm2deb brings to some others, as is-callable, is-regex and one
> build-dependencies, falafel.
> 
> following the falafel dependencies we get rollup and acorn as
> dependencies, those are very complicating packaging.
> 
> 
> On 04-12-2016 06:33, Ross Gammon wrote:
>> Hi Lucas,
>>
>> How are you getting on with node-tape? We only have a month to get it into 
>> Debian Stretch.
>>
>> For your information, the only dependency left for node-tape (as far as I 
>> know) is node-has. Node has consists of the following two lines of code:
>>
>> var bind = require('function-bind');
>> module.exports = bind.call(Function.call, Object.prototype.hasOwnProperty);
>>
>> It doesn't really make sense to create a whole package just for that. I was 
>> planning to either patch node-tape so that it doesn't require node-has, or 
>> just provide node-has as binary package of node-tape (in case other packages 
>> want to use it - which I had not checked). I can't imaging node-has ever 
>> changing that much upstream!
>>
>> Sorry for not documenting this issue earlier - busy.
>>
>> Regards,
>>
>> Ross




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

[Pkg-javascript-devel] Node-tape depends on node-has which is very small

[Ross Gammon]

Hi Lucas,

How are you getting on with node-tape? We only have a month to get it into 
Debian Stretch.

For your information, the only dependency left for node-tape (as far as I know) 
is node-has. Node has consists of the following two lines of code:

var bind = require('function-bind');
module.exports = bind.call(Function.call, Object.prototype.hasOwnProperty);

It doesn't really make sense to create a whole package just for that. I was 
planning to either patch node-tape so that it doesn't require node-has, or just 
provide node-has as binary package of node-tape (in case other packages want to 
use it - which I had not checked). I can't imaging node-has ever changing that 
much upstream!

Sorry for not documenting this issue earlier - busy.

Regards,

Ross



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

[Pkg-javascript-devel] Bug#844938: The new node-tap is causing FTBFS in node-inline-source-map

[Ross Gammon]

On 11/23/2016 11:43 PM, Jérémy Lal wrote:
> 2016-11-23 21:47 GMT+01:00 Ross Gammon :
>> tag 844938 + upstream
>> forwarded 844938 https://github.com/thlorenz/inline-source-map/issues/18
>> thanks
>>
>> Hi,
>>
>> I have just investigated what has changed that might be causing this
>> failure of the upstream testsuite, and it appears to be the recent
>> update of node-tap to Version 8.0.0.
>>
>> The bug has been passed upstream
>> (https://github.com/thlorenz/inline-source-map/issues/18), but if there
>> are any node-tap experts reading this, I would be grateful for a patch
>> to send there (as the Stretch release is looming).
> 
> Done !
> 

Thanks Jeremy!

I would have worked it out in the end, looking at the tap docs. But that
saved me a bundle of time.

Cheers,

Ross



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

[Pkg-javascript-devel] Bug#844922: Bug#844922: Bug#844922: Node-string-decoder

[Ross Gammon]

On 11/23/2016 08:59 AM, Jérémy Lal wrote:
> 2016-11-23 8:53 GMT+01:00 Ross Gammon :
>> Hi,
>>
>> This node module was originally packaged as it was a dependency of something
>> (I can't remember).
>>
>> If there is nothing depending on it, we should probably remove it from the
>> archive. The string-decoder function from the core nodejs should be used
>> instead (patching the module that needs it if required). Node-string-decoder
>> is mainly used when a nodejs project wants to stick to an old version of
>> this function.
>>
>> Regards,
> 
> All right, can you fill the ftp.debian.org RM request please ?
> 
> Jérémy
> 

Done!



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

[Pkg-javascript-devel] Bug#844938: The new node-tap is causing FTBFS in node-inline-source-map

[Ross Gammon]

tag 844938 + upstream
forwarded 844938 https://github.com/thlorenz/inline-source-map/issues/18
thanks

Hi,

I have just investigated what has changed that might be causing this
failure of the upstream testsuite, and it appears to be the recent
update of node-tap to Version 8.0.0.

The bug has been passed upstream
(https://github.com/thlorenz/inline-source-map/issues/18), but if there
are any node-tap experts reading this, I would be grateful for a patch
to send there (as the Stretch release is looming).

Regards,

Ross



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

[Pkg-javascript-devel] Bug#844922: Node-string-decoder

[Ross Gammon]

Hi,

This node module was originally packaged as it was a dependency of 
something (I can't remember).


If there is nothing depending on it, we should probably remove it from 
the archive. The string-decoder function from the core nodejs should be 
used instead (patching the module that needs it if required). 
Node-string-decoder is mainly used when a nodejs project wants to stick 
to an old version of this function.


Regards,

Ross

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

[Pkg-javascript-devel] Bug#845012: grunt: Grunt is missing the rimraf dependency

[Ross Gammon]

Package: grunt
Version: 1.0.1-2
Severity: grave
Justification: renders package unusable

Dear Praveen & helpers,

Thank you so much for all the hard work on grunt, and for putting up with so
much criticism in the process!

I am just building my first package with grunt, and hit a small snag. node-
rimraf is missing from grunt's dependencies in debian/control.

When building my package with grunt, I got the same error as that appearing on
the as-installed testing page for grunt:
https://ci.debian.net/data/packages/unstable/amd64/g/grunt/20161118_032242.autopkgtest.log.gz

The fix is quite simple, so forgive me if I don't provide a patch :-)

Regards,

Ross Gammon



-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-24-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

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

[Pkg-javascript-devel] Bug#844995: RFS: node-object-inspect/1.1.0-1 [RFP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-object-inspect"

* Package name: node-object-inspect
  Version : 1.1.0-1
  Upstream Author : James Halliday  (http://substack.net)
* URL : https://github.com/substack/object-inspect
* License : Expat
  Section : web

It builds this binary package:

node-object-inspect - string representations of objects in node and the browser

To access further information about this package, please visit the following
URL:

https://mentors.debian.net/package/node-object-inspect


Alternatively, one can download the package with dget using this command:

dget -x https://mentors.debian.net/debian/pool/main/n/node-object-inspect/node-
object-inspect_1.1.0-1.dsc

Debian packaging can be found here:
https://anonscm.debian.org/cgit/pkg-javascript/node-object-ispect.git

Changes since the last upload:

  * Initial release (Closes: #814284)


Regards,
Ross Gammon



-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-24-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

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

[Pkg-javascript-devel] Bug#844565: RFS: node-husl/6.0.1+dfsg-1 [ITP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-husl"

* Package name: node-husl
  Version : 6.0.1+dfsg-1
  Upstream Author : Alexei Boronine 
* URL : http://www.husl-colors.org/
* License : Expat
  Section : web

It builds these binary packages:

libjs-husl - Human-friendly HSL - Javascript
node-husl  - Human-friendly HSL - NodeJS

To access further information about this package, please visit the following
URL:

https://mentors.debian.net/package/node-husl


Alternatively, one can download the package with dget using this command:

dget -x https://mentors.debian.net/debian/pool/main/n/node-husl/node-
husl_6.0.1+dfsg-1.dsc

Debian packaging can be found here:
https://anonscm.debian.org/cgit/pkg-javascript/node-husl.git

Changes since the last upload:

  * Initial release (Closes: #844230)


Regards,
Ross Gammon



-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-24-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

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

[Pkg-javascript-devel] Bug#844545: RFP: node-yargs -- a modern, pirate-themed, successor to optimist

[Ross Gammon]

Package: wnpp
Severity: wishlist

* Package name: node-yargs
  Version : 6.4.0
  Upstream Author : Benjamin E. Coe 
* URL : http://yargs.js.org/
* License : Expat
  Programming Lang: JavaScript
  Description : a modern, pirate-themed, successor to optimist

 Yargs helps you build interactive command line tools by parsing arguments and
 generating an elegant user interface.
 .
 Yargs gives you:
 * commands and (grouped) options (like module run -n --force),
 * a dynamically generated help menu based on your arguments,
 * bash-completion shortcuts for commands and options.
 .
 Node.js is an event-based server-side JavaScript engine.

Yargs is a new dependency of node-carto, which needs to be updated for the new
kosmtik package. I am working on a couple of other dependencies of node-carto,
so if someone can help share the load with yargs and some of it's dependencies,
I would be very grateful.

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

[Pkg-javascript-devel] Bug#844079: node-generic-pool: Please package latest node-generic-pool

[Ross Gammon]

Package: node-generic-pool
Version: 2.0.3-1
Severity: wishlist

Dear Maintainer,

I am trying to package the latest node-kosmtik, and it depends on node-generic-
pool (>= 2.2.0). Currently Debian has 2.0.3-1, and upstream has released 3.1.1.

Current rdepends (which would have to be checked):
node-tilelive-mapnik
node-millstone
node-tilelive-bridge
node-pg

If I can help with preparing the package, then let me know.

Regards,

Ross



-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-24-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

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

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

[Ross Gammon]

Source: leaflet
Version: 0.7.7+20160312-1
Severity: wishlist

Dear Maintainer,

I am trying to finalise the packaging of the new kosmtik package, but it
requires a newer version of Leaflet (>= 1.0.0-beta.2) including the node
module. Debian currently has version 0.7.7+20160312-1, and 1.0.1 has been
released upstream.

There are a few reverse dependencies that would need to be checked:
libjs-leaflet-markercluster
qgis-common
libjs-wax
routino-www
qgis-common
gis-osm
flightgear-phi

Let me know if I can help with pulling together the new version.

Regards,

Ross



-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-24-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

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

[Pkg-javascript-devel] Bug#826560: kosmtik needs newer node-carto as well

[Ross Gammon]

Hi,

I am packaging node-kosmtik which also needs a newer node-carto version
(>= 0.15.2).

If I can help with preparing an upload, I am happy to help out.

Node-mapnik seems to be the only current reverse dependency.

Regards,

Ross



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

[Pkg-javascript-devel] Bug#844072: node-request: Please upload the latest version of node-request

[Ross Gammon]

Package: node-request
Version: 2.26.1-1
Severity: wishlist

Dear Maintainer,

I am working on finalising the new kosmtik package, and it depends on node-
request (>= 2.64.0). Currently only 2.26.1 is in Debian, and upstream have
released 2.78.1.

Would it be possible to have a new version? I can see 5 reverse dependencies,
but I haven't checked them:
npm
node-ytdl-core
node-gyp
node-pre-gyp
node-millstone
node-jsdom

I would be happy help with the update if you prefer.

Regards,

Ross



-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-24-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages node-request depends on:
ii  node-cookie-jar   0.3.1-1
ii  node-forever-agent0.5.1-1
ii  node-form-data0.1.0-1
ii  node-json-stringify-safe  5.0.0-1
ii  node-mime 1.3.4-1
ii  node-node-uuid1.4.0-1
ii  node-qs   2.2.4-1
ii  node-tunnel-agent 0.3.1-1
ii  nodejs4.2.6~dfsg-1ubuntu4.1

node-request recommends no packages.

Versions of packages node-request suggests:
pn  node-aws-sign
pn  node-hawk
pn  node-http-signature  
pn  node-oauth-sign  

-- no debconf information

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

Re: [Pkg-javascript-devel] Bug#844014: node-js-yaml

[Ross Gammon]

On 11/12/2016 09:17 AM, Jérémy Lal wrote:
> Putting back in the right order... 
> 
> On 12/11/16 00:25, Jérémy Lal wrote:
> 
>>
>>
>>     2016-11-11 20:48 GMT+01:00 Ross Gammon > <mailto:rossgam...@mail.dk>>:
>>
>> Package: node-js-yaml
>> Version: 3.6.1+dfsg-1
>> Severity: grave
>> Justification: renders package unusable
>>
>> Dear Maintainer,
>>
>> Node-js-yaml is currently uninstallable in unstable due to a
>> tight dependency
>> on node-esprima (< 3.0.0), when the current version of
>> node-esprima in unstable
>> is 3.1.0.
>>
>> The upstream testsuite passes fine with v3.1.0 of
>> node-esprima, so it should be
>> fine to just drop the (<3.0.0) dependency.
>>
>>     Regards,
>>
>> Ross
>>
>>
>> You're the node-js-yaml maintainer - do you need help ?
>>
>> Jérémy
>>
>>
> 
> 2016-11-12 8:31 GMT+01:00 Ross Gammon  <mailto:rossgam...@mail.dk>>:
> 
> Thanks Jeremy,
> 
> I am trying to finish off kosmtik packaging, and there are several
> dependencies that are either too old or too new. Just want to ping
> the other package maintainers (where the dependency is too old) first.
> 
> For js-yaml, it is an easy fix, and I just need to ask Gianfranco
> (previous sponsor) for DM upload rights to do it.
> 
> Cheers,
> 
> Ross
> 
> 
> it's blocking some other package i'm working on so i'm keen to solve
> this quickly,
> i'll do the upload if that's all right with you.
> 
> Jérémy
> 
> 

No problems. Go for it!



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

[Pkg-javascript-devel] Bug#844014: node-js-yaml

[Ross Gammon]

Thanks Jeremy,

I am trying to finish off kosmtik packaging, and there are several 
dependencies that are either too old or too new. Just want to ping the 
other package maintainers (where the dependency is too old) first.


For js-yaml, it is an easy fix, and I just need to ask Gianfranco 
(previous sponsor) for DM upload rights to do it.


Cheers,

Ross


On 12/11/16 00:25, Jérémy Lal wrote:



2016-11-11 20:48 GMT+01:00 Ross Gammon <mailto:rossgam...@mail.dk>>:


Package: node-js-yaml
Version: 3.6.1+dfsg-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Node-js-yaml is currently uninstallable in unstable due to a tight
dependency
on node-esprima (< 3.0.0), when the current version of
node-esprima in unstable
is 3.1.0.

The upstream testsuite passes fine with v3.1.0 of node-esprima, so
it should be
fine to just drop the (<3.0.0) dependency.

Regards,

Ross


You're the node-js-yaml maintainer - do you need help ?

Jérémy




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

[Pkg-javascript-devel] Bug#844014: node-js-yaml

[Ross Gammon]

Package: node-js-yaml
Version: 3.6.1+dfsg-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Node-js-yaml is currently uninstallable in unstable due to a tight dependency
on node-esprima (< 3.0.0), when the current version of node-esprima in unstable
is 3.1.0.

The upstream testsuite passes fine with v3.1.0 of node-esprima, so it should be
fine to just drop the (<3.0.0) dependency.

Regards,

Ross



-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-24-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

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

[Pkg-javascript-devel] Bug#844009: node-semver: Please package latest node-semver

[Ross Gammon]

Package: node-semver
Version: 2.1.0-2
Severity: wishlist

Dear Maintainer,

I am packaging node-kosmtick, and this requires at least version 5.0.3 of node-
semver.

The latest version released by upstream is 5.3.0, and the current version in
unstable is 2.1.0.

There are only a few reverse dependencies, and none of them seem to have strict
dependencies. Although I have not tested them.

I would be willing to help with the packaging.

Regards,

Ross



-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-24-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages node-semver depends on:
ii  nodejs  4.2.6~dfsg-1ubuntu4.1

node-semver recommends no packages.

node-semver suggests no packages.

-- no debconf information

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

Re: [Pkg-javascript-devel] Comments regarding node-js-yaml_3.6.1+dfsg-1_amd64.changes

[Ross Gammon]

Whoops. Thanks Chris.

On 09/08/2016 10:52 AM, Chris Lamb wrote:
> Please clarify support/demo_template/base64.js in d/copyright on next upload.
>
>  -- Chris Lamb   Thu, 08 Sep 2016 08:52:19 +

Fixed in git.

Regards,

Ross

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

[Pkg-javascript-devel] Bug#836569: RFS: node-js-yaml/3.6.1+dfsg-1 [RFP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-js-yaml"

* Package name: node-js-yaml
  Version : 3.6.1+dfsg-1
  Upstream Author : Dervus Grim 
* URL : https://github.com/nodeca/js-yaml
* License : Expat
  Section : web

It builds this binary package:

node-js-yaml - YAML 1.2 parser and serializer

To access further information about this package, please visit the following
URL:

  https://mentors.debian.net/package/node-js-yaml


Alternatively, one can download the package with dget using this command:

dget -x https://mentors.debian.net/debian/pool/main/n/node-js-yaml/node-js-
yaml_3.6.1+dfsg-1.dsc

For Debian packaging, it will eventually be found here:
https://anonscm.debian.org/cgit/pkg-javascript/node-js-yaml.git

Changes since the last upload:

 * Initial release (Closes: #805411)


Regards,
Ross Gammon



-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-24-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

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

[Pkg-javascript-devel] Bug#818319: node-convert-source-map testsuite failing

[Ross Gammon]

tags 818319 upstream
forwarded 818319 https://github.com/thlorenz/convert-source-map/issues/36
thanks

So, inline-source-map is now in unstable. Unfortunately, the testsuite in the 
latest version of convert-source-map
fails with this version of inline-source-map.

I will eventually come back and see if I can fix it, but it is not urgent.



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

[Pkg-javascript-devel] Bug#835671: RFS: node-inline-source-map/0.6.1-1 [ITP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-inline-source-map"

* Package name: node-inline-source-map
  Version : 0.6.1-1
  Upstream Author : Thorsten Lorenz  (http://thlorenz.com)
* URL : https://github.com/thlorenz/inline-source-map
* License : Expat
  Section : web

It builds this binary package:

node-inline-source-map - base64 encoded source mappings for a generated file

To access further information about this package, please visit the following
URL:

https://mentors.debian.net/package/node-inline-source-map


Alternatively, one can download the package with dget using this command:

dget -x https://mentors.debian.net/debian/pool/main/n/node-inline-source-map
/node-inline-source-map_0.6.1-1.dsc

Packaging can be obtained from:
https://anonscm.debian.org/cgit/pkg-javascript/node-inline-source-map.git

Changes since the last upload:

  * Initial release (Closes: #795114)


Regards,
Ross Gammon



-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-24-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

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

[Pkg-javascript-devel] Bug#822256: RFP: node-expresso -- TDD framework, light-weight, fast, CI-friendly

[Ross Gammon]

Package: wnpp
Severity: wishlist

* Package name: node-expresso
  Version : 0.9.2
  Upstream Author : TJ Holowaychuk 
* URL : https://github.com/visionmedia/expresso
* License : Expat
  Programming Lang: JavaScript
  Description : TDD framework, light-weight, fast, CI-friendly

 Expresso is a TDD framework for nodejs.
 .
 Node.js is an event-based server-side JavaScript engine.

Expresso is required to run the upstream testsuite in node-seq, has no
dependencies at all, and probably should be maintained within the Debian
Javascript Team.

Regards,

Ross

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

[Pkg-javascript-devel] Bug#822251: node-seq: Testsuite not being run - requires expresso to be packaged

[Ross Gammon]

Package: node-seq
Version: 0.3.5-1
Severity: wishlist

Dear Maintainer,

The testsuite is not run at build time at the moment. Expresso needs to be
packaged to enable the tests.

Regards,

Ross



-- System Information:
Debian Release: jessie/sid
  APT prefers wily-updates
  APT policy: (500, 'wily-updates'), (500, 'wily-security'), (500, 'wily'), 
(100, 'wily-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-30-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

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

[Pkg-javascript-devel] Bug#820291: node-seq: uninstallable in sid: Depends: node-chainsaw (< 0.1) but 0.1.0-1 is to be installed

[Ross Gammon]

Hi,

I am not to worried about node-seq being removed from testing at the
moment, as there are many other dependencies requiring packaging for
browserify first.

It looks like it is is not a simple matter of updating the Depends:
field in debian/control.

Cloning the upstream repo, merging some fixes for the testsuite from a
fork, npm install'ing the dependencies gives me a passing test (Expresso
is required for the tests - I must file a bug about that).

npm update'ing the chainsaw dependency to 0.1.0 gives me the following
test failure when running "npm test":
   uncaught undefined: RangeError: Maximum call stack size exceeded
at action (/home/ross/github/node-seq/index.js:76:11)
at call (/home/ross/github/node-seq/index.js:236:17)
at Array.forEach (native)
at Object.parEach (/home/ross/github/node-seq/index.js:230:17)
at EventEmitter.saw.next
(/home/ross/github/node-seq/node_modules/chainsaw/index.js:62:18)
at Object.extend (/home/ross/github/node-seq/index.js:491:13)
at EventEmitter.saw.next
(/home/ross/github/node-seq/node_modules/chainsaw/index.js:62:18)
at EventEmitter.saw.jump
(/home/ross/github/node-seq/node_modules/chainsaw/index.js:143:13)
at Function.cb (/home/ross/github/node-seq/index.js:39:21)
at next (/home/ross/github/node-seq/index.js:266:26)

I will need to see what changed in chainsaw. But I will probably
concentrate on all the other browserify dependencies first.

Regards,

Ross



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

[Pkg-javascript-devel] Bug#818319: node-convert-source-map: Testsuite not enabled

[Ross Gammon]

Package: node-convert-source-map
Version: 1.1.3-1
Severity: normal

Dear Maintainer,

Since inline-source-map is not packaged yet, the upstream tests cannot be run.
Once inline-source-map gets packaged, we should enable the tests during the
build process.



-- System Information:
Debian Release: 8.3
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

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

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

[Pkg-javascript-devel] Bug#742347: Bug#742347: overview of the tilemill situation and alternatives (mapbox, kosmtik)

[Ross Gammon]

Hi Antoine,

Thanks for that excellent summary! It has cleared up a confusion that I
had. More below:

On 03/13/2016 04:40 PM, Antoine Beaupré wrote:
>  1. Mapbox people have released a new product in september 2014 named
> [Mapbox studio classic][]. the code is a
> [still freely available][] and seems to be a
> [fork of tilemill][]. mapbox classic still has releases on github,
> last one is from november 2015
> 
>  [Mapbox studio classic]: https://www.mapbox.com/mapbox-studio-classic/#linux
>  [still freely available]: https://github.com/mapbox/mapbox-studio-classic
>  [fork of tilemill]: 
> https://github.com/mapbox/mapbox-studio-classic/blob/mb-pages/docs/-01-01-common-questions.md#how-is-mapbox-studio-related-to-tilemill#user-content-how-is-mapbox-studio-classic-related-to-tilemill

Actually, it looks like mapbox-studio was renamed mapbox-studio-classic
when they released the new mapbox-studio [3] which runs online (after
sign up).

> 
>  2. It looks like Mapbox studio classic has some sort of
> [Mapbox.com lock-in][], and there are certainly new copyright
> issues, if only with the [bundled fonts][]. but it could probably
> be packaged.
> 
>  [Mapbox.com lock-in]: 
> https://github.com/mapbox/mapbox-studio-classic/blob/mb-pages/docs/-01-01-common-questions.md#can-i-use-git-with-a-style-or-source-project
>  [bundled fonts]: 
> https://github.com/mapbox/mapbox-studio-classic/blob/mb-pages/docs/-01-01-common-questions.md#what-cancant-i-do-with-pro-fonts

Yes. Mapbox-studio (classic) needs a log in, but is probably worthwhile
for access to all the datasets. I have not signed up yet :-)

> 
>  3. Then there's [mapbox studio][], which is a
> [full rewrite of mapbox][]. You need to "signup" somehow to get
> access, even though parts of the code are free, namely the
> [Mapbox GL studio][] project
> 
>  [Mapbox GL studio]: https://github.com/mapbox/mapbox-gl-native/
>  [full rewrite of mapbox]: https://www.mapbox.com/help/upgrading-from-classic/
>  [mapbox studio]: https://www.mapbox.com/mapbox-studio/
> 
>  4. The [Openstreetmap-carto][] developpers have mostly switched to
> [kosmtik][] instead of Mapbox.
> 
>  [Openstreetmap-carto]: https://github.com/gravitystorm/openstreetmap-carto
>  [kosmtik]: https://github.com/kosmtik/kosmtik

Kosmtik will be the quickest to package. But as stated in the readme:
"Alpha version, installable only from source". We would need to create
an executable (which upstream themselves believe they are not ready for).

>  6. Ross has an [ITP for kosmtik][]. The package is waiting on other
> node dependencies to be uploaded (yes, again).
>  
>  [ITP for kosmtik]: https://bugs.debian.org/805308

Feel free to help out by picking up one of the RFP's :-)

> 
>  7. There is also an [ITP for Mapbox-studio][] yet it is unclear to me
> what that one means because the source code to Mapbox-studio
> doesn't seem to be available, as far as i can tell (and the ITP
> doesn't say either).
> 
>  [ITP for Mapbox-studio]: https://bugs.debian.org/#761914

This is where the confusion was. $ npm install mapbox-studio gets you:
https://www.npmjs.com/package/mapbox-studio
This points you to the source at github.com/mapbox/mapbox-studio which
redirects to github.com/mapbox/mapbox-studio-classic!

> 
>  8. There's no WNPP bug for Mapbox studio *classic* that I can
> found.

So now there is! I will retitle the mapbox-studio RFP to
mapbox-studio-classic, and the relevant Javascript Team task page:
https://wiki.debian.org/Javascript/Nodejs/Tasks/mapbox-studio
There is plenty here that needs packaging.

 there's still an [RFP for tilemill][], which should
> probably be closed now because the project seems dead and plenty
> of alternatives exist. I wonder if node some dependencies that
> were packaged for Tilemill actually now need to be *removed* from
> Debian, because they have become useless leaf packages... I am
> leaving the Tilemill RFP open for someone to clean that up.
> 
>  [RFP for tilemill]: https://bugs.debian.org/644767

We should not be too hasty here. Some of the dependencies may still be
required by other mapping apps. Also, tilemill is not completely dead.
The mapbox employees are not allowed to work on tilemill during work
time, but they will merge pull requests, and are happy to give wider
commit access. Someone stated on one of their bugs that their personal
fork of tilemill is working and is willing to push those changes back.
So it could be resurrected yet.

Of course, some packages may get removed from stretch automatically (RC)
anyway.

Cheers,

Ross



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

[Pkg-javascript-devel] Bug#818189: RFP: node-browserify-zlib -- Full zlib module for browserify

[Ross Gammon]

Package: wnpp
Severity: wishlist

* Package name: node-browserify-zlib
  Version : 0.1.4
  Upstream Author : Devon Govett 
* URL : https://github.com/devongovett/browserify-zlib
* License : Expat
  Programming Lang: JavaScript
  Description : Full zlib module for browserify

 Emulates Node's zlib module for Browserify using pako. It uses the actual Node
 source code and passes the Node zlib tests by emulating the C++ binding that
 actually calls zlib.
 .
 Node.js is an event-based server-side JavaScript engine.

Node-browserify-zlib is required for browserity and would probably best be
maintained within the Debian Javascript Team.

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

[Pkg-javascript-devel] Bug#818188: RFP: node-assert -- commonjs assert - node.js api compatible

[Ross Gammon]

Package: wnpp
Severity: wishlist

* Package name: node-assert
  Version : 1.3.0
  Upstream Author : Roman Shtylman [http://shtylman.com/]
* URL : https://github.com/defunctzombie/commonjs-assert
* License : Expat
  Programming Lang: JavaScript
  Description : commonjs assert - node.js api compatible

 This module is used for writing unit tests for your applications, you can
 access it with require('assert').
 .
 The API is derived from the commonjs 1.0 unit testing spec and the node.js
 assert module
 .
 Node.js is an event-based server-side JavaScript engine.

node-assert is needed for browserify and would be best maintained within the
Debian Javascript Team.

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

[Pkg-javascript-devel] Bug#818100: RFS: node-seq/0.3.5-1 [ITP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-seq"

* Package name: node-seq
  Version : 0.3.5-1
  Upstream Author : James Halliday  (http://substack.net)
* URL : https://github.com/substack/node-seq
* License : Expat
  Section : web

It builds those binary packages:

node-seq   - Chainable asynchronous flow control

To access further information about this package, please visit the following
URL:

  http://mentors.debian.net/package/node-seq


Alternatively, one can download the package with dget using this command:

dget -x http://mentors.debian.net/debian/pool/main/n/node-seq/node-
seq_0.3.5-1.dsc

The packaging can be found here:
http://anonscm.debian.org/cgit/pkg-javascript/node-seq.git/

Changes since the last upload:

  * Initial release (Closes: #802008)


Regards,
Ross Gammon



-- System Information:
Debian Release: 8.3
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

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

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

[Pkg-javascript-devel] Bug#816552: RFS: node-json-localizer/0.0.3-1 [RFP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-json-localizer"

* Package name: node-json-localizer
  Version : 0.0.3-1
  Upstream Author : Yohan Boniface
* URL : https://github.com/yohanboniface/json-localizer/
* License : WTFPL
  Section : web

It builds this binary package:

node-json-localizer - Utility to localize a json object

To access further information about this package, please visit the following
URL:

  http://mentors.debian.net/package/node-json-localizer


Alternatively, one can download the package with dget using this command:

dget -x http://mentors.debian.net/debian/pool/main/n/node-json-localizer
/node-json-localizer_0.0.3-1.dsc

Debian packaging can be found here:
http://anonscm.debian.org/cgit/pkg-javascript/node-json-localizer.git

Changes since the last upload:

  * Initial release (Closes: #805413)


Regards,
Ross Gammon



-- System Information:
Debian Release: jessie/sid
  APT prefers wily-updates
  APT policy: (500, 'wily-updates'), (500, 'wily-security'), (500, 'wily'), 
(100, 'wily-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-30-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

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

[Pkg-javascript-devel] Bug#816195: RFP: node-jscs -- JavaScript Code Style

[Ross Gammon]

Package: wnpp
Severity: wishlist

* Package name: node-jscs
  Version : 2.10.1
  Upstream Author : Marat Dulin  (https://github.com/jscs-
dev/node-jscs/graphs/contributors)
* URL : http://jscs.info
* License : Expat
  Programming Lang: JavaScript
  Description : JavaScript Code Style

 SCS is a code style linter/formatter for programmatically enforcing your
 style guide. You can configure JSCS for your project/company using over 150
 validation rules, including presets from popular style guides like jQuery,
 Airbnb, Google, and more.
 .
 Node.js is an event-based server-side JavaScript engine.

Dependencies:
NPM   Debian
jscs (2.10.1) None
├─ babel-jscs (^2.0.0)None
├─ chalk (~1.1.0) None
├─ cli-table (~0.3.1) None
├─ commander (~2.9.0) node-commander (2.4.0-1)
├─ escope (^3.2.0)None
├─ esprima (~2.7.0)   None
├─ estraverse (^4.1.0)None
├─ exit (~0.1.2)  None
├─ glob (^5.0.1)  node-glob (4.0.5-1)
├─ htmlparser2 (3.8.3)node-htmlparser2
(3.7.3-1)
├─ js-yaml (~3.4.0)   None
├─ jscs-jsdoc (^1.3.1)None
├─ jscs-preset-wikimedia (~1.0.0) None
├─ jsonlint (~1.6.2)  None
├─ lodash (~3.10.0)   node-lodash
(2.4.1+dfsg-3)
├─ minimatch (~3.0.0) node-minimatch (1.0.0-1)
├─ natural-compare (~1.2.2)   None
├─ pathval (~0.1.1)   None
├─ prompt (~0.2.14)   None
├─ reserved-words (^0.1.1)None
├─ resolve (^1.1.6)   node-resolve (0.3.1-1)
├─ strip-bom (^2.0.0) None
├─ strip-json-comments (~1.0.2)   None
├─ to-double-quotes (^2.0.0)  None
├─ to-single-quotes (^2.0.0)  None
├─ vow (~0.4.8)   None
├─ vow-fs (~0.3.4)None
└─ xmlbuilder (^3.1.0)None

Build dependencies:
NPM   Debian
browserify (^12.0.0)  None
chai (^3.3.0) None
coveralls (~2.11.2)   None
has-ansi (~2.0.0) None
jshint (~2.8.0)   None
mocha (^2.2.0)node-mocha (1.20.1-1)
regenerate (~1.2.1)   None
rewire (^2.3.1)   None
sinon (^1.13.0)   None
sinon-chai (^2.8.0)   None
unicode-7.0.0 (~0.1.5)None
unit-coverage (^4.0.1)None
xml2js (~0.4.4)   node-xml2js (0.2.8-1)

Node-jscs is probably best maintained in the Debian Javascript Team.

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

[Pkg-javascript-devel] Bug#816194: RFP: node-covert -- code coverage command for javascript

[Ross Gammon]

Package: wnpp
Severity: wishlist

* Package name: node-covert
  Version : 1.1.0
  Upstream Author : James Halliday  (http://substack.net)
* URL : https://github.com/substack/covert
* License : Expat
  Programming Lang: JavaScript
  Description : code coverage command for javascript

 Most code coverage libraries do weird things I don't like, such as writing
 all their junk to directories and files in a completely out-of-band way.

 Covert only uses stderr and stdout, and doesn't write to any files. It
 bundles with browserify --bare and a transform instead of hijacking
 require(). All the reporting goes through a unix pipeline on process.stdin
 and process.stdout. It works really well with simple unix pipelines.
 .
 Node.js is an event-based server-side JavaScript engine.

Node-covert is needed for several node packages and would be best maintained
within the Debian Javascript Team.

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

[Pkg-javascript-devel] Bug#816191: RFS: node-function-bind/1.1.0-1 [RFP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-function-bind"

* Package name: node-function-bind
  Version : 1.1.0-1
  Upstream Author : Jake Verbaten 
* URL : https://github.com/Raynos/function-bind
* License : Expat
  Section : web

It builds this binary package:

node-function-bind - Implementation of Function.prototype.bind

To access further information about this package, please visit the following
URL:

  http://mentors.debian.net/package/node-function-bind


Alternatively, one can download the package with dget using this command:

dget -x http://mentors.debian.net/debian/pool/main/n/node-function-bind
/node-function-bind_1.1.0-1.dsc

Debian packaging can be found here:
http://anonscm.debian.org/cgit/pkg-javascript/node-function-bind.git/

Changes since the last upload:

  * Initial release (Closes: #814281)


Regards,
Ross Gammon



-- System Information:
Debian Release: 8.3
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

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

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

[Pkg-javascript-devel] Bug#814286: RFP: node-resumer -- a through stream that starts paused and resumes on the next tick

[Ross Gammon]

Package: wnpp
Severity: wishlist

* Package name: node-resumer
  Version : 0.0.0
  Upstream Author : James Halliday  (http://substack.net)
* URL : https://github.com/substack/resumer
* License : Expat
  Programming Lang: JavaScript
  Description : a through stream that starts paused and resumes on the next
tick

 Return a through stream that starts out paused and resumes on the next tick,
unless somebody called .pause().
 .
 This module has the same signature as through.
 .
 Node.js is an event-based server-side JavaScript engine.

Node-resumer is a dependency of node-tape (https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=798278) and should probably be maintained within the
Debian Javascript Team.

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

[Pkg-javascript-devel] Bug#814284: RFP: node-object-inspect -- string representations of objects in node and the browser

[Ross Gammon]

Package: wnpp
Severity: wishlist

* Package name: node-object-inspect
  Version : 1.1.0
  Upstream Author : James Halliday  (http://substack.net)
* URL : https://github.com/substack/object-inspect
* License : Expat
  Programming Lang: JavaScript
  Description : string representations of objects in node and the browser

 Node-object-inspect provides string representations of objects in node and the
browser.
 .
 Node.js is an event-based server-side JavaScript engine.

Node-object-inspect is a dependency of node-tape (https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=798278) and should probably be maintained within the
Debian Javascript Team.

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

[Pkg-javascript-devel] Bug#814283: RFP: node-has -- Object.prototype.hasOwnProperty.call shortcut

[Ross Gammon]

Package: wnpp
Severity: wishlist

* Package name: node-has
  Version : 1.0.1
  Upstream Author : Thiago de Arruda 
* URL : https://github.com/tarruda/has
* License : Expat
  Programming Lang: JavaScript
  Description : Object.prototype.hasOwnProperty.call shortcut

 Has is a shortcut for Object.prototype.hasOwnProperty.call.
 .
 Node.js is an event-based server-side JavaScript engine.

Node-has is a dependency of node-tape (https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=798278) and should probably be maintained within the
Debian Javascript Team.

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

[Pkg-javascript-devel] Bug#814281: RFP: node-function-bind -- Implementation of Function.prototype.bind

[Ross Gammon]

Package: wnpp
Severity: wishlist

* Package name: node-function-bind
  Version : 1.0.2
  Upstream Author : Raynos 
* URL : https://github.com/Raynos/function-bind
* License : Expat
  Programming Lang: JavaScript
  Description : Implementation of Function.prototype.bind

 Function-bind can be used for unit tests, and is useful for webframeworks that
do not have the function-bind.
 .
 Node.js is an event-based server-side JavaScript engine.

Node-function-bind is a dependency of node-tape (https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=798278), and should probably be maintained within the
Debian Javascript Team.

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

[Pkg-javascript-devel] Bug#809499: RFP: node-es6ify -- browserify v2 transform to compile ES6 to ES5 on the fly

[Ross Gammon]

Package: wnpp
Severity: wishlist

* Package name: node-es6ify
  Version : 1.6.0
  Upstream Author : Thorsten Lorenz [http://thlorenz.com/]
* URL : https://thlorenz.github.io/es6ify/
* License : Expat
  Programming Lang: Javacript
  Description : browserify v2 transform to compile ES6 to ES5 on the fly

Es6ify uses a browserify v2 transform to compile JavaScript.next (ES6) to
JavaScript.current (ES5) on the fly.

Node.js is an event-based server-side JavaScript engine.

node-isstream is a build dependency of Browserify
(https://bugs.debian.org/780357).

Dependencies:
NPM   Debian
es6ify (1.6.0)None
├─ through (~2.2.7)   node-through2 (1.1.1-1)
├─ traceur (0.0.79)   None
│  ├─ commander (2.6) node-commander
(2.4.0-1)
│  ├─ glob (4.3)  node-glob (4.0.5-1)
│  ├─ rsvp (^3.0.13)  None
│  ├─ semver (2.x)node-semver (2.1.0-2)
│  └─ source-map-support (~0.2.8) None
│ └─ source-map (0.1.32)  node-source-map
(0.1.40-1)
└─ xtend (~2.2.0) node-extend (2.0.0-1)

Warnings occured:
 [warning] xtend: extend does the same job
 [warning] through: through2 is better maintained, see node-jsonstream for a
patch

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

[Pkg-javascript-devel] Bug#809493: RFP: node-browser-unpack -- parse a bundle generated by browser-pack

[Ross Gammon]

Package: wnpp
Severity: wishlist

* Package name: node-browser-unpack
  Version : 1.1.1
  Upstream Author : James Halliday 
* URL : https://github.com/substack/browser-unpack
* License : Expat
  Programming Lang: Javascript
  Description : parse a bundle generated by browser-pack

Browser-unpack parses a bundle generated by browser-pack. Browser-pack packs
node-style source files from a json stream into a browser bundle.

Node.js is an event-based server-side JavaScript engine.

Node-isstream is a build dependency of Browserify
(https://bugs.debian.org/780357).

Dependencies:
NPM   Debian
browser-unpack (1.1.1)None
├─ acorn (^2.1.0) None
├─ browser-pack (^5.0.1)  None
├─ concat-stream (^1.5.0) None
└─ minimist (^1.1.1)  None

Build dependencies:
NPM   Debian
browser-pack (~2.0.0) None
tape (^4.0.1) None

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

[Pkg-javascript-devel] Bug#809407: RFS: node-isstream/0.1.2+dfsg-1 [ITP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-isstream"

* Package name: node-isstream
  Version : 0.1.2+dfsg-1
  Upstream Author : Rod Vagg 
* URL : https://github.com/rvagg/isstream
* License : Expat
  Section : web

It builds this binary package:

node-isstream - Determine if an object is a Stream

To access further information about this package, please visit the following
URL:

  http://mentors.debian.net/package/node-isstream


Alternatively, one can download the package with dget using this command:

dget -x http://mentors.debian.net/debian/pool/main/n/node-isstream/node-
isstream_0.1.2+dfsg-1.dsc

The Debian packaging can eventually be found here:
http://anonscm.debian.org/cgit/pkg-javascript/node-isstream.git

Changes since the last upload:

  * Initial release (Closes: #802012)
  * Patch README.md to fix spelling

Regards,
Ross Gammon



-- System Information:
Debian Release: 8.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

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

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

[Pkg-javascript-devel] Bug#809401: RFS: node-isarray/1.0.0-1

[Ross Gammon]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "node-isarray"

* Package name: node-isarray
  Version : 1.0.0-1
  Upstream Author : Julian Gruber 
(http://juliangruber.com)
* URL : https://github.com/juliangruber/isarray
* License : Expat
  Section : web

It builds this binary package:

node-isarray - JavaScript Array#isArray for older browsers

To access further information about this package, please visit the following
URL:

  http://mentors.debian.net/package/node-isarray


Alternatively, one can download the package with dget using this command:

dget -x http://mentors.debian.net/debian/pool/main/n/node-isarray/node-
isarray_1.0.0-1.dsc

The Debian packaging is available here:
http://anonscm.debian.org/cgit/pkg-javascript/node-isarray.git

Changes since the last upload:

  * New upstream release
  * Override dh_auto_build & test targets


Regards,
Ross Gammon



-- System Information:
Debian Release: 8.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

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

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

[Pkg-javascript-devel] Bug#808823: RFS: node-cross-spawn-async/2.1.1-1

[Ross Gammon]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "node-cross-spawn-async"

* Package name: node-cross-spawn-async
  Version : 2.1.1-1
  Upstream Author : Indigo United 
* URL : https://github.com/IndigoUnited/node-cross-spawn-async
* License : Expat
  Section : web

It builds this binary package:

node-cross-spawn-async - Cross platform child_process#spawn

To access further information about this package, please visit the following
URL:

  http://mentors.debian.net/package/node-cross-spawn-async


Alternatively, one can download the package with dget using this command:

dget -x http://mentors.debian.net/debian/pool/main/n/node-cross-spawn-async
/node-cross-spawn-async_2.1.1-1.dsc

The Debian packaging can be found here:
https://anonscm.debian.org/cgit/pkg-javascript/node-cross-spawn-async.git

Changes since the last upload:

  * New upstream release
  * Refresh patches
  * Add node-rimraf build dependency for tests & patch the new test

Regards,
Ross Gammon



-- System Information:
Debian Release: 8.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

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

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

[Pkg-javascript-devel] Bug#808354: RFS: node-core-util-is/1.0.2-1

[Ross Gammon]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "node-core-util-is"

* Package name: node-core-util-is
  Version : 1.0.2-1
  Upstream Author : Isaac Z. Schlueter 
* URL : https://github.com/isaacs/core-util-is
* License : Expat
  Section : web

It builds this binary package:

node-core-util-is - util.is* functions introduced in Node v0.12 for older
versions

To access further information about this package, please visit the following
URL:

  http://mentors.debian.net/package/node-core-util-is


Alternatively, one can download the package with dget using this command:

dget -x http://mentors.debian.net/debian/pool/main/n/node-core-util-is
/node-core-util-is_1.0.2-1.dsc

The Debian packaging can be found here:
http://anonscm.debian.org/cgit/pkg-javascript/node-core-util-is.git

Changes since the last upload:

  * New upstream release
  * Update copyright due to new LICENSE file added upstream
  * Use https for Vcs Browser URL
  * Enable new tests provided by upstream
  * Patch upstream test to require assert instead of tap
  * Unapply patches from source

Regards,
Ross Gammon



-- System Information:
Debian Release: jessie/sid
  APT prefers wily-updates
  APT policy: (500, 'wily-updates'), (500, 'wily-security'), (500, 'wily'), 
(100, 'wily-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-19-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

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

[Pkg-javascript-devel] Bug#802224: Latest node-source-map now needs webpack

[Ross Gammon]

Hi,

I checked with Leo if he would be okay with me doing the update of
node-source-map, and he was.

But unfortunately, whilst the current version uses a makefile to build,
the latest upstream needs webpack to build, which has not yet been packaged.

I will do an RFP/ITP soon.

Regards,

Ross



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

[Pkg-javascript-devel] Bug#742347: Bug#742347: Fwd: Re: Bug#742347: Bug#742347: tilemill vs mapbox studio?

[Ross Gammon]

On 11/06/2015 04:16 PM, Ross Gammon wrote:
> I will do an ITP & create a task page over the weekend. But please jump
> in when/if any of you like. My current work rate is not very high (one
> package every other day).

Sorry it took so long. I had problems with creating the Task page
(python script borking due to some string substitution problem I
couldn't track down).

So I have created an ITP for kosmtik, and blocked it with some RFPs &
existing ITPs (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805308).

We should probably move any further discussion of kosmtik there.

Feel free to chip in with some packaging (including any of my ITPs if I
am too slow).

Cheers,

Ross



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

[Pkg-javascript-devel] Bug#805415: RFP: node-leaflet-formbuilder -- Helpers to build forms in Leaflet

[Ross Gammon]

Package: wnpp
Severity: wishlist
Owner: Ross Gammon 
X-Debbugs-CC: pkg-javascript-devel@lists.alioth.debian.org

* Package name: node-leaflet-formbuilder
  Version : 0.2.1
  Upstream Author : Yohan Boniface
* URL :
https://github.com/yohanboniface/Leaflet.FormBuilder#readme
* License : WTFPL
  Programming Lang: JavaScript
  Description : Helpers to build forms in Leaflet

 Helpers to build forms synchronized with Leaflet objects.
 .
 Node.js is an event-based server-side JavaScript engine.

node-leaflet-formbuilder is required for node-kosmtik and has no
dependencies.



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

[Pkg-javascript-devel] Bug#805413: Subject: RFP: node-json-localizer -- Utility to localize a json object

[Ross Gammon]

Package: wnpp
Severity: wishlist
Owner: Ross Gammon 
X-Debbugs-CC: debian-de...@lists.debian.org
X-Debbugs-CC: pkg-javascript-devel@lists.alioth.debian.org

* Package name: node-json-localizer
  Version : 0.0.3
  Upstream Author : Yohan Boniface
* URL : https://github.com/yohanboniface/json-localizer/
* License : WTFPL
  Programming Lang: JavaScript
  Description : Utility to localize a json object

 When you need humans to localize a json object from a config file. Typical
 use case is for a local config file to extend an application config on the
 fly.
 .
 Node.js is an event-based server-side JavaScript engine.

node-json-localizer is required for node-kosmtik, and has no dependencies.



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

[Pkg-javascript-devel] Bug#805411: Subject: RFP: node-js-yaml -- YAML 1.2 parser and serializer

[Ross Gammon]

Package: wnpp
Severity: wishlist
Owner: Ross Gammon 
X-Debbugs-CC: debian-de...@lists.debian.org
X-Debbugs-CC: pkg-javascript-devel@lists.alioth.debian.org

* Package name: node-js-yaml
  Version : 3.4.3
  Upstream Author : Dervus Grim 
* URL : https://github.com/nodeca/js-yaml
* License : Expat
  Programming Lang: JavaScript
  Description : YAML 1.2 parser and serializer

 This is a Javascript implementation of YAML, a human friendly data
 serialization language. Started as PyYAML port, it was completely rewritten
 from scratch. Now it's very fast, and supports 1.2 spec.
 .
 Node.js is an event-based server-side JavaScript engine.

node-js-yaml is required for node-kosmtik
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805308).

Dependencies:
NPM   Debian
js-yaml (3.4.3)   None
├─ argparse (^1.0.2)  None
└─ esprima (^2.6.0)   None

Build dependencies:
NPM   Debian
ansi (*)  node-ansi (0.3.0-2)
benchmark (*) None
eslint (0.24.1)   None
eslint-plugin-nodeca (^1.0.3) None
istanbul (*)  None
mocha (*) node-mocha (1.20.1-1)



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

[Pkg-javascript-devel] Bug#804451: RFS: node-concat-stream/1.5.1-1 [ITP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-concat-stream"

* Package name: node-concat-stream
  Version : 1.5.1-1
  Upstream Author : [fill in name and email of upstream]
* URL : [fill in URL of upstreams web site]
* License : [fill in]
  Section : web

It builds this binary package:

node-concat-stream - writable stream that concatenates strings

To access further information about this package, please visit the following
URL:

  http://mentors.debian.net/package/node-concat-stream


Alternatively, one can download the package with dget using this command:

dget -x http://mentors.debian.net/debian/pool/main/n/node-concat-stream
/node-concat-stream_1.5.1-1.dsc

Debian packaging can be found be found here:
http://anonscm.debian.org/cgit/pkg-javascript/node-concat-stream.git

Changes since the last upload:

  * Initial release (Closes: #796351)


Regards,
Ross Gammon



-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-31-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

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

[Pkg-javascript-devel] Bug#804252: RFS: node-readable-stream/2.0.3-1 [ITP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-readable-stream"

* Package name: node-readable-stream
  Version : 2.0.3-1
  Upstream Author : Streams WG Team 
* URL : https://github.com/nodejs/readable-stream#readme
* License : Expat
  Section : web

It builds this binary package:

node-readable-stream - Streams3, a user-land copy of the stream library from
iojs v2.x

To access further information about this package, please visit the following
URL:

http://mentors.debian.net/package/node-readable-stream


Alternatively, one can download the package with dget using this command:

dget -x http://mentors.debian.net/debian/pool/main/n/node-readable-stream/node-
readable-stream_2.0.3-1.dsc

Debian packaging can be found here:
http://anonscm.debian.org/cgit/pkg-javascript/node-readable-stream.git

Changes since the last upload:

  * Initial release (Closes: #796355)


Regards,
Ross Gammon



-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-31-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

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

[Pkg-javascript-devel] Bug#742347: Fwd: Re: Bug#742347: Bug#742347: tilemill vs mapbox studio?

[Ross Gammon]

Sorry - dropping the bug and Antoine was unintentional, so forwarding my
reply to javascript list. Also not sure if Bas is still readiing
Javascript list (so cc'd).


 Forwarded Message 
Subject: Re: [Pkg-javascript-devel] Bug#742347: Bug#742347: tilemill vs
mapbox studio?
Date: Fri, 6 Nov 2015 15:57:58 +0100
From: Ross Gammon 
To: pkg-javascript-devel@lists.alioth.debian.org

On 11/05/2015 05:11 PM, Jérémy Lal wrote:
> 
> 
> 2015-11-05 17:04 GMT+01:00 Bas Couwenberg  <mailto:sebas...@xs4all.nl>>:
> 
> On 2015-11-05 16:59, Antoine Beaupré wrote:
> 
> On 2015-11-05 09:52:19, Bas Couwenberg wrote:
> 
> The openstreetmap-carto developers have mostly switched to
> kosmtic:
> 
> https://github.com/kosmtik/kosmtik
> 
> 
> is that a fork of tilemill? how does it differ?
> 
> 
> It's not a fork. It's not a Mapbox project.
> 
> maybe a new ITP should be opened for this then?
> 
> 
> It's still alpha, but shows much more promise than mapbox-studio as
> an alternative to tilemill.
> 
> If you want to spend time packaging an alternative for tilemill, I
> think kosmtik is your best option.
> 
> 
> Indeed it looks like an alternative to tilemill.
> Mapbox studio classic is not really as good, and to be released mapbox
> studio (but i don't know when)
> is very promising.

Every now and then I try running tilemill from the github source tree to
see if it is close to something that could be packaged. But I didn't
have success the last couple of times. There is certainly no sniff of a
coming release. It is a shame considering all of the hard work Dave put
in to package all the dependencies.

Not knowing about kosmtk, I started working on mapbox (the one released
in npm):
https://wiki.debian.org/Javascript/Nodejs/Tasks/mapbox-studio
Feel free to grab one of the dependencies to package if you are looking
for work.

But kosmtik certainly looks like it would be a much quicker win, and a
better place to start:
$ npm2deb depends kosmtik
Dependencies:
NPM   Debian
kosmtik (0.0.12)  None
├─ carto (^0.15.2)node-carto (0.9.5-2)
├─ generic-pool (^2.2.0)  node-generic-pool
(2.0.3-1)
├─ js-yaml (^3.4.2)   None
├─ json-localizer (0.0.3) None
├─ leaflet (^0.7.3)   None
├─ leaflet-formbuilder (^0.2.0)   None
├─ leaflet-hash (^0.2.1)  None
├─ mapnik (^3.4.7)node-mapnik
(1.2.3-1build1)
├─ nomnom (^1.8.1)None
├─ npm (^3.3.5)   None
├─ request (^2.64.0)  node-request
(2.26.1-1)
└─ semver (^5.0.3)node-semver (2.1.0-2)

Build dependencies:
NPM   Debian
mocha (^2.2.5)node-mocha (1.20.1-1)

I will do an ITP & create a task page over the weekend. But please jump
in when/if any of you like. My current work rate is not very high (one
package every other day).

Cheers,

Ross




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


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

Re: [Pkg-javascript-devel] Bug#742347: Bug#742347: tilemill vs mapbox studio?

[Ross Gammon]

On 11/05/2015 05:11 PM, Jérémy Lal wrote:
> 
> 
> 2015-11-05 17:04 GMT+01:00 Bas Couwenberg  >:
> 
> On 2015-11-05 16:59, Antoine Beaupré wrote:
> 
> On 2015-11-05 09:52:19, Bas Couwenberg wrote:
> 
> The openstreetmap-carto developers have mostly switched to
> kosmtic:
> 
> https://github.com/kosmtik/kosmtik
> 
> 
> is that a fork of tilemill? how does it differ?
> 
> 
> It's not a fork. It's not a Mapbox project.
> 
> maybe a new ITP should be opened for this then?
> 
> 
> It's still alpha, but shows much more promise than mapbox-studio as
> an alternative to tilemill.
> 
> If you want to spend time packaging an alternative for tilemill, I
> think kosmtik is your best option.
> 
> 
> Indeed it looks like an alternative to tilemill.
> Mapbox studio classic is not really as good, and to be released mapbox
> studio (but i don't know when)
> is very promising.

Every now and then I try running tilemill from the github source tree to
see if it is close to something that could be packaged. But I didn't
have success the last couple of times. There is certainly no sniff of a
coming release. It is a shame considering all of the hard work Dave put
in to package all the dependencies.

Not knowing about kosmtk, I started working on mapbox (the one released
in npm):
https://wiki.debian.org/Javascript/Nodejs/Tasks/mapbox-studio
Feel free to grab one of the dependencies to package if you are looking
for work.

But kosmtik certainly looks like it would be a much quicker win, and a
better place to start:
$ npm2deb depends kosmtik
Dependencies:
NPM   Debian
kosmtik (0.0.12)  None
├─ carto (^0.15.2)node-carto (0.9.5-2)
├─ generic-pool (^2.2.0)  node-generic-pool
(2.0.3-1)
├─ js-yaml (^3.4.2)   None
├─ json-localizer (0.0.3) None
├─ leaflet (^0.7.3)   None
├─ leaflet-formbuilder (^0.2.0)   None
├─ leaflet-hash (^0.2.1)  None
├─ mapnik (^3.4.7)node-mapnik
(1.2.3-1build1)
├─ nomnom (^1.8.1)None
├─ npm (^3.3.5)   None
├─ request (^2.64.0)  node-request (2.26.1-1)
└─ semver (^5.0.3)node-semver (2.1.0-2)

Build dependencies:
NPM   Debian
mocha (^2.2.5)node-mocha (1.20.1-1)

I will do an ITP & create a task page over the weekend. But please jump
in when/if any of you like. My current work rate is not very high (one
package every other day).

Cheers,

Ross



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

[Pkg-javascript-devel] Bug#803979: RFS: node-string-decoder/0.10.25-1 [ITP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-string-decoder"

* Package name: node-string-decoder
  Version : 0.10.25-1
  Upstream Author : Rod Vagg 
* URL : https://github.com/rvagg/string_decoder
* License : Expat
  Section : web

It builds this binary package:

node-string-decoder - string_decoder module from Node core for browsers

To access further information about this package, please visit the following
URL:

http://mentors.debian.net/package/node-string-decoder


Alternatively, one can download the package with dget using this command:

dget -x http://mentors.debian.net/debian/pool/main/n/node-string-decoder/node-
string-decoder_0.10.25-1.dsc

The Debian packaging can be found here:

http://anonscm.debian.org/cgit/pkg-javascript/node-string-decoder.git

Changes since the last upload:

  [ Bas Couwenberg ]
  * Initial release (Closes: #779998)

Regards,
Ross Gammon



-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-31-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

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

[Pkg-javascript-devel] Bug#802603: RFS: node-defined/1.0.0-1 [ITP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-defined"

* Package name: node-defined
  Version : 1.0.0-1
  Upstream Author : James Halliday  (http://substack.net)
* URL : https://github.com/substack/defined
* License : Expat
  Section : web

It builds this binary package:

node-defined - return the first argument that is `!== undefined`

To access further information about this package, please visit the following
URL:

  http://mentors.debian.net/package/node-defined


Alternatively, one can download the package with dget using this command:

dget -x http://mentors.debian.net/debian/pool/main/n/node-defined/node-
defined_1.0.0-1.dsc

Debian packaging can be found here:
http://anonscm.debian.org/cgit/pkg-javascript/node-defined.git/

Changes since the last upload:

  * Initial release (Closes: #802595)


Regards,
Ross Gammon



-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-30-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

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

[Pkg-javascript-devel] Bug#802529: RFS: node-deep-equal/1.0.1-1 [ITP]

[Ross Gammon]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-deep-equal"

* Package name: node-deep-equal
  Version : 1.0.1-1
  Upstream Author : James Halliday  (http://substack.net)
* URL : https://github.com/substack/node-deep-equal#readme
* License : Expat
  Section : web

It builds this binary package:

node-deep-equal - node's assert.deepEqual algorithm

To access further information about this package, please visit the following
URL:

  http://mentors.debian.net/package/node-deep-equal


Alternatively, one can download the package with dget using this command:

dget -x http://mentors.debian.net/debian/pool/main/n/node-deep-equal/node-
deep-equal_1.0.1-1.dsc

Debian packaging can be found here:
http://anonscm.debian.org/cgit/pkg-javascript/node-deep-equal.git

Changes since the last upload:

  * Initial release (Closes: #802518)


Regards,
Ross Gammon



-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-30-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

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

[Pkg-javascript-devel] Bug#802518: ITP: node-deep-equal -- node's assert.deepEqual algorithm

[Ross Gammon]

Package: wnpp
Severity: wishlist
Owner: Ross Gammon 

* Package name: node-deep-equal
  Version : 1.0.1
  Upstream Author : James Halliday  (http://substack.net)
* URL : https://github.com/substack/node-deep-equal#readme
* License : Expat
  Programming Lang: Javascript
  Description : node's assert.deepEqual algorithm

 Node's assert.deepEqual() algorithm as a standalone module.
 .
 This module is around 5 times faster than wrapping assert.deepEqual()
 in a try/catch.
 .
 Node.js is an event-based server-side JavaScript engine.

Node-deep-equal is required for tape
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798278) and will be
maintained within the Debian Javascript Team.

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

[Pkg-javascript-devel] Bug#802516: RFS: node-util-deprecate/1.0.2-1

[Ross Gammon]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "node-util-deprecate"

* Package name: node-util-deprecate
  Version : 1.0.2-1
  Upstream Author : Nathan Rajlich  (http://n8.io/)
* URL : https://github.com/TooTallNate/util-deprecate
* License : MIT
  Section : web

It builds this binary package:

node-util-deprecate - Node.js's `util.deprecate()` function with browser
support

To access further information about this package, please visit the following
URL:

http://mentors.debian.net/package/node-util-deprecate


Alternatively, one can download the package with dget using this command:

dget -x http://mentors.debian.net/debian/pool/main/n/node-util-deprecate/node-
util-deprecate_1.0.2-1.dsc

The Debian packaging can be found here:
https://anonscm.debian.org/cgit/pkg-javascript/node-util-deprecate.git/

Changes since the last upload:

 * New upstream release


Regards,
Ross Gammon



-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-30-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

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