From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Joris Lijssens <joris.lijssens@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/libcoap: bump to version 4.3.4
Date: Thu, 2 Nov 2023 14:41:29 +0100 [thread overview]
Message-ID: <20231102144129.26d5ac6b@windsurf> (raw)
In-Reply-To: <20231101223719.36953-1-fontaine.fabrice@gmail.com>
On Wed, 1 Nov 2023 23:37:19 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> - Drop patch (already in version)
> - LIBCOAP_IGNORE_CVES is not needed after bump
> - Update hash of license file: LGPL-2.1 added when RIOT support with
> https://github.com/obgm/libcoap/commit/8d869fff047d34a1c825ffc1bab5d3fde28c75b7
>
> https://github.com/obgm/libcoap/blob/v4.3.4/ChangeLog
> https://github.com/obgm/libcoap/compare/v4.3.1...v4.3.4
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> ...0001-Backport-fix-for-CVE-2023-30362.patch | 59 -------------------
> package/libcoap/libcoap.hash | 4 +-
> package/libcoap/libcoap.mk | 6 +-
> 3 files changed, 3 insertions(+), 66 deletions(-)
> delete mode 100644 package/libcoap/0001-Backport-fix-for-CVE-2023-30362.patch
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-11-02 13:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 22:37 [Buildroot] [PATCH 1/1] package/libcoap: bump to version 4.3.4 Fabrice Fontaine
2023-11-02 13:41 ` 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=20231102144129.26d5ac6b@windsurf \
--to=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=joris.lijssens@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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