From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] libpopt: Version bump. 1.18 -> 1.19
Date: Wed, 28 Sep 2022 16:28:55 +0200 [thread overview]
Message-ID: <20220928142855.3560836-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20220922131601.2871846-1-christian.melki@t2data.com>
Thanks, applied as 10b4f41510dd11d71ca2b1a999d043fddfc8563c.
Michael
[sent from post-receive hook]
On Wed, 28 Sep 2022 16:28:55 +0200, Christian Melki <christian.melki@t2data.com> wrote:
> https://github.com/rpm-software-management/popt/releases/tag/popt-1.19-release
> Mostly bugfixes.
>
> * Be explicit about new configure option, as default.
> * License file changed. Actually funny. Listed as MIT, but
> for 22 years, it went unnoticed that the actual license file was wrong.
> This is now corrected.
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20220922131601.2871846-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/libpopt.make b/rules/libpopt.make
> index 4289d45f3e36..86259fd5e9a0 100644
> --- a/rules/libpopt.make
> +++ b/rules/libpopt.make
> @@ -15,8 +15,8 @@ PACKAGES-$(PTXCONF_LIBPOPT) += libpopt
> #
> # Paths and names
> #
> -LIBPOPT_VERSION := 1.18
> -LIBPOPT_MD5 := 450f2f636e6a3aa527de803d0ae76c5a
> +LIBPOPT_VERSION := 1.19
> +LIBPOPT_MD5 := eaa2135fddb6eb03f2c87ee1823e5a78
> LIBPOPT := popt-$(LIBPOPT_VERSION)
> LIBPOPT_SUFFIX := tar.gz
> LIBPOPT_URL := \
> @@ -24,7 +24,7 @@ LIBPOPT_URL := \
> LIBPOPT_SOURCE := $(SRCDIR)/$(LIBPOPT).$(LIBPOPT_SUFFIX)
> LIBPOPT_DIR := $(BUILDDIR)/$(LIBPOPT)
> LIBPOPT_LICENSE := MIT
> -LIBPOPT_LICENSE_FILES := file://COPYING;md5=cb0613c30af2a8249b8dcc67d3edb06d
> +LIBPOPT_LICENSE_FILES := file://COPYING;md5=e0206ac9471d06667e076212db20c5f4
>
> # ----------------------------------------------------------------------------
> # Prepare
> @@ -39,7 +39,8 @@ LIBPOPT_CONF_OPT := \
> $(GLOBAL_LARGE_FILE_OPTION) \
> --disable-build-gcov \
> --$(call ptx/endis, PTXCONF_LIBPOPT_NLS)-nls \
> - --disable-rpath
> + --disable-rpath \
> + --disable-werror
>
> # ----------------------------------------------------------------------------
> # Target-Install
prev parent reply other threads:[~2022-09-28 14:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 13:16 [ptxdist] [PATCH] " Christian Melki
2022-09-28 14:28 ` Michael Olbrich [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=20220928142855.3560836-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=christian.melki@t2data.com \
--cc=ptxdist@pengutronix.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