Re: ✗ patchtest: failure for "[rocko] openssl10: Upgrade 1.0..." and 3 more

[Stefan Agner <stefan@agner.ch>]

On 2017-11-17 23:53, Patchwork wrote:
> == Series Details ==
> 
> Series: "[rocko] openssl10: Upgrade 1.0..." and 3 more
> Revision: 1
> URL   : https://patchwork.openembedded.org/series/9855/
> 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 a17f3ec910)
> 
> * Patch            [rocko,1/4] openssl10: Upgrade 1.0.2l -> 1.0.2m
>  Issue             Missing or incorrectly formatted CVE tag in
> included patch file [test_cve_tag_format]
>   Suggested fix    Correct or include the CVE tag on cve patch with
> format: "CVE: CVE-YYYY-XXXX"
> 
> * Issue             A patch file has been added, but does not have a
> Signed-off-by tag [test_signed_off_by_presence]
>   Suggested fix    Sign off the added patch file
> (meta/recipes-connectivity/openssl/openssl-1.0.2m/0001-aes-armv4-bsaes-armv7-sha256-armv4-.pl-make-it-work-.patch)

The patch is a backport from upstream and does not have a Signed-off
line there.. Should I still add one?

Ack on the other two.

--
Stefan

> 
> * 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-connectivity/openssl/openssl/0001-aes-asm-aes-armv4-bsaes-armv7-.pl-make-it-work-with-.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@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