From: Hongxu Jia <hongxu.jia@windriver.com>
To: <openembedded-core@lists.openembedded.org>,
"Burton, Ross" <ross.burton@intel.com>
Subject: Re: ✗ patchtest: failure for Upgrade 7 packages
Date: Fri, 30 Mar 2018 15:26:28 +0800 [thread overview]
Message-ID: <77cd677d-8c26-9eac-1dae-22afa985f447@windriver.com> (raw)
In-Reply-To: <20180330070529.2394.14955@do.openembedded.org>
On 2018年03月30日 15:05, Patchwork wrote:
> == Series Details ==
>
> Series: Upgrade 7 packages
> Revision: 1
> URL : https://patchwork.openembedded.org/series/11622/
> 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 LIC_FILES_CHKSUM changed on target libgpg-error but there is no "License-Update" tag in commit message [test_lic_files_chksum_modified_not_mentioned]
> Suggested fix Include "License-Update: <description>" into the commit message with a brief description
> Current checksum file://COPYING;md5=59530bdf33659b29e73d4adb9f9f6552 file://COPYING.LIB;md5=2d5025d4aa3495befef8f17206a5b0a1 file://src/gpg-error.h.in;endline=23;md5=beae1e44d8d5c265d194760276033a7c file://src/init.c;endline=20;md5=872b2389fe9bae7ffb80d2b91225afbc
> New checksum file://COPYING;md5=59530bdf33659b29e73d4adb9f9f6552 file://COPYING.LIB;md5=2d5025d4aa3495befef8f17206a5b0a1 file://src/gpg-error.h.in;endline=23;md5=fc7423b56d5f7163a9a2acf9fe2f8d6b file://src/init.c;endline=20;md5=872b2389fe9bae7ffb80d2b91225afbc
It already includes "License-Update: <description>":
...
1. License-Update: update years from 2003-2004 to 2001-2018,
and add a new line 'SPDX-License-Identifier: LGPL-2.1+'
...
Should I remove the starting "1. "?
> * Issue Patches not removed from tree [test_src_uri_left_files]
> Suggested fix Amend the patch containing the software patch file removal
> Patch avoid-host-contamination.patch
> Patch mkdir-p.patch
> Patch do-not-check-local-libpng-source.patch
> Patch ghostscript-9.02-genarch.patch
> Patch ghostscript-9.21-prevent_recompiling.patch
> Patch ghostscript-9.16-Werror-return-type.patch
> Patch cups-no-gcrypt.patch
> Patch ghostscript-9.15-parallel-make.patch
It already removes them from tree.
Should I git format-patch without "-M"?
//Hongxu
>
>
> 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
>
next prev parent reply other threads:[~2018-03-30 7:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-30 6:46 [PATCH 0/7] Upgrade 7 packages Hongxu Jia
2018-03-30 6:46 ` [PATCH 1/7] ncureses: 6.0+20171125 -> 6.1 Hongxu Jia
2018-03-30 6:46 ` [PATCH 2/7] bash: 4.4.12 -> 4.4.18 Hongxu Jia
2018-03-30 6:46 ` [PATCH 3/7] ghostscript: 9.21 -> 9.23 Hongxu Jia
2018-03-30 6:46 ` [PATCH 4/7] libgpg-error: 1.27 -> 1.28 Hongxu Jia
2018-03-30 6:46 ` [PATCH 5/7] dhcp: 4.3.6 -> 4.4.1 Hongxu Jia
2018-03-30 6:46 ` [PATCH 6/7] gnupg: upgrade 2.2.4 -> 2.2.5 Hongxu Jia
2018-03-30 6:46 ` [PATCH 7/7] man-db: upgrade 2.8.1 -> 2.8.2 Hongxu Jia
2018-03-30 7:05 ` ✗ patchtest: failure for Upgrade 7 packages Patchwork
2018-03-30 7:26 ` Hongxu Jia [this message]
2018-03-30 7:44 ` Richard Purdie
2018-03-30 7:57 ` Hongxu Jia
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=77cd677d-8c26-9eac-1dae-22afa985f447@windriver.com \
--to=hongxu.jia@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.