New Upstream Release - yosys
There were merge conflicts while merging a new upstream version.
More details
Historical runs
- upstream-merged-conflicts: Merging upstream version 0.25 resulted in conflicts.
- run-disappeared: Worker started processing new run 95c46f11-623b-4291-aec5-2b34165bbfab rather than cf7c52d1-a3e5-487f-9505-e8864e8ae9a7
- worker-clone-incomplete-read: IncompleteRead(0 bytes read)
- new-upstream-tarball-missing: New upstream version (yosys/0.20+ds) found, but was missing when retrieved as tarball from <UScanSource(<GitWorkingTree of /tmp/janitorwce07smr/yosys>, subpath='', top_level=False, auto_fix=True)>.
- codemod-command-failed: Script ['deb-new-upstream', '--refresh-patches'] failed to run with code 1
- worker-exception: EOF occurred in violation of protocol (_ssl.c:2396)
- nothing-to-do: Last upstream version 0.15 already imported. Import a snapshot by specifying --snapshot.
- quilt-refresh-error: An error occurred refreshing quilt patch 0016-opt_mem_priority-Fix-non-ascii-char-in-help-message.patch: Applying patch debian/patches/0016-opt_mem_priority-Fix-non-ascii-char-in-help-message.patch patching file manual/command-reference-manual.tex Hunk #1 FAILED at 3163. Hunk #2 succeeded at 3770 (offset 109 lines). Hunk #3 FAILED at 7475. 2 out of 3 hunks FAILED -- rejects in file manual/command-reference-manual.tex patching file passes/opt/opt_mem_priority.cc Hunk #1 FAILED at 34. 1 out of 1 hunk FAILED -- rejects in file passes/opt/opt_mem_priority.cc Patch debian/patches/0016-opt_mem_priority-Fix-non-ascii-char-in-help-message.patch does not apply (enforce with -f)