From: Peter Korsgaard <peter@korsgaard.com>
To: Yann E. MORIN <yann.morin.1998@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [git commit] package/rockchip-mali: fix hash of generated archive
Date: Fri, 13 Oct 2023 12:23:10 +0200 [thread overview]
Message-ID: <87v8ba6ctt.fsf@48ers.dk> (raw)
In-Reply-To: <20230930221348.6363783D49@busybox.osuosl.org> (Yann E. MORIN's message of "Sun, 1 Oct 2023 00:13:20 +0200")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> commit: https://git.buildroot.net/buildroot/commit/?id=f7f2de3da7e1a5af4e2773ff6bb9e528159be7d3
> branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master
> The "official" repository we used to reference disapeared quite some
> time ago, so in commit 8c25838b53e6 (package/rockchip-mali: fix build
> failure due to missing URL) we switched to using a mirror.
> The tarballs generated on the Github side have a top-level directory
> that is named "repo-name-HASH", so when we switched to a repository
> named "libmali" to one named "mirrors", the content of the generated
> tarball changed, even though the content of the files did not.
> We can't just change the hash to the new value, or that would conflict
> with thecopy on s.b.o and older versions of Buildroot.
> So, we drop one cahr from the commit hash, which eans the tarball name
> changes, and thus we can calculate a new hash for that tarball, and
> there will be no conflict with any existing tarball on s.b.o.
> Reported-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
Committed to 2023.02.x and 2023.08.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-10-13 10:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-30 22:13 [Buildroot] [git commit] package/rockchip-mali: fix hash of generated archive Yann E. MORIN
2023-10-13 10:23 ` Peter Korsgaard [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=87v8ba6ctt.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=yann.morin.1998@free.fr \
/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