From: Christian Melki <christian.melki@t2data.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH] chrpath: Version bump. 0.16 -> 0.18
Date: Tue, 7 Jan 2025 18:42:30 +0100 [thread overview]
Message-ID: <20250107174230.1322671-1-christian.melki@t2data.com> (raw)
Minor fixes.
https://codeberg.org/pere/chrpath/src/tag/release_0.18/NEWS
* Add patch to generate configure. Seems the packaging
has left it out this time.
* Change URL to match the new release.
Signed-off-by: Christian Melki <christian.melki@t2data.com>
---
patches/chrpath-0.18/autogen.sh | 1 +
rules/host-chrpath.make | 6 +++---
2 files changed, 4 insertions(+), 3 deletions(-)
create mode 120000 patches/chrpath-0.18/autogen.sh
diff --git a/patches/chrpath-0.18/autogen.sh b/patches/chrpath-0.18/autogen.sh
new file mode 120000
index 000000000..9f8a4cb7d
--- /dev/null
+++ b/patches/chrpath-0.18/autogen.sh
@@ -0,0 +1 @@
+../autogen.sh
\ No newline at end of file
diff --git a/rules/host-chrpath.make b/rules/host-chrpath.make
index 6b7d3d0de..fe09c8979 100644
--- a/rules/host-chrpath.make
+++ b/rules/host-chrpath.make
@@ -14,12 +14,12 @@ HOST_PACKAGES-$(PTXCONF_HOST_CHRPATH) += host-chrpath
#
# Paths and names
#
-HOST_CHRPATH_VERSION := 0.16
-HOST_CHRPATH_MD5 := 2bf8d1d1ee345fc8a7915576f5649982
+HOST_CHRPATH_VERSION := 0.18
+HOST_CHRPATH_MD5 := 3220be4f47361bfd0b76e2132c0219c0
HOST_CHRPATH_SUFFIX := tar.gz
HOST_CHRPATH := chrpath-$(HOST_CHRPATH_VERSION)
HOST_CHRPATH_TARBALL := chrpath_$(HOST_CHRPATH_VERSION).orig.$(HOST_CHRPATH_SUFFIX)
-HOST_CHRPATH_URL := http://snapshot.debian.org/archive/debian/20140119T220629Z/pool/main/c/chrpath/$(HOST_CHRPATH_TARBALL)
+HOST_CHRPATH_URL := http://snapshot.debian.org/archive/debian/20250106T091447Z/pool/main/c/chrpath/$(HOST_CHRPATH_TARBALL)
HOST_CHRPATH_SOURCE := $(SRCDIR)/$(HOST_CHRPATH).$(HOST_CHRPATH_SUFFIX)
HOST_CHRPATH_DIR := $(HOST_BUILDDIR)/$(HOST_CHRPATH)
HOST_CHRPATH_LICENSE := GPL-2.0-only
--
2.34.1
reply other threads:[~2025-01-07 17:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250107174230.1322671-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