I guess this means rpmfusion is running behind, or does it imply something else? I update first thing each morning and such an explanation seems unusual:
[root@WS1 bobg]# dnf update Last metadata expiration check: 0:01:18 ago on Sun Jul 26 06:05:27 2020. Dependencies resolved.
Problem 1: cannot install the best update candidate for package vlc-core-1:3.0.11-4.fc32.x86_64 - nothing provides libebml.so.5()(64bit) needed by vlc-core-1:3.0.11-7.fc32.x86_64 - nothing provides libmatroska.so.7()(64bit) needed by vlc-core-1:3.0.11-7.fc32.x86_64 Problem 2: package vlc-1:3.0.11-7.fc32.x86_64 requires vlc-core(x86-64) = 1:3.0.11-7.fc32, but none of the providers can be installed - cannot install the best update candidate for package vlc-1:3.0.11-4.fc32.x86_64 - nothing provides libebml.so.5()(64bit) needed by vlc-core-1:3.0.11-7.fc32.x86_64 - nothing provides libmatroska.so.7()(64bit) needed by vlc-core-1:3.0.11-7.fc32.x86_64 =========================================================================================================== Package Architecture Version Repository Size =========================================================================================================== Skipping packages with broken dependencies: vlc x86_64 1:3.0.11-7.fc32 rpmfusion-free-updates 1.5 M vlc-core x86_64 1:3.0.11-7.fc32 rpmfusion-free-updates 9.8 M
Transaction Summary =========================================================================================================== Skip 2 Packages
Nothing to do. Complete!
On Sun, 26 Jul 2020 11:01:04 -0400 Bob Goodwin wrote:
I guess this means rpmfusion is running behind, or does it imply something else? I update first thing each morning and such an explanation seems unusual:
I usually just give things a few days to get back in sync. Tends to happen eventually. I got the same error yesterday.
On Sun, Jul 26, 2020 at 9:01 AM Bob Goodwin bobgoodwin@fastmail.us wrote:
I guess this means rpmfusion is running behind, or does it imply something else? I update first thing each morning and such an explanation seems unusual:
It means that rpmfusion is running ahead. They pushed vlc to stable before the Fedora libebml-1.4.0-1.fc32 and libmatroska-1.6.0-1 updates went stable:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-c5e96618e7
It should clear up soon, once the Fedora update gets pushed to stable.
On 2020-07-26 11:09, Tom Horsley wrote:
I usually just give things a few days to get back in sync. Tends to happen eventually. I got the same error yesterday.
. Yes I thought the same except it seems unusual to get such a lengthy explanation of it not updating?
On 2020-07-26 11:13, Jerry James wrote:
It means that rpmfusion is running ahead. They pushed vlc to stable before the Fedora libebml-1.4.0-1.fc32 and libmatroska-1.6.0-1 updates went stable:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-c5e96618e7
It should clear up soon, once the Fedora update gets pushed to stable.
. I can wait then, thanks for responding ...
-
Bob Goodwin -
Jerry James -
Tom Horsley