Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 v2] package/mender-update-modules: fix LICENSE hash
Date: Tue, 27 Oct 2026 13:59:41 +0100	[thread overview]
Message-ID: <auCgGxiJaYUrMKSA@windsurf> (raw)
In-Reply-To: <20261027101235.2876416-1-titouan.christophe@mind.be>

On Tue, Oct 27, 2026 at 11:12:35AM +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`. This seems to be
> the case since the introduction of mender-update-modules in Buildroot:
> the license file hasn't been updated upstream for more than 7y [1], and
> the buildroot package was introduced in May 2025 as Buildroot commit
> a474642fdcd8 ("package/mender-update-modules: new package").

Crazy that this has been incorrect from the start!

> [1] https://github.com/mendersoftware/mender-update-modules/commits/master/LICENSE
> 
> Signed-off-by: Titouan Christophe <titouan.christophe@mind.be>

I've added a Fixes: tag:

Fixes: a474642fdcd8 ("package/mender-update-modules: new package")

and applied.

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-10-27 12:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-27 10:12 [Buildroot] [PATCH v2] package/mender-update-modules: fix LICENSE hash Titouan Christophe via buildroot
2026-10-27 12:59 ` Thomas Petazzoni via buildroot [this message]
2026-10-27 14:18   ` Adam Duskett
2026-10-27 14:28     ` Titouan Christophe 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=auCgGxiJaYUrMKSA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox