From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: update: ffmpeg to 5.1.2 [Draft]
Date: Sun, 05 Mar 2023 22:39:04 +0100 [thread overview]
Message-ID: <20230305213904._oKmPkgsdiW2m_p7B0rEcph1LrrYGhAXHSZa7T7L3OE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41470@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 818 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/pull/41470#issuecomment-1455213426
Comment:
This PR is failing all checks, is missing a lot of revbumps and didn't get any attention from the author since it was opened. If anyone is interested in continuing this work, please open a new PR and base it on @tibequadorian's work linked above which was way more complete and wasn't just a simple revbump (which this update definitely isn't).
It would be acceptable to have a ffmpeg4 package and switch all packages that don't work with ffmpeg 5 to it if:
* there are important packages that don't work with ffmpeg 5 and can not be made to work with ffmpeg 5 reliably
* at the same time, ffmpeg is updated to v5 and all packages that work with it get rebuilt for ffmpeg (5)
next prev parent reply other threads:[~2023-03-05 21:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 12:27 [PR PATCH] " absrd
2023-01-05 23:14 ` Danoloan10
2023-01-06 8:57 ` icp1994
2023-01-06 16:44 ` Danoloan10
2023-01-06 19:23 ` Johnnynator
2023-01-31 17:12 ` motorto
2023-03-05 21:08 ` milgra
2023-03-05 21:34 ` paper42
2023-03-05 21:39 ` paper42 [this message]
2023-03-19 15:43 ` zlice
2023-03-19 16:16 ` icp1994
2023-03-19 16:23 ` zlice
2023-03-19 16:25 ` zlice
2023-03-19 16:32 ` icp1994
2023-03-19 21:07 ` paper42
2023-03-19 21:07 ` paper42
2023-03-19 23:11 ` zlice
2023-06-18 2:07 ` github-actions
2023-07-02 2:10 ` [PR PATCH] [Closed]: " github-actions
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=20230305213904._oKmPkgsdiW2m_p7B0rEcph1LrrYGhAXHSZa7T7L3OE@z \
--to=paper42@users.noreply.github.com \
--cc=ml@inbox.vuxu.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
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;
as well as URLs for NNTP newsgroup(s).