zypper dub: requirement: libopenconnet.so.3()(64bit) cannot be provided

English Install/Boot/Login
1

Hi,
yesterday i wanted to do a zypper dup on my tumbleweed laptop, and directly got this error:

Problem: NetworkManager-openconnect-gnome-0.9.10.0-3.1.x86_64 requires libopenconnect.so.3()(64bit), but this requirement cannot be provided
deleted providers: openconnect-6.00-4.1.x86_64
Solution 1: deinstallation of NetworkManager-openconnect-gnome-0.9.10.0-3.1.x86_64
Solution 2: keep obsolete openconnect-6.00-4.1.x86_64
Solution 3: break NetworkManager-openconnect-gnome-0.9.10.0-3.1.x86_64 by ignoring some of its dependencies

i choosed option “c”: break the update.
Today i tried it again and still got the same message.

What should i do?

2

I went with solution 1, because I mainly use KDE. So it won’t bother me if I cannot use a Cisco VPN from Gnome.

If I were a Gnome user, and if I depended on that software, then I would go with solution 2.

There’s actually a message about this on the factory mailing list. It seems that the Gnome version of the software is failing to build.

3

I have both installed on my laptop (kde and gnome) for testing reasons (i normaly use only kde too) so i think i will wait for a few days maybe someone manage to fix the package in the next days, if not i will go with option 2.
thanks.

4

Hi
It’s fixed in GNOME:Factory… hasn’t made it to Tumbleweed…

5

Thanks. I’m pretty sure that it will automatically re-install, once it is released in Tumbleweed. It is bound to at least be recommended by something, or else I would not have had it installed previously.

6

“NetworkManager-openconnect-gnome” is not installed here on KDE based system. I didn’t see any conflicts upgrading “openSUSE Tumbleweed 20141205-0 -> 20141206-0”, i.e. using zypper dup.

7

There is still no fix, is there any experience of how long it usally takes to have an existing fix in the tumbleweed repos?

8

Apologies for the delay - I was struggling badly the last week to get a snapshot out - some harsh changes entered on Dec 9 that caused a lot of troubl - together with some openQA overload, it was doomed.
Nevertheless, we managed to get a stable snapshot out again today (snapshot is dated 20141216) which should contain the fix for NetworkManager-openconnect. See also the announcement mail at http://lists.opensuse.org/opensuse-factory/2014-12/msg00217.html

My target is to get a snapshot out as often as possible. Having checkins, QA and all that, it theoretically possible to get one daily (if all is good), but the aim is certainly to have one every 2 - 3 days. This time we were just hit by some unlickly coincidences.

Cheers,
Dominique

9

Hi Dominique
Thanks for dropping by with an update, it’s appreciated :slight_smile:

10

Yes, it is working now, thank you very much.

11

Thanks. I’m updating now. i see that it is reinstalling that openconnect package, which I allowed it to remove. I won’t be able to check whether it works, because I don’t actually use it.

Oh, and I notice that “zypper dup” did not present me with a license approval screen this time.

12

That’s correct - the license screen has been removed; it really does not make sense on a system you’re basically regularly updating using ‘zypper dup’ - so libzypp only shows licenses of newly installed packages, not on updates anymore.

13

Thanks for confirmation, I hoped its absence would become permanent for snapshot upgrades. It was a bit tedious, although visually underlining the presence of a new snapshot in the update. Generally speaking, updating new Tumbleweed has been a breeze here so far. :slight_smile:

14

I didn’t install snapshot 20141216 probably as I haven’t used Tumbleweed since its release until today when I used “zypper -v dup” to receive snapshot 20141217. A license agreement was displayed (thought I saw EULA). Is that as it should be?

15

That’s probably correct.

I updated to 20141217 today, and did not see a EULA.

However: My normal practice is to start with:


zypper up libsolv-tools libzypp zypper rpm

That separately updates zypper before I do the main “zypper dup”.

So I did my update with the updated zypper and did not see the EULA. You did your update with the old zypper and did see the EULA. That sounds right. Next update you won’t see the EULA.

16

Ah yes, a pre-emptive zypper up would explain the difference. I saw the update to libzypp so might see the fix next snapshot, but couldn’t correlate that to your
earlier result. Thanks for the details. :slight_smile: