Last week I updated my computer from leap 42.2 to leap 42.3. Following the update assistance for the installed packages, I get the following error message
patch:openSUSE-2017-1100-1.noarch steht in Konflikt mit libvlc5.x86_64 < 2.2.6-3.1, das von libvlc5-2.2.4-32.4.2.x86_64 zur Verfügung gestellt wurde
Thank you very much for your help to remove this conflict.
Hi, update libvlc5 from the official Leap 42.3 Update repo, or download the package from here: https://download.opensuse.org/repositories/openSUSE:/Leap:/42.3:/Update/standard/x86_64/libvlc5-2.2.6-3.1.x86_64.rpm
You do not explain how you did it. It could be that such a problem is due to doing the update not correct.
Better check which repos you have now
LANG=C zypper lr -d
Followed your link, and the update worked accepting the updates on all dependencies. The suggested update button disappeared, so basically my problem is solved. Thank you very much!
I downloaded the installation file, created a bootable memory stick and selected “update” in the installation menu. After that I simply clicked trough the installation assistant accepting all the suggested steps. The repository list reads as follows:
# | Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service
---+---------------------------+-----------------------------------------------------+---------+-----------+---------+----------+--------+--------------------------------------------------------------------------+--------
1 | openSUSE-Leap-42.3-0 | openSUSE-Leap-42.3-0 | No | ---- | ---- | 99 | yast2 | hd:///?device=/dev/disk/by-id/usb-058f_6387_13021912000002-0:0-part2 |
2 | ownbrander_polybox | Desktop Client project polybox (openSUSE_Leap_42.2) | Yes | (r ) Yes | No | 99 | rpm-md | https://polybox.ethz.ch/repo/openSUSE_Leap_42.2 |
3 | repo-debug | openSUSE-Leap-42.3-Debug | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/distribution/leap/42.3/repo/oss/ |
4 | repo-debug-non-oss | openSUSE-Leap-42.3-Debug-Non-Oss | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/distribution/leap/42.3/repo/non-oss/ |
5 | repo-debug-update | openSUSE-Leap-42.3-Update-Debug | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/update/leap/42.3/oss/ |
6 | repo-debug-update-non-oss | openSUSE-Leap-42.3-Update-Debug-Non-Oss | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/update/leap/42.3/non-oss/ |
7 | repo-non-oss | openSUSE-Leap-42.3-Non-Oss | Yes | (r ) Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/leap/42.3/repo/non-oss/ |
8 | repo-oss | openSUSE-Leap-42.3-Oss | Yes | (r ) Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/leap/42.3/repo/oss/ |
9 | repo-source | openSUSE-Leap-42.3-Source | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/source/distribution/leap/42.3/repo/oss/ |
10 | repo-source-non-oss | openSUSE-Leap-42.3-Source-Non-Oss | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/source/distribution/leap/42.3/repo/non-oss/ |
11 | repo-update | openSUSE-Leap-42.3-Update | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/42.3/oss/ |
12 | repo-update-non-oss | openSUSE-Leap-42.3-Update-Non-Oss | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/42.3/non-oss/
Any further suggestions on that?
I see at least one 42.2 repo still in your list. Remove it or change it to it’s 43.3 equivalent and do a zypper dup from that one.
And again I notice that you did NOT include the prompts (before and after) nor the command. Is it really so difficult to increase your mouse copy sweep a little bit to include that information? It is not always crucial, but often it gives important information to your potential helpers.
As far as I saw on the webpage of the publisher, there no 42.3 version. Could that cause problems?
Of course, excuse me, I’ll take care to include it in the future. Thank you very much for your help.
It depends. The packages there may need older library packages, which they then either have (and then you don’t have the current ones), or they haven’t and then they will be broken.
Thus the maintainers there saying there isn’t a new one, bu not ensuring you that it will work with (and not break) your 42.3 are not complete with the information they should provide.
Personally, I would ask myself if I really need a product that is not kept up-to-date by the maintainers.