I ran my usual update this morning and have suddenly started getting problems with i586 packages, which is weird as I’m running x86_64. I’ve held off updating for now but is there a simple fix or way to determine where I report this?
[richard@andromeda-ascendant ~]$ uname -a
Linux andromeda-ascendant 4.7.5-1-default #1 SMP PREEMPT Mon Sep 26 08:11:45 UTC 2016 (02c4d35) x86_64 x86_64 x86_64 GNU/Linux
[richard@andromeda-ascendant ~]$ rpm -qa | grep broadcom
broadcom-wl-kmp-default-6.30.223.248_k4.7.5_1-9.31.x86_64
broadcom-wl-kmp-default-6.30.223.248_k4.7.4_2-9.30.x86_64
broadcom-wl-kmp-default-6.30.223.248_k4.7.4_2-9.29.x86_64
broadcom-wl-kmp-default-6.30.223.248_k4.7.5_1-9.32.x86_64
broadcom-wl-6.30.223.248-9.32.x86_64
[richard@andromeda-ascendant ~]$ rpm -qa | grep vlc-codecs
vlc-codecs-2.2.4-12.3.x86_64
[richard@andromeda-ascendant ~]$ zypper lr --details
# | Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service
--+------------------+------------------+---------+-----------+---------+----------+--------+---------------------------------------------------------------+--------
1 | packman | packman | Yes | (r ) Yes | Yes | 95 | rpm-md | http://packman.jacobs-university.de/suse/openSUSE_Tumbleweed/ |
2 | repo-debug | repo-debug | Yes | (r ) Yes | Yes | 99 | yast2 | http://download.opensuse.org/tumbleweed/repo/debug |
3 | repo-non-oss | repo-non-oss | Yes | (r ) Yes | Yes | 99 | yast2 | http://download.opensuse.org/tumbleweed/repo/non-oss |
4 | repo-oss | repo-oss | Yes | (r ) Yes | Yes | 99 | yast2 | http://download.opensuse.org/tumbleweed/repo/oss |
5 | repo-src-non-oss | repo-src-non-oss | Yes | (r ) Yes | Yes | 99 | yast2 | http://download.opensuse.org/tumbleweed/repo/src-non-oss |
6 | repo-src-oss | repo-src-oss | Yes | (r ) Yes | Yes | 99 | yast2 | http://download.opensuse.org/tumbleweed/repo/src-oss |
7 | repo-update | repo-update | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/tumbleweed/ |
[richard@andromeda-ascendant ~]$ sudo zypper dup
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command.
Loading repository data...
Reading installed packages...
Computing distribution upgrade...
5 Problems:
Problem: nothing provides libavcodec56(unrestricted) needed by vlc-codecs-2.2.4-13.1.i586
Problem: nothing provides kernel-uname-r = 4.7.6-1-default needed by broadcom-wl-kmp-default-6.30.223.248_k4.7.6_1-10.2.i586
Problem: nothing provides kernel-uname-r = 4.7.6-1-default needed by broadcom-wl-kmp-default-6.30.223.248_k4.7.6_1-10.2.i586
Problem: nothing provides kernel-uname-r = 4.7.6-1-default needed by broadcom-wl-kmp-default-6.30.223.248_k4.7.6_1-10.2.i586
Problem: nothing provides kernel-uname-r = 4.7.6-1-default needed by broadcom-wl-kmp-default-6.30.223.248_k4.7.6_1-10.2.i586
Problem: nothing provides libavcodec56(unrestricted) needed by vlc-codecs-2.2.4-13.1.i586
Solution 1: keep obsolete vlc-codecs-2.2.4-12.3.x86_64
Solution 2: break vlc-codecs-2.2.4-13.1.i586 by ignoring some of its dependencies
Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c] (c): c
Wait some time. It is known that zypper falls back to i586 packages if it cannot find x86_64 ones. Sometimes building of packages fails so only partial results get published. Or mirror you happen to be using is out of sync
And broadcom-wl seems to have been built for kernel 4.7.6 already, while currently there’s still only 4.7.5 in the Tumbleweed repo.
Apparently there’s been a kernel update in Factory, which hasn’t been published yet.
You need to wait for the next Tumbleweed snapshot for that to be “fixed” I suppose.
Yes it should, and according to your error message it tried to, but that requires libavcodec56(unrestricted) which seems not to be available.
Regarding i586, I suppose zypper tried to use x86_64 first, failed, tried i586 as fallback, which failed as well, and then it only reported the latter failure…
Though AFAICS, libavcodec56 should be in the Packman repo for Tumbleweed.
If it still doesn’t work, what conflict do you get if you explicitly try to install vlc-codecs-2.2.4-13.1?
sudo zypper in vlc-codecs-2.2.4-13.1
Maybe that provides more clues what the actual problem is…
Ok, I had a look in the Packman build service, and I think I know what the problem is:
vlc-codecs explicitly requires libavcodec56(unrestricted) (probably to make sure that you have the full/uncrippled libavcodec from Packman).
But libavcodec56 doesn’t provide libavcodec56(unrestricted), only libavcodec-full (which probably has the same purpose).
Just in case somebody else is reading this (and doesn’t bother to read the mailinglist discussion):
Actually Packman’s ffmpeg2/libavcodec56 is just a link to the package in Factory (but built with all restricted codecs).
The Factory package has been “fixed” (or rather adjusted to the change in vlc) already in the devel project, but the submit request to Factory is still pending review/staging.
So it may be a few days until it enters Tumbleweed and Packman, but then the problem should be gone.
For now, just keep the old vlc-codecs.
And the broadcom-wl problem should not occur any more, as kernel 4.7.6 is in the repos already AFAICS (there was a new Tumbleweed snapshot released today, which also includes Plasma 5.8.0… )
)