<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">Am 17.09.2018 um 21:03 schrieb Patchwork <<a href="mailto:patchwork@patchwork.openembedded.org" class="">patchwork@patchwork.openembedded.org</a>>:</div><br class="Apple-interchange-newline"><div class=""><div class="">== Series Details ==<br class=""><br class="">Series: python3{,-native}: update to 3.7.0 (rev3)<br class="">Revision: 3<br class="">URL : <a href="https://patchwork.openembedded.org/series/13851/" class="">https://patchwork.openembedded.org/series/13851/</a><br class="">State : failure<br class=""><br class="">== Summary ==<br class=""><br class=""><br class="">Thank you for submitting this patch series to OpenEmbedded Core. This is<br class="">an automated response. Several tests have been executed on the proposed<br class="">series by patchtest resulting in the following failures:<br class=""><br class=""><br class=""><br class="">* Issue Added patch file is missing Upstream-Status in the header [test_upstream_status_presence_format] <br class=""> Suggested fix Add Upstream-Status: <Valid status> to the header of meta/recipes-devtools/python/python3/uuid_when_cross_compiling.patch<br class=""> Standard format Upstream-Status: <Valid status><br class=""> Valid status Pending, Accepted, Backport, Denied, Inappropriate [reason], Submitted [where]<br class=""><br class=""><br class=""><br class="">If you believe any of these test results are incorrect, please reply to the<br class="">mailing list (<a href="mailto:openembedded-core@lists.openembedded.org" class="">openembedded-core@lists.openembedded.org</a>) raising your concerns.<br class="">Otherwise we would appreciate you correcting the issues and submitting a new<br class="">version of the patchset if applicable. Please ensure you add/increment the<br class="">version number when sending the new version (i.e. [PATCH] -> [PATCH v2] -><br class="">[PATCH v3] -> ...).<br class=""><br class="">---<br class="">Guidelines: <a href="https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines" class="">https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines</a><br class="">Test framework: <a href="http://git.yoctoproject.org/cgit/cgit.cgi/patchtest" class="">http://git.yoctoproject.org/cgit/cgit.cgi/patchtest</a><br class="">Test suite: <a href="http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe" class="">http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe</a><br class=""></div></div></blockquote></div><div class=""><br class=""></div><div class="">I understand this policy. I have an issue wrt. this particular one.</div><div class="">Why? Well - the patch seems to be reasonable submitted to upstream, since it's a</div><div class="">quirk and likely an error. OTOH - supporting Yocto and OpenEmbedded in getting</div><div class="">software up-to-date is one thing - having my name in the Python contributors is</div><div class="">something complete different.</div><div class=""><br class=""></div><div class="">Please find someone else doing that.</div><div class=""><br class=""></div><div class="">Thanks in advance,</div><div class="">Jens</div><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">-- </div><div class="">Jens Rehsack - <a href="mailto:rehsack@gmail.com" class="">rehsack@gmail.com</a></div></div></div>
</div>
<br class=""></body></html>