Bug 1215210 - not installable providers: libwebkit2gtk-4_1-0-2.38.6-150400.4.39.1.x86_64
Summary: not installable providers: libwebkit2gtk-4_1-0-2.38.6-150400.4.39.1.x86_64
Status: RESOLVED DUPLICATE of bug 1214093
Alias: None
Product: openSUSE Distribution
Classification: openSUSE
Component: Maintenance (show other bugs)
Version: Leap 15.5
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Mr Maintenance
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-09-11 13:03 UTC by Lubos Kocman
Modified: 2023-09-12 07:19 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Lubos Kocman 2023-09-11 13:03:21 UTC 
From my Leap 15.5 machine

lkocman@localhost:~> sudo zypper up --allow-vendor-change
Refreshing service 'NVIDIA'.
Refreshing service 'openSUSE'.
Loading repository data...
Reading installed packages...

The following 3 package updates will NOT be installed:
  libjavascriptcoregtk-4_1-0 libopenh264-7 libwebkit2gtk-4_1-0
Nothing to do.

Michal Svec reached out to me regarding this issue and seems like we did not release updated -lang package based on his output

Problem: 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 
 not installable providers: libwebkit2gtk-4_1-0-2.38.6-150400.4.39.1.x86_64[repo-oss] 
 Solution 1: Following actions will be done: 
 do not install patch:openSUSE-SLE-15.5-2023-3419-1.noarch 
 do not install patch:openSUSE-SLE-15.5-2023-3556-1.noarch 
 Solution 2: deinstallation of WebKit2GTK-4.1-lang-2.38.6-150400.4.42.4.noarch 
 Solution 3: break WebKit2GTK-4.1-lang-2.38.6-150400.4.42.4.noarch by ignoring some of its dependencies
Comment 1 Marcus Meissner 2023-09-12 07:19:36 UTC 
dup of bug 1214093

*** This bug has been marked as a duplicate of bug 1214093 ***