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
signature.asc
Description: PGP signature
