From: Ionen Wolkens <ionen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [PATCH] ffmpeg-compat.eclass: new eclass
Date: Tue, 11 Mar 2025 01:14:29 -0400 [thread overview]
Message-ID: <Z8_GtbNlwyfAEra2@eversor> (raw)
In-Reply-To: <pan$3c5b4$22e4ff72$9366dbd4$8be0c105@cox.net>
[-- Attachment #1: Type: text/plain, Size: 1656 bytes --]
On Tue, Mar 11, 2025 at 04:37:50AM -0000, Duncan wrote:
> Ionen Wolkens posted on Sun, 9 Mar 2025 15:34:51 -0400 as excerpted:
>
> > On Sat, Mar 08, 2025 at 10:34:31PM -0500, Ionen Wolkens wrote:
> >> Sending this to dev ML in advance given it's simple and "probably"
> >> won't need to change the code further.
>
> So the will-be-slot tracker bugs may in the (long) bug list at the bottom
> of the PR, but I didn't see them specifically named either here or in the
> PR. In the interest of preventing duplicated effort here's what I found
Yes, migration & tracker bugs haven't been handled yet, that's for
a follow up (after merge). The only exception is moc which is used
as an example.
Right now this is mostly fixing bugs of ffmpeg itself, not the bugs
of revdeps, all while preparing things to start checking these.
> Bottom line: As the PM says a 4-compat slot is likely to be short-lived.
Indeed, albeit still need to recheck some of the in-tree packages
(likewise for other ffmpeg versions), tracker bugs can be missing
things esp. if some devs added upper bounds without filing a bug.
For ffmpeg-7, some may still need to be discovered -- tinderboxes
unmasking it sometimes don't catch everything.
Can probably kill 4 anytime anyhow, but no hurry, ffmpeg-4 isn't too
broken yet.
> > See the `rewrite live ebuild` commit message if want details, some
> > changes are debatable and may anger some users, albeit I'm mostly aiming
> > for stabler ffmpeg.
>
> Having looked over that live ebuild commit message, LGTM; yes a bunch of
> changes but no "anger some users" here! =:^)
Cool :)
--
ionen
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2025-03-11 5:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-09 3:34 [gentoo-dev] [PATCH] ffmpeg-compat.eclass: new eclass Ionen Wolkens
2025-03-09 10:17 ` James Le Cuirot
2025-03-09 10:27 ` Ionen Wolkens
2025-03-09 10:33 ` James Le Cuirot
2025-03-09 15:22 ` Ionen Wolkens
2025-03-09 16:45 ` Eli Schwartz
2025-03-09 18:47 ` Ionen Wolkens
2025-03-09 19:34 ` Ionen Wolkens
2025-03-11 4:37 ` [gentoo-dev] " Duncan
2025-03-11 5:14 ` Ionen Wolkens [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=Z8_GtbNlwyfAEra2@eversor \
--to=ionen@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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