All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Raphaël Mélotte" <raphael.melotte@mind.be>
Cc: buildroot@buildroot.org, Julien Olivain <ju.o@free.fr>,
	arnout@rnout.be, romain.naour@smile.fr,
	Fiona Klute <fiona.klute@gmx.de>, Marcus Hoffmann <bubu@bubu1.eu>
Subject: Re: [Buildroot] [PATCH 2/3] package/gumbo-parser: update hash following Codeberg changes
Date: Wed, 16 Sep 2026 23:37:23 +0200	[thread overview]
Message-ID: <aqsLoHzcU6UWyYGg@windsurf> (raw)
In-Reply-To: <20260820105705.1502630-2-raphael.melotte@mind.be>

Hello,

Adding a number of other Buildroot maintainers in Cc.

On Thu, Aug 20, 2026 at 12:57:00PM +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]).
> 
> Since it only affects a small number of packages for us (3 on master)
> and the upstream discussion seems to consider it a "one time change",
> just update the hash to match the new one.
> 
> [1]: https://codeberg.org/Codeberg/Community/issues/2861
> 
> Signed-off-by: Raphaël Mélotte <raphael.melotte@mind.be>
> ---
>  package/gumbo-parser/gumbo-parser.hash | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/package/gumbo-parser/gumbo-parser.hash b/package/gumbo-parser/gumbo-parser.hash
> index b8809d4db9..8e0dd91629 100644
> --- a/package/gumbo-parser/gumbo-parser.hash
> +++ b/package/gumbo-parser/gumbo-parser.hash
> @@ -1,5 +1,5 @@
>  # Locally computed:
> -sha256  dbdc159dc8e5c6f3f254e50bce689dd9e439064ff06c165d5653410a5714ab66  0.13.2.tar.gz
> +sha256  90bea83283760339da194fb90112a532854c13cd1eabdabc7ef7a4dede1dbc9d  0.13.2.tar.gz

Unfortunately I don't think we can do that. sources.buildroot.net has
most likely cached the previous version of the tarball.

Has this package published a new release so that we can do the bump +
hash chance at the same time?

Otherwise, is there a trick we could use to generate a different
filename?

Same applies to PATCH 3/3 in your series.

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

  reply	other threads:[~2026-09-16 21:37 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 [this message]
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 ` [Buildroot] [PATCH 1/3] package/fcft: use release tarball instead of archive Thomas Petazzoni via buildroot
2026-09-25 14:43 ` 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=aqsLoHzcU6UWyYGg@windsurf \
    --to=buildroot@buildroot.org \
    --cc=arnout@rnout.be \
    --cc=bubu@bubu1.eu \
    --cc=fiona.klute@gmx.de \
    --cc=ju.o@free.fr \
    --cc=raphael.melotte@mind.be \
    --cc=romain.naour@smile.fr \
    --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.