From: Baruch Siach via buildroot <buildroot@buildroot.org>
To: Christian Stewart via buildroot <buildroot@buildroot.org>
Cc: Christian Stewart <christian@aperture.us>,
Julien Olivain <ju.o@free.fr>,
Vincent Fazio <vfazio@xes-inc.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH v1 1/1] package/mmc-utils: fix hash mismatch for readme file
Date: Wed, 11 Dec 2024 08:50:58 +0200 [thread overview]
Message-ID: <878qsm7lwt.fsf@tarshish> (raw)
In-Reply-To: <20241211004940.14204-1-christian@aperture.us> (Christian Stewart via buildroot's message of "Tue, 10 Dec 2024 16:49:40 -0800")
Hi Christian,
On Tue, Dec 10 2024, Christian Stewart via buildroot wrote:
> Commit b03dc5: package/mmc-utils: bump to 523d8f3cfb21
>
> The README hash changed causing a build failure:
>
> https://github.com/skiffos/SkiffOS/actions/runs/12266361526/job/34224344838#step:8:60617
>
> Update the hash for the README.md file to fix the issue.
The patch updates README hash. Is that a typo?
baruch
> Reproduce: make mmc-utils-legal-info
>
> Signed-off-by: Christian Stewart <christian@aperture.us>
> ---
> package/mmc-utils/mmc-utils.hash | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/package/mmc-utils/mmc-utils.hash b/package/mmc-utils/mmc-utils.hash
> index 48bfd7bc04..3da95d8070 100644
> --- a/package/mmc-utils/mmc-utils.hash
> +++ b/package/mmc-utils/mmc-utils.hash
> @@ -1,3 +1,3 @@
> # Locally computed
> sha256 1ae5706ce56bfedda94a01e87c5151ac750fb849987aeb74ff89d70f43556131
> mmc-utils-523d8f3cfb219d800f45860892e742e3a355f1bb-git4.tar.gz
> -sha256 4207d81122a02555f78c5a11b61c83a331ee03dc933e1ef9dd932ef9b434d12d README
> +sha256 49cd65f67b516078ff7e0dbe639972dad21ed3858246e3969fc8a8fc2a4dca66 README
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-12-11 6:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 0:49 [Buildroot] [PATCH v1 1/1] package/mmc-utils: fix hash mismatch for readme file Christian Stewart via buildroot
2024-12-11 6:50 ` Baruch Siach via buildroot [this message]
2024-12-11 7:39 ` Christian Stewart via buildroot
2024-12-12 19:49 ` Peter Korsgaard
2024-12-11 8:11 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2024-12-11 13:33 Vincent Fazio
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=878qsm7lwt.fsf@tarshish \
--to=buildroot@buildroot.org \
--cc=baruch@tkos.co.il \
--cc=christian@aperture.us \
--cc=ju.o@free.fr \
--cc=thomas.petazzoni@bootlin.com \
--cc=vfazio@xes-inc.com \
/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