Date: Fri, 17 Mar 2023 06:54:35 +0000 From: bugzilla-noreply@freebsd.org To: multimedia@FreeBSD.org Subject: [Bug 261302] multimedia/ffmpeg: update to 6.0 Message-ID: <bug-261302-12827-4yGQ0C4kBw@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-261302-12827@https.bugs.freebsd.org/bugzilla/> References: <bug-261302-12827@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D261302 --- Comment #53 from Daniel Engberg <diizzy@FreeBSD.org> --- graphics/gnash: Mark port broken during update of FFmpeg 6.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D270206 ...a bit of an update: I apologize about the flood of mails, I'm working on this on spare (free) t= ime so it's a bit sporadic and I prefer to push things as soon as possible rath= er that letting notes sit for days.=20 Anyhow, I'd suggest that we're going to be a bit more aggressive on this up= date otherwise we'll still be stuck with 4.4 until infinity. By that I mean we'll likely going to mark some packages as broken and/or need to create a separa= te port for FFmpeg 4.X. This will however conflict with any other version of FFmpeg so its really a "no other way" solution and needs to be justified wi= th good reasoning more than port X is broken. As for timeline I'd suggest that we commit 6.0 somewhere around 1 week efte= r q2 branching unless there major issues discovered. I'll try to get around during the weekend creating the last batch of PRs po= rts being reported as broken namely a few listed here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D261302#c47 Due to limited resources and time it would very helpful if people could look though PRs and do runtime testing. I would also be nice if you could test patches with FFmpeg 4 (current version in tree, I've only done testing with 6.0) and see if we can merge these before landing 6.0. Best regards, Daniel --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-261302-12827-4yGQ0C4kBw>