From: Danilo Bargen <mail@dbrgn.ch>
To: james.hilliard1@gmail.com
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] Hash verification from GitHub
Date: Sun, 16 Jan 2022 23:37:58 +0100 [thread overview]
Message-ID: <20220116233758.59918490@c3po> (raw)
In-Reply-To: <CADvTj4qFSfOYQ+AkOsQyGgNbuRROEmgx1giiKGaJn2jRVyhsOw@mail.gmail.com>
Hello James
> Just use the hash buildroot generated for you, it should be correct.
> (...)
> Yeah, it's not going to match since buildroot is doing stuff like
> vendoring the cargo deps before generating the tarball
Ahh, that explains it. Does this mean that for Cargo based packages, it
will always be TOFU and checksums provided by the project / maintainer
cannot be used (because they will mismatch)?
Danilo
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-01-16 22:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-16 22:04 [Buildroot] Hash verification from GitHub Danilo Bargen
2022-01-16 22:14 ` James Hilliard
2022-01-16 22:37 ` Danilo Bargen [this message]
2022-01-16 22:51 ` James Hilliard
2022-01-17 10:17 ` Yann E. MORIN
2022-01-17 10:24 ` Danilo Bargen
2022-01-17 10:32 ` Yann E. MORIN
2022-01-17 15:54 ` Yann E. MORIN
2022-01-17 16:06 ` Yann E. MORIN
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=20220116233758.59918490@c3po \
--to=mail@dbrgn.ch \
--cc=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.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