Bug 2143509 - Libavif can't find libdav1d.so.5 since Dav1d-1.0.0
Summary: Libavif can't find libdav1d.so.5 since Dav1d-1.0.0
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: libavif
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Robert-André Mauchin 🐧
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-17 04:12 UTC by Rik Ske
Modified: 2022-12-10 00:36 UTC (History)
3 users (show)

Fixed In Version: libavif-0.11.1-4.el9
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-12-10 00:36:50 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Rik Ske 2022-11-17 04:12:10 UTC
Description of problem:

Problem is that dav1d is build (since version 1.0.0) to compile the lib file as libdav1d.so.6 instead of libdav1d.so.5 (can be reviewed in the dav1d spec file). 
With the result on EL 9.1 that libavif can't find libdav1d.so.5 as compiled with:

# dnf install libavif
Last metadata expiration check: 0:32:40 ago on Thu 17 Nov 2022 04:19:06 AM CET.
Error: 
 Problem: conflicting requests
  - nothing provides libdav1d.so.5()(64bit) needed by libavif-0.10.1-3.el9.x86_64

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

libavif-0.10.1-3.el9.x86_64
dav1d-1.0.0-2.el9.x86_64

dav1d.spec
%files -n libdav1d
%license COPYING doc/PATENTS
%{_libdir}/libdav1d.so.6*

How reproducible:

Recompile libavif with dav1d

Expected results:

Fix the issue. Recompile the package and distribute it via EPEL.

Comment 1 Fedora Update System 2022-12-02 14:43:44 UTC
FEDORA-EPEL-2022-385df27ee1 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-385df27ee1

Comment 2 Fedora Update System 2022-12-10 00:36:50 UTC
FEDORA-EPEL-2022-385df27ee1 has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.


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