From: Patchwork <patchwork@patchwork.openembedded.org>
To: Hong Liu <hongl.fnst@cn.fujitsu.com>
Cc: openembedded-core@lists.openembedded.org
Subject: ✗ patchtest: failure for xz:5.2.3 -> 5.2.4
Date: Fri, 20 Jul 2018 10:02:57 -0000 [thread overview]
Message-ID: <20180720100257.13844.47753@do.openembedded.org> (raw)
In-Reply-To: <20180720093813.16328-1-hongl.fnst@cn.fujitsu.com>
== Series Details ==
Series: xz:5.2.3 -> 5.2.4
Revision: 1
URL : https://patchwork.openembedded.org/series/13124/
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 xz 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=c475b6c7dca236740ace4bba553e8e1c file://COPYING.GPLv2;md5=b234ee4d69f5fce4486a80fdaf4a4263 file://COPYING.GPLv3;md5=d32239bcb673463ab874e80d47fae504 file://COPYING.LGPLv2.1;md5=4fbd65380cdd255951079008b364516c file://lib/getopt.c;endline=23;md5=2069b0ee710572c03bb3114e4532cd84
New checksum file://COPYING;md5=97d554a32881fee0aa283d96e47cb24a file://COPYING.GPLv2;md5=b234ee4d69f5fce4486a80fdaf4a4263 file://COPYING.GPLv3;md5=d32239bcb673463ab874e80d47fae504 file://COPYING.LGPLv2.1;md5=4fbd65380cdd255951079008b364516c file://lib/getopt.c;endline=23;md5=2069b0ee710572c03bb3114e4532cd84
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
prev parent reply other threads:[~2018-07-20 10:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 9:38 [PATCH] [PATCH] xz:5.2.3 -> 5.2.4 Hong Liu
2018-07-20 10:02 ` Patchwork [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=20180720100257.13844.47753@do.openembedded.org \
--to=patchwork@patchwork.openembedded.org \
--cc=hongl.fnst@cn.fujitsu.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