September 2009 - Zypp Development - openSUSE Mailing Lists

[zypp-devel] Commit download policy to use as default.
by Rastislav Krupanský 01 Oct '09

01 Oct '09

Hi. I've just updated libzypp to 6.17.2-9.6.i586, which already includes options for the ability to download all packages first and then install. Are they implemented and can we start testing all possibilities for YaST by editing /etc/zypp/zypp.conf? ## Commit download policy to use as default. ## ## DownloadOnly, Just download all packages to the local cache. ## Do not install. Implies a dry-run. ## ## DownloadInAdvance, First download all packages to the local cache. ## Then start to install. ## ## DownloadInHeaps, Similar to DownloadInAdvance, but try to split ## the transaction into heaps, where at the end of ## each heap a consistent system state is reached. ## ## DownloadAsNeeded Alternating download and install. Packages are ## cached just to avid CD/DVD hopping. This is the ## traditional behaviour. ## ## <UNSET> If a value is not set, empty or unknown, we pick ## some save default. ## ## commit.downloadMode = I just want to be sure. Thanks a lot. -- S pozdravom / Best regards, Rasto -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

2 1

[zypp-devel] Re: Improvement of zypper
by Jano Kupec 30 Sep '09

30 Sep '09

Hi! On 09/30/2009 11:08 AM, Cecil Westerhof wrote: > Jano, > > I was the one 'complaining' about zypper. ;-] > You said you could use some help with improving zypper. How could I > help? It depends on what you want and are able to do. There are lots of ways to help. From fixing bugs, to developing features, giving ideas how to do a new feature, testing & sending us feedback, updating the zypper wiki, translations, and various other little stuff. Zypper is written in C++ and is stored in a git repository, so if you're familiar with these, you can jump into the development right away :O) Or you can propose how the overall install progress should look like - it's not easy to come up with some good looking and informative way to do this in a terminal, that would also be reasonably easy to implement (e.g. work with the limitation that only the very last line can be overwritten). See also http://en.opensuse.org/Zypper/Development http://en.opensuse.org/Zypper/Bugs_For_Adoption But you mentioned you like to use YaST. Are you sure you want to spend your time on a tool that you don't use all the time? :O) But if you're a good C++ developer, you can also hack libzypp - the library that powers both YaST and zypper. Let us know if something catches your interest. > I send it to you, because I get a bounce on zypp-devel(a)opensuse.org. Hmm.. it seems the severs in Nuremberg have some problems. CCing the list, just in case it works now. -- cheers, jano Ján Kupec YaST team ---------------------------------------------------------(PGP)--- Key ID: 637EE901 Fingerprint: 93B9 C79B 2D20 51C3 800B E09B 8048 46A6 637E E901 ---------------------------------------------------------(IRC)--- Server: irc.freenode.net Nick: jniq Channels: #zypp #yast #suse #susecz ---------------------------------------------------------(EOF)---

1 0

[zypp-devel] 6.17.1: New method ui::Selectable::updateCandidateObj
by Michael Andres 23 Sep '09

23 Sep '09

Hi! I added a new method ui::Selectable::updateCandidateObj. As you know it's not sufficient to simply look for an available package with higher version, when looking for an update candidate. There are more policies to respect, like the ones for arch and vendor changes. Also repo priorities may influence the result. updateCandidateObj will return you whether the candidateObj matches the active solver policies and has a greater version, and no PoolItem otherwise. So if the UI wants to suggest Selectables that could be updated, it could suggest the ones providing an updateCandidateObj, and not all where the candidate has 'just' a greater version. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma(a)novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

1 0

[zypp-devel] Power Outage
by ml-admin＠opensuse.org 11 Sep '09

11 Sep '09

Broadcast message from ml-admin(a)opensuse.org (/dev/pts/0) at 07:30 GMT ... The system is going down for halt NOW! -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

1 0

[zypp-devel] yum vs zypp performance
by Zhu, Peter J 10 Sep '09

10 Sep '09

Hi, I did a yum vs zypp performance evaluation against a yum repository. Just like what http://duncan.mac-vicar.com/blog/archives/309 suggested, zypper is better than yum if I just stop after yum/zypper ask user if do a really installation/update. Summary: yum make dbcache 14.985s zypper ref -B 9.435s yum install make 6.935s zypper in make: 1.247s yum upgrade 17.486s zypper update: 1.795s But if I did a real installation/update with 57 packages in one time, zypper performance is worse than yum. Yum just needs 5m38s but zypper needs 6m40s. I can see some difference is that yum would try download all the packages at first and then install them in local system while zypper would do an iteration of retrieve/install one by one that should be the root cause. Any comments/ Thanks, Peter -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

9 12

[zypp-devel] unable to run zypper because of solv-file error
by Zhu, Peter J 10 Sep '09

10 Sep '09

Hi, I tried run zypper with yum repo in a moblin system but always failed. I used zypper 1.2.2 and libzypp 6.11.4, very new. At first stage, it always failed with "zypper refresh". After debugging, I found it's because libzypp/zypp/media/proxyinfo/ProxyInfoSysconfig.cc doesn't initialize the _enabled=false which got it always try to add '--http-proxy=' to call augeas. After fixing this, it can refresh cache successfully. But as I tried to "zypper in cmake", it always complains that "Error reading solv-file: /var/cache/zypp/solv/@System/solv". And I found the solv file is VOID(has zero bytes). Any idea why this happens? Or Should I go back to an old version? Look forward to your suggestions Peter -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

3 2

[zypp-devel] Re: FW: Bug maybe? zypper lu
by Duncan Mac-Vicar Prett 07 Sep '09

07 Sep '09

On Monday 24 August 2009 21:32:17 Vickers, Mark wrote: > What is the cruft before the work "Repository" > > zypper lu |less > > > Reading installed packages... > Patches > > ESC[?1034hRepository | Name | Version | Category | Status > -----------------+------+---------+----------+------- > Updates for 11.0 | hal | 620 | security | Needed > > > zypper --version > zypper 0.11.11 Color output your terminal does not seem to support. I have the same problem always with git diff ;-) -- Duncan Mac-Vicar P. - Engineering Manager, YaST SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

4 5