Hello! Almost a similar situation happened to me now, on the 20261018 snapshot sudo zypper ref && sudo zypper -vvv dup appeared this way It wants to install some new packages that i am not sure if they are accurate
What should i do? I don’t want to install them unless they are necessary, but they seem more like an error than a necessity to me.
Does zypper dup --no-recommends bring in those as well?
BTW, zypper ref is not needed before a zypper dup (unless you tweaked the standard zypper config of course).
Yes, with the Tumbleweed snapshot 20261018 there were a couple of new packages which were installed due to a couple of new dependencies – I took a look at the Zypper log and the systemd Journal but couldn’t quickly find the relevant entries …
No. The most likely explanation is the splitting of libabsl into separate packages. Reason I think so is that Leap has only one libabsl package, TW now has 99 packages.
And taking a look at the upstream information about Abseil → <https://abseil.io/>
Abseil is an open source collection of C++ libraries drawn from the most fundamental pieces of Google’s internal codebase. These libraries are the nuts-and-bolts that underpin almost everything Google runs. Bits and pieces of these APIs are embedded in most of our open source projects, and Abseil aims to bring them together into one comprehensive project. Abseil encompasses the most basic building blocks of Google’s codebase: code that is production-tested and will be fully maintained for years to come.
There are a few main reasons we recommend Abseil as your first choice for utility code when starting a new C++ project:
Compatibility with current and future C++ standards, and planned evolution over time
Compatibility with Google OSS projects - these are the foundational types for things like Protocol Buffers, gRPC, and TensorFlow
Upgrade Support - make it easy to live at head
Production Experience - These are the interfaces that we are using in Google production
Interest in a different set of design priorities than the C++ standard
It seems that, Tumbleweed has split the Abseil collection of C++ libraries into a scheme of one package per library – instead of offering the library collection as a single package.
Exactly why it has been decided to do this – I have absolutely no idea → on a quick search, I’ve found nothing in the RPM Change Log which could shed some light on the reason why …
@bmwiedemann can probably provide an answer, I suspect since it’s developed for MicroOS that it was split to keep space down for the likes of embedded systems…
In simple words: to hold the maintenance effort low. That means, if you ship a package divided in 10 subpackages for one distribution flavor, you ship it the same way for another flavor. And not x packages for flavour a, y packages for flavour b and z packages for flavour c.
Currently this system has 56 Abseil library packages installed – including four 32-bit variants.
Attempted to “remove --clean-deps’ a few of the installed Abseil packages, which resulted in large lists of dependent packages (sometimes more than 200) which would also be removed.
Therefore, it seems that, the current list of installed Abseil library packages can not be reduced …
At the expense of further bloating /var/log/zypper.log with all those additional transactions, besides the additional zypper/rpm transaction overhead, right? I see two parts to maintenance, output (package production, by a noble few), and input (updating, by the multitude).
And with what effect on mirrors, with gargantuan numbers of packages in a single directory, compared to numerous (? other + all the many Debian-based) other distros apparently taken aback long ago by huge directories and subdividing their repos into alphanumerics?
I, like @hui I guess, prefer packager reasoning over user opinions. And I don’t have any_whatever to give about whether my beloved system is complete with 800 or 5000 packages. As long as it does what I want, the number of packages is totally irrelevant.
In this particular we’re talking about a collection of C++ libraries.
And, programming language libraries tend to be stable – apart from changes made to adapt to changes in the related programming language – which don’t happen too often anyway, for the simple reason that, if a language changes too often, the programming community will either revolt, go crazy or, reject the affected language …
Therefore, I suspect that, the collection of C++ lilbraries with the name “Abseil” will be fairly stable and therefore, updates will tend to be quite rare …