Quoting Jérémy Lal (2014-04-30 21:09:41)
> Le mercredi 30 avril 2014 à 14:34 +0200, Jonas Smedegaard a écrit :
>> Quoting Jérémy Lal (2014-04-30 12:53:22)
>>> Le mercredi 30 avril 2014 à 12:35 +0200, Leo Iannacone a écrit :
On 30 April 2014 02:10, Jonas Smedegaard wrote:
> Status of packa
Quoting Jérémy Lal (2014-04-30 01:43:03)
> Le mercredi 30 avril 2014 à 00:46 +0200, Jonas Smedegaard a écrit :
>> Quoting Jérémy Lal (2014-04-29 16:03:04)
>>> In case you're missing the time, i can review and upload later
>>> today.
>>
>> I suspect you couldn't (or shouldn't) upload yet: At least
On Wed, Apr 30, 2014, at 05:40 AM, Jonas Smedegaard wrote:
> Hi Ramakrishnan,
>
> Quoting Ramakrishnan Muthukrishnan (2014-04-24 04:00:58)
> > I noticed that uglify has two series of releases and two upstream
> > repositories maintained, one for 1.x versions and another for 2.x and
> > Debian pa
Le jeudi 01 mai 2014 à 01:11 +0200, Jérémy Lal a écrit :
> Le jeudi 01 mai 2014 à 00:18 +0200, Jonas Smedegaard a écrit :
> > Quoting Leo Iannacone (2014-04-30 23:26:44)
> > > On 30 April 2014 23:11, Jérémy Lal wrote:
> > > > It's not all right to remove other files without good reasons.
> > > > H
Le jeudi 01 mai 2014 à 00:18 +0200, Jonas Smedegaard a écrit :
> Quoting Leo Iannacone (2014-04-30 23:26:44)
> > On 30 April 2014 23:11, Jérémy Lal wrote:
> > > It's not all right to remove other files without good reasons.
> > > Here, you can have a doubt about the license of the other css file,
Quoting Leo Iannacone (2014-04-30 23:26:44)
> On 30 April 2014 23:11, Jérémy Lal wrote:
> > It's not all right to remove other files without good reasons.
> > Here, you can have a doubt about the license of the other css file, but
> > there is no doubt the js file is correctly licensed, so no reas
On 30 April 2014 23:11, Jérémy Lal wrote:
> It's not all right to remove other files without good reasons.
> Here, you can have a doubt about the license of the other css file, but
> there is no doubt the js file is correctly licensed, so no reason to
> prune it.
But ... does it make sense leave
Le mercredi 30 avril 2014 à 22:55 +0200, Leo Iannacone a écrit :
> On 30 April 2014 22:20, Jérémy Lal wrote:
> > Le mercredi 30 avril 2014 à 21:48 +0200, Leo Iannacone a écrit :
> >> node-css-parse is ready here:
> >>
> >> http://anonscm.debian.org/gitweb/?p=pkg-javascript/node-css-parse.git
> >
>
On 30 April 2014 22:20, Jérémy Lal wrote:
> Le mercredi 30 avril 2014 à 21:48 +0200, Leo Iannacone a écrit :
>> node-css-parse is ready here:
>>
>> http://anonscm.debian.org/gitweb/?p=pkg-javascript/node-css-parse.git
>
> * upstream is actually
> https://github.com/reworkcss/css-parse
You're righ
Le mercredi 30 avril 2014 à 22:11 +0200, Leo Iannacone a écrit :
> node-character-parser is ready here:
>
> http://anonscm.debian.org/gitweb/?p=pkg-javascript/node-character-parser.git
>
> On 30 April 2014 21:48, Leo Iannacone wrote:
> > node-css-parse is ready here:
> >
> > http://anonscm.debia
Le mercredi 30 avril 2014 à 21:48 +0200, Leo Iannacone a écrit :
> node-css-parse is ready here:
>
> http://anonscm.debian.org/gitweb/?p=pkg-javascript/node-css-parse.git
* upstream is actually
https://github.com/reworkcss/css-parse
* benchmarks/large.css must be excluded, for it contains way to
node-character-parser is ready here:
http://anonscm.debian.org/gitweb/?p=pkg-javascript/node-character-parser.git
On 30 April 2014 21:48, Leo Iannacone wrote:
> node-css-parse is ready here:
>
> http://anonscm.debian.org/gitweb/?p=pkg-javascript/node-css-parse.git
--
Ubuntu Member - http://l
node-css-parse is ready here:
http://anonscm.debian.org/gitweb/?p=pkg-javascript/node-css-parse.git
___
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript
Le mercredi 30 avril 2014 à 14:34 +0200, Jonas Smedegaard a écrit :
> [assuming all involved are subscribed: posting only to bugreport]
>
> Quoting Jérémy Lal (2014-04-30 12:53:22)
> > Le mercredi 30 avril 2014 à 12:35 +0200, Leo Iannacone a écrit :
> >> On 30 April 2014 02:10, Jonas Smedegaard w
FYI: The status of the node-debug source package
in Debian's testing distribution has changed.
Previous version: 0.6.0-1
Current version: 0.8.1-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will rece
FYI: The status of the rickshaw source package
in Debian's testing distribution has changed.
Previous version: 1.4.6-1
Current version: 1.5.0.dfsg-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will r
Your message dated Wed, 30 Apr 2014 16:51:35 +
with message-id
and subject line Bug#742178: fixed in node-express 4.1.1~dfsg-1
has caused the Debian Bug report #742178,
regarding node-express: Please update node-express to the latest release
to be marked as done.
This means that you claim tha
Your message dated Wed, 30 Apr 2014 16:51:35 +
with message-id
and subject line Bug#742178: fixed in node-express 4.1.1~dfsg-1
has caused the Debian Bug report #742178,
regarding node-express 4.0 released
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 30 Apr 2014 18:31:24 +0200
Source: node-express
Binary: node-express
Architecture: source all
Version: 4.1.1~dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Jon
node-express_4.1.1~dfsg-1_amd64.changes uploaded successfully to localhost
along with the files:
node-express_4.1.1~dfsg-1_all.deb
node-express_4.1.1~dfsg-1.dsc
node-express_4.1.1~dfsg.orig.tar.gz
node-express_4.1.1~dfsg-1.debian.tar.xz
Greetings,
Your Debian queue daemon (running
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 27 Apr 2014 16:33:48 +0200
Source: node-parseurl
Binary: node-parseurl
Architecture: source all
Version: 1.0.1-1
Distribution: unstable
Urgency: low
Maintainer: Debian Javascript Maintainers
Changed-By: Leo Ianna
[assuming all involved are subscribed: posting only to bugreport]
Quoting Jérémy Lal (2014-04-30 12:53:22)
> Le mercredi 30 avril 2014 à 12:35 +0200, Leo Iannacone a écrit :
>> On 30 April 2014 02:10, Jonas Smedegaard wrote:
>>> Status of packaging is that these libraries needs packaging first:
>
Your message dated Wed, 30 Apr 2014 13:43:44 +0200
with message-id <5360e1f0.8010...@pocock.pro>
and subject line duplicate
has caused the Debian Bug report #746120,
regarding jssip: FTBFS: make[2]: java: Command not found
to be marked as done.
This means that you claim that the problem has been d
On 30 April 2014 12:53, Jérémy Lal wrote:
>> About node-source-map:
>> It build-depends on dryice (>=0.4.8). You can find a pre-release
>> package in pkg-javascript/node-dryice.git repository.
>> Once it done/uploaded to unstable, we will be able to build source-map.
>
> I can help about that, but
Le mercredi 30 avril 2014 à 12:35 +0200, Leo Iannacone a écrit :
> Hi Jonas,
>
> On 30 April 2014 02:10, Jonas Smedegaard wrote:
> > Status of packaging is that these libraries needs packaging first:
> >
> > node-source-map
> > node-uglify-to-browserify
>
> About node-uglify-to-browserify:
>
Hi Jonas,
On 30 April 2014 02:10, Jonas Smedegaard wrote:
> Status of packaging is that these libraries needs packaging first:
>
> node-source-map
> node-uglify-to-browserify
About node-uglify-to-browserify:
You do not really need to package it, since it's only related to
uglify2.x (it has n
Quoting Jérémy Lal (2014-04-30 11:59:08)
> Le mercredi 30 avril 2014 à 11:45 +0200, Jonas Smedegaard a écrit :
>> Quoting Leo Iannacone (2014-04-30 10:20:28)
>>> On 30 April 2014 02:39, Jérémy Lal wrote:
If /usr/lib/nodejs/express/package.json exists, nodejs uses it to
find the entry po
Le mercredi 30 avril 2014 à 11:45 +0200, Jonas Smedegaard a écrit :
> Quoting Leo Iannacone (2014-04-30 10:20:28)
> > On 30 April 2014 02:39, Jérémy Lal wrote:
> >> If /usr/lib/nodejs/express/package.json exists, nodejs uses it to
> >> find the entry point of the module.
> >
> > Here more info ab
Quoting Leo Iannacone (2014-04-30 10:20:28)
> On 30 April 2014 02:39, Jérémy Lal wrote:
>> Interesting.
>
> Really, which tools do you use to inspect files covered by some
> copyright in a software?
Depends on the needs - concretely I currently use exiftool and otfinfo.
For more details please
Hi Leo,
On Mi 30 Apr 2014 10:49:12 CEST, Leo Iannacone wrote:
Hi Mike!
On 30 April 2014 10:27, Mike Gabriel
wrote:
you could start with preparing packages for the new dependencies...
I will start with the devDependencies:
"devDependencies": {
"mocha": "1.16.2",
"expect.js": "
Hi Mike!
On 30 April 2014 10:27, Mike Gabriel wrote:
> you could start with preparing packages for the new dependencies...
I will start with the devDependencies:
"devDependencies": {
"mocha": "1.16.2",
"expect.js": "0.3.1",
"supertest": "0.8.2",
"superagent": "0.17.0",
"is
Node browserify is a kind of software which makes node modules
compatible and runnable for browsers.
It seems many modules use it, so it would be nice package it.
I have taken a look, and it madly depends on dozens of packages/modules[0].
My question is:
do you know if exist something else whic
Hi Leo,
On Mi 30 Apr 2014 10:15:04 CEST, Leo Iannacone wrote:
After some investigation, I discovered upstream is developing a new
release major 1.0.0.
I guess it is better wait for it. Dependencies are deeply changing in
the master branch:
https://github.com/LearnBoost/socket.io/blob/master/
Hi all,
I would like to make mocha available in debian:
https://github.com/visionmedia/mocha
To do that, we need jade, which is required by mocha as dependency.
If you want help, here the task page about packaging jade:
https://wiki.debian.org/Javascript/Nodejs/Tasks/Jade
Regards,
Leo.
--
U
On 30 April 2014 02:39, Jérémy Lal wrote:
> Interesting.
Really, which tools do you use to inspect files covered by some
copyright in a software?
> It's now accessible (thank you Leo) from the Nodejs page, as "best
> practice" manual:
> https://wiki.debian.org/Javascript/Nodejs/Manual
>
> it is
After some investigation, I discovered upstream is developing a new
release major 1.0.0.
I guess it is better wait for it. Dependencies are deeply changing in
the master branch:
https://github.com/LearnBoost/socket.io/blob/master/package.json
Best,
Leo.
--
Ubuntu Member - http://launchpad.ne
36 matches
Mail list logo
