From: Denys Dmytriyenko <denis@denix.org>
To: Nicolas Ferre <nicolas.ferre@microchip.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH] devmem2: Change source URL to regain access to it
Date: Tue, 14 Mar 2017 12:14:31 -0400 [thread overview]
Message-ID: <20170314161431.GJ15664@denix.org> (raw)
In-Reply-To: <20170228150119.21252-1-nicolas.ferre@microchip.com>
On Tue, Feb 28, 2017 at 04:01:19PM +0100, Nicolas Ferre wrote:
> Change URL due to connexion error on the original page.
> As the header of the new devmem2.c source file has changed, change the
> signature and the LIC_FILES_CHKSUM specificaiton.
Oh, great! So, now, everyone who has this file cached locally would have to
invalidate their mirrors? Moreover, if you are building master and morty or
older, you can't reuse the same source mirror as each of the builds will
complain about bad checksums...
--
Denys
> Signed-off-by: Nicolas Ferre <nicolas.ferre@microchip.com>
> ---
> meta-oe/recipes-support/devmem2/devmem2.bb | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/meta-oe/recipes-support/devmem2/devmem2.bb b/meta-oe/recipes-support/devmem2/devmem2.bb
> index e48cc9210bb3..c42eb5e0b1c5 100644
> --- a/meta-oe/recipes-support/devmem2/devmem2.bb
> +++ b/meta-oe/recipes-support/devmem2/devmem2.bb
> @@ -1,9 +1,9 @@
> SUMMARY = "Simple program to read/write from/to any location in memory"
> LICENSE = "GPLv2+"
> -LIC_FILES_CHKSUM = "file://devmem2.c;endline=28;md5=dd68f2b0a5184b3db3dc25c99e0bd0cd"
> +LIC_FILES_CHKSUM = "file://devmem2.c;endline=38;md5=a9eb9f3890384519f435aedf986297cf"
> PR = "r7"
>
> -SRC_URI = "http://www.lartmaker.nl/lartware/port/devmem2.c \
> +SRC_URI = "http://www.free-electrons.com/pub/mirror/devmem2.c \
> file://devmem2-fixups-2.patch;apply=yes;striplevel=0"
> S = "${WORKDIR}"
>
> @@ -18,5 +18,5 @@ do_install() {
> install devmem2 ${D}${bindir}
> }
>
> -SRC_URI[md5sum] = "be12c0132a1ae118cbf5e79d98427c1d"
> -SRC_URI[sha256sum] = "ec382c90af3ef2f49695ff14a4d6521e58ac482c4e29d6c9ebca8768f699c191"
> +SRC_URI[md5sum] = "e23f236e94be4c429aa1ceac0f01544b"
> +SRC_URI[sha256sum] = "3b15515693bae1ebd14d914e46d388edfec2175829ea1576a7a0c8606ebbe639"
> --
> 2.9.0
>
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2017-03-14 16:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 15:01 [meta-oe][PATCH] devmem2: Change source URL to regain access to it Nicolas Ferre
2017-03-14 16:14 ` Denys Dmytriyenko [this message]
2017-03-14 17:37 ` Alexandre Belloni
2017-03-14 18:13 ` Martin Jansa
2017-03-14 18:33 ` Alexandre Belloni
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=20170314161431.GJ15664@denix.org \
--to=denis@denix.org \
--cc=nicolas.ferre@microchip.com \
--cc=openembedded-devel@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