Bug 3075

Summary:	libavdevice.so.55 numerous libX* dependencies in ffmpeg-libs
Product:	Fedora	Reporter:	Nicolas Chauvet <kwizart>
Component:	ffmpeg	Assignee:	Dominik 'Rathann' Mierzejewski <dominik>
Status:	RESOLVED EXPIRED
Severity:	normal	CC:	kwizart
Priority:	P5
Version:	20
Hardware:	All
OS:	GNU/Linux
namespace:
Bug Depends on:	3366
Bug Blocks:

Description Nicolas Chauvet 2013-12-17 12:39:34 CET

According to ldd /usr/lib64/libavdevice.so.55.5.100, there are numerous dependencies in this library. Specially SDL and libX* libpulse.
This is a problem as ffmpeg-libs is specially used by headless packages.

# repoquery --whatrequires "libavdevice.so.55()(64bit)"
bino-0:1.4.4-1.fc20.x86_64
ffmpeg-0:2.1.1-1.fc20.x86_64
ffmpeg-devel-0:2.1.1-1.fc20.x86_64
gpac-0:0.5.0-8.20130914svn.fc20.x86_64
gpac-libs-0:0.5.0-8.20130914svn.fc20.x86_64
mlt-0:0.9.0-3.fc20.x86_64
mpv-0:0.2.4-4.fc20.x86_64

According to repoquery, the same question would apply to mlt, others (excluding gpac, but we shoudln't care there) are already Xorg dependents as player.

I sugguest to move the libavdevice.so.55 to the ffmpeg package instead of ffmpeg-libs. this library will hence not be multilib, that requires mlt/gpac to be in the multilibs exeption.

Another solution would be to drop a ffmpeg-X-libs or ffmpeg-libavdevice sub-package.

Any advices welcomed.

Comment 1 Dominik 'Rathann' Mierzejewski 2014-09-21 02:02:42 CEST

What exactly is the problem you'd like to solve here?

Comment 2 Dominik 'Rathann' Mierzejewski 2014-09-23 00:33:12 CEST

As discussed on IRC, I'm not against splitting off libavdevice into a subpackage. Recommended package name is just "libavdevice", i.e. %package -n libavdevice. I'll get to it in a week or two if Julian doesn't beat me to it.

Comment 3 Dominik 'Rathann' Mierzejewski 2015-02-01 02:38:19 CET

This should be fixed in 2.4.6-2.fc21.

Comment 4 Emmanuel Seyman 2015-06-25 09:45:04 CEST

RPMFusion is no longer releasing updates for this version of Fedora. This bug
will be set to RESOLVED:EXPIRED next week to reflect this.

If the problem persists after upgrading to the latest version of Fedora, please
update the version field of this bug (and re-open it if it has been closed).

Comment 5 Emmanuel Seyman 2015-07-03 16:36:17 CEST

Setting to RESOLVED:EXPIRED since RPMFusion is no longer releasing updates for
this version of Fedora.