Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Kuhls <bernd@kuhls.net>
To: buildroot@buildroot.org
Subject: [Buildroot] [PATCH 1/1] docs/migrating.adoc: document the tarball suffix update for Cargo-fetch packages
Date: Wed, 15 Jul 2026 17:59:32 +0200	[thread overview]
Message-ID: <20260715155932.9265-1-bernd@kuhls.net> (raw)

We changed the suffix of tarballs for Cargo-fetched packages, which
affects out-of-tree packages, so it makes sense to document that in
the migration guide.

Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
---
 docs/manual/migrating.adoc | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/docs/manual/migrating.adoc b/docs/manual/migrating.adoc
index 230754be76..68f09e1bae 100644
--- a/docs/manual/migrating.adoc
+++ b/docs/manual/migrating.adoc
@@ -258,3 +258,9 @@ from +true+ to +false+, in line with upstream defaults. If you need
 +EnableNetworkConfiguration=true+ to let +iwd+ handle network
 configuration for active wifi connections, adjust +/etc/iwd/main.conf+
 in your build (see xref:rootfs-custom[] for options).
+
+Due to the update of Rust to a version greater than 1.96.1 $comment was
+added to .cargo-checksum.json to clarify that this file is not a
+security mechanism. Tarballs generated by Cargo-fetched packages have
+changed, therefore the suffix of such tarballs has been changed from
++-cargo5+ to +-cargo6+.
-- 
2.47.3

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2026-07-15 15:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-15 15:59 Bernd Kuhls [this message]
2026-07-15 19:18 ` [Buildroot] [PATCH 1/1] docs/migrating.adoc: document the tarball suffix update for Cargo-fetch packages Julien Olivain 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=20260715155932.9265-1-bernd@kuhls.net \
    --to=bernd@kuhls.net \
    --cc=buildroot@buildroot.org \
    /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