FYI: The status of the node-merge-stream source package
in Debian's testing distribution has changed.
Previous version: 1.0.1-1
Current version: 1.0.1-2
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you wi
FYI: The status of the node-liftoff source package
in Debian's testing distribution has changed.
Previous version: 2.3.0-2
Current version: 2.3.0-3
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will re
FYI: The status of the node-es6-promise source package
in Debian's testing distribution has changed.
Previous version: 4.2.5-1
Current version: 4.2.5-2
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you wil
FYI: The status of the ejs.js source package
in Debian's testing distribution has changed.
Previous version: 1.0.0+dfsg1-1
Current version: (not in testing)
Hint: Package not in unstable
The script that generates this mail tries to extract removal
reasons from comments in the britney hint
FYI: The status of the node-media-typer source package
in Debian's testing distribution has changed.
Previous version: 0.3.0-1
Current version: 0.3.0-2
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you wil
FYI: The status of the node-chart.js source package
in Debian's testing distribution has changed.
Previous version: 1.0.2-1
Current version: 2.7.3+dfsg-3
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you w
Your message dated Sat, 02 Mar 2019 22:37:07 +
with message-id
and subject line Bug#921625: fixed in node-gyp 3.8.0-5
has caused the Debian Bug report #921625,
regarding node-gyp install fails
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 02 Mar 2019 23:11:39 +0100
Source: node-gyp
Architecture: source
Version: 3.8.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Jérémy Lal
Closes: 921625
Changes:
node-gyp_3.8.0-5_source.changes uploaded successfully to localhost
along with the files:
node-gyp_3.8.0-5.dsc
node-gyp_3.8.0-5.debian.tar.xz
node-gyp_3.8.0-5_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
--
Pkg-javascript-devel mailing lis
Le sam. 2 mars 2019 à 18:21, Paolo Greppi a écrit :
> I got the same error on amd64 while running yarnpkg in root of vscode
> source:
>
> git clone https://github.com/Microsoft/vscode
> cd vscode
> yarnpkg
> ...
> [4/4] Building fresh packages...
> [1/14] ⠠ gc-signals
> [2/14] ⠠ keytar
> [3/14] ⠠
Processing commands for cont...@bugs.debian.org:
> block 898259 by 921625
Bug #898259 [wnpp] RFP: vscode -- Microsoft Visual Studio Code
898259 was blocked by: 842420
898259 was not blocking any bugs.
Added blocking bug(s) of 898259: 921625
>
End of message, stopping processing here.
Please conta
I got the same error on amd64 while running yarnpkg in root of vscode source:
git clone https://github.com/Microsoft/vscode
cd vscode
yarnpkg
...
[4/4] Building fresh packages...
[1/14] ⠠ gc-signals
[2/14] ⠠ keytar
[3/14] ⠠ native-is-elevated
[4/14] ⠐ native-keymap
error /root/vscode/node_modules
On Sat, Mar 2, 2019 at 12:17 AM, Xavier wrote:
Le 01/03/2019 à 19:04, Paolo Greppi a écrit :
I have given signal-desktop a first look.
In terms of dependencies, apart from electron (ehm...) this is what
I
found:
- to be updated:
1. node-chalk: 2.3.0 -> 2.4.1
2. node-espree: 3.5.
13 matches
Mail list logo
