Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: libva in F31 is based on 2.6.0-pre1 pre-release, which is missing some APIs present in 2.6.0 final. Version-Release number of selected component (if applicable): libva-2.6.0-0.1.fc31.x86_64 How reproducible: Always Steps to Reproduce: 1. install libva-devel 2. grep slice_data_num_emu_prevn_bytes /usr/include/va/va_dec_hevc.h Actual results: no match Expected results: uint16_t slice_data_num_emu_prevn_bytes; Additional info: This was added in https://github.com/intel/libva/commit/95eb8cf469367b532b391042fa0e77ca513ac94e#diff-dc3ce5eacf55b5dffa4e978ce39dac83 which made it into 2.6.0 final: https://github.com/intel/libva/blob/2.6.0/va/va_dec_hevc.h#L489 .
IIRC, there is a little ABI break by updating to 2.6.1 What's the issue with keeping this ?
I asked for 2.6.0. Is there an ABI break between 2.6.0-pre1 and 2.6.0 too? The issue behind this is intel-mediasdk-20.1.0, which doesn't build against libva-2.6.0-pre1 but does build with 2.6.0 (minimum requirement is 2.6.0 and F31 build pretends to be 2.6.0, but really isn't).
From my recall it was between 2.6.0-pre1 and 2.6.0. But after double check I don't see any, so I've updated to 2.6.1 (ABI break safe).
Once that said, I would be more confortable if intel-media-sdk can be made for development releases only, so we can have a coherant intel media stack across the whole distribution. (so update intel-media-sdk only for f32+).
There are no incompatible API or ABI changes between 19.3.0 and 20.1.0 as far as rpmsodiff and abipkgdiff are concerned. Are you still against?
(In reply to Dominik 'Rathann' Mierzejewski from comment #5) > There are no incompatible API or ABI changes between 19.3.0 and 20.1.0 as > far as rpmsodiff and abipkgdiff are concerned. Are you still against? Yes, I'm still against. The problem is that there are still ABI break involved in the intel media stack and there are also runtime or even build time deps with the whole components. For example intel-media-driver 20.1.1 claims to build with libva-2.6.x, but actually requires libva-2.7.0 (currently in f32+). So I don't want a "mixed experience" with some components updated to the newer and others not. We will probably miss bugs that would be caught any intel continuous integration.
FEDORA-2020-3cd4a9d1eb has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-3cd4a9d1eb
I see. Thanks for the info. I won't update intel-mediasdk in F31, then. Thanks for fixing this one, anyway.
FEDORA-2020-3cd4a9d1eb has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-3cd4a9d1eb` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-3cd4a9d1eb See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-3cd4a9d1eb has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report.