I may have just not noticed this before, but today when doing a zypper dup, after listing all of the actions that were going to take place, zypper also output “Backend: classic_rpmtrans”.
Is this something new, and if so, what does it mean? Are other backends available, and if so, what are they, what are the advantages and disadvantages of each and how do I change zypper backends?
My apologies if this has been present all along and I just hadn’t noticed until now.
Thanks!
A more trustworthy information source is the official libzypp and openSUSE documentation. No need to reference and advertise untested 3rd party tools which are not tested and distributed by openSUSE.
@sylerner2 openSUSE is developing the libzypp function even further. At the moment the “classic” mode is still used and standard. But you can already test future developements via experimental environmental variables. The environment variable are explained here:
https://doc.opensuse.org/projects/libzypp/HEAD/zypp-envars.html
The single rpm transaction backend is properly explained in the SLES documentation:
At the moment there are still some issues with this experimental feature, which can easily be seen by users which closely follows bugzilla. So only use it if you are able to troubleshoot update issues because of the use and are able and willing to properly report it via bugzilla.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.