From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] web: move 5.0 to olddownloads
Date: Tue, 31 Oct 2023 01:06:07 +0100
Message-ID: <20231031000607.GO3543730@pb2> (raw)
In-Reply-To: <0101018b7dc9deae-1c34bcc6-35b6-4331-96f9-5cdc21c0133b-000000@us-west-2.amazonses.com>
[-- Attachment #1.1: Type: text/plain, Size: 1189 bytes --]
On Sun, Oct 29, 2023 at 11:34:23PM +0000, Cosmin Stejerean via ffmpeg-devel wrote:
>
>
> > On Oct 20, 2023, at 9:01 AM, Michael Niedermayer <michael@niedermayer.cc> wrote:
> >
> > our downstream list shows no maintained users of that release
> > https://trac.ffmpeg.org/wiki/Downstreams
>
> I was trying to track down the status of OpenMandriva Lx 3 because it's listed as a downstream for ffmpeg 4.0. While doing this I noticed that Lx 3 is EOL as of 2019-07-16. The current active version of OpenMandriva is Lx 4.3, and it seems to be packaging ffmpeg 5.0 based on https://openmandriva.pkgs.org/4.3/openmandriva-main-release-x86_64/ffmpeg-5.0-1-omv4050.x86_64.rpm.html
>
> I'm not directly familiar with OpenMandriva I was just chasing up the 4.0 relationship. I updated the wiki based on this information but it would be good for someone familiar with OpenMandriva to confirm. Based on that it might make sense to keep 5.0 and consider moving 4.0 to old downloads.
i agree
thx for checking this
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
No great genius has ever existed without some touch of madness. -- Aristotle
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
prev parent reply other threads:[~2023-10-31 0:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 16:01 Michael Niedermayer
2023-10-29 0:29 ` Michael Niedermayer
[not found] ` <B6CC8AB9-C11C-4A78-9EB8-18571CF2FBA6@cosmin.at>
2023-10-29 23:34 ` Cosmin Stejerean via ffmpeg-devel
2023-10-31 0:06 ` Michael Niedermayer [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=20231031000607.GO3543730@pb2 \
--to=michael@niedermayer.cc \
--cc=ffmpeg-devel@ffmpeg.org \
/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
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git