From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] openssh: Non-change version bump. 10.0p1 -> 10.0p2
Date: Thu, 12 Jun 2025 21:31:53 +0200 [thread overview]
Message-ID: <20250612193153.2320519-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20250525170439.2084354-1-christian.melki@t2data.com>
Thanks, applied as ac6e9a2d488356f336dabe2aaa5542fffd82d252.
Michael
[sent from post-receive hook]
On Thu, 12 Jun 2025 21:31:53 +0200, Christian Melki <christian.melki@t2data.com> wrote:
> 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>
> Message-Id: <20250525170439.2084354-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/openssh.make b/rules/openssh.make
> index 1c4b74455d10..4eb9448fd28d 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
prev parent reply other threads:[~2025-06-12 19:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-25 17:04 [ptxdist] [PATCH] " Christian Melki
2025-06-12 19:31 ` 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=20250612193153.2320519-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