binary:node-jingle-filetransfer-session is NEW.
binary:node-jingle-filetransfer-session is NEW.
source:node-jingle-filetransfer-session 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
Open
node-jingle-filetransfer-session_2.0.2-1_amd64.changes uploaded successfully to
localhost
along with the files:
node-jingle-filetransfer-session_2.0.2-1.dsc
node-jingle-filetransfer-session_2.0.2.orig.tar.gz
node-jingle-filetransfer-session_2.0.2-1.debian.tar.xz
node-jingle-filetransfer-se
node-jingle-session_2.0.3-1_amd64.changes uploaded successfully to localhost
along with the files:
node-jingle-session_2.0.3-1.dsc
node-jingle-session_2.0.3.orig.tar.gz
node-jingle-session_2.0.3-1.debian.tar.xz
node-jingle-session_2.0.3-1_all.deb
node-jingle-session_2.0.3-1_amd64.buildinf
binary:node-uuid is NEW.
binary:node-uuid is NEW.
node-uuid_3.3.2.orig.tar.gz is only available in 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)
binary:node-jingle-session is NEW.
binary:node-jingle-session is NEW.
source:node-jingle-session 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
node-uuid_3.3.2-2_amd64.changes uploaded successfully to localhost
along with the files:
node-uuid_3.3.2-2.dsc
node-uuid_3.3.2-2.debian.tar.xz
node-node-uuid_3.3.2-2_all.deb
node-uuid_3.3.2-2_all.deb
node-uuid_3.3.2-2_amd64.buildinfo
Greetings,
Your Debian queue daemon (running
Il
Le ven. 28 sept. 2018 à 07:27, Petter Reinholdtsen a
écrit :
> Control: tags -1 + help upstream confirmed
>
> [Jérémy Lal]
> > Depending on nodejs-legacy was a serious bug in the first place.
> > Anyway (nodejs >= 6.11.2~) installs /usr/bin/node now.
>
> I had a look at this, and do not know
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 28 Sep 2018 15:46:02 +
Source: science.js
Binary: libjs-sciencejs
Architecture: source
Version: 1.9.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Petter Rein
science.js_1.9.3-3_source.changes uploaded successfully to localhost
along with the files:
science.js_1.9.3-3.dsc
science.js_1.9.3-3.debian.tar.xz
science.js_1.9.3-3_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
--
Pkg-javascript-devel mai
Your message dated Fri, 28 Sep 2018 13:35:21 +
with message-id
and subject line Bug#876618: fixed in science.js 1.9.3-2
has caused the Debian Bug report #876618,
regarding science.js build-depends on removed nodejs-legacy
to be marked as done.
This means that you claim that the problem has be
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 28 Sep 2018 13:16:36 +
Source: science.js
Binary: libjs-sciencejs
Architecture: source
Version: 1.9.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Petter Rein
science.js_1.9.3-2_source.changes uploaded successfully to localhost
along with the files:
science.js_1.9.3-2.dsc
science.js_1.9.3-2.debian.tar.xz
science.js_1.9.3-2_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
--
Pkg-javascript-devel mai
binary:node-timeago.js is NEW.
binary:node-timeago.js is NEW.
source:node-timeago.js 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
node-timeago.js_3.0.2+dfsg-1_amd64.changes uploaded successfully to localhost
along with the files:
node-timeago.js_3.0.2+dfsg-1.dsc
node-timeago.js_3.0.2+dfsg.orig.tar.xz
node-timeago.js_3.0.2+dfsg-1.debian.tar.xz
node-timeago.js_3.0.2+dfsg-1_all.deb
node-timeago.js_3.0.2+dfsg-1_amd64.bu
14 matches
Mail list logo
