From: Stuart Henderson <stu@spacehopper.org>
Subject: Re: graphics/ffmpeg: update to 8.0
To: ports@openbsd.org, andrey0bolkonsky@gmail.com, tobhe@openbsd.org, thfr@openbsd.org, uaa@openbsd.org, rsadowski@openbsd.org, pascal@stumpf.co, espie@openbsd.org, landry@openbsd.org, kn@openbsd.org, kirby@openbsd.org, jeremy@openbsd.org, brad@comstyle.com, noiseless-ak@yandex.ru
Date: Sat, 20 Sep 2025 12:55:44 +0100

IMO it is worth committing diffs to preemptively fix ports with
newer FFmpeg before the update, as long as they don't break with
the old version - I only skimmed the diff but it looked like
these are generally safe from a quick look.

(also if there is a choice between fixing by adding a patch, and
fixing by updating the relevant port, updating would generally be
preferred)


On 2025/09/20 00:45, Kirill A. Korinsky wrote:
> ports@,
> 
> I'd like to update graphics/ffmpeg to 8.0.
> 
> I had attached a diff as gz which updated ffmpeg and fixes build of
> everything. My bulk on -current/amd64 ended as:
> 
>   Elapsed time=1 day 21:22:13
>   I=12230 B=0 Q=0 T=0 F=0 !=115
>   E=emulators/retroarch lang/apl math/wxMaxima net/synapse net/py-tinytuya! www/tuba
> 
> All errors aren't ffmpeg related.
> 
> Here https://kirill.korins.ky/pub/ffmpeg8/ is the same diff and prebuilt
> unsigned packages from this bulk to make testing who willing do it easy.
> 
> I also add to CC maintainers of all affected ports.
> 
> Well, I run my laptop on ffmpeg8 for something between one and two weeks,
> when I've worked to fix all ports, so far no regression noticed.
> 
> Anyone willing to test it? Or OK it?
> 
> Thus, I do not plan to move forward with it until the unlock.
> 
> --
> wbr, Kirill