From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: "Sven Püschel" <s.pueschel@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] rtmpdump: version bump 2021-02-19-gf1b83c10d8be -> 2024-03-01-g6f6bb1353fc8
Date: Sun, 26 Oct 2025 21:33:03 +0100 [thread overview]
Message-ID: <20251026203303.981051-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20251024215331.1696508-1-s.pueschel@pengutronix.de>
Thanks, applied as bffa011046b9e05992baf8374e34118b31680a49.
Michael
[sent from post-receive hook]
On Sun, 26 Oct 2025 21:33:03 +0100, Sven Püschel <s.pueschel@pengutronix.de> wrote:
> The double md5 sum was a result from a URL change without a new version.
> Therefore two md5 sums were valid ones to keep the cached downloads
> valid. As we now update the version, we don't have existing versions
> in the cache and thereore can only use the md5 for the current URL.
>
> Signed-off-by: Sven Püschel <s.pueschel@pengutronix.de>
> Message-Id: <20251024215331.1696508-1-s.pueschel@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/rtmpdump.make b/rules/rtmpdump.make
> index 81127c23f61b..f70ca734ba44 100644
> --- a/rules/rtmpdump.make
> +++ b/rules/rtmpdump.make
> @@ -15,8 +15,8 @@ PACKAGES-$(PTXCONF_RTMPDUMP) += rtmpdump
> # Paths and names
> #
> # No tags: use a fake descriptive commit-ish to include the date
> -RTMPDUMP_VERSION := 2021-02-19-gf1b83c10d8be
> -RTMPDUMP_MD5 := 33390d59c4eac5ae34ac155804d44fb6 b0f9380fc56d42e5a12094c467188de9
> +RTMPDUMP_VERSION := 2024-03-01-g6f6bb1353fc8
> +RTMPDUMP_MD5 := 0e47613afcf77bf039fe6761f7b6c1f6
> RTMPDUMP := rtmpdump-$(RTMPDUMP_VERSION)
> RTMPDUMP_SUFFIX := tar.gz
> RTMPDUMP_URL := git+https://git.ffmpeg.org/rtmpdump.git;tag=$(RTMPDUMP_VERSION)
prev parent reply other threads:[~2025-10-26 20:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-24 21:52 [ptxdist] [PATCH v2] " Sven Püschel
2025-10-26 20:33 ` 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=20251026203303.981051-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
--cc=s.pueschel@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