Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#231 closed defect (invalid)

libvpx-1.61-1 conflicts with FFmpeg

Reported by: Dave Yeo Owned by:
Priority: major Milestone:
Component: rpm Version:
Severity: low Keywords:
Cc: dave.r.yeo@…

Description

Attempting to update to libvpx-1.61-1.oc00 (i686) results in this error,

[u'ERROR with transaction check vs depsolve:', 'libvpx2.dll is needed by (installed) ffmpeg-libs-2.8.6-2.oc)).i686', u'Please report this error at http://yumbaseurl.org/report']

as libvpx-1.61-1 contains libvpx4.dll.

Change History (5)

comment:1 by dmik, 8 years ago

Please give me the exact command you are trying to execute with the full output. This must not happen as 1.6.1 RPMs provide a package libvpx-legacy-2 which contains libvpx2.dll and is marked as a replacement for libvpx <= 1.4.0. I have ffmpeg-libs here installed as well and updating libvpx from 1.4.0 to 1.6.1 works smoothly with yum. Are you calling rpm -U directly?

Last edited 8 years ago by dmik (previous) (diff)

comment:2 by Dave Yeo, 8 years ago

I used wget to download libvpx-1.6.1-1.oc00.i686.rpm and libvpx-devel-1.6.1-1.oc00.i686.rpm, installed to my local repository and then used ANPN 1.1 to upgrade by right-clicking on libvpx-devel and choosing upgrade, ANPM gave me a list with the regular libvpx and devel that needed downloading, I clicked yes and got the error that I quoted above. I then removed the ffmpeg-libs and successfully upgraded.
Now reinstalling both the main and devel packages with yum reinstall libvpx-[-devel] re-installs with no mention of the legacy package.
Doing yum install ffmpeg, libvpx-legacy-2 is in the list of dependencies. Note I previously only had the ffmpeg libs installed.

comment:3 by dmik, 8 years ago

Resolution: invalid
Status: newclosed

So this explains why it failed for you — libvpx-legacy-2 (that provides libvpx2.dll needed by ffmpeg[-libs]) was missing and ANMP (yum) did nothing about a replacement for libvpx that would give it libvpx2.dll. This scenario is certainly not supported, neither by yum nor by our RPM packages. You could download all related sub-packages to solve this problem but that may be tricky sometimes as not all related sub-packages carry the same base name (there are cases like XXX and libXXX built from one .spec).

Anyway, not a bug.

Last edited 8 years ago by dmik (previous) (diff)

comment:4 by Dave Yeo, 8 years ago

Actually the bug is that just updating the devel package doesn't try to download the legacy package. Trying on a different install, upgrading libvpx fails due to missing dependency of the legacy package.
Quite a few times previously I've also correctly had install/upgrade failures when a dependency was missing.
Years ago (with Debian) I got into the habit of going straight to installing the developer package just so I could see all the dependencies.

comment:5 by dmik, 8 years ago

Sorry, I can't confirm what you write. I just tried it again to be double sure: I reverted libvpx and libvpx-devel back to 1.4.0-2 (no legacy no nothing, but with ffmpeg-libs that depend on 1.4.0 runtime). Then all three runs of yum update, yum update libvpx and yum update libvpx-devel gave me exactly the same result: offered to install 3 packages (libvpx and libvpx-devel 1.6.1 and libvpx-legacy-2 — all in one go, i.e. through the dependency check). I let the latter one run and the install well successfully, no broken dependencies. So it must be your local setup.

Note: See TracTickets for help on using tickets.