From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: "Sven Püschel" <s.pueschel@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] libmd: version bump 1.1.0 -> 1.3.0
Date: Fri, 13 Nov 2026 09:38:44 +0100 [thread overview]
Message-ID: <20261113083844.1378258-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20261020103705.2665647-1-s.pueschel@pengutronix.de>
Thanks, applied as 56ca4e138a4a38552a72fef88f1a397aef151d64.
Michael
[sent from post-receive hook]
On Fri, 13 Nov 2026 09:38:44 +0100, Sven Püschel <s.pueschel@pengutronix.de> wrote:
> The license file changed due to year adjustments, general
> cleanup and the addition of SHA3 and SHAKE support [1].
> Latter is also licensed under the 2 clause BSD license
> (named BSD-2-clause-contributors in the COPYING file).
> Therefore no change to the license field is necessary.
>
> Also based on the configure_helper.py output added the year 2038 switch.
>
> [1] https://gitlab.freedesktop.org/libbsd/libmd/-/commit/4442c4b9528bc1f9fba2623035fe49fdaba89170
>
> Signed-off-by: Sven Püschel <s.pueschel@pengutronix.de>
> Message-Id: <20261020103705.2665647-1-s.pueschel@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/libmd.make b/rules/libmd.make
> index 1a04a5722ef7..b8393d57b25c 100644
> --- a/rules/libmd.make
> +++ b/rules/libmd.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_LIBMD) += libmd
> #
> # Paths and names
> #
> -LIBMD_VERSION := 1.1.0
> -LIBMD_SHA256 := 1bd6aa42275313af3141c7cf2e5b964e8b1fd488025caf2f971f43b00776b332
> +LIBMD_VERSION := 1.3.0
> +LIBMD_SHA256 := fc0f1eb6b6766470326f2c014693809190e67dba84274a6fbae9d4912d066706
> LIBMD := libmd-$(LIBMD_VERSION)
> LIBMD_SUFFIX := tar.xz
> LIBMD_URL := https://libbsd.freedesktop.org/releases/$(LIBMD).$(LIBMD_SUFFIX)
> @@ -23,7 +23,7 @@ LIBMD_SOURCE := $(SRCDIR)/$(LIBMD).$(LIBMD_SUFFIX)
> LIBMD_DIR := $(BUILDDIR)/$(LIBMD)
> LIBMD_LICENSE := BSD-3-Clause AND BSD-2-Clause AND ISC AND Beerware AND public_domain
> LIBMD_LICENSE_FILES := \
> - file://COPYING;md5=0436d4fb62a71f661d6e8b7812f9e1df
> + file://COPYING;md5=261bf22602270e2b29c53930d409a3ca
>
> # ----------------------------------------------------------------------------
> # Prepare
> @@ -35,7 +35,8 @@ LIBMD_LICENSE_FILES := \
> LIBMD_CONF_TOOL := autoconf
> LIBMD_CONF_OPT := \
> $(CROSS_AUTOCONF_USR) \
> - $(GLOBAL_LARGE_FILE_OPTION)
> + $(GLOBAL_LARGE_FILE_OPTION) \
> + --$(call ptx/endis, PTXDIST_Y2038)-year2038
>
> # ----------------------------------------------------------------------------
> # Target-Install
prev parent reply other threads:[~2026-11-13 8:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 10:37 [ptxdist] [PATCH] " Sven Püschel
2026-11-13 8:38 ` 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=20261113083844.1378258-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
--cc=s.pueschel@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