Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 01 Mar 2018 12:10:32 +0530
Source: node-d3-dispatch
Binary: node-d3-dispatch
Architecture: source
Version: 1.0.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 01 Mar 2018 12:10:32 +0530
Source: node-d3-dispatch
Binary: node-d3-dispatch
Architecture: source
Version: 1.0.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
On വ്യാഴം 01 മാർച്ച് 2018 02:28 വൈകു, Chris Lamb wrote:
> Pirate,
>
>> 1. If a single ftp master is in disagreement, there should be a team
>> decision (in previous cases of disagreement also, other team members did
>> not get involved).
>
> I'm lost already, sorry. As I understand the case of
On വ്യാഴം 01 മാർച്ച് 2018 03:24 വൈകു, Chris Lamb wrote:
> Apologies, but this reads like another non-sequitur to me. Why would deciding
> on a number of days before one can assume _no_ dissent make any difference at
> all to the case of three.js given that you are claiming there _is_ dissent?
I
Pirate,
> 1. If a single ftp master is in disagreement, there should be a team
> decision (in previous cases of disagreement also, other team members did
> not get involved).
I'm lost already, sorry. As I understand the case of three.js's recent
rejection, no other ftp-master said anything and
Pirate Praveen wrote:
> > I'm lost already, sorry. As I understand the case of three.js's recent
> > rejection, no other ftp-master said anything and thus there cannot be
> > any dissention.
>
> I think it would be better if that is made explicit else how many days
> should someone wait to see
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 01 Mar 2018 14:14:33 +0530
Source: node-d3-drag
Binary: node-d3-drag
Architecture: source
Version: 1.2.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 01 Mar 2018 14:14:33 +0530
Source: node-d3-drag
Binary: node-d3-drag
Architecture: source
Version: 1.2.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
On 14963 March 1977, Pirate Praveen wrote:
> 1. If a single ftp master is in disagreement, there should be a team
> decision (in previous cases of disagreement also, other team members did
> not get involved).
I wonder why you think "a single ftpmaster". We are a team. We closely
coordinate what
node-d3-drag_1.2.1-3_source.changes uploaded successfully to localhost
along with the files:
node-d3-drag_1.2.1-3.dsc
node-d3-drag_1.2.1-3.debian.tar.xz
node-d3-drag_1.2.1-3_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
--
node-d3-dispatch_1.0.3-3_source.changes uploaded successfully to localhost
along with the files:
node-d3-dispatch_1.0.3-3.dsc
node-d3-dispatch_1.0.3-3.debian.tar.xz
node-d3-dispatch_1.0.3-3_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
--
node-prismjs_1.11.0+dfsg-1_amd64.changes uploaded successfully to localhost
along with the files:
node-prismjs_1.11.0+dfsg-1.dsc
node-prismjs_1.11.0+dfsg.orig.tar.xz
node-prismjs_1.11.0+dfsg-1.debian.tar.xz
node-prismjs_1.11.0+dfsg-1_all.deb
node-prismjs_1.11.0+dfsg-1_amd64.buildinfo
node-d3-ease_1.0.3-3_source.changes uploaded successfully to localhost
along with the files:
node-d3-ease_1.0.3-3.dsc
node-d3-ease_1.0.3-3.debian.tar.xz
node-d3-ease_1.0.3-3_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 01 Mar 2018 16:38:26 +0530
Source: node-d3-ease
Binary: node-d3-ease
Architecture: source
Version: 1.0.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 01 Mar 2018 16:38:26 +0530
Source: node-d3-ease
Binary: node-d3-ease
Architecture: source
Version: 1.0.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
node-d3-force_1.1.0-3_source.changes uploaded successfully to localhost
along with the files:
node-d3-force_1.1.0-3.dsc
node-d3-force_1.1.0-3.debian.tar.xz
node-d3-force_1.1.0-3_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
--
Pirate Praveen writes ("Re: [Pkg-javascript-devel]
three.js_80+dfsg2-2_amd64.changes REJECTED"):
> On വ്യാഴം 01 മാർച്ച് 2018 03:48 വൈകു, Joerg Jaspert wrote:
> > I wonder why you think "a single ftpmaster". We are a team. We closely
> > coordinate what we do and how we do it. When one of us
node-require-dir_1.0.0-1_source.changes uploaded successfully to localhost
along with the files:
node-require-dir_1.0.0-1.dsc
node-require-dir_1.0.0.orig.tar.gz
node-require-dir_1.0.0-1.debian.tar.xz
node-require-dir_1.0.0-1_source.buildinfo
Greetings,
Your Debian queue daemon
binary:node-prismjs is NEW.
binary:node-prismjs is NEW.
source:node-prismjs is NEW.
Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so please be
On വ്യാഴം 01 മാർച്ച് 2018 03:48 വൈകു, Joerg Jaspert wrote:
> On 14963 March 1977, Pirate Praveen wrote:
>
>> 1. If a single ftp master is in disagreement, there should be a team
>> decision (in previous cases of disagreement also, other team members did
>> not get involved).
>
> I wonder why you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 01 Mar 2018 17:41:50 +0530
Source: node-d3-force
Binary: node-d3-force
Architecture: source
Version: 1.1.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 01 Mar 2018 17:41:50 +0530
Source: node-d3-force
Binary: node-d3-force
Architecture: source
Version: 1.1.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 01 Mar 2018 19:54:06 +0530
Source: node-require-dir
Binary: node-require-dir
Architecture: source
Version: 1.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 01 Mar 2018 19:54:06 +0530
Source: node-require-dir
Binary: node-require-dir
Architecture: source
Version: 1.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
On Mon, Jan 22, 2018 at 12:20:35PM +0530, Pirate Praveen wrote:
> On ഞായര് 21 ജനുവരി 2018 11:08 വൈകു, Pirate Praveen wrote:
> > My logs were from before mocha 4 is uploaded to unstable. Now we need to
> > fix the tests for mocha 4 (this bug), as well as chai 4 (the other bug I
> > reported).
>
On വ്യാഴം 01 മാർച്ച് 2018 10:47 വൈകു, Gunnar Wolf wrote:
> We should not wait for dissent just forever. The issue you mention was
> rejected by ftp-masters, then brought to the TC, then dismissed by the
> TC as not-our-role-to-overrule-delegates, and some more days
> passed. Do you really think
Pirate Praveen dijo [Thu, Mar 01, 2018 at 03:15:42PM +0530]:
> >> 1. If a single ftp master is in disagreement, there should be a team
> >> decision (in previous cases of disagreement also, other team members did
> >> not get involved).
> >
> > I'm lost already, sorry. As I understand the case of
FYI: The status of the node-magic-string source package
in Debian's testing distribution has changed.
Previous version: 0.22.4-4
Current version: 0.22.4-5
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you
FYI: The status of the node-rollup-plugin-replace source package
in Debian's testing distribution has changed.
Previous version: 2.0.0-1
Current version: 2.0.0-2
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a
FYI: The status of the node-rollup-plugin-commonjs source package
in Debian's testing distribution has changed.
Previous version: 8.3.0-1
Current version: 8.3.0-2
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a
node-neo-async_2.5.0-1_amd64.changes uploaded successfully to localhost
along with the files:
node-neo-async_2.5.0-1.dsc
node-neo-async_2.5.0.orig.tar.gz
node-neo-async_2.5.0-1.debian.tar.xz
node-neo-async_2.5.0-1_all.deb
node-neo-async_2.5.0-1_amd64.buildinfo
Greetings,
Your
FYI: The status of the node-rollup-plugin-json 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
FYI: The status of the node-rollup-plugin-string source package
in Debian's testing distribution has changed.
Previous version: 2.0.2-2
Current version: 2.0.2-3
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a
FYI: The status of the node-rollup-plugin-node-resolve source package
in Debian's testing distribution has changed.
Previous version: (not in testing)
Current version: 3.0.3-2
--
This email is automatically generated once a day. As the installation of
new packages into testing happens
Processing control commands:
> block 843951 by -1
Bug #843951 [node-async] [node-async] Please update to version 1.5.2
843951 was blocked by: 733586
843951 was blocking: 843952 890611
Added blocking bug(s) of 843951: 891895
--
843951: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843951
binary:node-neo-async is NEW.
binary:node-neo-async is NEW.
source:node-neo-async is NEW.
Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so please
36 matches
Mail list logo
