From: "Bruce Ashfield" <bruce.ashfield@gmail.com>
To: Alex Stewart <alex.stewart@ni.com>
Cc: meta-virtualization@lists.yoctoproject.org
Subject: Re: [meta-virtualization][m-c-s][PATCH 1/2] salt: correct LICENSE md5sum
Date: Fri, 27 Aug 2021 10:53:46 -0400 [thread overview]
Message-ID: <20210827145343.GA23990@gmail.com> (raw)
In-Reply-To: <20210823191932.2555152-1-alex.stewart@ni.com>
Thanks for the fixes, these are now merged.
Bruce
In message: [meta-virtualization][m-c-s][PATCH 1/2] salt: correct LICENSE md5sum
on 23/08/2021 Alex Stewart wrote:
> The md5sum "ac9a49d8..." has never been a salt LICENSE file hashsum.
> Salt_3001 verification therefore fails after fetch.
>
> Set the LICENSE file hashsum to the correct value as of salt upstream
> commit a1d07e9cc5d84895468bf360390754c4d68308d9 - which services salt
> 3001.
>
> Signed-off-by: Alex Stewart <alex.stewart@ni.com>
> ---
> meta-openstack/recipes-support/salt/salt_3001.1.bb | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta-openstack/recipes-support/salt/salt_3001.1.bb b/meta-openstack/recipes-support/salt/salt_3001.1.bb
> index 9b485d699b5e01ed287256b96e33249e98b02ae0..c789ab94c44bb6fd8713f15174b4ffa91a173e47 100644
> --- a/meta-openstack/recipes-support/salt/salt_3001.1.bb
> +++ b/meta-openstack/recipes-support/salt/salt_3001.1.bb
> @@ -1,7 +1,7 @@
> HOMEPAGE = "http://saltstack.com/"
> SECTION = "admin"
> LICENSE = "Apache-2.0"
> -LIC_FILES_CHKSUM = "file://LICENSE;md5=89aea4e17d99a7cacdbeed46a0096b10"
> +LIC_FILES_CHKSUM = "file://LICENSE;md5=ac9a49d86925151327b277d6a3999a07"
> DEPENDS = "\
> python3-msgpack \
> python3-pyyaml \
> --
> 2.32.0
>
>
>
>
prev parent reply other threads:[~2021-08-27 14:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 19:19 [meta-virtualization][m-c-s][PATCH 1/2] salt: correct LICENSE md5sum Alex Stewart
2021-08-23 19:19 ` [meta-virtualization][m-c-s][PATCH 2/2] salt: use $BPN in SRC_URI Alex Stewart
2021-08-27 14:53 ` Bruce Ashfield [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=20210827145343.GA23990@gmail.com \
--to=bruce.ashfield@gmail.com \
--cc=alex.stewart@ni.com \
--cc=meta-virtualization@lists.yoctoproject.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 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.