From: Jose Lamego <jose.a.lamego@linux.intel.com>
To: Jussi Kukkonen <jussi.kukkonen@intel.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: ✗ patchtest: failure for libgcrypt: fix CVE-2017-9526 (rev2)
Date: Fri, 14 Jul 2017 08:12:04 -0500 [thread overview]
Message-ID: <01e393aa-f547-c6a2-7e9c-a93ee8ce24bb@linux.intel.com> (raw)
In-Reply-To: <CAHiDW_FjapMrVu=URNJNo4T0K+99XByZSeVGK743WdMFpLSOuA@mail.gmail.com>
On 07/14/2017 02:57 AM, Jussi Kukkonen wrote:
> On 13 July 2017 at 21:38, Patchwork
> <patchwork@patchwork.openembedded.org
> <mailto:patchwork@patchwork.openembedded.org>> wrote:
>
> == Series Details ==
>
> Series: libgcrypt: fix CVE-2017-9526 (rev2)
> Revision: 2
>
>
> Not sure if this should be a patchwork bug or not? This patch is
> showing up as a revision 2 of the other patch when in reality they are
> patches for two separate branches.
>
> - Jussi
There is a request to handle older release patch submissions in
Patchwork (bug 10716) planned to be completed in 2.5, however, I may be
able to implement the change in the following days.
Jose
>
>
>
> URL : https://patchwork.openembedded.org/series/7732/
> <https://patchwork.openembedded.org/series/7732/>
> 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:
>
>
>
> * Patch [pyro] libgcrypt: fix CVE-2017-9526
> Issue Missing or incorrectly formatted CVE tag in
> commit message [test_cve_presence_in_commit_message]
> Suggested fix Include a "CVE-xxxx-xxxx" tag in the commit message
>
>
>
> If you believe any of these test results are incorrect, please
> reply to the
> mailing list (openembedded-core@lists.openembedded.org
> <mailto: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] -> ...).
>
> ---
> Test framework:
> http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
> <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>
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> <mailto:Openembedded-core@lists.openembedded.org>
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
> <http://lists.openembedded.org/mailman/listinfo/openembedded-core>
>
>
>
>
--
Jose Lamego | OTC Embedded Platform & Tools | GDC
prev parent reply other threads:[~2017-07-14 13:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 17:48 [PATCH][pyro] libgcrypt: fix CVE-2017-9526 Ross Burton
2017-07-13 18:38 ` ✗ patchtest: failure for libgcrypt: fix CVE-2017-9526 (rev2) Patchwork
2017-07-14 7:57 ` Jussi Kukkonen
2017-07-14 13:12 ` Jose Lamego [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=01e393aa-f547-c6a2-7e9c-a93ee8ce24bb@linux.intel.com \
--to=jose.a.lamego@linux.intel.com \
--cc=jussi.kukkonen@intel.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox