From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Geoff Levand <geoff@infradead.org>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/flannel: Bump to version 0.25.2
Date: Wed, 29 May 2024 20:18:52 +0200 [thread overview]
Message-ID: <ZldxjKMyzPIK1djL@landeda> (raw)
In-Reply-To: <31d643d8-4bca-4817-a6f2-a40ac0d77d37@infradead.org>
Geoff, All,
On 2024-05-29 17:58 +0900, Geoff Levand spake thusly:
> On 5/29/24 15:30, Peter Korsgaard wrote:
> >>>>>> "Geoff" == Geoff Levand <geoff@infradead.org> writes:
> > > -sha256 8406a3b2b799344197c79f96e5b39ea7b6228f0bb2cb069b5f44dce684e29b9b flannel-0.25.1-go2.tar.gz
> > > +sha256 565dedf012a358d87d6bb89a4b7118a4a7ab9a3aada9b9bf76349ca5e451d954 flannel-0.25.2-go2.tar.gz
> > Hmm, I get a different hash here?
> > ERROR: while checking hashes from package/flannel/flannel.hash
> > ERROR: flannel-0.25.2-go2.tar.gz has wrong sha256 hash:
> > ERROR: expected: 565dedf012a358d87d6bb89a4b7118a4a7ab9a3aada9b9bf76349ca5e451d954
> > ERROR: got : e181a5e4233db47b0f03718ea801274c3a6024d235ead76e974f3df4f4183de1
> I see this in the build log;
> flannel-0.25.2-go2.tar.gz: OK (sha256: 565dedf012a358d87d6bb89a4b7118a4a7ab9a3aada9b9bf76349ca5e451d954)
> >>> flannel 0.25.2 Extracting
> Maybe there was some problem with your download of flannel-0.25.2-go2.tar.gz
The issue has been identified:
- we now require tar >= 1.35 (for reproducibility of tarballs)
- we check whether the tar on the host system is suitable
- if not, then we build our own host-tar, and use that
So we should always use a valid tar: either the system one, or our own.
However (there is always a "however"), the user can set TAR in their
environment, to instruct Buildroot to use that specific tar. For
example, it is possible to do:
$ TAR=tar-1.35 make
So, when we check whether the host tar is suitable, we in fact check
that $(TAR) as provided by the user (and if not given, then we default
to looking 'tar' in PATH).
But we do not use $(TAR) from the download helper infrastructure, where
we only use 'tar'.
so, when the user has a system with an older tar in PATH, but provides a
TAR=tar-1.35 when building, then there is a discrepancy between the tar
we check, and the one we use.
Boom.
That's what happened to Peter.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-05-29 18:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 0:15 [Buildroot] [PATCH] package/flannel: Bump to version 0.25.2 Geoff Levand
2024-05-29 6:30 ` Peter Korsgaard
2024-05-29 8:58 ` Geoff Levand
2024-05-29 18:18 ` Yann E. MORIN [this message]
2024-05-30 18:17 ` Peter Korsgaard
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=ZldxjKMyzPIK1djL@landeda \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=geoff@infradead.org \
--cc=thomas.petazzoni@bootlin.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 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.