From: Roland Hieber <rhi@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: distrokit@pengutronix.de
Subject: Re: [DistroKit] [PATCH] tf-a: add current hash of v2.12 archive from Github
Date: Tue, 7 Jan 2025 14:45:59 +0100 [thread overview]
Message-ID: <20250107134559.usqg5da74op7b645@pengutronix.de> (raw)
In-Reply-To: <d8e6e46a-72c9-4f6b-99ae-3d264dc7843e@pengutronix.de>
On Tue, Jan 07, 2025 at 12:30:47PM +0100, Ahmad Fatoum wrote:
> On 07.01.25 12:19, Roland Hieber wrote:
> > On Tue, Dec 17, 2024 at 09:25:37AM +0100, Ahmad Fatoum wrote:
> >> Downloading the current release manually with:
> >>
> >> curl -L 'https://github.com/ARM-software/arm-trusted-firmware/archive/refs/tags/v2.12.tar.gz' | md5sum
> >>
> >> confirms that the hash has changed:
> >>
> >> 5b90a1c21210702e64234a2beb79f23a -
> >>
> >> I am unsure why, but to fix build breakage, let's list both hashes as
> >> after extraction of both archives, the contents were found to be
> >> completely identical.
> >
> > Have you tried diffoscope? I don't have the old tarball, but sometimes the date
> > in the tar header differs when archives are re-packed by git.
>
> Good idea. I was lucky and still had the old tarball lying around.
>
> The difference is that the old tarball had a top-level directory
> named trusted-firmware-a-2.12 and the old one calls it
> arm-trusted-firmware-2.12.
>
> I am not sure what caused this rename, but apparently PTXdist
> doesn't mind what the top-level directory is called when extracting.
Ah! git-archive is smart and sets the date in the tarball header to the date of
the commitish from which it builds the tarball, and thus produces reproducable
tarballs. But it takes the first folder part from the name of the git
repository, and in DistroKit commit 3e11c53d98c0b (2024-04-24, "tf-a: Change
download URL") the download URL was changed from
"https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git" to the current
"https://github.com/ARM-software/arm-trusted-firmware/", which changed that
name.
PTXdist doesn't care as it creates the source folder with the name $(TF_A_DIR),
and extracts the tarball inside it by skipping the first folder part (tar's
--strip-components parameter, which is set to $(TF_A_STRIP_LEVEL), which
defaults to 1).
- Roland
--
Roland Hieber, Pengutronix e.K. | rhi@pengutronix.de |
Steuerwalder Str. 21 | https://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2025-01-07 13:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 8:25 Ahmad Fatoum
2024-12-17 8:33 ` Robert Schwebel
2025-01-07 11:19 ` Roland Hieber
2025-01-07 11:30 ` Ahmad Fatoum
2025-01-07 13:45 ` Roland Hieber [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=20250107134559.usqg5da74op7b645@pengutronix.de \
--to=rhi@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=distrokit@pengutronix.de \
/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