From: Martin Jansa <martin.jansa@gmail.com>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 6/7] stress: update checksums to match upstream tarball
Date: Mon, 3 Aug 2015 18:58:32 +0200 [thread overview]
Message-ID: <20150803165832.GC2465@jama> (raw)
In-Reply-To: <fd641de4c497143e62a5f662584ff91c65bec9da.1438619216.git.alexander.kanavin@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 2036 bytes --]
On Mon, Aug 03, 2015 at 07:29:53PM +0300, Alexander Kanavin wrote:
> COPYING checksum has changed because the previous upstream tarball
> (taken from Fedora) had GPLv3 in it, but author's tarball has GPLv2.
> Otherwise the tarballs are identical
>
> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
> ---
> meta/recipes-extended/stress/stress_1.0.4.bb | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/meta/recipes-extended/stress/stress_1.0.4.bb b/meta/recipes-extended/stress/stress_1.0.4.bb
> index df96fc0..00d9940 100644
> --- a/meta/recipes-extended/stress/stress_1.0.4.bb
> +++ b/meta/recipes-extended/stress/stress_1.0.4.bb
> @@ -2,13 +2,13 @@ DESCRIPTION = "Deliberately simple workload generator for POSIX systems. It \
> imposes a configurable amount of CPU, memory, I/O, and disk stress on the system."
> HOMEPAGE = "http://people.seas.harvard.edu/~apw/stress/"
> LICENSE = "GPLv2"
> -LIC_FILES_CHKSUM = "file://COPYING;md5=d32239bcb673463ab874e80d47fae504"
> +LIC_FILES_CHKSUM = "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"
>
> SRC_URI = "http://people.seas.harvard.edu/~apw/stress/stress-${PV}.tar.gz \
Did you forget to update this? Commit message says something about
Fedora tarball...
Please also use $"{BPN}/${BP}" instead of "stress/stress-${PV}"
> file://texinfo.patch \
> "
>
> -SRC_URI[md5sum] = "a607afa695a511765b40993a64c6e2f4"
> -SRC_URI[sha256sum] = "369c997f65e8426ae8b318d4fdc8e6f07a311cfa77cc4b25dace465c582163c0"
> +SRC_URI[md5sum] = "890a4236dd1656792f3ef9a190cf99ef"
> +SRC_URI[sha256sum] = "057e4fc2a7706411e1014bf172e4f94b63a12f18412378fca8684ca92408825b"
>
> inherit autotools
> --
> 2.1.4
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2015-08-03 16:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-03 16:29 [PATCH 0/7] More recipe reporting fixes Alexander Kanavin
2015-08-03 16:29 ` [PATCH 1/7] fotowall: update SRC_URI to use github instead of qt-apps.org Alexander Kanavin
2015-08-07 9:26 ` Robert Yang
2015-08-07 11:01 ` Richard Purdie
2015-08-07 12:27 ` Alexander Kanavin
2015-08-03 16:29 ` [PATCH 2/7] distcc: update SRC_URI to not use Google Code Alexander Kanavin
2015-08-07 9:25 ` Robert Yang
2015-08-07 9:40 ` Khem Raj
2015-08-07 11:00 ` Richard Purdie
2015-08-03 16:29 ` [PATCH 3/7] gptfdisk: update to 1.0.0 Alexander Kanavin
2015-08-03 16:29 ` [PATCH 4/7] oprofile: reorder SRC_URI lines to fix upstream version check Alexander Kanavin
2015-08-03 16:29 ` [PATCH 5/7] xf86-video-omapfb: switch SRC_URI to debian git repo Alexander Kanavin
2015-08-07 11:33 ` Richard Purdie
2015-08-03 16:29 ` [PATCH 6/7] stress: update checksums to match upstream tarball Alexander Kanavin
2015-08-03 16:58 ` Martin Jansa [this message]
2015-08-03 17:11 ` Alexander Kanavin
2015-08-03 16:29 ` [PATCH 7/7] recipeutils.py: allow all characters in regexes used to parse version strings Alexander Kanavin
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=20150803165832.GC2465@jama \
--to=martin.jansa@gmail.com \
--cc=alexander.kanavin@linux.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