Comment # 5 on bug 4628 from
(In reply to Nicolas Chauvet from comment #3)
> I don't understand why the chromium-freeworld package still drop a
> chromium-libs-media-freeworld sub-package ?! What the point ?

The idea is that there are 
chromium-libs-media-freeworld and chromium-libs-media that can be freely
exchanged:

$ rpm -qa | grep chromium
chromium-libs-media-freeworld-60.0.3112.101-1.fc26.x86_64
chromium-common-60.0.3112.101-1.fc26.x86_64
chromium-libs-60.0.3112.101-1.fc26.x86_64
chromium-60.0.3112.101-1.fc26.x86_64

$ dnf install chromium-libs-media
...
Installed:
  chromium-libs-media.x86_64 60.0.3112.101-1.fc26

$ dnf remove chromium-libs-media-freeworld
...
Removed:
  chromium-libs-media-freeworld.x86_64 60.0.3112.101-1.fc26

$ rpm -qa | grep chromium
chromium-common-60.0.3112.101-1.fc26.x86_64
chromium-libs-60.0.3112.101-1.fc26.x86_64
chromium-libs-media-60.0.3112.101-1.fc26.x86_64
chromium-60.0.3112.101-1.fc26.x86_64

...

I believe that's the point. What's wrong with that?


(In reply to Nicolas Chauvet from comment #4)
> For some reason, trying to install the scratch build has installed
> chromium-libs-media-59.0.3071.104-1.fc26.x86_64 (from the base repo). Why ?
> I've chromium-59.0.3071.104-1.fc26.x86_64 installed because of the previous
> dependency breakage.

No idea, how are you installing?

> Also, when installing , the freeworld packages complained about
> /usr/lib64/chromium-browser/libffmpeg.so not a symlink (so the alternatives
> are not created).

How are you installing? I can install just fine.

> Seems like a version check is needed somewhere.
> But then this strict dependency check is annoying because it will means
> breakage when the fedora package is not updated along the rpmfusion one.

This will eventually get scripted.


You are receiving this mail because: