busybox: fix typo in CVE-2016-2147_2.patch Upstream-Status tag
PATCH 1/1 busybox: fix typo in CVE-2016-2147_2.patch Upstream-Status tag
--- meta/recipes-core/busybox/busybox/CVE-2016-2147_2.patch | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
meta/recipes-core/busybox/busybox/CVE-2016-2147_2.patch +1 -1
@@ -4,7 +4,7 @@ Date: Fri, 11 Mar 2016 00:26:58 +0100 Subject: [PATCH] udhcpc: fix a warning in debug code Signed-off-by: Denys Vlasenko <[email protected]> -Upsteam-Status: Backport +Upstream-Status: Backport CVE: CVE-2016-2147 regression fix https://git.busybox.net/busybox/commit/?id=1b7c17
Signature · 1 line
1.9.1
✗ patchtest: failure for busybox: fix typo in CVE-2016-2147_2.patch Upstream-Status tag
== Series Details ==
Series: busybox: fix typo in CVE-2016-2147_2.patch Upstream-Status tag
Revision: 1
URL : https://patchwork.openembedded.org/series/6429/
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 busybox: fix typo in CVE-2016-2147_2.patch Upstream-Status tag 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 ([email protected]) 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 Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe
Re: ✗ patchtest: failure for busybox: fix typo in CVE-2016-2147_2.patch Upstream-Status tag
Quoted 16 lines · Patchwork
== Series Details ==
Series: busybox: fix typo in CVE-2016-2147_2.patch Upstream-Status tag
Revision: 1
URL : https://patchwork.openembedded.org/series/6429/
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:
Quoted 3 lines
* Patch busybox: fix typo in CVE-2016-2147_2.patch Upstream-Status tag 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
Andre,
there is no need to send a second revision due to the above patchtest issue. The system detected the CVE on shortlog thus triggering the check on the commit message, but for this case there is no need. Will fix this.
Leo
Quoted 14 lines
If you believe any of these test results are incorrect, please reply to the mailing list ([email protected]) 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 Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe
Re: ✗ patchtest: failure for busybox: fix typo in CVE-2016-2147_2.patch Upstream-Status tag
Quoted 18 lines · Leonardo Sandoval
Quoted 9 lines · Patchwork
== Series Details ==
Series: busybox: fix typo in CVE-2016-2147_2.patch Upstream-Status tag
Revision: 1
URL : https://patchwork.openembedded.org/series/6429/
State : failure== Summary ==
Quoted 7 lines
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 busybox: fix typo in CVE-2016-2147_2.patch Upstream-Status tag 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
Quoted 6 lines
Andre,
there is no need to send a second revision due to the above patchtest issue. The system detected the CVE on shortlog thus triggering the check on the commit message, but for this case there is no need. Will fix this.
Thanks Leo.
Quoted 12 lines
Quoted 12 lines
If you believe any of these test results are incorrect, please reply to the mailing list ([email protected]) 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 Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe