From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] bash: Hash for tarball 5.3 changed upstream.
Date: Fri, 29 Aug 2025 11:46:15 +0200 [thread overview]
Message-ID: <20250829094615.2619157-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20250804170353.2121549-1-christian.melki@t2data.com>
Thanks, applied as bab62913bfb3b6c0a169b68b8d35289bba0e9e96.
Michael
[sent from post-receive hook]
On Fri, 29 Aug 2025 11:46:15 +0200, Christian Melki <christian.melki@t2data.com> wrote:
> Minor difference. Unknown why it needed a new tarball.
>
> $ diff -urN bash-5.3.old bash-5.3
> Binary files bash-5.3.old/po/ka.gmo and bash-5.3/po/ka.gmo differ
> diff -urN bash-5.3.old/po/stamp-po bash-5.3/po/stamp-po
> --- bash-5.3.old/po/stamp-po 1970-01-01 01:00:00.000000000 +0100
> +++ bash-5.3/po/stamp-po 2025-07-30 15:27:52.000000000 +0200
> @@ -0,0 +1 @@
> +timestamp
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20250804170353.2121549-1-christian.melki@t2data.com>
> [mol: keep the old hash to avoid breaking already downloaded archives]
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/bash.make b/rules/bash.make
> index c727c61a0238..bf7511720a4c 100644
> --- a/rules/bash.make
> +++ b/rules/bash.make
> @@ -14,7 +14,7 @@ PACKAGES-$(PTXCONF_BASH) += bash
> # Paths and names
> #
> BASH_VERSION := 5.3
> -BASH_MD5 := 4c7fb7d82586f93ab1d833ef20378ee8
> +BASH_MD5 := 977c8c0c5ae6309191e7768e28ebc951 4c7fb7d82586f93ab1d833ef20378ee8
> BASH := bash-$(BASH_VERSION)
> BASH_SUFFIX := tar.gz
> BASH_URL := $(call ptx/mirror, GNU, bash/$(BASH).$(BASH_SUFFIX))
prev parent reply other threads:[~2025-08-29 9:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-04 17:03 [ptxdist] [PATCH] " Christian Melki
2025-08-29 9:46 ` 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=20250829094615.2619157-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