From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Titouan Christophe <titouan.christophe@mind.be>
Cc: buildroot@buildroot.org,
Adam Duskett <adam.duskett@amarulasolutions.com>
Subject: Re: [Buildroot] [PATCH] package/mender-update-modules: fix LICENSE hash
Date: Mon, 26 Oct 2026 22:16:12 +0100 [thread overview]
Message-ID: <at_C_0FxgMSAQzDs@windsurf> (raw)
In-Reply-To: <20261026111813.2325455-1-titouan.christophe@mind.be>
On Mon, Oct 26, 2026 at 12:18:13PM +0100, Titouan Christophe via buildroot wrote:
> The SHA256 sum of the LICENSE file was incorrect, leading to a failure
> when running `make mender-update-modules-legal-info`
Which Buildroot commit broke this?
We have LTS maintainers who need to know whether this will require a
backport to a LTS branch you know :-)
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
prev parent reply other threads:[~2026-10-26 21:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 11:18 [Buildroot] [PATCH] package/mender-update-modules: fix LICENSE hash Titouan Christophe via buildroot
2026-10-26 21:16 ` Thomas Petazzoni 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=at_C_0FxgMSAQzDs@windsurf \
--to=buildroot@buildroot.org \
--cc=adam.duskett@amarulasolutions.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=titouan.christophe@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 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.