Bug 1186879

I did a clean install from scratch and have the exact same problem except my yast readline.doc conflict wants to remove 1313 modules! When I set don't install, then tried to select an optional patch, the message comes back up and the checkbox clears. Right now, there is no way to update 15.3.

*** Bug 1186891 has been marked as a duplicate of this bug. ***

It seems to be same/related to Bug 1186866 as well.

(In reply to Mario Guzman from comment #1)
> I did a clean install from scratch and have the exact same problem except my
> yast readline.doc conflict wants to remove 1313 modules! When I set don't
> install, then tried to select an optional patch, the message comes back up
> and the checkbox clears. Right now, there is no way to update 15.3.

There is a way to update, I did through zypper up in a terminal, and then that patch is not there.

Btw, After upgrade I also had a message that one repository was incorrect (or something like that) After doing a refresh of all repositories via yast and trusting the new Suse repo, this was solved and I was able to update.

see bug 1186866

the sle repo is fluctuating depending for what SLES service pack we released updates last... a bug in the script that does the import I assume.

Just now I released a 15-sp3 sles update ... this might temporary cure the readline-doc issue.

Just an FYI, nothing changed as of today other than there was a YAST Main update which I updated from Yast. Also, this is odd: when I do a zypper up, it does not show the patch(es) I saw on Yast, instead, it shows an update available for yast-trans which does not show up in yast. So yast and zypper are out of sync.

To be precise: When I update via yast it says:
"patch:SUSE-2021-1526.1.noarch conflicts with readline-doc<7.0-19.3.1 provided by ...."

Installation would remove 1313 packages, I don't do that. When I select do not install, there is a recommended patch for bash, but the box must be left unchecked or the original message reappears. I was able to install an update for yast-main.

When I do a "zypper up" it list yast-trans as a new package, and would remove yast-trans-en and yast-trans-en_us. At no time did "zypper up" ever display the yast-main and bash updates seen in yast. And yast never displayed the yast-trans update.

I would have thought they should always be the same.

Created attachment 849968 [details]
Screen shot of proplem popup

Same issue here (first online update after upgrade with repository updates enabled)

I'm also wondering whether the right repository had been activated as my repository is labeled as "Update repository with updates from SUSE Linux Enterprise 15".

leap 15.3 imports SLES updates directly, so this repository is expected.


The readline-doc issue should now have been resolved.

Is anyone seeing other problems (Excepting libreoffice)?

I have been able to install this patch now. I also got some other updates too, that worked well.
I don't have anymore pending updates anywhere at the moment.

The Updater Applet now runs fine (with path SUSE-2021-1526 and 50+ others).

The only other problem I encountered with updates after the upgrade to Leap 15.3 was an inconsistency found by the Updater Applet for libLLVM11 (needs /bin/sh; strangle since /bin/sh of course is present). This I resolved already yesterday by running zypper up, which did not complain.

Thanks for solving the problem!

Meanwhile there occurred new problems:
The following patches lead to lots of conflicts and cannot be installed:
! | SUSE-2020-2950    | patch | 1       | noarch | Update repository with updates from SUSE Linux Enterprise 15
! | SUSE-2020-3129    | patch | 1       | noarch | Update repository with updates from SUSE Linux Enterprise 15
! | SUSE-2020-3792    | patch | 1       | noarch | Update repository with updates from SUSE Linux Enterprise 15
! | SUSE-2021-1200    | patch | 1       | noarch | Update repository with updates from SUSE Linux Enterprise 15
! | SUSE-2021-1235    | patch | 1       | noarch | Update repository with updates from SUSE Linux Enterprise 15
! | SUSE-2021-1243    | patch | 1       | noarch | Update repository with updates from SUSE Linux Enterprise 15
! | SUSE-2021-1244    | patch | 1       | noarch | Update repository with updates from SUSE Linux Enterprise 15
! | SUSE-2021-1245    | patch | 1       | noarch | Update repository with updates from SUSE Linux Enterprise 15
! | SUSE-2021-1499    | patch | 1       | noarch | Update repository with updates from SUSE Linux Enterprise 15
! | SUSE-2021-1569    | patch | 1       | noarch | Update repository with updates from SUSE Linux Enterprise 15
! | SUSE-2021-1589    | patch | 1       | noarch | Update repository with updates from SUSE Linux Enterprise 15
! | SUSE-2021-221     | patch | 1       | noarch | Update repository with updates from SUSE Linux Enterprise 15
! | SUSE-2021-27      | patch | 1       | noarch | Update repository with updates from SUSE Linux Enterprise 15
! | SUSE-2021-308     | patch | 1       | noarch | Update repository with updates from SUSE Linux Enterprise 15
! | SUSE-2021-510     | patch | 1       | noarch | Update repository with updates from SUSE Linux Enterprise 15
! | SUSE-2021-521     | patch | 1       | noarch | Update repository with updates from SUSE Linux Enterprise 15
! | SUSE-2021-538     | patch | 1       | noarch | Update repository with updates from SUSE Linux Enterprise 15
! | SUSE-2021-572     | patch | 1       | noarch | Update repository with updates from SUSE Linux Enterprise 15
! | SUSE-2021-76      | patch | 1       | noarch | Update repository with updates from SUSE Linux Enterprise 15
! | SUSE-2021-931     | patch | 1       | noarch | Update repository with updates from SUSE Linux Enterprise 15
! | SUSE-2021-985     | patch | 1       | noarch | Update repository with updates from SUSE Linux Enterprise 15

So it seems, that this issue still exists.

Created attachment 850059 [details]
Screen shot with more problems in popup

(In reply to Marcus Meissner from comment #10)
> Is anyone seeing other problems (Excepting libreoffice)?

After installing two zypper patches, there are many problems (see attachment).

Created attachment 850068 [details]
zypper output

I just uploaded an attachment with zypper up output at this point in time. Maybe this is helpful.

we are going over them and releasing fixes as fast as we can.

i hope to get it solved this week

I can confirm Ulrich's observation of a long list of conflict in yast2 online update after "zypper up". This is on a system that was freshly installed from Build142.1 and "zypper dup"ed a day after the release day. Start of list looks mostly the same. Number 2 is "patch:SUSE-2021-76-1.noarch" for me. In total, I count 15 conflicts. 1 patch wants to uninstall over 1000 packages, a few want to uninstall hundreds.

In addition to 14 cases of "the to be installed ..." I also have 1 conflict concerning "the installed zypper-search-packages-plugin-0.7-5.35.noarch". It is reported to have a "requirement [that] cannot be provided". Does this mean my system is currently in a broken state even though I always pressed "Cancel" when conflicts were shown?

Yast update still same as I previously reported on a non-upgrade clean install. Below is todays list if it helps. I also saw a bunch of architecture change messages:
architecture change of libgstsdp-1_0-0-1.16.3-4.3.1.x86_64 to libgstsdp-1_0-0-1.16.3-4.3.1.i586


the to be installed patch:SUSE-2020-3792-1.noarch conflicts with 'gzip.x86_64 < 1.10-4.3.1' provided by the installed gzip-1.10-3.11.1.x86_64

the to be installed patch:SUSE-2021-510-1.noarch conflicts with 'ucode-intel.x86_64 < 20210216-3.64.1' provided by the installed ucode-intel-20210216-2.19.1.x86_64

the to be installed patch:SUSE-2021-931-1.noarch conflicts with 'libnghttp2-14.x86_64 < 1.40.0-3.11.1' provided by the installed libnghttp2-14-1.40.0-3.5.1.x86_64

the to be installed patch:SUSE-2021-1235-1.noarch conflicts with 'numactl.x86_64 < 2.0.14-4.3.1' provided by the installed numactl-2.0.14-1.1.x86_64

the to be installed patch:SUSE-2021-1499-1.noarch conflicts with 'webkit2gtk-4_0-injected-bundles.x86_64 < 2.32.0-3.74.1' provided by the installed webkit2gtk-4_0-injected-bundles-2.32.0-3.15.1.x86_64

the to be installed patch:SUSE-2021-1589-1.noarch conflicts with 'libnuma1.x86_64 < 2.0.14-4.6.1' provided by the installed libnuma1-2.0.14-1.1.x86_64

the to be installed patch:SUSE-2021-1654-1.noarch conflicts with 'libxml2-tools.x86_64 < 2.9.7-3.34.1' provided by the installed libxml2-tools-2.9.7-3.31.1.x86_64

deinstallation of discthe to be installed patch:SUSE-2021-1654-1.noarch conflicts with 'libxml2-tools.x86_64 < 2.9.7-3.34.1' provided bythe to be installed patch:SUSE-2021-1765-1.noarch conflicts with 'libX11-xcb1.x86_64 < 1.6.5-3.18.1' provided by the installed libX11-xcb1-1.6.5-3.15.1.x86_64

 the installed libxml2-tools-2.9.7-3.31.1.x86_64
over-backend-fwupd-5.18.5-bp153.1.36.x86_64

deinstallation of ksshthe to be installed patch:SUSE-2021-1765-1.noarch conflicts with 'libX11-xcb1.x86_64 < 1.6.5-3.18.1' provided by the installed libX11-xcb1-1.6.5-3.15.1.x86_64
askpass5-5.18.5-bp153.1.23.x86_64

the to be installed patch:SUSE-2021-1914-1.noarch conflicts with 'libopenmpt0.x86_64 < 0.3.28-2.13.1' provided by the installed libopenmpt0-0.3.19-2.10.1.x86_64

the to be installed patch:SUSE-2020-3129-1.noarch conflicts with 'sysconfig-netconfig.x86_64 < 0.85.6-3.6.1' provided by the installed sysconfig-netconfig-0.85.6-3.3.1.x86_64

tracked in bug 1186642

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