Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Matt Weber <matthew.weber@collins.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/xml-security-c: bump to version 2.0.4
Date: Mon, 24 Jan 2022 22:02:51 +0100	[thread overview]
Message-ID: <20220124220251.65336d07@windsurf> (raw)
In-Reply-To: <20220123212757.781999-1-fontaine.fabrice@gmail.com>

On Sun, 23 Jan 2022 22:27:57 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:

> Version 2.0.4 of the Apache XML Security for C++ has been released,
> correcting support for OpenSSL earlier than 1.1.
> 
> Version 2.0.3 of the Apache XML Security for C++ has been released,
> adding support for OpenSSL 3.0.0.
> 
> Drop patch (already in version) and so autoreconf
> 
> https://santuario.apache.org/cindex.html
> 
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
>  ...ariable-cache-option-for-getcwd-test.patch | 50 -------------------
>  package/xml-security-c/xml-security-c.hash    |  4 +-
>  package/xml-security-c/xml-security-c.mk      |  5 +-
>  3 files changed, 3 insertions(+), 56 deletions(-)
>  delete mode 100644 package/xml-security-c/0001-autoconf-variable-cache-option-for-getcwd-test.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

      reply	other threads:[~2022-01-24 21:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-23 21:27 [Buildroot] [PATCH 1/1] package/xml-security-c: bump to version 2.0.4 Fabrice Fontaine
2022-01-24 21:02 ` 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=20220124220251.65336d07@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.com \
    --cc=matthew.weber@collins.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