From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Antoine Coutant <antoine.coutant@smile.fr>,
romain.naour@smile.fr, sebastian.weyer@smile.fr,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 2/3] package/ripgrep: bump to version 14.0.3
Date: Sat, 30 Dec 2023 19:00:19 +0100 [thread overview]
Message-ID: <20231230190019.434e1b4b@windsurf> (raw)
In-Reply-To: <ZY9Ej76T9DYHuLe3@landeda>
On Fri, 29 Dec 2023 23:13:35 +0100
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> If that's so, then we have a big problem: the hashes for all the
> cargo-based packages will change, and thus it means we will have to
> name the generated archive based on the cargo version used to do the
> vendoring. That would apply to:
Note that I also encountered some hash mismatch on some Rust/Cargo
package recently, and BR was falling back to sources.buildroot.net. I
did not have the time to investigate at the time (I was looking into
another issue, and didn't want to enter an infinite recursion of
problem solving quest). And now, I don't remember with which package I
encountered this. But yes, it seems like we have a reproducibility
issue.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-12-30 18:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-28 15:26 [Buildroot] [PATCH v2 1/3] package/{rust, rust-bin}: bump to version 1.74.1 Antoine Coutant
2023-12-28 15:26 ` [Buildroot] [PATCH v2 2/3] package/ripgrep: bump to version 14.0.3 Antoine Coutant
2023-12-29 22:13 ` Yann E. MORIN
2023-12-30 18:00 ` Thomas Petazzoni via buildroot [this message]
2023-12-30 19:44 ` Yann E. MORIN
2023-12-30 22:08 ` Yann E. MORIN
2023-12-31 9:25 ` Yann E. MORIN
2023-12-31 11:01 ` Yann E. MORIN
2023-12-31 14:25 ` Yann E. MORIN
2023-12-31 14:36 ` Yann E. MORIN
2024-01-10 14:22 ` Romain Naour
2024-01-10 14:29 ` Antoine Coutant
2024-01-10 20:27 ` Yann E. MORIN
2023-12-28 15:26 ` [Buildroot] [PATCH v2 3/3] support/testing: test_rust.py: Add test to check correct vendoring Antoine Coutant
2023-12-30 18:01 ` [Buildroot] [PATCH v2 1/3] package/{rust, rust-bin}: bump to version 1.74.1 Thomas Petazzoni via buildroot
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=20231230190019.434e1b4b@windsurf \
--to=buildroot@buildroot.org \
--cc=antoine.coutant@smile.fr \
--cc=romain.naour@smile.fr \
--cc=sebastian.weyer@smile.fr \
--cc=thomas.petazzoni@bootlin.com \
--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 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.