Updating glibc and filesystem on Tumbleweed
I have a server running Tumbleweed. It is a bit behind in terms of updates for reasons that are not relevant to my question (a Python 2-based server I don't dare mess up). I want to update a library with a package from OBS. That package has been built with a newer version of glibc. So zypper wants to update glibc as well. And a couple others like filesystem. My Tumbleweed is before the lib move. I guess glibc usually contains support for older versions. I have 2.30, it wants to update to 2.35. An update such as this seems plausible. But the filesystem update seems odd in that I would have expected many more things to need to be updated when the move happened. I know that there are links in place that should help. Still... I have snapper enabled. So maybe I can try and see what happens. But I'm not sure about this one. Any thoughts? -- Roger Oberholtzer
* Roger Oberholtzer <roger.oberholtzer@gmail.com> [07-28-22 05:16]:
I have a server running Tumbleweed. It is a bit behind in terms of updates for reasons that are not relevant to my question (a Python 2-based server I don't dare mess up).
I want to update a library with a package from OBS. That package has been built with a newer version of glibc. So zypper wants to update glibc as well. And a couple others like filesystem. My Tumbleweed is before the lib move.
I guess glibc usually contains support for older versions. I have 2.30, it wants to update to 2.35. An update such as this seems plausible.
But the filesystem update seems odd in that I would have expected many more things to need to be updated when the move happened. I know that there are links in place that should help. Still...
I have snapper enabled. So maybe I can try and see what happens. But I'm not sure about this one.
Any thoughts?
I would think that a zypper dup would provide you with a list of upgrades and warning about conflicts. at a minimum you could start zypper dup and examine the involved actions and determine whether you have a problem. and as in all software, nothing is guarenteed :) gud luk, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
On Thu, Jul 28, 2022 at 4:00 PM Patrick Shanahan <paka@opensuse.org> wrote:
I would think that a zypper dup would provide you with a list of upgrades and warning about conflicts. at a minimum you could start zypper dup and examine the involved actions and determine whether you have a problem.
I think that zypper dup will list just about all installed packages. It has been a while. If I just look at updating filesystem (which will do the lib move stuff), it says: The following NEW package is going to be installed: compat-usrmerge-tools The following package is going to be upgraded: filesystem Given the wholesale movement of libraries this update will do, this looks minimal. I am guessing that the compatibility links that it sets up make packages that still expect things in the old location to work.
and as in all software, nothing is guarenteed :)
That is the way of things. But one can still be cautious and not tempt fate unnecessarily! -- Roger Oberholtzer
participants (2)
-
Patrick Shanahan -
Roger Oberholtzer