Skip to contentSkip to conversation

diffoscope: upgrade 136 -> 141

PATCH In review Joshua Watt 2 participants 2 messages Apr 22, 2020

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 diffoscope: upgrade 136 -> 141

From: Upgrade Helper <[email protected]>

---
 .../diffoscope/{diffoscope_136.bb => diffoscope_141.bb}       | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-support/diffoscope/{diffoscope_136.bb => diffoscope_141.bb} (75%)
meta/recipes-support/diffoscope/diffoscope_141.bb renamed from meta/recipes-support/diffoscope/diffoscope_136.bb +2 -2
similarity index 75%
rename from meta/recipes-support/diffoscope/diffoscope_136.bb
rename to meta/recipes-support/diffoscope/diffoscope_141.bb
index 3e3e1dfc00..d80e2982a8 100644
@@ -7,8 +7,8 @@ PYPI_PACKAGE = "diffoscope"
 
 inherit pypi setuptools3
 
-SRC_URI[md5sum] = "c84d8d308a40176ba2f5dc4abdbf6f73"
-SRC_URI[sha256sum] = "0d6486d6eb6e0445ba21fee2e8bdd3a366ce786bfac98e00e5a95038b7815f15"
+SRC_URI[md5sum] = "35329bb68861ff0d8245584b7ad408d7"
+SRC_URI[sha256sum] = "66a8d066f8f5ac18d02aa5148ada7c6f4ab094cd64d29e72b319c5e7df151fc0"
 
 RDEPENDS_${PN} += "binutils vim squashfs-tools python3-libarchive-c python3-magic"
 
Signature · 1 line
2.17.1
#1 lore raw

✗ patchtest: failure for diffoscope: upgrade 136 -> 141

== Series Details ==

Series: diffoscope: upgrade 136 -> 141
Revision: 1
URL : https://patchwork.openembedded.org/series/23833/
State : failure

== Summary ==

Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on the proposed series by patchtest resulting in the following failures:

* Patch            diffoscope: upgrade 136 -> 141
 Issue             Invalid author <[email protected]> in commit message [test_non_auh_upgrade] 
  Suggested fix    Resend the series with a valid patch's author

If you believe any of these test results are incorrect, please reply to the mailing list ([email protected]) raising your concerns. Otherwise we would appreciate you correcting the issues and submitting a new version of the patchset if applicable. Please ensure you add/increment the version number when sending the new version (i.e. [PATCH] -> [PATCH v2] -> [PATCH v3] -> ...).

---

Guidelines:     https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
Test suite:     http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe