Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Patchwork <patchwork@patchwork.openembedded.org>
To: Jens Rehsack <sno@netbsd.org>
Cc: openembedded-core@lists.openembedded.org
Subject: ✗ patchtest: failure for perl{,-native}: Update 5.24.4 -> 5.28.1
Date: Fri, 14 Dec 2018 10:03:25 -0000	[thread overview]
Message-ID: <20181214100325.2330.29791@do> (raw)
In-Reply-To: <20181214094319.2935-1-sno@netbsd.org>

== Series Details ==

Series: perl{,-native}: Update 5.24.4 -> 5.28.1
Revision: 1
URL   : https://patchwork.openembedded.org/series/15340/
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 perl-native 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=5b122a36d0f6dc55279a0ebc69f3c60b 		    file://Artistic;md5=2e6fd2475335af892494fe1f7327baf3
  New checksum     file://Copying;md5=5b122a36d0f6dc55279a0ebc69f3c60b 		    file://Artistic;md5=71a4d5d9acc18c0952a6df2218bb68da

* Patch            perl{,-native}: Update 5.24.4 -> 5.28.1
 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"



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



  reply	other threads:[~2018-12-14 10:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-14  9:43 [PATCH] perl{,-native}: Update 5.24.4 -> 5.28.1 Jens Rehsack
2018-12-14 10:03 ` Patchwork [this message]
2018-12-14 11:57 ` Richard Purdie

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=20181214100325.2330.29791@do \
    --to=patchwork@patchwork.openembedded.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sno@netbsd.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