New Upstream Snapshot - node-any-promise
Creating a dist tarball from an upstream source repository snapshot failed.
More details
Historical runs
- dist-command-failed: Command 'SCHROOT=sid-amd64-sbuild PYTHONPATH=/:/usr/lib/python311.zip:/usr/lib/python3.11:/usr/lib/python3.11/lib-dynload:/usr/local/lib/python3.11/dist-packages:/usr/lib/python3/dist-packages /usr/bin/python3 -m janitor.debian.dist --log-directory=/tmp/janitor-workergzz2r1g7 --packaging=/tmp/janitor-workergzz2r1g7/node-any-promise.git/debian --apt-update --apt-dist-upgrade' returned non-zero exit status 1.
- killed: Command 'SCHROOT=unstable-amd64-sbuild PYTHONPATH=/:/code:/code/breezy:/code/dulwich:/code/lintian-brush:/code/ognibuild:/code/silver-platter:/code/buildlog-consultant:/code/upstream-ontologist:/code/debmutate:/code/python-debian/lib:/usr/lib/python310.zip:/usr/lib/python3.10:/usr/lib/python3.10/lib-dynload:/usr/local/lib/python3.10/dist-packages:/usr/lib/python3/dist-packages /usr/bin/python3 -m janitor.dist --packaging=/tmp/janitorul14ufhx/node-any-promise/debian' returned non-zero exit status 137.
- quilt-refresh-error: An error occurred refreshing quilt patch switch-test-from-ava-to-tape.diff: Applying patch debian/patches/switch-test-from-ava-to-tape.diff can't find file to patch at input line 8 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |Description: switch test from ava to tape |Author: Xavier Guimard <yadd@debian.org> |Forwarded: not-needed |Last-Update: 2020-02-18 | |--- a/test/bluebird-shortcut.js |+++ b/test/bluebird-shortcut.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 31 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/bluebird.js |+++ b/test/bluebird.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 52 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/browser.js |+++ b/test/browser.js -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 60 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/defaults.js |+++ b/test/defaults.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 80 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/es6-promise-shortcut.js |+++ b/test/es6-promise-shortcut.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 103 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/es6-promise.js |+++ b/test/es6-promise.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 124 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/global.js |+++ b/test/global.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 147 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/lie-shortcut.js |+++ b/test/lie-shortcut.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 168 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/lie.js |+++ b/test/lie.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 189 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/native-promise-only-shortcut.js |+++ b/test/native-promise-only-shortcut.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 212 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/native-promise-only.js |+++ b/test/native-promise-only.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 233 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/pinkie-shortcut.js |+++ b/test/pinkie-shortcut.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 254 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/pinkie.js |+++ b/test/pinkie.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 275 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/polyfill.js |+++ b/test/polyfill.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 297 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/promise-shortcut.js |+++ b/test/promise-shortcut.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 320 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/promise.js |+++ b/test/promise.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 341 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/q-shortcut.js |+++ b/test/q-shortcut.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 364 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/q.js |+++ b/test/q.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 385 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/register-local.js |+++ b/test/register-local.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 406 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/rsvp-shortcut.js |+++ b/test/rsvp-shortcut.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 429 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/rsvp.js |+++ b/test/rsvp.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 450 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/vow-shortcut.js |+++ b/test/vow-shortcut.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 471 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/vow.js |+++ b/test/vow.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 492 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/when-shortcut.js |+++ b/test/when-shortcut.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 515 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/when.js |+++ b/test/when.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored Patch debian/patches/switch-test-from-ava-to-tape.diff does not apply (enforce with -f)
- command-failed: Command 'SCHROOT=unstable-amd64-sbuild PYTHONPATH=/:/code:/code/breezy:/code/dulwich:/code/lintian-brush:/code/ognibuild:/code/silver-platter:/code/buildlog-consultant:/code/upstream-ontologist:/code/debmutate:/code/python-debian/lib:/usr/lib/python39.zip:/usr/lib/python3.9:/usr/lib/python3.9/lib-dynload:/usr/local/lib/python3.9/dist-packages:/usr/lib/python3/dist-packages /usr/bin/python3 -m janitor.dist --packaging=/tmp/janitorfi6wo165/node-any-promise/debian' returned non-zero exit status 1.
- command-failed: Command 'SCHROOT=unstable-amd64-sbuild PYTHONPATH=/:/code:/code/breezy:/code/dulwich:/code/lintian-brush:/code/ognibuild:/code/silver-platter:/code/buildlog-consultant:/code/upstream-ontologist:/code/debmutate:/code/python-debian/lib:/usr/lib/python39.zip:/usr/lib/python3.9:/usr/lib/python3.9/lib-dynload:/usr/local/lib/python3.9/dist-packages:/usr/lib/python3/dist-packages /usr/bin/python3 -m janitor.dist --packaging=/tmp/janitorfployarx/node-any-promise/debian' returned non-zero exit status 1.
- quilt-refresh-error: An error occurred refreshing quilt patch switch-test-from-ava-to-tape.diff: Applying patch debian/patches/switch-test-from-ava-to-tape.diff can't find file to patch at input line 8 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |Description: switch test from ava to tape |Author: Xavier Guimard <yadd@debian.org> |Forwarded: not-needed |Last-Update: 2020-02-18 | |--- a/test/bluebird-shortcut.js |+++ b/test/bluebird-shortcut.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 31 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/bluebird.js |+++ b/test/bluebird.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 52 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/browser.js |+++ b/test/browser.js -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 60 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/defaults.js |+++ b/test/defaults.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 80 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/es6-promise-shortcut.js |+++ b/test/es6-promise-shortcut.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 103 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/es6-promise.js |+++ b/test/es6-promise.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 124 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/global.js |+++ b/test/global.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 147 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/lie-shortcut.js |+++ b/test/lie-shortcut.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 168 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/lie.js |+++ b/test/lie.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 189 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/native-promise-only-shortcut.js |+++ b/test/native-promise-only-shortcut.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 212 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/native-promise-only.js |+++ b/test/native-promise-only.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 233 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/pinkie-shortcut.js |+++ b/test/pinkie-shortcut.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 254 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/pinkie.js |+++ b/test/pinkie.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 275 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/polyfill.js |+++ b/test/polyfill.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 297 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/promise-shortcut.js |+++ b/test/promise-shortcut.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 320 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/promise.js |+++ b/test/promise.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 341 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/q-shortcut.js |+++ b/test/q-shortcut.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 364 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/q.js |+++ b/test/q.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 385 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/register-local.js |+++ b/test/register-local.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 406 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/rsvp-shortcut.js |+++ b/test/rsvp-shortcut.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 429 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/rsvp.js |+++ b/test/rsvp.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 450 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/vow-shortcut.js |+++ b/test/vow-shortcut.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 471 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/vow.js |+++ b/test/vow.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 492 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/when-shortcut.js |+++ b/test/when-shortcut.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 515 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test/when.js |+++ b/test/when.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored Patch debian/patches/switch-test-from-ava-to-tape.diff does not apply (enforce with -f)
- command-failed: Command 'SCHROOT=unstable-amd64-sbuild PYTHONPATH=/:/code:/code/breezy:/code/dulwich:/code/lintian-brush:/code/ognibuild:/code/silver-platter:/code/buildlog-consultant:/code/upstream-ontologist:/code/debmutate:/code/python-debian/lib:/usr/lib/python39.zip:/usr/lib/python3.9:/usr/lib/python3.9/lib-dynload:/usr/local/lib/python3.9/dist-packages:/usr/lib/python3/dist-packages /usr/bin/python3 -m janitor.dist --packaging=/tmp/janitor52a32h5k/node-any-promise/debian' returned non-zero exit status 137.