From: Christian Melki <christian.melki@t2data.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH] libslirp: Version bump. 4.8.0 -> 4.9.0
Date: Wed, 12 Feb 2025 20:55:54 +0100 [thread overview]
Message-ID: <20250212195554.2795439-1-christian.melki@t2data.com> (raw)
Corrected a big mistake in the rules file I didn't previously notice.
It was pointing to a static 4.7.0 url, despite being 4.8.0 in the version.
Correct it. Technically this bumps it through two releases.
https://gitlab.freedesktop.org/slirp/libslirp/-/releases/v4.9.0
https://gitlab.freedesktop.org/slirp/libslirp/-/releases/v4.8.0
Signed-off-by: Christian Melki <christian.melki@t2data.com>
---
rules/libslirp.make | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/rules/libslirp.make b/rules/libslirp.make
index 4f0832ddc..1db03cee7 100644
--- a/rules/libslirp.make
+++ b/rules/libslirp.make
@@ -14,11 +14,11 @@ PACKAGES-$(PTXCONF_LIBSLIRP) += libslirp
#
# Paths and names
#
-LIBSLIRP_VERSION := 4.8.0
-LIBSLIRP_MD5 := 4f701d26a46fe9bf6db302aef6ed467f
+LIBSLIRP_VERSION := 4.9.0
+LIBSLIRP_MD5 := 31dbbfe667297a5931e56ba78f69c64f
LIBSLIRP := libslirp-v$(LIBSLIRP_VERSION)
LIBSLIRP_SUFFIX := tar.bz2
-LIBSLIRP_URL := https://gitlab.freedesktop.org/slirp/libslirp/-/archive/v4.7.0/$(LIBSLIRP).$(LIBSLIRP_SUFFIX)
+LIBSLIRP_URL := https://gitlab.freedesktop.org/slirp/libslirp/-/archive/v$(LIBSLIRP_VERSION)/$(LIBSLIRP).$(LIBSLIRP_SUFFIX)
LIBSLIRP_SOURCE := $(SRCDIR)/$(LIBSLIRP).$(LIBSLIRP_SUFFIX)
LIBSLIRP_DIR := $(BUILDDIR)/$(LIBSLIRP)
LIBSLIRP_LICENSE := BSD-3-Clause AND MIT
--
2.34.1
next reply other threads:[~2025-02-12 19:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 19:55 Christian Melki [this message]
2025-02-17 7:24 ` [ptxdist] [APPLIED] " Michael Olbrich
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=20250212195554.2795439-1-christian.melki@t2data.com \
--to=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