From: Christian Melki <christian.melki@t2data.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH] openssh: Non-change version bump. 10.0p1 -> 10.0p2
Date: Sun, 25 May 2025 19:04:39 +0200 [thread overview]
Message-ID: <20250525170439.2084354-1-christian.melki@t2data.com> (raw)
Apparently the p1 release name was a mistake and name is changed to p2.
Although the same tarball exists as p1 (no hash change), change
the tarball name to p2 to remove any chance of confusion.
I didn't chatch this mistake at the time of the last version bump,
so lets fix this now.
https://seclists.org/oss-sec/2025/q2/35
Signed-off-by: Christian Melki <christian.melki@t2data.com>
---
rules/openssh.make | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/rules/openssh.make b/rules/openssh.make
index 941aacde8..0fd37b51b 100644
--- a/rules/openssh.make
+++ b/rules/openssh.make
@@ -15,7 +15,7 @@ PACKAGES-$(PTXCONF_OPENSSH) += openssh
#
# Paths and names
#
-OPENSSH_VERSION := 10.0p1
+OPENSSH_VERSION := 10.0p2
OPENSSH_MD5 := 689148621a2eaa734497b12bed1c5202
OPENSSH := openssh-$(OPENSSH_VERSION)
OPENSSH_SUFFIX := tar.gz
--
2.34.1
next reply other threads:[~2025-05-25 17:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-25 17:04 Christian Melki [this message]
2025-06-12 19:31 ` [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=20250525170439.2084354-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