Leap 15.5 package update failures

English Install/Boot/Login
1

I encountered the following three failed package updates with error messages:

- the to be installed patch:openSUSE-SLE-15.5-2023-2811-1.noarch conflicts with 'libfido2-1.x86_64 

- the to be installed patch:openSUSE-SLE-15.5-2023-3468-1.noarch conflicts with 'python3-text-unidecode 

- the installed WebKit2GTK-4.1-lang-2.38.6-150400.4.42.4.noarch requires 'WebKit2GTK-4.1 = 2.38.6', but this requirement cannot be provided

What can I do to solve those conflicts?

1 Like
2

There were package name changes and a bug report involved with this known issue. I don’t know if the fix hit the mirrors yet, but running sudo zypper up should resolve the problem.

3

The problem is still there.

Yes, using “zypper up” will update your system. But it won’t solve the problem.

I just tried “zypper patch -D” a few minutes ago, and it still finds conflicts. It looks as if the proposed fix is still being tested.

1 Like
4

Sure it will, especially if whatever the fix is for doesn’t involve anything OP uses. There will be no conflict that won’t resolve using up instead of patch. :slight_smile: A working update will show up in due course.

5

Nothing prevents you from skipping patch that causes conflicts using zypper patch. Which will have exactly the same effect - some updates will not be installed. It is hardly can be called “resolution” - it is temporary workaround.

2 Likes
6

@klerai:

When I installed the following patch list last Thursday the 31st of August, I simply took the option to remove “WebKit2GTK-4.0-lang” –

2023-08-31 15:23:03|patch  |openSUSE-SLE-15.5-2023-3413|1|noarch|repo-sle-update|important|feature|needed|applied|
2023-08-31 15:23:03|patch  |openSUSE-SLE-15.5-2023-3468|1|noarch|repo-sle-update|low|recommended|needed|applied|
2023-08-31 15:23:03|patch  |openSUSE-SLE-15.5-2023-3388|1|noarch|repo-sle-update|important|recommended|needed|applied|
2023-08-31 15:23:03|patch  |openSUSE-SLE-15.5-2023-3438|1|noarch|repo-sle-update|low|security|needed|applied|
2023-08-31 15:23:03|patch  |openSUSE-SLE-15.5-2023-3451|1|noarch|repo-sle-update|moderate|recommended|needed|applied|
2023-08-31 15:23:03|patch  |openSUSE-SLE-15.5-2023-3470|1|noarch|repo-sle-update|low|recommended|needed|applied|
2023-08-31 15:23:03|patch  |openSUSE-SLE-15.5-2023-3437|1|noarch|repo-sle-update|moderate|recommended|needed|applied|
2023-08-31 15:23:03|patch  |openSUSE-SLE-15.5-2023-3464|1|noarch|repo-sle-update|low|recommended|needed|applied|
2023-08-31 15:23:03|patch  |openSUSE-SLE-15.5-2023-3394|1|noarch|repo-sle-update|important|security|needed|applied|
2023-08-31 15:23:03|patch  |openSUSE-SLE-15.5-2023-3419|1|noarch|repo-sle-update|important|security|needed|applied|
2023-08-31 15:23:03|patch  |openSUSE-SLE-15.5-2023-3460|1|noarch|repo-sle-update|low|recommended|needed|applied|
2023-08-31 15:23:03|patch  |openSUSE-SLE-15.5-2023-3440|1|noarch|repo-sle-update|low|security|needed|applied|
2023-08-31 15:23:03|patch  |openSUSE-SLE-15.5-2023-3457|1|noarch|repo-sle-update|moderate|recommended|needed|applied|
2023-08-31 15:23:03|patch  |openSUSE-SLE-15.5-2023-3323|1|noarch|repo-sle-update|moderate|recommended|not-needed|applied|
2023-08-31 15:23:03|patch  |openSUSE-SLE-15.5-2023-3447|1|noarch|repo-sle-update|moderate|security|needed|applied|
2023-08-31 15:23:03|patch  |openSUSE-SLE-15.5-2023-3454|1|noarch|repo-sle-update|important|security|needed|applied|
2023-08-31 15:23:03|patch  |openSUSE-SLE-15.5-2023-3466|1|noarch|repo-sle-update|moderate|recommended|needed|applied|
2023-08-31 15:23:03|patch  |openSUSE-SLE-15.5-2023-3472|1|noarch|repo-sle-update|low|security|needed|applied|
2023-08-31 15:23:03|patch  |openSUSE-SLE-15.5-2023-3480|1|noarch|repo-sle-update|moderate|recommended|needed|applied|
2023-08-31 15:23:03|patch  |openSUSE-SLE-15.5-2023-3418|1|noarch|repo-sle-update|moderate|recommended|needed|applied|
2023-08-31 15:23:03|patch  |openSUSE-SLE-15.5-2023-3465|1|noarch|repo-sle-update|moderate|recommended|needed|applied|
2023-08-31 15:23:03|patch  |openSUSE-SLE-15.5-2023-3410|1|noarch|repo-sle-update|moderate|recommended|needed|applied|
2023-08-31 15:23:03|patch  |openSUSE-SLE-15.5-2023-3497|1|noarch|repo-sle-update|important|security|needed|applied|
2023-08-31 15:23:03|patch  |openSUSE-SLE-15.5-2023-3393|1|noarch|repo-sle-update|important|recommended|needed|applied|
2023-08-31 15:23:03|patch  |openSUSE-SLE-15.5-2023-3485|1|noarch|repo-sle-update|moderate|recommended|needed|applied|
2023-08-31 15:23:03|patch  |openSUSE-SLE-15.5-2023-3433|1|noarch|repo-sle-update|low|security|needed|applied|
2023-08-31 15:23:03|patch  |openSUSE-SLE-15.5-2023-3461|1|noarch|repo-sle-update|moderate|security|needed|applied|

Searching for the removed package reveals the following –

 > zypper search WebKit
Repository-Daten werden geladen...
Installierte Pakete werden gelesen...

S  | Name                                       | Summary                                                   | Type
---+--------------------------------------------+-----------------------------------------------------------+-----------
 . 
 . 
   | WebKit2GTK-4.0-lang                        | Translations for package webkit2gtk3-soup2                | Paket
   | WebKit2GTK-4.1-lang                        | Translations for package webkit2gtk3                      | Paket
 . 
 . 
 >

I have neither the “webkit2gtk3-soup2” source package nor the “webkit2gtk3” source package installed on this system.

  • It seems that, the “WebKit2GTK” language packages are only needed if, you’re going to compile the contents of the “webkit2gtk3” source packages yourself.
7

Your suggestion help me to solve all my issues.

Using Yast2-> Software Management, I found the following WebKit packages available for update:

  • libwebkit2gtk-4_0-37 webkit2gtk-4_0-injected-bundles webkit2gtk-4_1-injected-bundles WebKitGTK-4.1-lang
    following the conflict resolver, I de-installed the conflicting packages. - This has solved both issues, WebKit and Fido2 updates,

As for the unidecode conflict, I switched the provide from home:arachnos to Suse. After that, all Python package updates went smoothly.

Thanks a lot for all the good comments.

8

Similar Problem with Leap 15.4

Problem: the installed WebKit2GTK-4.0-lang-2.38.6-150400.4.42.4.noarch requires ‘WebKit2GTK-4.0 = 2.38.6’, but this requirement cannot be provided
not installable providers: libwebkit2gtk-4_0-37-2.36.0-150400.2.13.x86_64[repo-oss]
libwebkit2gtk-4_0-37-2.36.3-150400.4.3.1.x86_64[repo-sle-update]
libwebkit2gtk-4_0-37-2.36.4-150400.4.6.2.x86_64[repo-sle-update]
libwebkit2gtk-4_0-37-2.36.5-150400.4.9.1.x86_64[repo-sle-update]
libwebkit2gtk-4_0-37-2.36.7-150400.4.12.1.x86_64[repo-sle-update]
libwebkit2gtk-4_0-37-2.36.8-150400.4.15.1.x86_64[repo-sle-update]
libwebkit2gtk-4_0-37-2.38.2-150400.4.22.1.x86_64[repo-sle-update]
libwebkit2gtk-4_0-37-2.38.3-150400.4.25.1.x86_64[repo-sle-update]
libwebkit2gtk-4_0-37-2.38.5-150400.4.34.2.x86_64[repo-sle-update]
libwebkit2gtk-4_0-37-2.38.6-150400.4.39.1.x86_64[repo-sle-update]
Solution 1: deinstallation of WebKit2GTK-4.0-lang-2.38.6-150400.4.42.4.noarch
Solution 2: do not install patch:openSUSE-SLE-15.4-2023-3419-1.noarch
Solution 3: break WebKit2GTK-4.0-lang-2.38.6-150400.4.42.4.noarch by ignoring some of its dependencies

9

chose option 1 (deinstall webkit_lang)

Choose from above solutions by number or cancel [1/2/3/c/d/?] (c): 1
Resolving dependencies…
Resolving package dependencies…

The following item is locked and will not be changed by any action:
Available:
fakeroot

The following 2 packages are going to be upgraded:
libjavascriptcoregtk-4_0-18 libwebkit2gtk-4_0-37

The following NEW package is going to be installed:
WebKitGTK-4.0-lang

The following NEW patch is going to be installed:
openSUSE-SLE-15.4-2023-3419

The following 2 packages are going to be REMOVED:
libwebkit2gtk3-lang WebKit2GTK-4.0-lang

2 packages to upgrade, 1 new, 2 to remove.
Overall download size: 27.4 MiB. Already cached: 0 B. After the operation, additional 7.4 MiB
will be used.
Continue? [y/n/v/…? shows all options] (y):

10

everything seems to work.
a reboot will tell
wish me luck : )

11

I like when the last message in the thread is like this and then nobody ever hears about this person

12

We’re wishing you lots and lots of luck … :innocent: