FYI: The status of the node-tty-browserify source package
in Debian's testing distribution has changed.
Previous version: (not in testing)
Current version: 0.0.0-2
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a
Your message dated Tue, 01 Aug 2017 17:05:46 +
with message-id
and subject line Bug#754462: fixed in nodejs 6.11.2~dfsg-1
has caused the Debian Bug report #754462,
regarding Package node conflicts (?) with nodejs-legacy
to be marked as done.
This means that you claim that the problem has been
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 01 Aug 2017 18:40:46 +0200
Source: nodejs
Binary: nodejs-dev nodejs
Architecture: source
Version: 6.11.2~dfsg-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Jér
nodejs_6.11.2~dfsg-1_source.changes uploaded successfully to localhost
along with the files:
nodejs_6.11.2~dfsg-1.dsc
nodejs_6.11.2~dfsg.orig.tar.gz
nodejs_6.11.2~dfsg-1.debian.tar.xz
nodejs_6.11.2~dfsg-1_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.
Processing commands for cont...@bugs.debian.org:
> block 761441 by 858856
Bug #761441 [wnpp] RFP: node-istanbul -- a JS code coverage tool written in JS
761441 was not blocked by any bugs.
761441 was blocking: 779492 779498
Added blocking bug(s) of 761441: 858856
> thanks
Stopping processing here.
2017-08-01 7:59 GMT+02:00 Ross Gammon :
> On 07/31/2017 08:05 PM, Jérémy Lal wrote:
>
> Hi team,
>
> 2017-07-31 19:17 GMT+02:00 Tollef Fog Heen :
>
>>
>> The technical committee was asked in bug #862051 to revisit the decision
>> in
>> bug #614907 (conflict between the ax25-node package and the no
