On 27/09/2012 17:48, Dominique Dumont wrote:
>
> Hello
>
> I need a recent version of nodejs (> 0.8) for ares project.
>
> I can bite the bullet and (try to) package version 0.8.10. Before jumping on
> that, I'd like to check whether this has already beed done in javascript team?
>
> All the
On 13/09/2012 23:27, Moritz Muehlenhoff wrote:
> Package: libv8
> Severity: grave
> Tags: security
>
> Hi,
> please check the status of these security issues in libv8.
> They were all fixed in Chrome, but it's not clearly from
> which Chrome release the libv8 package in Wheezy was cut:
>
> http:/
On 16/08/2012 23:45, Luca Falavigna wrote:
> Hi!
>
> this is a quick update on what's going on with your package in NEW.
>
> We're holding it due to a library transition which would affect some reverse
> dependencies. As Wheezy is frozen, Release Team asked us to refrain from
> processing package
> On Thursday 27 September 2012 21:10:27 Jérémy Lal wrote:
> Before anything, latest is 0.8.11.
> My "plan" was to
> - update latest npm dependencies
> - package missing node-gyp dependencies
> - package node-gyp
> - update to latest npm
> - update libv8
>
Hi,
thank you for your report,
On 01/10/2012 13:30, Colin Watson wrote:
> Package: eyes.js
> Version: 0.1.7-1
> Severity: serious
> Tags: patch
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu ubuntu-patch quantal
>
> eyes.js fails to build in unstable following the node -> nodejs
debcheckout libv8
git checkout master-experimental
git-buildpackage
Jérémy.
On 24/10/2012 16:52, Thomas Schaaf wrote:
> Okay I need another version of libv8. So lets git clone it and build
> it ourselves.
___
Pkg-javascript-devel mailing list
Pkg-j
On 04/10/2012 21:42, Igor Pashev wrote:
> Package: nodejs
> Version: 0.6.19~dfsg1-5
> Severity: normal
>
> Dear Maintainer,
>
> I'm porting Debian on illumos kernel and using GNU toolchain (GCC, binutils,
> etc.)
>
> Node.js' build system sucks so much that cannot detect features of the
> compi
On 31/10/2012 21:31, Sébastien Villemot wrote:
> [Please CC me, I’m not subscribed to the list]
>
> Dear node.js maintainers,
>
> My prospective package julia (ITP: #691912) has libuv among its
> dependencies.
>
> I am therefore considering the possibility of having a libuv package in
> Debian.
On 07/11/2012 20:29, Sébastien Villemot wrote:
> Jérémy Lal writes:
>
>> On 31/10/2012 21:31, Sébastien Villemot wrote:
>>> [Please CC me, I’m not subscribed to the list]
>>>
>>> Dear node.js maintainers,
>>>
>>> My prospective package
On 13/12/2012 04:14, Jeff Cliff wrote:
> Package: npm
> Version: 1.1.4~dfsg-2
> Severity: normal
>
> Dear Maintainer,
> It seems like the npm version of grunt-recess is no longer valid, or
> something.
npm installs version 0.1.0 by default - it should be 0.1.4.
There is a bug somewhere indeed.
A
latest + stable = 3.13.7.5
API is still changing too much on 3.14, 3.15
source :
http://www.upstream-tracker.org/versions/v8.html
i will be glad to prepare 3.13 for an upload to experimental.
Jérémy.
On 15/12/2012 19:07, Carl Fürstenberg wrote:
> Source: libv8
> Version: 3.8.9.20-2
> Severity:
Hi,
i want to switch to a simpler and more efficient way
of using gbp branches for the packages i am maintaining :
* always import on "upstream" branch
* work on latest versions is made on "master" branch
* create branches of "master" when needed, but use them
only for bug fixing (typically: "ma
On 15/12/2012 21:27, Jonas Smedegaard wrote:
> Quoting Jérémy Lal (2012-12-15 20:32:35)
>> i want to switch to a simpler and more efficient way
>> of using gbp branches for the packages i am maintaining :
>>
>> * always import on "upstream" branch
>> *
On 16/12/2012 12:40, Jonas Smedegaard wrote:
> I like that our current structures work well for unstable, testing,
> stable and oldstable - i.e. that it is only tricky to handle
> experimental which we make no promises for anyway.
>
> I suspect the better approach than force-merging with "--stra
On 16/12/2012 23:00, Allison Randal wrote:
> The details on these two CVE's are 403 for me:
>
> CVE-2012-5120
> https://code.google.com/p/chromium/issues/detail?id=150729
>
> CVE-2012-5128
> https://code.google.com/p/chromium/issues/detail?id=157124
>
> So presumably they're still embargoed and
On 11/12/2012 23:42, Cédric Boutillier wrote:
>
> Dear JavaScript team members,
>
> I would like to kindly ask you to review my first two JavaScript
> packages to see if they are conform to what is expected. Those are
> dependencies of a Ruby tool, mdpress, used to create presentations from
> Mar
On 11/12/2012 23:42, Cédric Boutillier wrote:
>
> Dear JavaScript team members,
>
> I would like to kindly ask you to review my first two JavaScript
> packages to see if they are conform to what is expected. Those are
> dependencies of a Ruby tool, mdpress, used to create presentations from
> Mar
On 19/12/2012 22:39, Markus Frosch wrote:
> Hey all,
>> There might be an issue with apple-touch-icon.png,
>> the name of that file rings like non-free to me...
>
> Just a quick note here, thats apple's idea of providing a higher
> resolution favicon.
>
> Its also possible to specify another file
On 02/01/2013 19:00, Moritz Muehlenhoff wrote:
> On Sun, Dec 16, 2012 at 11:08:34PM +0100, Jérémy Lal wrote:
>> On 16/12/2012 23:00, Allison Randal wrote:
>>> The details on these two CVE's are 403 for me:
>>>
>>> CVE-2012-5120
>>> https://
On 14/01/2013 21:46, Jonas Smedegaard wrote:
> Quoting Rick Waldron (2013-01-14 21:09:42)
>> It's strange to me this is even an issue that's being argued, I would
>> assume that a Debian package maintainer would be responsible enough to
>> keep up with the latest stable releases of whatever they
On 16/01/2013 12:00, Jonas Smedegaard wrote:
> Quoting David I. Lehn (2013-01-16 01:12:17)
>> I would also like to see nodejs updated and have been working on it a
>> bit.
>
> We all would like to see Nodejs updated.
>
>
>> I'm kind of amazed that anyone would have to justify upgrading an
>> a
On 02/01/2013 19:00, Moritz Muehlenhoff wrote:
> On Sun, Dec 16, 2012 at 11:08:34PM +0100, Jérémy Lal wrote:
>> On 16/12/2012 23:00, Allison Randal wrote:
>>> The details on these two CVE's are 403 for me:
>>>
>>> CVE-2012-5120
>>> https://
On 25/01/2013 22:26, Jonathan Nieder wrote:
> found 650345 npm/1.1.4~dfsg-2
> quit
>
> Hi,
>
> Dominique Dumont wrote:
>
>> # bug has been fixed by Jeremy and Jonas
>
> Thanks for the heads up. It doesn't seem to be fixed, though:
>
> $ npm install express
> [...]
> $ head -1 node_modules/e
On 18/02/2013 23:50, Marcelo Jorge Vieira wrote:
> Hello Team,
>
> I don't know if you know, jQuery, jQuery UI and jQuery Mobile now use
> Grunt [0] as build system. Maybe there are others libs that use it too.
>
> [0] https://github.com/gruntjs/grunt
>
>
> I intend to package Grunt [1], but th
On 24/02/2013 00:19, Daniel Pocock wrote:
>
> I've had a look at JsSIP:
>
> https://github.com/versatica/JsSIP
>
> In particular, it is built using a tool called grunt, and that requires
> nodejs and the npm tool
>
> It also pulls in some other dependencies:
>
> https://github.com/opentelecoms
Package: node-jquery
Severity: important
This package has major issues :
* it includes another copy of jquery.js
* it doesn't build the distributed file (which is wrapper.js + pristine
jquery.js).
* and finally it doesn't have any copyright/license for the included
wrapper.js.
Jérémy.
_
On 03/03/2013 22:41, Jonas Smedegaard wrote:
> Package: node-glob
> Severity: minor
>
> Both short and long description talks about node-glob being a binding to
> glob and fnmatch, but 3.x is a pure JavaScript implementation.
I propose to replace it with :
glob functionality for Node.js
node
On 13/03/2013 15:56, Dominique Dumont wrote:
>
> Hello
>
> I'm trying to update npm package on collab-maint with latest version. I've
> cleaned up the patches without too many problems. But the build fails on this
> error:
>
> dh_bugfiles -pnpm
> dh_install -pnpm
> cp: cannot stat ‘debian/t
On 13/03/2013 16:45, Dominique Dumont wrote:
> On Wednesday 13 March 2013 16:13:41 Jérémy Lal wrote:
>> Dominique, while it is very nice of you to help,
>> i'm not that happy with these commits :
>
> Ah. Sorry about that. I'll try to fix my mess...
>
>&g
Package: nodejs
Version: 0.10.1~dfsg1-1
Severity: normal
This bug is a placeholder for a segfaults that happens with
nodejs 0.10.x and its libv8 (3.14.5.8) dependency.
Upstream has a patch for libv8 to fix that bug, but i'm not sure
it is a libv8 bug :
--- a/src/v8utils.h
+++ b/src/v8utils.h
@@
On 26/03/2013 17:58, Dominique Dumont wrote:
> On Wednesday 13 March 2013 16:13:41 Jérémy Lal wrote:
>> i'm not that happy with these commits : as you have noticed npm needs
>> dfsg-repackaging, and it was a good occasion to exclude all node_modules.
>> I would have real
On 05/05/2012 01:21, Steven Chamberlain wrote:
> Package: src:nodejs
> Version: 0.6.16~dfsg1-2
> Severity: wishlist
> User: debian-...@lists.debian.org
> Usertags: kfreebsd
> X-Debbugs-Cc: debian-...@lists.debian.org
>
> Hi,
>
> Attached are *unfinished* patches for building nodejs on kfreebsd-*
On 11/04/2013 19:49, Michael Gebetsroither wrote:
> Package: npm
> Version: 1.1.4~dfsg-2
> Severity: normal
>
> Dear Maintainer,
>
> I just had a nodejs application which was not compatible with nodejs 0.6
> anymore and thus had to upgrade to 0.10 from experimental.
>
> Though it seems npm from
On 24/04/2013 06:23, Guido Günther wrote:
> Package: npm
> Followup-For: Bug #705236
>
> I wonder if it would make sense to ship npm from nodejs itself? This
> would make sure these are in sync. cc: the nodejs maintainers for that.
>
> If not I'd be happy to NMU a new npm version.
> Cheers,
I th
On 30/04/2013 06:19, micah wrote:
> Package: node-fstream-ignore
> Version: 0.0.6-1
> Severity: normal
>
> It seems that node-inherits >= 1.0.0 is not in the archive, but
> node-fstream-ignore depends on it:
Yes, it is fixed in node-fstream-ignore 0.0.6-2 which is sitting in NEW.
Jérémy.
_
On 05/05/2013 22:45, Marcelo Jorge Vieira wrote:
> Hi Jérémy,
>
> What do you think about backport nodejs to wheezy?
When the migration from nodejs 0.6 to nodejs 0.10 is finished,
all new packages will go to testing and be good candidates for backports.
The current status is :
* nodejs 0.10, li
Hi,
First please note that i am not talking here about minified versions
of javascript files that are shipped in upstream tarballs [0].
Please comment about what could be part of our javascript policy [1].
It might help future javascript maintainers.
A package that distribute minified files for
Daniel you ask me to explain some things i thought was common practice.
Below i try to give explanations ; please help me fix, refine, or reject
them.
On 06/05/2013 19:31, Daniel Kahn Gillmor wrote:
> On 05/06/2013 09:18 AM, Jérémy Lal wrote:
>
>> First please note that i am not
On 07/05/2013 14:49, Daniel Kahn Gillmor wrote:
> On 05/06/2013 02:21 PM, Jérémy Lal wrote:
>> Daniel you ask me to explain some things i thought was common practice.
>> Below i try to give explanations ; please help me fix, refine, or reject
>> them.
>
> thanks, i thi
On 09/05/2013 15:20, etherc...@ks3270816.kimsufi.com wrote:
> Package: npm
> Version: 1.1.4~dfsg-2
npm 1.2.x is in experimental, as well as nodejs 0.10.x.
But one dependency of npm, node-lockfile, is sitting in NEW
so you'll have to wait a little before you can install latest npm.
I'll close thi
On 09/05/2013 21:09, Daniel Kahn Gillmor wrote:
> On 05/09/2013 02:11 PM, David Prévot wrote:
>> Hi,
>>
>> Le 09/05/2013 13:40, Daniel Kahn Gillmor a écrit :
>>> why is this painful? During development, you install libjs-jquery
>>> alongside whatever other development tools, libraries, frameworks
On 21/05/2013 15:12, Luca BRUNO wrote:
> As such I'm going to open an ITP for libuv, and David Paleino
> suggested me to keep it within the js-team similarly to libv8.
> I've just joined the ML and sent a request for the alioth group;
> if nobody complains I'm going to fill the ITP and start worki
On 25/05/2013 23:30, Mike Gabriel wrote:
> Hi all,
>
> I am about to package require-kernel [1] as it is one of those many
> dependencies of etherpad-lite.
>
> Can anyone of you take a look at upstream's sources and give me a
> hint if it has to be packaged as libjs-require-kernel or as something
On 08/07/2013 05:08, Shawn Landden wrote:
> Package: npm
> Version: 1.2.18~dfsg-3
> Severity: normal
>
> I installed a few packages yesterday, and today realized npm was wasting 50M
> of my ram with copies of what it downloaded still in /tmp/npm-# folders
>
> it should clean this up, put it in /v
On 08/07/2013 12:38, Daniel Kahn Gillmor wrote:
> On 07/08/2013 03:33 AM, Jérémy Lal wrote:
>> On 08/07/2013 05:08, Shawn Landden wrote:
>>
>>> I installed a few packages yesterday, and today realized npm was wasting 50M
>>> of my ram with copies of what it downl
On 08/07/2013 14:23, Daniel Kahn Gillmor wrote:> On 07/08/2013 07:55 AM, Jérémy
Lal wrote:
>
>> I am curious about how `npm install mymodule` could be a target for an
>> attacker,
>> especially considering the temp directory is used only once (at (un)tar
>>
On 08/07/2013 16:06, Dominique Dumont wrote:
> On Monday 08 July 2013 14:36:24 Jérémy Lal wrote:
>> I still do not understand if this is really a security issue.
>> IMO if a program on your system does that, the whole system is compromised,
>> you can't really be hardeni
The security issue is fixed there :
https://github.com/isaacs/npm/commit/f4d31693
this will eventually come to npm debian package.
Jérémy.
___
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org
On 10/07/2013 18:59, Daniel Kahn Gillmor wrote:
> I notice that your message was sent privately to me,
> ../.. feel free to post copies of it to the BTS.
My mistake.
> On 07/10/2013 12:31 PM, Jérémy Lal wrote:
>> On 10/07/2013 18:17, Daniel Kahn Gillmor wrote:
>
>>
Hi,
On 21/07/2013 18:53, Luke Faraone wrote:
> Dear maintainer,
>
> Some licenses were omitted:
>
> libuv-0.10.8\checksparse.sh:
> Copyright (c) 2013, Ben Noordhuis
> not quite ISC
>
> ibuv-0.10.8\include\uv-private\ngx-queue.h :
> Copyright (C) Igor Sysoev
>
> Can you have the
Hi,
sorry for the total absence of reaction for months,
priority was to get nodejs running on "official" platforms.
If you still have a patch to propose for version 0.10.15~dfsg1-4,
i'll be glad to apply it.
Jérémy.
___
Pkg-javascript-devel mailing lis
Hi,
it would be nice to update uglifyjs to version 2,
less bugs, more features.
Please note that the update to uglifyjs version 2 is
going to break some build scripts, since upstream changed
some of its CLI options.
Regards,
Jérémy.
___
Pkg-javascrip
Hi,
Maybe it's time to remove part about
Depends nodejs (>= 0.6.19~dfsg1-3~)
?
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
On 22/08/2013 09:34, Paul Wise wrote:
> Whenever this idea has come up (including the current /javascript
> implementation) I have always thought it was a bad idea, especially
> for JavaScript. Exposing more than absolutely needed for each website
> at minimum is an information leakage. With JS or
On 24/08/2013 10:20, Luca BRUNO wrote:
> Jérémy Lal wrote:
>
>>> Some licenses were omitted:
>>>
>>> libuv-0.10.8\checksparse.sh:
>>> Copyright (c) 2013, Ben Noordhuis
>>> not quite ISC
>>>
>>> ibuv-0.10.8\include\uv
On 25/08/2013 19:56, Andreas Moog wrote:
> Package: node-mysql
> Version: 2.0.0~alpha8-1
> Severity: grave
> Justification: renders package unusable
>
> Dear Debian Javascript team, dear Mike,
>
> I tried to install node-mysql in a Debian/Unstable environment, but failed
> to achieve success:
>
cc-ing to pkg-javascript-devel.
On 26/08/2013 16:02, Jean-Michel Vourgère wrote:
> On Saturday 24 August 2013 09:39:58 Jérémy Lal wrote:
>> (...)
>> please notify here when libuv is in a usable state and i'll make
>> nodejs depend on it.
>
> Hi.
>
> I rece
On 29/08/2013 15:40, Mathieu Malaterre wrote:
> Package: npm
> Severity: normal
>
> I cannot seems to get npm (experimental package) to run nicely, it fails with:
oh boy, just give me the command you run...
anyway your bug is upstream :
https://github.com/gruntjs/grunt/pull/886
Cheers,
Jérémy.
On 29/08/2013 16:23, Mathieu Malaterre wrote:
> On Thu, Aug 29, 2013 at 4:14 PM, Jérémy Lal wrote:
>> On 29/08/2013 15:40, Mathieu Malaterre wrote:
>>> Package: npm
>>> Severity: normal
>>>
>>> I cannot seems to get npm (experimental package) to run n
Hi,
It is upstream's goal to improve on this, meanwhile it means
the next stable release of nodejs will have to Break all c++
modules (at their current versions).
Is there a way to ease transition that right now ?
Add nodejs << 0.11 in Depends ?
Jérémy.
_
On 01/09/2013 12:46, Jonas Smedegaard wrote:
> Quoting Jérémy Lal (2013-08-31 10:01:11)
>> It is upstream's goal to improve on this, meanwhile it means
>> the next stable release of nodejs will have to Break all c++
>> modules (at their current versions).
>> Is the
On 02/09/2013 09:08, Mike Gabriel wrote:
> Hi all,
>
> I am currently packaging nan [1]. The nan project is no real node-*
> project per se, it rather is a single header (.h) file.
>
> From the README.md: compiling ,,native addons [...] happily across
> versions, particularly 0.10 to 0.11/0.12, i
On 04/09/2013 12:01, Raphael Hertzog wrote:
> Hi,
>
> On Sun, 28 Jul 2013, Marcelo Jorge Vieira wrote:
>> There is a big problem, Grunt depends on the JSHint and it is not
>> DFSG-compatible (Crockford's license).
>>
>> Please read this:
>> http://lists.alioth.debian.org/pipermail/pkg-javascript-d
On 07/09/2013 21:00, Paul Richards Tagliamonte wrote:
>
> Howdy maintainer,
>
>
> Sorry, I've had to reject this package,
>
> The only hint as to why license this software is under is
> the line that says:
>
> "licenses": [{ "type": "BSD" }],
>
> In addition:
>
> * Redistributions o
On 18/09/2013 19:19, Steve Illichevskiy wrote:
> Package: npm
> Version: 1.1.4~dfsg-1
> ii nodejs0.6.12~dfsg1-1ubuntu1
> ii nodejs-dev0.6.12~dfsg1-1ubuntu1
Please update npm, nodejs packages, and try again.
npm should work but it's possible the failing installation
is for a m
On 29/09/2013 16:50, Jonas Smedegaard wrote:
> Hi Mahyuddin,
>
> Quoting Mahyuddin (2013-09-29 16:33:49)
>> Hi, i am new Debian Maintainer in Javascript Team
>
> Welcome aboard!
>
> If you haven't done so already, please read our mini-policy at
> https://wiki.debian.org/Javascript/Policy
>
> A
Hi,
i'll work from time to time on packaging node-express new
dependencies.
Right now i'm working on updating node-connect,
and replacing node-formidable (will be RM) by node-multiparty,
a better-maintained fork of it.
Other missing (direct /and/ indirect) dependencies of node-express:
* node-se
The actual problem of these two packages is that they have
Architecture: any
whereas they are in fact platform-independent.
They should be Architecture: all
Jérémy.
___
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http:
On 06/10/2013 11:28, Colin Watson wrote:
> On Sat, Oct 05, 2013 at 02:53:33PM +0200, Jonas Smedegaard wrote:
>> Feels to me that it would be better to fix this at its core instead of
>> covering over it by use of bogus build-dependency. I am sure you've
>> already considered that option, and wou
On 09/10/2013 08:52, Antonin Kral wrote:
> Package: wnpp
> Severity: normal
>
> I intend to orphan the mongodb package. I am totally snowed under
> workload at http://icflix.com , where are currently not using MongoDB so
> my response times are getting longer and longer...
Hello,
while i said in
On 09/10/2013 10:46, László Böszörményi (GCS) wrote:
> retitle 725854 ITA: mongodb -- object/document-oriented database (metapackage)
> owner 725854 !
> thanks
>
> Hi,
>
> I've already made new packages of MongoDB. Would like to adopt it.
> Either alone or with Jérémy under the hood of Javascript
On 11/10/2013 09:47, Daniel Pocock wrote:
> On 11/05/13 17:46, Marcelo Jorge Vieira wrote:
>> Hi Jérémy,
>>
>> On Sun, 2013-05-05 at 23:35 +0200, Jérémy Lal wrote:
>>> On 05/05/2013 22:45, Marcelo Jorge Vieira wrote:
>>>> Hi Jérémy,
>>>>
On 11/10/2013 10:22, Daniel Pocock wrote:
> On 11/10/13 10:20, Jérémy Lal wrote:
>> On 11/10/2013 09:47, Daniel Pocock wrote:
>>> On 11/05/13 17:46, Marcelo Jorge Vieira wrote:
>>>> Hi Jérémy,
>>>>
>>>> On Sun, 2013-05-05 at 23:35 +0200, Jéré
On 14/10/2013 09:04, László Böszörményi (GCS) wrote:
> On Thu, Oct 10, 2013 at 9:56 PM, Clement Hermann wrote:
>> As I need this for my job, I'm willing to help, if needed that is.
> Sure, I'm open for suggestions and other help as well.
>
>> Also, I willing to maintain a wheezy backport, see
>>
Hi, i am trying to update node-connect to latest version,
and it requires those Node.js modules (that are not yet
packaged):
https://github.com/visionmedia/node-pause
https://github.com/visionmedia/node-range-parser
https://github.com/visionmedia/node-fresh
https://github.com/visionmedia/bytes.js
On 24/10/2013 20:17, Mike Gabriel wrote:
> Hi Jeremy, hi Jonas,
>
> when I try to build nodejs from testing (0.10.20~dfsg1-1) for
> wheezy-backports, I get failures during the test runs [1]. This
> error, however, does not occur always. Today, one of the builds
> succeeded. All other builds failed
On 25/10/2013 13:19, Jonas Smedegaard wrote:
> Quoting Mike Gabriel (2013-10-25 13:05:48)
>> On Fr 25 Okt 2013 11:14:48 CEST, Jonas Smedegaard wrote:
>>> Quoting Mike Gabriel (2013-10-25 09:11:59)
>>>> On Do 24 Okt 2013 20:32:33 CEST, Jérémy Lal wrote:
>>&
Update:
On 20/10/2013 17:56, Jérémy Lal wrote:
> Hi, i am trying to update node-connect to latest version,
> and it requires those Node.js modules (that are not yet
> packaged):
>
> https://github.com/visionmedia/node-pause
Not needed in nodejs >= 0.10, can be patched o
On 03/11/2013 02:25, Andreas Beckmann wrote:
> Package: node-carto
> Version: 0.9.5-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
>
> Hi,
>
> during a test with piuparts I noticed your package fails to upgrade from
> 'testing'.
> It installed fine in 'testing', the
On 04/11/2013 19:50, Jonas Smedegaard wrote:
> Package: libjs-wax
> Version: 5.0.1+ds2-1
> Severity: normal
>
> Homepage now contains the following:
>
>> We’d highly recommend you use a current version of MapBox.js rather
>> than Wax for all future projects, and consider porting your code!
>
> S
On 19/11/2013 14:14, Thorsten Glaser wrote:
> Hi,
>
> I’ve got a FusionForge derivate properly packaged as Debian
> source package, and would like to keep that. (It’s used inhouse
> but publicly available.) Now, we are “restyling” it using the
> “Bootstrap” CSS/JS stuff, whose version 3.1 will use
On 27/11/2013 23:09, Dmitry Smirnov wrote:
> Hi David,
>
> Can I give you a hand with "node-jsdom"?
> We need its newer version for d3 [1], see ITP #676396:
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676396
>
> Thank you.
>
> [1]: http://d3js.org/
While it's a very good idea to p
On 30/12/2013 05:57, openda...@hushmail.com wrote:
> Package: seedrandom
>
> Unable to `npm install seedrandom` on Ubuntu (Linux 3.11.0-12-generic):
Your bug report wasn't properly filled, please read
https://help.ubuntu.com/community/reportbug
for information about reporting bugs to debian from
On 30/12/2013 03:27, Dmitry Smirnov wrote:
> Hi Jonas,
>
> On Sun, 29 Dec 2013 21:15:43 Jonas Smedegaard wrote:
>> Welcome to our team! :-D
>
> Thanks for warm welcome. :)
>
>> No, your request was hanging there unprocessed - sorry about that (most
>> of us in the team - now including yourself
On 30/12/2013 22:56, Dmitry Smirnov wrote:
> Source: node-jsdom
> Version: 0.2.13+dfsg1-1
> Severity: minor
>
> So I wonder if we can ship tests after all? Am I missing something?
You're right.
Also node-jsdom needs some help.
Would you like to take care of updating it ?
Jérémy.
___
Hi,
I wonder if there is a minimum official requirement for granting
SCM commit access to newcomers.
Regards and happy new year,
Jérémy
___
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/
On 05/01/2014 22:13, Mike Gabriel wrote:
> On Do 02 Jan 2014 16:29:30 CET, Jonas Smedegaard wrote:
>
>> Speaking of which:
>>
>> I have till now mostly used collab-maint instead of our own git
>> area to ease contributions from other Debian members. Alioth now
>> (since some time) allows any te
I am not sure this is the proper way to do it in nodejs.
I'll have a look and keep you informed.
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-javas
On 30/12/2013 05:39, openda...@hushmail.com wrote:
> Package: annostring
> Version: 0.2.2
>
> Unable to `npm install annostring` on Ubuntu (Linux 3.11.0-12-generic):
> ...
> 333 error node -v v0.10.15
> 334 error npm -v 1.2.18
> 335 verbose exit [ 1, true ]
It works here with the debian package n
Hi,
a similar question can be asked for v8-ppc port, too.
I need some help for taking a decision here.
If those ports pass v8 test suites and are maintained, then we should
consider having them in debian. I'm a little worried about security
issues, though.
Jérémy.
___
forwarded 736779 https://github.com/joyent/node/pull/6978
thank you
Meanwhile, do applying the patch replacing minified by unminified source
is enough ?
Jérémy.
___
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://l
Le lundi 27 janvier 2014 à 20:44 +0100, Jonas Smedegaard a écrit :
> Greetings, fellow Javascript hackers,
>
> Quoting Jonas Smedegaard (2014-01-02 16:29:30)
> > Quoting Jérémy Lal (2014-01-02 13:01:12)
> >> I wonder if there is a minimum official requirement for granting
Le vendredi 28 février 2014 à 10:32 +, Julian Gilbey a écrit :
> Package: npm
> Version: 1.3.10~dfsg-1
> Severity: important
>
> See
> http://blog.npmjs.org/post/78085451721/npms-self-signed-certificate-is-no-more
>
> npm was bombing out because of this :-(
Updating...
Jérémy.
___
Le mercredi 08 janvier 2014 à 09:52 +0100, Yolanda Robla a écrit :
> Package: nodejs
> Version: 0.10.15~dfsg1-4
> Severity: wishlist
>
> Dear Maintainer,
> >From Ubuntu we are updating some packages to show OS distribution
> when showing version of some packages.
> https://blueprints.launchpad.net
Le jeudi 20 mars 2014 à 11:14 +0100, Leo Iannacone a écrit :
> Package: node-express
> Version: 2.5.9-2
> Severity: wishlist
>
> Dear Maintainer,
>
> According with github, there are many release during last years
> you have not packaged.
>
> https://github.com/visionmedia/express/releases
>
>
Le mercredi 26 mars 2014 à 18:32 +0100, Leo Iannacone a écrit :
> Hi Jérémy,
>
> I'm going to start working on this.
>
> Is there some workflow in javascript maintainers you prefer I would follow ?
>
> Or just pull my packages in the mentors sponsors queue ?
>
> All the best,
>
> Leo.
If i'm
Hi,
yes, go ahead, i had that goal to package tilemill too, but died in the
way under an avalanche of other things to package.
I'll surely resume some work next month, unless somebody does it before.
Jérémy.
Le dimanche 30 mars 2014 à 16:58 -0400, anar...@debian.org a écrit :
> So it turns out
Le dimanche 30 mars 2014 à 18:46 -0400, Antoine Beaupré a écrit :
> Package: node-tilelive-mapnik
> Version: 0.6.1-1
> Severity: grave
>
> This package is basically unusable. While trying to package tilemill,
> I was trying to load this library, and got this:
>
Fixing it !
Jérémy.
___
Le dimanche 30 mars 2014 à 19:04 -0400, Antoine Beaupré a écrit :
> Package: node-jsdom
> Version: 0.8.10+dfsg1-1
> Severity: grave
>
> In addition to cssstyle (#742347), there are two more modules missing
> for this nodejs module to work: nwmatcher and htmlparser2.
>
> The latter is especially f
Thank you for this, the only missing pieces are:
* ideally, the name of the branch from which you created the mips patch
* i guess the LICENSE doesn't change, is there any new copyright
attribution to set ?
Jérémy.
___
Pkg-javascript-devel mailing list
101 - 200 of 577 matches
Mail list logo
