From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] libconfig: Update to 1.7.3
Date: Mon, 19 Dec 2022 12:36:39 +0000 [thread overview]
Message-ID: <1E622AC4-9A18-4D5E-BE76-75F75036432A@ipfire.org> (raw)
In-Reply-To: <20221218153023.3602050-1-matthias.fischer@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 3026 bytes --]
Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>
> On 18 Dec 2022, at 15:30, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>
> ...it just came my way...
>
> For details see:
> https://github.com/hyperrealm/libconfig/releases/tag/v1.7.3
>
> This release includes some bugfixes and enhancements.
>
> Fixed a memory access violation bug in config_clear()
> Various fixes to CMake and Visual Studio build files
> Added a Setting::isString() method
> Fixed a bug in config_setting_lookup() where the setting itself
> (instead of NULL) would be returned if the path was not found.
> Renamed all remaining internal methods that lacked a 'libconfig_'
> prefix.
>
> Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
> ---
> config/rootfiles/common/libconfig | 4 ++--
> lfs/libconfig | 6 +++---
> 2 files changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/config/rootfiles/common/libconfig b/config/rootfiles/common/libconfig
> index 633e1baf9..6c1e245ca 100644
> --- a/config/rootfiles/common/libconfig
> +++ b/config/rootfiles/common/libconfig
> @@ -9,12 +9,12 @@
> #usr/lib/libconfig++.la
> #usr/lib/libconfig++.so
> usr/lib/libconfig++.so.11
> -usr/lib/libconfig++.so.11.0.2
> +usr/lib/libconfig++.so.11.1.0
> #usr/lib/libconfig.a
> #usr/lib/libconfig.la
> #usr/lib/libconfig.so
> usr/lib/libconfig.so.11
> -usr/lib/libconfig.so.11.0.2
> +usr/lib/libconfig.so.11.1.0
> #usr/lib/pkgconfig/libconfig++.pc
> #usr/lib/pkgconfig/libconfig.pc
> #usr/share/info/libconfig.info
> diff --git a/lfs/libconfig b/lfs/libconfig
> index 58dbd8bff..4a34a878e 100644
> --- a/lfs/libconfig
> +++ b/lfs/libconfig
> @@ -1,7 +1,7 @@
> ###############################################################################
> # #
> # IPFire.org - A linux based firewall #
> -# Copyright (C) 2007-2018 IPFire Team <info(a)ipfire.org> #
> +# Copyright (C) 2007-2022 IPFire Team <info(a)ipfire.org> #
> # #
> # This program is free software: you can redistribute it and/or modify #
> # it under the terms of the GNU General Public License as published by #
> @@ -24,7 +24,7 @@
>
> include Config
>
> -VER = 1.7.2
> +VER = 1.7.3
>
> THISAPP = libconfig-$(VER)
> DL_FILE = $(THISAPP).tar.gz
> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
>
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>
> -$(DL_FILE)_BLAKE2 = 1b8bc54857feff506d5cd62312a35f0f8a123380567881bdb8241f2232c5281399e4283687a3254b8f43a92b8f7d5ff3f72ec4fd875bf1b9d5d6c7703014cc3c
> +$(DL_FILE)_BLAKE2 = 05d43022a937ed5ba35120170eca506051310cd7386b0a6a6c2f30186a079a02803c3d7ecb8dd49b50b5a706b282704605c250a306ada76b5241788eb1c575e6
>
> install : $(TARGET)
>
> --
> 2.34.1
>
prev parent reply other threads:[~2022-12-19 12:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-18 15:30 Matthias Fischer
2022-12-19 12:36 ` Michael Tremer [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=1E622AC4-9A18-4D5E-BE76-75F75036432A@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/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