node-on-finished_2.1.0-2.debian.tar.xz has incorrect size; deleting it
Greetings,
Your Debian queue daemon (running on host franck.debian.org)
___
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
node-on-finished_2.1.0-2.dsc has incorrect size; deleting it
node-on-finished_2.1.0-2.debian.tar.xz doesn't exist
Due to the errors above, the .changes file couldn't be processed.
Please fix the problems for the upload to happen.
Greetings,
Your Debian queue daemon (running on host
node-on-finished_2.1.0-2_sourceupload.changes uploaded successfully to localhost
along with the files:
node-on-finished_2.1.0-2.dsc
node-on-finished_2.1.0-2.debian.tar.xz
node-on-finished_2.1.0-2_all.deb
node-finished_2.1.0-2_all.deb
Greetings,
Your Debian queue daemon (running
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 14 Oct 2014 10:24:28 +0200
Source: node-on-finished
Binary: node-on-finished node-finished
Architecture: source all
Version: 2.1.0-2
Distribution: unstable
Urgency: low
Maintainer: Debian Javascript Maintainers
FYI: The status of the node-yazl source package
in Debian's testing distribution has changed.
Previous version: (not in testing)
Current version: 2.0.1-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you
node-finalhandler_0.3.0-1_amd64.changes uploaded successfully to localhost
along with the files:
node-finalhandler_0.3.0-1.dsc
node-finalhandler_0.3.0.orig.tar.gz
node-finalhandler_0.3.0-1.debian.tar.xz
node-finalhandler_0.3.0-1_all.deb
Greetings,
Your Debian queue daemon
node-serve-index_1.4.0-1_amd64.changes uploaded successfully to localhost
along with the files:
node-serve-index_1.4.0-1.dsc
node-serve-index_1.4.0.orig.tar.gz
node-serve-index_1.4.0-1.debian.tar.xz
node-serve-index_1.4.0-1_all.deb
Greetings,
Your Debian queue daemon (running on
binary:node-serve-index is NEW.
source:node-serve-index 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 patient.
Packages are
binary:node-finalhandler is NEW.
source:node-finalhandler 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 patient.
Packages are
See
https://github.com/andrewrk/node-multiparty/commit/11780f4a6e3e8c6d439639794c795bb5fdaefe97#commitcomment-8163898
According to this, if a package depends on readable-stream 1.1.x, then it
is actually puling in node 0.11 stream API. This means that patching it to
use built-in v0.10.29 stream
I fixed all the bugs in node-findit and submitted the patch to upstream:
https://github.com/substack/node-findit/pull/34
But I am afraid that upstream will not accept my code and I do not have
time to wait. So I have forked findit to findit2 and started using that in
my modules, because it fixes
11 matches
Mail list logo