- Zypp Development

[zypp-devel] enforce install from same src.rpm
by Olaf Hering 10 Feb '17

10 Feb '17

If a given package is provided by more than one repo, and if that package has subpackages, then it can easily happen that one of the subpackages comes from repoA while another one comes from repoB. That happens because the rpm dependencies are satisfied via SONAME for example. But each package might be configured and built differently, and if the subpackages link and/or communicate with each other the ABI may differ. In practice this happens with the ffmpeg and gstreamer packages from Leap/Tumbleweed and Packman/VideoLan. The result is a misbehaviour at runtime. The easy and obvious way is a 'zypper dup --from <repo>' to resolve that. No code changes needed for that. But I wonder if libzypp has enough info from the repository data to enforce that each subpackage comes from the same vendor:src.rpm. Olaf

2 1

[zypp-devel] GPG signed rpm-md repositories with subkeys?
by Joe Damato 03 Nov '16

03 Nov '16

Greetings: I was confused earlier today when trying to add a GPG-signed rpm-md type repository to my system. I noticed that zypper was listing the repository as not being signed. zypper refresh was telling me that the repository was signed with an unknown key and zypper lr was listing the repository as not supporting repo_gpgcheck. After some digging around the libzypper source (14.43.0) on my system (openSUSE 13.2) I believe I've tracked down the issue. The call to publicKeyExists in KeyRing::Impl::verifyFileSignatureWorkflow checks if the repomd.xml.asc signature's key ID is known. If the repomd.xml.asc was signed with a subkey of a GPG key (instead of a primary key), this check will fail even though the call to VerifyFile would succeed. Is this a known issue? Not sure what the best solution is for zypper, but one potential solution would be to simply ask GPG to verify the signature using the general keyring without first checking if a matching key id is in the keyring. The logic in verifyFileSignatureWorkflow can then be simplified as GPG would figure out if there's a matching key and this issue would be avoided. Thanks, Joe -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: zypp-devel+owner(a)opensuse.org

2 1

[zypp-devel] refreshed key is downloaded but not used
by Olaf Hering 11 Aug '16

11 Aug '16

What does it take to make use of an updated key? Looks like there are conditions which prevent zypper from using the updated key. See http://lists.opensuse.org/opensuse-buildservice/2016-08/msg00023.html Olaf

2 2

[zypp-devel] Re: [opensuse-buildservice] Enabling (only) Opensuse UPDATE repo breaks "zypper se" command output formatting
by lists＠ssl-mail.com 31 Jul '16

31 Jul '16

On Sat, Jul 30, 2016, at 12:52 PM, Andreas Stieger wrote: > The issue with your exact symtoms caused by calibre metadata is fixed in > the update repo since 21:21 CEST. Please try again. Just tried zypper clean --all zypper ref zypper se -s on several machines, and both at main, and alternative repo mirrors. All of them are still "padding" output like crazy. Maybe needs some more time to propagate across the repos & mirrors? Is there any zypp(er).conf that we can do to avoid the problem this/next time? -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: zypp-devel+owner(a)opensuse.org

1 1

[zypp-devel] Re: [opensuse-buildservice] Enabling (only) Opensuse UPDATE repo breaks "zypper se" command output formatting
by lists＠ssl-mail.com 30 Jul '16

30 Jul '16

On Sat, Jul 30, 2016, at 12:06 PM, Bruno Friedmann wrote: > On samedi, 30 juillet 2016 11.38:09 h CEST lists(a)ssl-mail.com wrote: > > the 'padded' output can bee seen here > > > > http://paste.opensuse.org/aa65f0b6 > > Confirmed on Leap, but still work on TW. > > A bugreport should be created, can you open one ? I read the bug report Andres referenced and the fix SR submitted to Factory (https://build.opensuse.org/request/show/415231) Isn't that just about a single package's problem? calibre? What I see is for any / all 'zypper se -s' attempts when the UPDATE repo is ENABLED. I guess I don't understand the fix, or if what I'm seeing is a different problem. -- 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] Enabling (only) Opensuse UPDATE repo breaks "zypper se" command output formatting
by lists＠ssl-mail.com 30 Jul '16

30 Jul '16

I'm running Opensuse Leap. If I disable the zypper Opensuse update repo enabled=0 baseurl=http://download.opensuse.org/update/leap/42.1/oss/ And exec for example zypper se -s | grep letsencrypt It works | letsencrypt.sh | package | 0.1.0-4.1 | noarch | opensuse-security | letsencrypt.sh | srcpackage | 0.1.0-4.1 | noarch | opensuse-security | letsencrypt.sh-apache2 | package | 0.1.0-4.1 | noarch | opensuse-security | letsencrypt.sh-nginx | package | 0.1.0-4.1 | noarch | opensuse-security But if I ENable it enabled=1 baseurl=http://download.opensuse.org/update/leap/42.1/oss/ The output is now padded with tens of thousands of spaces for each line I'm not gonna paste the output here, but zypper se -s | grep letsencrypt If > DISable the repo zypper se -s | grep letsencrypt > tmp1.txt > ENable the repo zypper se -s | grep letsencrypt > tmp2.txt you can see the difference in size -- 632 bytes vs 40K bytes! -rw-r--r-- 1 root root 632 Jul 30 11:15 tmp1.txt -rw-r--r-- 1 root root 40K Jul 30 11:08 tmp2.txt This is ONLY with this specific 'update' repo. All other repos work either way, enable or disabled. It's reproducible on a bunch of different machines here. -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: zypp-devel+owner(a)opensuse.org

1 1

[zypp-devel] Reset [Erase all PoolItems in] ResPool (sat::pool)
by Shalom Ray 11 Jul '16

11 Jul '16

Hello, I'm Shalom working on one-click-installer as part of GSoC, 2016. Following is a problem I've encountered while installing packages using Libzypp API. A bit of background information: OCI, in order to *display* information about packages listed in its specification file (.ymp), loads specific repository(ies) temporarily and uses PoolQuery API to query meta-data such as installedSize(), repository(), and so on. >> scoped_ptr<RepoManager> ZypperUtils::s_repoManager( new RepoManager( Pathname( "/tmp" ) ) ); >> initListedRepos() //loads only specific repos into pool/cache >> PoolQuery q; >> q.addKind( ResKind::package ); >> q.addAttribute( sat::SolvAttr::name, packageName ); >> q.setMatchExact(); >> return packageObject( q ); While installing packages, ResPool contains the temporary PoolItems which are no longer needed alongside the required PoolItems (from enabled repos). Following is the output before loading the enabled repositories to resolve missing dependencies of a package - +++++++++++++++ init pool +++++++++++++++++++++++ ResPool sat::pool(SERIAL(1))[356]{1repos|354slov} ResObjects: 354 package: 332 pattern: 1 srcpackage: 21 =+++++++++++++++++++++++++++++++++++++++++++++++= It is supposed to be +++++++++++++++ init pool +++++++++++++++++++++++ ResPool sat::pool(SERIAL(0))[2]{0repos|0slov} ResObjects: 0 =+++++++++++++++++++++++++++++++++++++++++++++++= to ensure no unwanted conflicts. Problem: So, is there a way to reset the sat pool before loading the enabled repos? I'm using the following code but wondering if there's a much better way to do it. >> Repository repo = s_zypp->pool().reposFind( "temp" ); // temp (alias) is the repo loaded into pool for temporary use >> repo.eraseFromPool(); Have a nice day. Best regards, Shalom -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: zypp-devel+owner(a)opensuse.org

2 1

[zypp-devel] Bug or wanted behaviour? zypp isn't installing requirements of metapackages if requirement cannot be fulfilled
by Daniel Spannbauer 24 May '16

24 May '16

Hello, I don't know if this is a bug or a wanted behaviour of zypper.... I'm building a meta-package which only has requirements and a small txt-file. So: test-pattern.rpm requires package a.rpm, b.rpm and c.rpm. Package b.rpm needs package e.rpm which is not available cause it isn't available through a repository. Zypper installes package a.rpm and c.rpm, but not b.rpm, it doesn't even complain about it. I would expect that zypper is claiming about the unfulfilled requirement of b.rpm and would ask what to do. Or am I totally wrong? Regards Daniel -- Daniel Spannbauer Systemadministration marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11 Rechbergstr. 4-6, D 87727 Babenhausen Mobil +49 171 4033220 http://www.marco.de/ Email ds(a)marco.de Geschäftsführer Martin Reuter HRB 171775 Amtsgericht München -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: zypp-devel+owner(a)opensuse.org

2 1

[zypp-devel] RPM database is inconsistent when a running instance of zypper was interrupted
by 李明 03 May '16

03 May '16

Hi , I recently encountered a problem using zypper install my package. I hope to get your help, thank you very much. Product: SUSE Linux Enterprise Server 11 SP3 (x86_64) Other Software and Versions Being Used: zypper-1.6.327-9.9 rpm-4.4.2.3-37.56.1 rpm-python-4.4.2.3-37.46.7 libzypp-9.38.8-0.7.1 Steps to reproduce: step 1. I build a custom RPM package, then build a zypper repo. custom RPM name: upg-client-1.0.0-1.x86_64 zypper repo: zypper ar file:///usr/src/packages/RPMS/ myrepo zypper refresh step 2. Write two Bash scripts for testing (contexts of these scripts shown in Additional Information), one for installing upg-client RPM and another for reproduce this problem. step 3. Run installing script, then run reproduce script. When the installing script is stopped, we can see that "rpm -qa |grep upg-client " and "rpm -q upg-client" is inconsistent. Additional: [script for installing upg-client RPM:] #!/bin/bash LOG_FILE=/home/cps/auto_run_new_2.log count=1 touch $LOG_FILE while true; do rpm -q upg-client if [ $? -ne 0 ];then echo "[`date`] upg-client-1.0.0-1.x86_64 not install, now install" >> $LOG_FILE zypper -n --gpg-auto-import-keys --no-gpg-checks in upg-client-1.0.0-1.x86_64 if [ $? -ne 0 ];then echo "[`date`] install upg-client-1.0.0-1.x86_64 failed" >> $LOG_FILE # exit 1 fi fi echo "==============sleep=================" echo "[`date`] =======sleeping 6=======" >> $LOG_FILE sleep 3 XXX=`sudo rpm -qa| grep upg-client` YYY=`sudo rpm -q upg-client` if [ x$XXX = x$YYY ];then echo "[`date`] auto:$count======ok======= " >> $LOG_FILE ((count++)) else if [ x$XXX = x ];then echo "[`date`] auto:$count======ok=======" >> $LOG_FILE ((count++)) else echo "[`date`] error" exit 1 fi fi echo ===remove======= zypper -n --gpg-auto-import-keys --no-gpg-checks remove -u upg-client-1.0.0-1.x86_64 if [ $? -ne 0 ];then echo "[`date`] uninstall upg-client-1.0.0-1.x86_64 failed" >> $LOG_FILE exit 1 fi done =============Dividing line================ [script for reproduce the problem:] #!/bin/bash while true do #find child rpm process pid=`ps aux| grep /var/cache/zypp/packages/myrepo/x86_64/upg-client-1.0.0-1.x86_64.rpm | grep '\-U' | awk '{print $2}'` if [ x$pid != x ];then kill -9 $pid echo yes else echo no fi sleep 0.5 done =============Dividing line================ [SPEC of upg-client package, we can run "dd if=/dev/zero of=./xxx bs=10M count=1" to create file "xxx"] Name:upg-client Summary:TEST Version:1.0.0 Release:1 Group:NCU License:GPL Vendor:NCU Source0: upg-client-%{version}.tar.gz BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root %description upg-client %prep %setup -q -n %{name}-%{version} %install file_list=$(find .) rm -rf %{buildroot} for file in $file_list do if [ -d $file ];then install -d %{buildroot}/$file elif [ -f $file ];then install -c -m 755 $file %{buildroot}/$file fi done %post %files %dir /usr/local/bin/upg-client /usr/local/bin/upg-client/xxx %changelog * Tue Nov 17 2015 EDU - test

2 1

[zypp-devel] [Modularity] Module metadata proposal (fwd)
by Michael Schroeder 16 Apr '16

16 Apr '16

FYI: ----- Forwarded message from Petr ??abata <contyk(a)redhat.com> ----- > Good news, everyone, > > the first draft of the module metadata format is now available > for you to comment on. We've decided to go with YAML so it > should be fairly readable. You can view the latest version here: > > https://pagure.io/fm-metadata/blob/master/f/metadata.yaml > > What is is: > The file defines basic properties of the module such as its > name, version, description, licenses, references to upstream > documentation or its content. Currently only RPM content > is supported but this can be easily extended in the future. > The metadata file is meant as both input and output of the > module build process (don't confuse it with package build > process), with various tools adding various new data to it, > such as vendor and buildsystem identifiers, timestamp of the > build, autogenerated lists of licenses or whatever you can > think of (well, maybe not whatever but close). The output is > then placed in the generated repository, container image or > any other module deliverable and can be processed by tools and > services consuming and delivering modules. > > What is isn't: > It's not a SPEC file. It doesn't say how to build individual > packages. And it's not a simple comps group either. It can > and does provide lots more additional data. > > It's not perfect and it's constantly evolving. Please, do > comment, ask questions and suggest improvements. > > Thanks, > P Cheers, Michael. -- Michael Schroeder mls(a)suse.de SUSE LINUX GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: zypp-devel+owner(a)opensuse.org

2 1