[OE-core] ✗ patchtest: failure for Add pypi.bbclass; python improvements

[Tim Orling]

I stand corrected. When I try to apply the mbox file from patchwork it throws:

error: patch fragment without header at line 147: @@ -172,6 +172,10 @@ SUMMARY_${PN}-png                                                                                  util="Python package extension utility support”

My guess is this is because the manifest files have lines that are 2500+ characters long.


> On Nov 23, 2017, at 12:31 PM, Tim Orling <timothy.t.orling at linux.intel.com> wrote:
> 
> I just manually applied the entire series on top of openembedded-core master, so this is definitely a false positive.
> 
>> On Nov 23, 2017, at 12:10 PM, Tim Orling <timothy.t.orling at linux.intel.com> wrote:
>> 
>> This seems like a false positive, as this series is based on top of master?
>> 
>> Is it expecting master for “poky” or master for “openembedded-core”?
>> 
>>> On Nov 23, 2017, at 11:37 AM, Patchwork <patchwork at patchwork.openembedded.org> wrote:
>>> 
>>> == Series Details ==
>>> 
>>> Series: Add pypi.bbclass; python improvements
>>> Revision: 1
>>> URL   : https://patchwork.openembedded.org/series/9940/
>>> 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             Series does not apply on top of target branch [test_series_merge_on_head] 
>>> Suggested fix    Rebase your series on top of targeted branch
>>> Targeted branch  master (currently at 33418ed064)
>>> 
>>> 
>>> 
>>> 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
>>> 
>> 
>> -- 
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core at lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
> 
> -- 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core