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

[richard.purdie at linuxfoundation.org]

On Tue, 2018-09-18 at 16:22 +0200, Jens Rehsack wrote:
> 	Error verifying signature: Failed to execute gpg.
> 
> 
> > Am 17.09.2018 um 21:03 schrieb Patchwork <patchwork at patchwork.opene
> > mbedded.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_Mess
> > age_Guidelines
> > Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
> > Test suite:     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.

Nobody is saying it has to be submitted upstream, although we obviously
do appreciate anyone doing that a lot. We do ask any patches which get
added have a status though so we have some idea what is happening to
them.

So in this case the status would be "Pending".

Cheers,

Richard