New Upstream Snapshot - node-chance
More details
Historical runs
- quilt-patch-out-of-date: Quilt patch replace-ava-by-jest.patch no longer applies
- quilt-refresh-error: An error occurred refreshing quilt patch replace-ava-by-jest.patch: Applying patch debian/patches/replace-ava-by-jest.patch can't find file to patch at input line 9 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |Description: replace ava by jest | This patch was generated using jest-codemods + some test removed |Author: Xavier Guimard <yadd@debian.org> |Forwarded: not-needed |Last-Update: 2021-01-07 | |--- a/test.archive/test.address.js |+++ b/test.archive/test.address.js -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 825 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test.archive/test.animal.js |+++ b/test.archive/test.animal.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 874 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test.archive/test.basic.js |+++ b/test.archive/test.basic.js -------------------------- No file to patch. Skipping patch. 8 out of 8 hunks ignored can't find file to patch at input line 1588 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test.archive/test.buffer.js |+++ b/test.archive/test.buffer.js -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 1633 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test.archive/test.company.js |+++ b/test.archive/test.company.js -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 1657 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test.archive/test.file.js |+++ b/test.archive/test.file.js -------------------------- No file to patch. Skipping patch. 3 out of 3 hunks ignored can't find file to patch at input line 1785 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test.archive/test.finance.js |+++ b/test.archive/test.finance.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 2086 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test.archive/test.helpers.js |+++ b/test.archive/test.helpers.js -------------------------- No file to patch. Skipping patch. 7 out of 7 hunks ignored can't find file to patch at input line 2609 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test.archive/test.misc.js |+++ b/test.archive/test.misc.js -------------------------- No file to patch. Skipping patch. 4 out of 4 hunks ignored can't find file to patch at input line 3023 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test.archive/test.mobile.js |+++ b/test.archive/test.mobile.js -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 3067 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test.archive/test.music.js |+++ b/test.archive/test.music.js -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 3142 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test.archive/test.normal.js |+++ b/test.archive/test.normal.js -------------------------- No file to patch. Skipping patch. 3 out of 3 hunks ignored can't find file to patch at input line 3287 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test.archive/test.person.js |+++ b/test.archive/test.person.js -------------------------- No file to patch. Skipping patch. 5 out of 5 hunks ignored can't find file to patch at input line 3884 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test.archive/test.regional.js |+++ b/test.archive/test.regional.js -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 3975 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test.archive/test.text.js |+++ b/test.archive/test.text.js -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 4134 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test.archive/test.time.js |+++ b/test.archive/test.time.js -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 4553 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- a/test.archive/test.web.js |+++ b/test.archive/test.web.js -------------------------- No file to patch. Skipping patch. 3 out of 3 hunks ignored Patch debian/patches/replace-ava-by-jest.patch 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/janitorqmedy80e/node-chance/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/janitor1roz5da6/node-chance/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/janitorb_pgo3js/node-chance/debian' returned non-zero exit status 137.
- 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/janitorq5o0g5c8/node-chance/debian' returned non-zero exit status 1.