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, Bernd Kuhls <bernd@kuhls.net>,
	 Mahyar Koshkouei <mahyar.koshkouei@gmail.com>
Subject: Re: [Buildroot] [PATCH] package/ffmpeg: fix hash for LGPLv2.1 license
Date: Mon, 19 Oct 2026 18:58:00 +0200	[thread overview]
Message-ID: <atZMFLJ5dncS58_w@windsurf> (raw)
In-Reply-To: <20261019153216.917663-1-titouan.christophe@mind.be>

On Mon, Oct 19, 2026 at 05:32:16PM +0200, Titouan Christophe via buildroot wrote:
> The LGPL v2.1 license file was edit in upstream commit 4225417da2 [1],
> which is included in ffmpeg 7.0, and Buildroot commit b68bde5643 [2]
> bumped to that version, which made ffmpeg-legal-info fail.
> 
> Fixes: b68bde564339e96397929b45c04d137bb65df43e
> 
> [1] 4225417da2 ("all: apply linter fixes")
>     https://github.com/FFmpeg/FFmpeg/commit/4225417da25e45ec807d44430fd8cc004402df02
> [2] b68bde5643 ("package/ffmpeg: bump version to 7.0.3")
>     https://gitlab.com/buildroot.org/buildroot/-/commit/b68bde564339e96397929b45c04d137bb65df43e
> 
> Signed-off-by: Titouan Christophe <titouan.christophe@mind.be>

Applied to master, thanks!

Best regards,

Thomas Petazzoni
-- 
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-19 16:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-19 15:32 [Buildroot] [PATCH] package/ffmpeg: fix hash for LGPLv2.1 license Titouan Christophe via buildroot
2026-10-19 16:58 ` 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=atZMFLJ5dncS58_w@windsurf \
    --to=buildroot@buildroot.org \
    --cc=bernd@kuhls.net \
    --cc=mahyar.koshkouei@gmail.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