From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Michael Fischer <mf@go-sys.de>
Cc: buildroot@busybox.net
Subject: Re: [Buildroot] [PATCH 1/1] package/sdl2_image: bump version to 2.6.2
Date: Sat, 17 Sep 2022 22:40:28 +0200 [thread overview]
Message-ID: <20220917224028.51d3c07a@windsurf> (raw)
In-Reply-To: <20220822080923.31060-1-mf@go-sys.de>
On Mon, 22 Aug 2022 10:09:23 +0200
Michael Fischer <mf@go-sys.de> wrote:
> Fixed a number of security issues
As discussed, I dropped this part from the commit log.
> -sha256 bdd5f6e026682f7d7e1be0b6051b209da2f402a2dd8bd1c4bd9c25ad263108d0 SDL2_image-2.0.5.tar.gz
> -sha256 45079362e2230154205413a6940544ca94e3479ccf76205c71c4f542a6815d25 COPYING.txt
> +# Locally calculated after checking https://www.libsdl.org/projects/SDL_image/release/SDL2_image-2.6.2.tar.gz.sig
> +sha256 48355fb4d8d00bac639cd1c4f4a7661c4afef2c212af60b340e06b7059814777 SDL2_image-2.6.2.tar.gz
> +sha256 28aabfed22b3cb0b7e23ef40385e4f66297c960082f029c96d073cc1d4e008d5 LICENSE.txt
So indeed, COPYING.txt is gone, and LICENSE.txt is now there, but you
had forgotten to update the SDL2_IMAGE_LICENSE_FILES variable, causing
a build failure when doing "make legal-info".
I fixed both aspects, and applied to master. 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:[~2022-09-17 20:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 8:09 [Buildroot] [PATCH 1/1] package/sdl2_image: bump version to 2.6.2 Michael Fischer
2022-08-23 19:35 ` Thomas Petazzoni via buildroot
2022-08-24 7:46 ` Michael Fischer
2022-09-17 20:40 ` Thomas Petazzoni [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=20220917224028.51d3c07a@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
--cc=mf@go-sys.de \
/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