From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Raphaël Mélotte" <raphael.melotte@mind.be>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/3] package/fcft: use release tarball instead of archive
Date: Wed, 16 Sep 2026 23:35:17 +0200 [thread overview]
Message-ID: <aqsLfxHIUxIthJ4W@windsurf> (raw)
In-Reply-To: <20260820105705.1502630-1-raphael.melotte@mind.be>
On Thu, Aug 20, 2026 at 12:56:59PM +0200, Raphaël Mélotte via buildroot wrote:
> Codeberg has changed the way it generate hashes for at least some of
> the generated tarballs (see [1]).
>
> This change affects tarballs generated by Codeberg, but not release
> artifacts.
> fcft turns out to have a proper release available, so use it.
>
> [1]: https://codeberg.org/Codeberg/Community/issues/2861
>
> Signed-off-by: Raphaël Mélotte <raphael.melotte@mind.be>
Applied, after adding a Fixes: tag pointing to the autobuilder issue
being fixed. Thanks!
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:[~2026-09-16 21:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 10:56 [Buildroot] [PATCH 1/3] package/fcft: use release tarball instead of archive Raphaël Mélotte via buildroot
2026-08-20 10:57 ` [Buildroot] [PATCH 2/3] package/gumbo-parser: update hash following Codeberg changes Raphaël Mélotte via buildroot
2026-09-16 21:37 ` Thomas Petazzoni via buildroot
2026-09-17 6:50 ` Peter Korsgaard
2026-09-17 7:22 ` Thomas Petazzoni via buildroot
2026-08-20 10:57 ` [Buildroot] [PATCH 3/3] package/wmenu: " Raphaël Mélotte via buildroot
2026-09-16 21:35 ` Thomas Petazzoni via buildroot [this message]
2026-09-25 14:43 ` [Buildroot] [PATCH 1/3] package/fcft: use release tarball instead of archive Raphaël Mélotte 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=aqsLfxHIUxIthJ4W@windsurf \
--to=buildroot@buildroot.org \
--cc=raphael.melotte@mind.be \
--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.