On Fri, Jun 27, 2014 at 12:35 AM, Emilien Klein
wrote:
> Hi andrewrk,
>
> Let us know if you need more information.
A couple questions for you:
1. Should I create ITPs for each and every one of the new modules (about
65)?
2. How does one package up modules that contain C++ code?
For me these
On Fri, Jun 27, 2014 at 1:39 PM, Jérémy Lal wrote:
> Le vendredi 27 juin 2014 à 21:28 +0200, Emilien Klein a écrit :
> > 2014-06-27 17:34 GMT+02:00 Andrew Kelley :
> > > On Fri, Jun 27, 2014 at 12:35 AM, Emilien Klein <
> emilien+deb...@klein.st>
> > > wrote
same job (but it works only for two
objects), see node-through2 for a patch
[error] readable-stream: Only nodejs >= 0.10.x is in debian, see
node-multiparty for a patch
On Thu, Jun 26, 2014 at 1:19 PM, Andrew Kelley wrote:
> Hello pkg-javascript-devel team,
>
> I am andrewrk fr
Hello pkg-javascript team,
I have completed many Node.js packages and more are on the way. I'm looking
for someone to sponsor these packages:
node-abstract-leveldown
node-ansi-regex
node-ansi-styles
node-bindings < node-leveldown depends on this one
node-bl
node-crc32-stream
node-def
brary-index (depends on diacritics)
node-mv (depends on ncp)
node-ncp
node-pend
node-prr
node-strip-ansi (depends on ansi-regex)
node-stylus
node-supports-color
node-tar-stream (depends on bl and end-of-stream)
node-zfill
On Sun, Jun 29, 2014 at 9:25 PM, A
from #debian-multimedia
andrewrk: why did you remove the ncp binary?
fsateler, it clutters up the global bin namespace, and why would
you ever use it instead of plain old cp ?
it seems common for node module authors to include useless
binaries with their libraries
another one: https://github.c
,
debug 1.0.2)
On Mon, Jun 30, 2014 at 8:41 AM, Andrew Kelley wrote:
> Updated ready-for-sponsorship list. I'll try to keep this email to one per
> day from now on.
>
> node-abstract-leveldown
> node-ansi-regex
> node-ansi-styles
> node-bindings
> node-bl
> node-
The proper package for upstream to depend on is uuid:
https://www.npmjs.org/package/uuid
I'd rather patch upstream sources that incorrectly do require('node-uuid')
instead of patching upstream sources (mine included) that correctly do
require('uuid').
__
at the network graph you can see uuid is at least equally well
maintained, if not better: https://github.com/broofa/node-uuid/network
On Fri, Jul 4, 2014 at 12:31 PM, Jérémy Lal wrote:
> Le vendredi 04 juillet 2014 à 12:14 -0700, Andrew Kelley a écrit :
> > The proper package f
On Fri, Jul 4, 2014 at 2:24 PM, Leo Iannacone wrote:
>
> >> Le vendredi 04 juillet 2014 à 12:14 -0700, Andrew Kelley a écrit :
> >> > I'd rather patch upstream sources that incorrectly do
> require('node-uuid')
> >> > instead of patch
As an upstream author I'm happy to switch to using uid-safe. I don't know
what you're referring to with 'mz'.
On Fri, Jul 4, 2014 at 5:20 PM, Leo Iannacone wrote:
> On 5 July 2014 00:16, Andrew Kelley wrote:
> > On Fri, Jul 4, 2014 at 2:24 PM, Leo Iannacone
Thorsten,
My apologies for not noticing this. Good catch. I will be more careful in
the future.
On Fri, Jul 11, 2014 at 5:00 AM, Thorsten Alteholz <
ftpmas...@ftp-master.debian.org> wrote:
>
> Hi Andrew,
>
> unfortunately I have to reject your package.
>
> The license in LICENSE does not match
On Mon, Jul 28, 2014 at 4:26 AM, Thorsten Alteholz <
ftpmas...@ftp-master.debian.org> wrote:
> danse.ogg seems to be created by Kevin MacLeod. Normally he licenses his
> stuff under CC BY. Can you please confirm that he is the author and then
> add an entry to debian/copyright.
Good catch Thorst
On Sat, Jul 12, 2014 at 3:57 AM, Frederic Peters wrote:
> Steve McIntyre wrote:
>
> > I've seen ITPs for a massive set of tiny-looking node libraries go
> > past on -devel in the last few months, so I thought it was about time
> > I looked at one. I'm a bit worried by what I've seen, considering
OK.
Thorsten,
Please feel free to reject node-errno as well. The upstream repository that
I am ultimately trying to get all the dependencies uploaded for is now
updated to have less dependencies, and among others, node-errno is no
longer required. I am unaware of any other projects that intend to
On Thu, Sep 11, 2014 at 2:06 PM, Jérémy Lal wrote:
> Moving to pkg-javascript
>
> Le jeudi 11 septembre 2014 à 10:03 -0700, Andrew Kelley a écrit :
> > node-mv
>
> nodemodules-fs
>
Looks like this is not started yet, so I will start it.
>
> > node-connect-s
On Tue, Sep 9, 2014 at 12:52 PM, Jérémy Lal wrote:
>
> i think method 2 of
> https://wiki.debian.org/Renaming_a_Package
>
> applies here. Can you do it, then i'll review and upload ?
>
All done and ready for review.
___
Pkg-javascript-devel mailing list
On Thu, Sep 11, 2014 at 2:28 PM, Andrew Kelley wrote:
>
> > node-connect-static
>>
>> i know it's easier said than done, but can you consider doing a PR to
>> serve-static with the feature(s) you're missing ?
>>
>> if not, then yes, bundle it insi
On Thu, Sep 11, 2014 at 9:50 PM, Andrew Kelley wrote:
> On Tue, Sep 9, 2014 at 12:52 PM, Jérémy Lal wrote:
>>
>> i think method 2 of
>> https://wiki.debian.org/Renaming_a_Package
>>
>> applies here. Can you do it, then i'll review and upload ?
>>
>
I am working on packaging jsondiffpatch:
https://github.com/benjamine/jsondiffpatch
This would be:
Source package: jsondiffpatch.js
Node package: node-jsondiffpatch
libjs package: libjs-jsondiffpatch
Node package part is done. The hard part is the libjs package. The
repository ships with build/*
On Sat, Sep 20, 2014 at 7:33 PM, Jérémy Lal wrote:
> * npm actually discourages "npm install -g" in favor of
> cd thismodule; npm link
> cd thatmodule; npm link thismodule
>
I think npm encourages using `npm install` which would put dependencies in
a local folder called "node_modules" and wo
On Thu, Oct 2, 2014 at 5:39 AM, Thorsten Alteholz <
ftpmas...@ftp-master.debian.org> wrote:
> I marked your package for accept, but please remove the samples and test
> directories from the source tarball (or take care of the minified files
> in it).
>
Thank you. I will do that right away.
By th
To provide a possible alternative for upstream projects which depend on
browserify, which is a heavy dependency dragging many things along with it,
I have created a module called browserify-lite:
https://github.com/andrewrk/browserify-lite
My question, should I package this module for Debian? Or
On Oct 2, 2014 11:49 PM, "Jérémy Lal" wrote:
>
> Le jeudi 02 octobre 2014 à 20:57 -0700, Andrew Kelley a écrit :
> > To provide a possible alternative for upstream projects which depend on
> > browserify, which is a heavy dependency dragging many things along with
it,
See
https://github.com/andrewrk/node-multiparty/commit/11780f4a6e3e8c6d439639794c795bb5fdaefe97#commitcomment-8163898
According to this, if a package depends on readable-stream 1.1.x, then it
is actually puling in node 0.11 stream API. This means that patching it to
use built-in v0.10.29 stream AP
I fixed all the bugs in node-findit and submitted the patch to upstream:
https://github.com/substack/node-findit/pull/34
But I am afraid that upstream will not accept my code and I do not have
time to wait. So I have forked findit to findit2 and started using that in
my modules, because it fixes b
On Wed, Oct 15, 2014 at 12:44 AM, Jérémy Lal wrote:
> > What should I do?
>
> Since both have same API, i'd add your patches as quilt patches to
> node-findit that is already in debian and add a binary package
> node-findit2 (symlinking /usr/lib/nodejs/findit to findit2).
>
> Or the reverse, chan
On Thu, Oct 16, 2014 at 2:17 PM, Andrew Kelley wrote:
> On Wed, Oct 15, 2014 at 12:44 AM, Jérémy Lal wrote:
>
>> > What should I do?
>>
>> Since both have same API, i'd add your patches as quilt patches to
>> node-findit that is already in debian an
On Fri, Oct 17, 2014 at 12:15 AM, Jérémy Lal wrote:
> Le jeudi 16 octobre 2014 à 14:17 -0700, Andrew Kelley a écrit :
> > On Wed, Oct 15, 2014 at 12:44 AM, Jérémy Lal wrote:
> >
> > > > What should I do?
> > >
> > > Since both have same API, i'
On Fri, Oct 17, 2014 at 3:40 PM, Jérémy Lal wrote:
> Le vendredi 17 octobre 2014 à 15:04 -0700, Andrew Kelley a écrit :
> > On Fri, Oct 17, 2014 at 12:15 AM, Jérémy Lal wrote:
> >
> > > Le jeudi 16 octobre 2014 à 14:17 -0700, Andrew Kelley a écrit :
> > > &
On Fri, Oct 17, 2014 at 3:43 PM, Andrew Kelley wrote:
>
>
> On Fri, Oct 17, 2014 at 3:40 PM, Jérémy Lal wrote:
>
>> Le vendredi 17 octobre 2014 à 15:04 -0700, Andrew Kelley a écrit :
>> > On Fri, Oct 17, 2014 at 12:15 AM, Jérémy Lal wrote:
>> >
>>
Good idea. Done.
On Fri, Oct 17, 2014 at 4:06 PM, Jérémy Lal wrote:
> Le vendredi 17 octobre 2014 à 16:03 -0700, Andrew Kelley a écrit :
> > Alright, node-findit2 is packaged up and ready for review and upload. I
> > think we should send a note to the FTP masters that it will r
On Oct 17, 2014 4:11 PM, "Andrew Kelley" wrote:
>
> Good idea. Done.
>
> On Fri, Oct 17, 2014 at 4:06 PM, Jérémy Lal wrote:
>> Maybe it can be written in the long description of the package ?
>> "This module is a backward-compatible rewrite of node-fin
On Sun, Oct 19, 2014 at 5:34 PM, Debian FTP Masters <
ftpmas...@ftp-master.debian.org> wrote:
> binary:node-findit2 is NEW.
> source:node-findit2 is NEW.
>
> Your package has been put into the NEW queue, which requires manual action
> from the ftpteam to process.
>
Hi FTP masters,
This module, n
Leo,
The upstream maintainer of serve-static is going to release 1.6.5 (1.6.4
currently in danger of getting removed from debian) with the bug fix in it:
https://github.com/expressjs/serve-static/commit/0399e399935bab99530d6926094b4451438c2d50#commitcomment-9590955
When that happens will you go
It seems I have been unsubscribed from pkg-javascript-devel for some reason
and I did not see
http://lists.alioth.debian.org/pipermail/pkg-javascript-devel/2015-January/009894.html
until now.
On Wed, Feb 4, 2015 at 1:16 PM, Andrew Kelley wrote:
> Leo,
>
> The upstream maintainer of ser
Jérémy,
Thank you for fixing node-serve-static. I have filed a bug for an unblock
on the package: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778566
Could you do the same for node-tap? Perhaps even by deleting the failing
test? Then I will file an unblock on node-tap.
Regards,
Andrew
_
:16.0 +
@@ -1,3 +1,9 @@
+node-findit2 (2.2.3-2) unstable; urgency=medium
+
+ * remove build dependency on buggy dependency: node-tap
+
+ -- Andrew Kelley Mon, 16 Feb 2015 19:25:08 +
+
node-findit2 (2.2.3-1) unstable; urgency=medium
* Initial release (Closes: #765772)
diff -Nru
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package node-tap
The bug that caused this package to be scheduled for autoremoval is
fixed with this small patch which disables a single test.
This does not affect the behav
Hi Jérémy,
I'm working on updating node-leveldown to the new upstream release and I
need a newer node-nan release to do so. Want some help with node-nan?
___
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alio
On Sun, May 17, 2015 at 12:51 AM Jérémy Lal wrote:
>
> can you check if that goes well with reverse build dependencies please ?
>
Yes. Fortunately the only reverse build dependencies are node-leveldown
(which I am working on) and node-ws, which is supposed to be on nan version
1.8.x anyway.
_
Hi Jérémy,
Daniel is interested in browserify-lite and I have completed and packaged
up some feature requests that he had. He has offered to upload the new
version this time.
Daniel, I have done all the packaging and created the tag etc. All that
remains is for you to check out the code from git,
42 matches
Mail list logo
