From: "Raphaël Mélotte via buildroot" <buildroot@buildroot.org>
To: buildroot@buildroot.org
Cc: "Raphaël Mélotte" <raphael.melotte@mind.be>
Subject: [Buildroot] [PATCH 3/3] package/wmenu: update hash following Codeberg changes
Date: Thu, 20 Aug 2026 12:57:01 +0200 [thread overview]
Message-ID: <20260820105705.1502630-3-raphael.melotte@mind.be> (raw)
In-Reply-To: <20260820105705.1502630-1-raphael.melotte@mind.be>
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>
---
| 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--git a/package/wmenu/wmenu.hash b/package/wmenu/wmenu.hash
index c4941001f4..71b2ff9d37 100644
--- a/package/wmenu/wmenu.hash
+++ b/package/wmenu/wmenu.hash
@@ -1,3 +1,3 @@
# Locally computed
-sha256 4e6aea3f8975fec720f6eb87aad620d5297a8a5a137615e4cf047e95d2b9d308 0.2.0.tar.gz
+sha256 b1b593a80310085a90bd349d458ffbcfacf875d74468ae4428bdf5692a671ef9 0.2.0.tar.gz
sha256 500f0a221b2f3667676f6a084fb4e92ba4f74d09f45bc492e55aec4dd296bff2 LICENSE
--
2.54.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-08-20 10:57 UTC|newest]
Thread overview: 3+ 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-08-20 10:57 ` Raphaël Mélotte via buildroot [this message]
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=20260820105705.1502630-3-raphael.melotte@mind.be \
--to=buildroot@buildroot.org \
--cc=raphael.melotte@mind.be \
/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