[OE-core] ✗ patchtest: failure for python3{,-native}: update to 3.7.0 (rev3)

[Jens Rehsack]

> Am 17.09.2018 um 21:03 schrieb Patchwork <patchwork at patchwork.openembedded.org>:
> 
> == Series Details ==
> 
> Series: python3{,-native}: update to 3.7.0 (rev3)
> Revision: 3
> URL   : https://patchwork.openembedded.org/series/13851/
> 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:
> 
> 
> 
> * Issue             Added patch file is missing Upstream-Status in the header [test_upstream_status_presence_format]
>  Suggested fix    Add Upstream-Status: <Valid status> to the header of meta/recipes-devtools/python/python3/uuid_when_cross_compiling.patch
>  Standard format  Upstream-Status: <Valid status>
>  Valid status     Pending, Accepted, Backport, Denied, Inappropriate [reason], Submitted [where]
> 
> 
> 
> If you believe any of these test results are incorrect, please reply to the
> mailing list (openembedded-core at lists.openembedded.org) 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 <http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe>


I understand this policy. I have an issue wrt. this particular one.
Why? Well - the patch seems to be reasonable submitted to upstream, since it's a
quirk and likely an error. OTOH - supporting Yocto and OpenEmbedded in getting
software up-to-date is one thing - having my name in the Python contributors is
something complete different.

Please find someone else doing that.

Thanks in advance,
Jens
--
Jens Rehsack - rehsack at gmail.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20180918/726d3bfc/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20180918/726d3bfc/attachment-0002.sig>