>
> zypper ref
> Repository '15.5_SignalDM' is up to date.
> Repository 'Keepass' is up to date.
> Repository 'Printing System Development Project (15.5)' is up to date.
> Repository 'Security_leap15.5' is up to date.
> Repository 'nVidia Graphics Drivers' is up to date.
> Repository 'Packman Repository' is up to date.
> Repository 'Update repository of openSUSE Backports' is up to date.
> Repository 'Non-OSS Repository' is up to date.
> Repository 'Open H.264 Codec (openSUSE Leap)' is up to date.
> Repository 'Main Repository' is up to date.
> Repository 'Update repository with updates from SUSE Linux Enterprise 15' is up to date.
> Repository 'Main Update Repository' is up to date.
> Repository 'Update Repository (Non-Oss)' is up to date.
> All repositories have been refreshed.
Thanks - I was hoping that something here might give us some insight.
What is the output from zypper patch -D? (The -D makes it a dry run, so it’ll give you the messages but won’t make changes to your system). It looks like the updater is actually attempting to apply patches rather than updates; doing this from the CLI might tell us which one is attempting to remove glibc.
The following 6 NEW patches are going to be installed:
openSUSE-SLE-15.5-2023-4003 openSUSE-SLE-15.5-2023-4110 openSUSE-SLE-15.5-2023-4294 openSUSE-SLE-15.5-2023-4474 openSUSE-SLE-15.5-2023-4561 openSUSE-SLE-15.5-2023-4828
The following 6 packages are going to be REMOVED:
apparmor-docs glibc glibc-32bit glibc-extra libjavascriptcoregtk-4_0-18 nscd
6 packages to remove.
After the operation, 38.2 MiB will be freed.
Continue? [y/n/v/…? shows all options] (y):
My guess is that once the patch is applied, if you reboot and run rpm -qa | grep -i glibc, you’ll see a glibc package is in fact still installed.
You could also deselect this patch and apply the others. If you do that, you could check that apparmor-docs is still installed, since the zypper patch -D command shows that that package would be removed when applying the patch.
The system is attempting to apply patches, not updates.
I would never, ever recommend running updates in the background, much less scheduled (which I recognize this in and of itself does not do). Not for any OS or system. There’s always the possibility that an update breaks something, and it’s too easy to forget that you’ve set the system up to do this. That leads to support questions that go along the lines of “my system’s broken and I didn’t change anything!” (Except of course, the system’s owner did, they just forgot that they’d set that up.)
Patches are subsets of updates. Sometimes patches are the only valid alternative. In the long term updates are the preferred option. I conclude this from some five decades of experience with a huge variety of systems.
I don’t recommend this for every system. However openSUSE improved their processes and procedures in the past decade dramatically. Thus I gave the frequent dup of Tumbleweed a try on infamous host erlangen, which is my main machine.
Host erlangen gets upgraded daily by a scheduled service running in the background.
I frequently read similar claims. Thus I confronted these with reality. I started with host erlangen and subsequently converted all my hosts. As this worked fine I started to convert the hosts of other users as well. And trust me, they don’t pose support questions.
Despite massive warnings encountered everywhere I converted all hosts to a single partition of btrfs. This made switching backups from rsync to btrbk (based on btrfs send/receive) feasible. The resulting improvements are yet another great experience.
The reality is, that experienced administrators with basic technical knowledge, don’t let run upgrades/updates unattended in the background. It is always advises to inspect the list of packages to be updated/upgraded and have the possibilty for corrective actions prior start of the update/upgrade (excluding, locking, deinstallation, … of packages befor start). This is most relevant on Tumbleweed…
Experienced administrators follow the openSUSE mailing list and are able to control the update/upgrade by delaying it, modify the set of packages and so on. Blindly upgrading in the background without control over the process doesn’t fit the claim of experience and reality…
You will note that in this case, the user sees patches available, but no updates available. Thus, they are not handled the same way.
How you manage your system is up to you. You have experience and enough of an understanding of the best practices to make a decision that works for you in your specific instance.
That is different than making a blanket statement that suggests that inexperienced users should make the same decision. They don’t have the experience or background to understand the consequences of their action and if those consequences are things they can live with.
You are getting off topic here. Let’s stay on topic and help the OP here with their issue.
I tried to install the patches as suggested. The output is below. Now the system outputs “nothing to do” when running zypper up or zypper patch.
(before doing this I also removed the keepass repository as suggested above, if that makes any difference).
What has happened here?
W9020:/var/log # zypper patch
Loading repository data...
Reading installed packages...
Resolving package dependencies...
The following 2 NEW patches are going to be installed:
openSUSE-SLE-15.5-2023-4003 openSUSE-SLE-15.5-2023-4110
The following 5 packages are going to be REMOVED:
apparmor-docs glibc glibc-32bit glibc-extra nscd
5 packages to remove.
After the operation, 10.8 MiB will be freed.
Continue? [y/n/v/...? shows all options] (y): y
Checking for file conflicts: .................................................................................................................................................................[done]
( 1/10) Removing apparmor-docs-3.0.4-150500.11.6.1.noarch ....................................................................................................................................[done]
error: package apparmor-docs-3.0.4-150500.11.6.1.noarch is not installed
( 2/10) Removing apparmor-docs-3.0.4-150500.11.6.1.noarch ...................................................................................................................................[error]
Removal of (143178)apparmor-docs-3.0.4-150500.11.6.1.noarch(@System) failed:
Error: Subprocess failed. Error: RPM failed: Command exited with status 1.
Abort, retry, ignore? [a/r/i] (a): r
error: package apparmor-docs-3.0.4-150500.11.6.1.noarch is not installed
( 2/10) Removing apparmor-docs-3.0.4-150500.11.6.1.noarch ...................................................................................................................................[error]
Removal of (143178)apparmor-docs-3.0.4-150500.11.6.1.noarch(@System) failed:
Error: Subprocess failed. Error: RPM failed: Command exited with status 1.
Abort, retry, ignore? [a/r/i] (a): i
( 3/10) Removing glibc-2.31-150300.58.1.x86_64 ...............................................................................................................................................[done]
error: package glibc-2.31-150300.58.1.x86_64 is not installed
( 4/10) Removing glibc-2.31-150300.58.1.x86_64 ..............................................................................................................................................[error]
Removal of (143411)glibc-2.31-150300.58.1.x86_64(@System) failed:
Error: Subprocess failed. Error: RPM failed: Command exited with status 1.
Abort, retry, ignore? [a/r/i] (a): i
( 5/10) Removing glibc-32bit-2.31-150300.58.1.x86_64 .........................................................................................................................................[done]
error: package glibc-32bit-2.31-150300.58.1.x86_64 is not installed
( 6/10) Removing glibc-32bit-2.31-150300.58.1.x86_64 ........................................................................................................................................[error]
Removal of (143414)glibc-32bit-2.31-150300.58.1.x86_64(@System) failed:
Error: Subprocess failed. Error: RPM failed: Command exited with status 1.
Abort, retry, ignore? [a/r/i] (a): i
( 7/10) Removing glibc-extra-2.31-150300.58.1.x86_64 .........................................................................................................................................[done]
error: package glibc-extra-2.31-150300.58.1.x86_64 is not installed
( 8/10) Removing glibc-extra-2.31-150300.58.1.x86_64 ........................................................................................................................................[error]
Removal of (143418)glibc-extra-2.31-150300.58.1.x86_64(@System) failed:
Error: Subprocess failed. Error: RPM failed: Command exited with status 1.
Abort, retry, ignore? [a/r/i] (a): i
( 9/10) Removing nscd-2.31-150300.58.1.x86_64 ................................................................................................................................................[done]
error: package nscd-2.31-150300.58.1.x86_64 is not installed
(10/10) Removing nscd-2.31-150300.58.1.x86_64 ...............................................................................................................................................[error]
Removal of (145162)nscd-2.31-150300.58.1.x86_64(@System) failed:
Error: Subprocess failed. Error: RPM failed: Command exited with status 1.
Abort, retry, ignore? [a/r/i] (a): i
Also, the following command as requested ( I ran this command BEFORE the above )
zypper se -si glibc
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+-------------------+---------+--------------------+--------+-------------------------------------------------------------
i+ | glibc | package | 2.31-150300.63.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
i+ | glibc | package | 2.31-150300.58.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
i | glibc-32bit | package | 2.31-150300.63.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
i | glibc-32bit | package | 2.31-150300.58.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
i | glibc-devel | package | 2.31-150300.63.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
i | glibc-extra | package | 2.31-150300.63.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
i | glibc-extra | package | 2.31-150300.58.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
i | glibc-lang | package | 2.31-150300.63.1 | noarch | Update repository with updates from SUSE Linux Enterprise 15
i | glibc-locale | package | 2.31-150300.63.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
i | glibc-locale-base | package | 2.31-150300.63.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
i | linux-glibc-devel | package | 5.14-150500.12.3.2 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15