Bug 2297750 - Update to 1.5.3
Summary: Update to 1.5.3
Keywords:
Status: NEW
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: vmaf
Version: epel8
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Nicolas Chauvet (kwizart)
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-07-14 15:59 UTC by Brian J. Murrell
Modified: 2025-06-03 06:34 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)
RPM spec file (4.29 KB, text/plain)
2024-07-14 15:59 UTC, Brian J. Murrell
no flags Details

Description Brian J. Murrell 2024-07-14 15:59:57 UTC
Created attachment 2039561 [details]
RPM spec file

Description of problem:
EPEL8 could use an update of vmaf to 1.5.3 to allow other software to be updated.

Version-Release number of selected component (if applicable):
1.3.15-2

Please find attached a spec file for an update to 1.5.3.  I am happy to submit that as a PR somewhere if that is the preferred process.

Comment 1 Nicolas Chauvet (kwizart) 2024-07-15 07:08:04 UTC
Thanks for the report.

Which component do you want to see in epel8 that requires vmaf ?

Comment 2 Nicolas Chauvet (kwizart) 2024-07-15 07:40:05 UTC
rpmsodiff analysis shows that they aren't really compatible despite keeping the same SONAME. (there are underlying ABI Break)

libvmaf.so.0 is already used by rpmfusion ffmpeg in el8.

Comment 3 Brian J. Murrell 2024-07-23 03:49:30 UTC
That's really annoying and dysfunctional that upstream breaks ABI without bumping the SONAME.  Do they realise they are doing this?  Perhaps they are ignorant and need to add some ABI breakage testing to their development and testing processes?  Maybe you can suggest they do that and describe how you determined they are doing it?

But yes, the motivation for updating this is ffmpeg in el8.  I just need to find the time submit all of the work for that.  I hope I can find that soon but have lots of other "real life" tasks taking priority.

Comment 4 Nicolas Chauvet (kwizart) 2024-07-23 07:14:04 UTC
So what's the problem with ffmpeg as 4.2 in epel8 ? Specially as this version will keep support for vaapi and vlc-3

Comment 5 Brian J. Murrell 2024-07-23 08:34:20 UTC
Jellyfin requires ffmpeg >= 4.4 so the ffmpeg in RPMFusion prevents Jellyfin from being usable on EL8.

Comment 6 Nicolas Chauvet (kwizart) 2024-07-23 10:44:42 UTC
Seriously, get yourself an EL9 (or fedora) for anything multimedia related.

jellyfin in the next release (I guess at some point) will use newer ffmpeg, so you would better use a more modern distro.

Even it should be possible to work on centos stream 10 "soon".

I think ffmpeg-4 would be relevant for el8 for "slow pace projects" that are kept in rpmfusion whereas others branches are in fedora, but it's not to create a "completely new ffmpeg" in EL8 for this transition.

Comment 7 Brian J. Murrell 2024-07-23 16:40:11 UTC
Yeah, EL9 is the goal ultimately and I tried to get there on that machine but unfortunately RH dropped support for the (admittedly ageing, but perfectly usable otherwise) processor I have in that machine.

Fedora's 6-month major version churn is too frequent for that machine.  I have enough actual workstations that are on Fedora and need upgrading every 6 months that I don't want to add yet another if I can avoid it.

So, I need to do a hardware upgrade there before I can do an EL major version upgrade.  Was hoping EL8 would keep that machine going until it ran out of steam or I can find the time and budget (but mostly time) to upgrade the hardware in that machine.


Note You need to log in before you can comment on or make changes to this bug.