- Zypp Development

How to get started with writing a library that uses libzypp?
by Srinidhi B 03 Mar '24

03 Mar '24

Hello List, I've tried to search the list archives, the openSUSE Wiki, and the developer documentation of libzypp. But couldn't find any recent content around my question. Hence, writing to the list. I need to implement a wrapper library over libzypp to fetch some simple software management information from the system like: * list of available updates - recommended - security * when was the last update installed (if possible) * is the system registered? * apply available updates (optional/future) But I'm not able to get started with a basic library. I've tried to go through the existing implementations. Most of the implementations start with calling `getZypp()` to acquire the lock. I'm not able to figure out what should be the next step. Is there any guide, blog post, document, or (newer) example that would help me understand the process? Should I be using libzypp directly or should I use PackageKit? I'm more comfortable writing in C rather than C++. Any recommendations and pointers would be greatly appreciated! Regards, Srinidhi.

4 3

Can zypper reveal what order it would install RPMs in?
by Brian Reichert 07 Dec '23

07 Dec '23

I have set of home-grown RPMs that I'm trying to use zypper to install. They all have misc 'Requires' directives that I hoped would drive what order they are installed. I'm running into challenges wherein zypper seemingly is not honoring them; some are going in out-of-order. Is there are way of having zypper reveal dependency loops, and how it expects to solve them, without committing to an installation pass? -- Brian Reichert <reichert(a)numachi.com> BSD admin/developer at large

2 1

How to handle vendor change when replacing a package
by Srinidhi B 07 Dec '22

07 Dec '22

Hello List, We are trying to replace a package in our product that provides the same functionality. We have made changes to our package as documented at - https://en.opensuse.org/openSUSE:Upgrade_dependencies_explanation - but when "zypper patch" command is run, we are receiving a vendor conflict. If we run "zypper patch --allow-vendor-change" then the package dependencies are handled correctly. Both the vendor names are set to be equivalent. Hence my question is, how can we handle the vendor conflict when replacing a package? Any insights here would be greatly appreciated. Regards, Srinidhi.

3 3

How to localize pattern description in SLES 15 SP3
by Gaurav Kumar 05 May '22

05 May '22

Hello Team, In SLES 15 SP3, how are the patterns and package descriptions translated? Until SLES 12 SP5, we were modifying the package package-translations by merging the po files for a translated language and creating the package-translations-$lang.mo files In SLES 15 SP3, I tried to do the same, merging all po files for a translated language and creating the package-translations-$lang.mo files. Now in SLES 15 SP3 during installation, if I change the language I am not getting the translated description for the patterns. I would really appreciate it if you could help us understand how to localize our patterns and package descriptions. Regards, Gaurav.

2 1

Re: Call for testers: zypp tech preview
by Michael Andres 01 Sep '21

01 Sep '21

On Wednesday 01 September 2021 14:54:59 Neal Gompa wrote: > Is there a way I can force the new librpm backend at compile-time? Not by now, but we can offer one. As a reminder: https://github.com/openSUSE/libzypp/issues/340 -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres, E&I, ma(a)suse.com, Phone: ++49 (0)911 - 74 053-0 +------------------------------------------------------------------+ SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg Germany, (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer +------------------------------------------------------------------+

1 0

Call for testers: zypp tech preview
by Benjamin Zeller 01 Sep '21

01 Sep '21

In the last months the zypp team worked on the basics for speeding up and modernizing the zypper/libzypp codebase. Some of those projects are now available to Tumbleweed and can be enabled and tested. Please keep in mind that those changes currently are tech previews, so zypper might crash or even break your system. New RPM transaction backend for zypper: Traditionally zypper executes rpm separately for each operation in a transaction. This requires some hacks and workarounds and is not fully compatible to running all operations in one single transaction. It is also a lot slower for big transactions ( like dup with many packages ). Therefore we have implemented a new backend that runs all operations in a single big transaction via librpm. It can be enabled by setting: ZYPP_SINGLE_RPMTRANS=1 in zyppers environment. Issues/Changes with ZYPP_SINGLE_RPMTRANS=1 zypper ... : - Changes how file conflicts work, since they are now executed by librpm we are not able to generate a callback to ask the user if the error should be ignored. In the presence of file conflicts, the transaction will report an error and will not execute unless --replacefiles is also used. - Currently there is also a issue that could potentially break your system in very specific preconditions. We put in a safety net that will protect you on Tumbleweed, however it still remains a issue for all systems that are PREUsrMerge and use the single transaction mode to apply the update. For example if you are on Leap and want to upgrade to Tumbleweed. This is the bug in question: https://bugzilla.suse.com/show_bug.cgi?id=1189788 - Breaks Yast / PackageKit softwaremanager if enabled system wide: Due to changes in the reporting , especially new reports, this would break the Yast software manager and Packagekit, so if you use one of the two technologies enable this feature explicitly per command: `env ZYPP_SINGLE_RPMTRANS=1 zypper dup`. New zypper HTTP backend: Another project we have been working on is parallelizing downloads, for this a new async downloader backend was implemented. While it currently won't have massive impact on performance due to the frontend code not requesting files asynchronously, it will do some additional mirror rating and as soon as we update the frontend code will bring more benefits. This can be enabled via setting the env var: ZYPP_MEDIANETWORK=1 If you find any bugs or issues please let us know. Preferably via: https://bugzilla.opensuse.org/ Product: openSUSE Tumbleweed Component: libzypp (or zypper if available) And please attach the /var/log/zypper.log to the bugreport. -- Benjamin Zeller<bzeller(a)suse.de> Systems Programmer SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuremberg, Germany Tel: +49-911-74053-0; Fax: +49-911-7417755;https://www.suse.com/ (HRB 36809, AG Nürnberg) Managing Director: Felix Imendörffer

2 1

ZYPP: Changes regarding project Lotus and the introduction of PTFs
by Michael Andres 10 Jun '21

10 Jun '21

Hi. (Available since libzypp-17.27.0) The introduction of PTFs brings a few changes which may affect the YAST package selector: A while ago we introduced retracted patches/packages. In some respects PTFs and retracted packages behave similar: Independently of their version they will never be considered as a candidate by the resolver unless one explicitly selects them. This is why we sort retracted packages always to the end of the list of available version of a package (in zypp:ui:Selectable). And we will now do the same with PTFs. While it's disfavored to select and install retracted packages, selecting a PTF, and deselecting it once the official patches contain the fix, will be common. Nevertheless they are no candidate in the 'normal' package selection, but must be selected explicitely. Due to this we introduced the term of 'blacklisted' packages. Blacklisted = Retracted || Ptf Blacklisted packages are those which are sorted to the end of the lists and are otherwise ignored by the resolver. You need to explicitly select them if you want them. According to the already available isRetracted() methods in sat::Solvable, PoolItem, ResObjects and hasRetracted(), hasRetractedInstalled() methods in ui::Selectable, we now introduced isBlacklisted(), hasBlacklisted(), hasBlacklistedInstalled() methods which cover any type of blacklisted items. And of course the corresponding *Ptf() methods, so you can tell why some item is blacklisted. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres, E&I, ma(a)suse.com, Phone: ++49 (0)911 - 74 053-0 +------------------------------------------------------------------+ SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg Germany, (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer +------------------------------------------------------------------+

2 1

Beware: libzypp code cleanup - YAST related legacy code
by Michael Andres 04 Mar '21

04 Mar '21

Hi, we found some YAST(?) related legacy code inside libzypp, which we will remove in the next version unless someone speaks up now: Introduced before 2005 during commit: A) Creation of /var/log/YaST2/config_diff_DATE.log files including the first 25 lines of config file diffs upon .rpmnew/.rpmsave creation. B) After a write to the config_diff_DATE.log file, /var/lib/update-messages/yast2-packagemanager.rpmdb.configfiles is opened and immediately closed again. We plan to drop that code. If you need something like this, we can provide you a callback sending the path of the 2 config files and you and create the diff as you need it.. C) zypp::RpmDb::setBackupPath called from within yast-pkg-bindings, src/Package.cc and available in ruby as Pkg.SetBackupPath(). This turns on creation of tarballs collecting the modified (binary) files of each package before updating it. This simple kind of backup was introduced to save self-compiled binaries/kernels before they were overwritten by rpm. Whoever compiled a linux kernel on a pre-Pentium architecture known, why this feature was valuable at that time. We will for now deprecate the method and disable the backup. However it may be that YAST still has has some 'Create backups during installation' button which triggers a call to this, please remove it. It's wasted time and disk space most probably. Thanks. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres, E&I, ma(a)suse.com, Phone: ++49 (0)911 - 74 053-0 +------------------------------------------------------------------+ SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg Germany, (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer +------------------------------------------------------------------+

1 0

[zypp-devel] JFYI: libyzpp 17.23.2 switches from using -std=c++14 to c++17
by Michael Andres 09 Mar '20

09 Mar '20

Hi. This switch alone should not have impact on the apps linking against libzypp. But Future APIs may make use of new stl types like std::string_view or the filesystem library, ..... You won't be able to use them if you stay with an older standard. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres, E&I, ma(a)suse.com, Phone: ++49 (0)911 - 74 053-0 +------------------------------------------------------------------+ SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg Germany, (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer +------------------------------------------------------------------+ -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: zypp-devel+owner(a)opensuse.org

1 0

[zypp-devel] HEADS-UP: TW20200229: libzypp-17.23.0 is broken... try to avoid using it.
by Michael Andres 03 Mar '20

03 Mar '20

[https://bugzilla.suse.com/show_bug.cgi?id=1165476] Package status computation regarding unneeded, orphaned, recommended and suggested is broken in libyzpp-17.23.0. Try to avoid using it and wait for the fix in libzypp-17.23.1. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres, E&I, ma(a)suse.com, Phone: ++49 (0)911 - 74 053-0 +------------------------------------------------------------------+ SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg Germany, (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer +------------------------------------------------------------------+ -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: zypp-devel+owner(a)opensuse.org

1 0