Your message dated Fri, 21 Sep 2012 22:41:01 +
with message-id
and subject line Bug#687052: fixed in npm 1.1.4~dfsg-2
has caused the Debian Bug report #687052,
regarding npm - error installing redis
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Fri, 21 Sep 2012 22:41:01 +
with message-id
and subject line Bug#681356: fixed in npm 1.1.4~dfsg-2
has caused the Debian Bug report #681356,
regarding npm: Add build-essential as a Recommends
to be marked as done.
This means that you claim that the problem has been dealt wi
Your message dated Fri, 21 Sep 2012 22:41:01 +
with message-id
and subject line Bug#686894: fixed in npm 1.1.4~dfsg-2
has caused the Debian Bug report #686894,
regarding npm: please run under nodejs, not node
to be marked as done.
This means that you claim that the problem has been dealt with
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 22 Sep 2012 00:19:00 +0200
Source: npm
Binary: npm
Architecture: source all
Version: 1.1.4~dfsg-2
Distribution: unstable
Urgency: low
Maintainer: Debian Javascript Maintainers
Changed-By: Jonas Smedegaard
Descri
npm_1.1.4~dfsg-2_amd64.changes uploaded successfully to localhost
along with the files:
npm_1.1.4~dfsg-2.dsc
npm_1.1.4~dfsg-2.debian.tar.gz
npm_1.1.4~dfsg-2_all.deb
Greetings,
Your Debian queue daemon (running on host franck.debian.org)
_
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 21 Sep 2012 23:23:16 +0200
Source: nodejs
Binary: nodejs-dev nodejs nodejs-dbg nodejs-legacy
Architecture: source all i386
Version: 0.6.19~dfsg1-5
Distribution: unstable
Urgency: low
Maintainer: Debian Javascript Mai
Your message dated Fri, 21 Sep 2012 23:37:13 +0200
with message-id <20120921233713.2be266b1@local>
and subject line Bug fixed
has caused the Debian Bug report #670117,
regarding carto: should recommend or suggest node-millstone
to be marked as done.
This means that you claim that the problem has b
nodejs_0.6.19~dfsg1-5_i386.changes uploaded successfully to localhost
along with the files:
nodejs_0.6.19~dfsg1-5.dsc
nodejs_0.6.19~dfsg1-5.debian.tar.gz
nodejs-legacy_0.6.19~dfsg1-5_all.deb
nodejs-dev_0.6.19~dfsg1-5_i386.deb
nodejs_0.6.19~dfsg1-5_i386.deb
nodejs-dbg_0.6.19~dfsg1-5_i386
Processing commands for cont...@bugs.debian.org:
> #npm (1.1.4~dfsg-3) UNRELEASED; urgency=low
> #
> # * debian/control:
> #+ Tighten nodejs version to the one after the rename.
> #+ Suggests: build-essential. Closes: #681356.
> #
> limit source npm
Limiting to bugs with field 'source' co
Processing commands for cont...@bugs.debian.org:
> severity 680894 normal
Bug #680894 [npm] npm: npm fails to install some modules while post-installing
Opa
Severity set to 'normal' from 'important'
> merge 687052 680894
Bug #687052 [npm] npm - error installing redis
Bug #687052 [npm] npm - error
Processing commands for cont...@bugs.debian.org:
> merge 687052 680894
Bug #687052 [npm] npm - error installing redis
Unable to merge bugs because:
severity of #680894 is 'important' not 'normal'
Failed to merge 687052: Did not alter merged bugs
Debbugs::Control::set_merged('transcript', '
On 12-09-21 at 11:15am, Jérémy Lal wrote:
> On 21/09/2012 10:59, David Paleino wrote:
> > On Fri, 21 Sep 2012 09:52:49 +0200, Jérémy Lal wrote:
> >
> >> I'm okay with the patch and how you put it in
> >> 2003_rename_node_to_nodejs.patch. Before anything else, could you
> >> update nodejs Breaks
Your message dated Fri, 21 Sep 2012 10:32:47 +
with message-id
and subject line Bug#684418: fixed in node-semver 1.0.13-2
has caused the Debian Bug report #684418,
regarding node-semver: cannot install npm on sid armhf, b/c nodejs breaks
node-semver
to be marked as done.
This means that you
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 21 Sep 2012 12:18:26 +0200
Source: node-semver
Binary: node-semver
Architecture: source all
Version: 1.0.13-2
Distribution: unstable
Urgency: low
Maintainer: Debian Javascript Maintainers
Changed-By: Jérémy Lal
De
node-semver_1.0.13-2_i386.changes uploaded successfully to localhost
along with the files:
node-semver_1.0.13-2.dsc
node-semver_1.0.13-2.debian.tar.gz
node-semver_1.0.13-2_all.deb
Greetings,
Your Debian queue daemon (running on host franck.debian.org)
__
Processing commands for cont...@bugs.debian.org:
> #npm (1.1.4~dfsg-2) UNRELEASED; urgency=low
> #
> # * debian/patches:
> #+ 1002_only_use_numeric_UIDs_and_GIDs_in_spawn.patch
> # Upstream commit. Closes: #687052.
> #+ 2006_rename_node_to_nodejs.patch replaces "node" by
> # pro
Processing commands for cont...@bugs.debian.org:
> #node-semver (1.0.13-3) UNRELEASED; urgency=low
> #
> # * Rename node shebang to nodejs. Closes: #684418.
> #
> limit source node-semver
Limiting to bugs with field 'source' containing at least one of 'node-semver'
Limit currently set to 'source'
On 21/09/2012 10:59, David Paleino wrote:
> On Fri, 21 Sep 2012 09:52:49 +0200, Jérémy Lal wrote:
>
>> I'm okay with the patch and how you put it in
>> 2003_rename_node_to_nodejs.patch. Before anything else, could you update
>> nodejs Breaks relations to match the current status after your latest
On Fri, 21 Sep 2012 09:52:49 +0200, Jérémy Lal wrote:
> I'm okay with the patch and how you put it in
> 2003_rename_node_to_nodejs.patch. Before anything else, could you update
> nodejs Breaks relations to match the current status after your latest
> node-carto (&al.) upload ?
What should I chang
On 20/09/2012 16:49, David Paleino wrote:
> Hello everybody,
>
> I just made a commit to the nodejs package, fixing a bug I found in node-waf.
> This bug popped up while building node-mapnik (trying to fix its RC bug); in
> practice node-waf looks for /usr/bin/node instead of nodejs.
>
> Jonas, I
20 matches
Mail list logo
