April 2008 - Zypp Development - openSUSE Mailing Lists

[zypp-devel] [SoC-student] libzypp HTTP download failover
by Gerard Farràs i Ballabriga 28 Apr '08

28 Apr '08

Hello :-) My name is Gerard Farràs, I am a graduate student in Computer Science at the UOC [1], in Barcelona, and I am interested, within the framework of the Google Summer code [2] in developing the project "Concept for libzypp doing failover when downloading packages from download.opensuse.org "[3]. Do you know if there are already many students interested in this project? Because, if any, I can even sign up in some other project... Moreover, I have already begun installing the development environment and doing a look at the code: Is this list the most appropriate for the doubts that arise me? Thank you! [1] http://www.uoc.edu [2] http://code.google.com/soc/2008/ [3] http://en.opensuse.org/Libzypp/Failover -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

7 18

[zypp-devel] libzypp-4.15.1: persistent soft locks
by Michael Andres 25 Apr '08

25 Apr '08

JFYI libzypp-4.15.1 - Prevent deselected or deleted items from being re-selected due to recommends (aka. persistent soft locks). Unlike hard locked, those items will be automatically selected if required. The list of soft locked items is stored in /var/lib/zypp/SoftLocks. The file is read when the target is loaded, and automatically updated on commit. It's not a configfile, that's why it is not in /etc/zypp. Maybe we need some switch to turn it off. -- 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] keyring callback changes
by Jano Kupec 25 Apr '08

25 Apr '08

Hi all, if anyone familiar with current repository download code in libzypp can spare some time and review https://bugzilla.novell.com/show_bug.cgi?id=366467#c10 i would be thankful for their opinions. Just read the comment and the following patch. The problem: the patch is about the keyring callbacks and passing some "context" info of the gpg keys in question to the callbacks. (the patch contains also merging of askUserToTrustKey() and askUserToImportKey() into one, but you can ignore that). Thanx, jano -- 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] Re: [zypp-commit] r9774 - /trunk/zypper/src/zypper-utils.cc
by Michael Matz 25 Apr '08

25 Apr '08

Hi Josef, On Tue, 22 Apr 2008, jreidinger(a)svn.opensuse.org wrote: > Author: jreidinger > Date: Tue Apr 22 12:07:08 2008 > New Revision: 9774 > > URL: http://svn.opensuse.org/viewcvs/zypp?rev=9774&view=rev > Log: > move replace_all to zypp and change inplace replace to gsub, which have > better performance Your own testcase said something else: zypper gsub boost user time: 769 system time: 0 jano replace_all boost user time: 689 system time: 0 boost replace_all boost user time: 8626 system time: 6 gsub is slower. That's also expected, as it needs to copy the whole string. Ciao, Michael. -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

3 7

[zypp-devel] zypp-refresh-wrapper (new)
by Jan Kupec 24 Apr '08

24 Apr '08

Hi, so far, zypp-checkpatches-wrapper has been used in the updater applets to refresh repos (needs root access) and check for patches. This solution was not too flexible though and as there came a need to check also for package updates, Thomas added the xml-updates command to zypper directly. But that solution lacked the ability to do the suid refresh. So with Thomas we agreed that we'll try a different approach: drop zypp-checkpatches-wrapper, use a new refresh-only suid wrapper and once called, use zypper query commands directly as normal non-root to do whathever queries you like (zypper --xmlout list-updates in the case of the updater applets). The zypp-refresh and zypp-refresh-wrapper is fairly general thing then, so my question is whether we should package it in zypper package or directly in the libzypp package. I'd also appreciate opinions on this solution. @Security: zypp-refresh-wrapper will be much simpler than the previous zypp-checkpatches-wrapper, so this should be an increase in security, too. Cheers, jano -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

4 5

[zypp-devel] libzypp-4.15.0: "name[.arch][ op edition]" dependencies
by Michael Andres 24 Apr '08

24 Apr '08

JFYI With libzypp-4.15.0 class Capability allows to create dependencies restricted to a specific architectue. The format for such dependency string is: "name[.arch][ op edition]" Example: MIL << sat::WhatProvides( Capability("amarok") ) << endl; MIL << sat::WhatProvides( Capability("amarok.i586") ) << endl; MIL << sat::WhatProvides( Capability("amarok.x86_64") ) << endl; MIL << sat::WhatProvides( Capability("amarok.sparc") ) << endl; Will print either all providers of amarok, or only those with architecture i586 or x86_64 (2){ (744)amarok-1.4.9.1-4.x86_64(openSUSE-11.0-x86_64) (3641)amarok-1.4.9.1-4.i586(openSUSE-11.0) } (1){ (3641)amarok-1.4.9.1-4.i586(openSUSE-11.0) } (1){ (744)amarok-1.4.9.1-4.x86_64(openSUSE-11.0-x86_64) } (0){} -- 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

Re: [zypp-devel] libzypp-4.6.1: Allow prioritizing repos.
by Jan Engelhardt 23 Apr '08

23 Apr '08

In http://lists.opensuse.org/zypp-devel/2008-03/msg00137.html you write: >Jan Kupec wrote: >>Jan Engelhardt wrote: >>>If you default to 50, you only have 50 possible repositories below it >>>if an unsigned integer is used. And if you use a signed integer, just >>>default to 0. >> >>IMO 99 (least) is a safe default. You can always raise it, and if you >>really have to, you can as well use values below 99 [100,]. That's not >>yum conform, but our implementation will not hind you. > >YUM: >[..] >to a repository entry, where /N/ is an integer number from 1 to 99. The >default priority for repositories is 99. The repositories with the >lowest priority number have the highest priority. >[..] zypp implementing the yum way just leaves me speechless, it is just WRONG. Why limit the priority value to 1..99? Why make it hard to figure out what's low and high? smart did it the right way, where a higher (greater) number means higher priority --- simple mnenomic. -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

5 8

[zypp-devel] Re: suggestion from packaging list about parallelizing install
by Peter Poeml 23 Apr '08

23 Apr '08

Hi, I'm picking this up from opensuse-packaging, where I'm not subscribed, so I cannot follow up there, but it fits better on the zypp-devel list anyway. I wanted to give my feedback about a feature which was suggested. In suse.lists.opensuse-packaging, Lukas wrote: >> Are a few minutes installation time really that important? Sure it's >> 50% according to your numbers but it's still minutes. >> Has anyone actually tried to optimize the traditional installation >> method? Like preloading rpms or reorder them on the medium to avoid >> seeks on the cdrom? > Reordering RPMs should be done according to dependencies but libzypp=20 > solver can 'randomize' them a bit ;) > > There are some more important features that would make the traditional=20 > installation method faster: > > * Downloading and Installation in more threads > (installation of RPM doesn't block downloading) In principle a fine idea, and I had something like that in mind for a long time myself, however: To *reliably* avoid brokenness of the system in case the download can't complete (network outage, packages don't match the metadata or similar), it is *obligatory* to me (admin viewpoint) to first completely download all packages, before starting to install them. Therefore I prefer the "yum" method: download all packages, then try (in a test transaction) whether updating/installing them works, then apply. For these reasons, I would be careful with parallel downloads. Of course, if libzypp doesn't do that anyway, it could at least download the next package while still installing another one. Would be a nice improvement for our users. > * Installing more RPMs at once. > (a lot of small RPMs have to initialize RPM database, lock it, > unlock it..., and again...) This is actually what yum does. Peter

2 1

[zypp-devel] Feedback concerning the new SAT-solver
by Stefan Schubert 23 Apr '08

23 Apr '08

Harald König is one of our "oldest" beta testers and known for VERY strange test environments :-) -------- Original-Nachricht -------- Betreff: [Bug 304266] Dependency checking nightmare Datum: Tue, 22 Apr 2008 11:35:07 -0600 (MDT) Von: bugzilla_noreply(a)novell.com An: schubi(a)novell.com https://bugzilla.novell.com/show_bug.cgi?id=304266 User koenig(a)linux.de added comment https://bugzilla.novell.com/show_bug.cgi?id=304266#c25 --- Comment #25 from Harald Koenig <koenig(a)linux.de> 2008-04-22 11:35:07 MST --- (In reply to comment #7 from Stefan Schubert) > So I suggest, that we will try it with the next beta again. > Feel free to reopen the bug if you are still not satisfied with the solver > performance. And give me a new testcase again. > Your machine is a nice "grass play area" to find such things. :-) back to the old theread "update depencecy checking sux" : update -- last weekend I've updated a copy of my 10.3 x64_64 real-work notebook system form 10.3 (current) to 11.0-beta using DVD5 image and it really worked like a charm!!! which means, only some 10 dependency conflicts (plenty of forein RPMs e.g. from packman, and own RPMs with different versions/requirements) which have been resolved in ~5 turns within less than 10 minutes -- GREAT !!!! (finally, after update nightmares with 10.2 and 10.3:-((( I'm _really_ impressed about the new packaging/dependency system, thanks! unfortuneately my old AMD1200 is out of operation right now (needed some "spare" parts -- maybe it's back for beta-2, cross fingers and stay tuned ;-)) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. -- ******************************************************************************* Stefan Schubert SUSE LINUX GmbH - Maxfeldstrasse 5 - D-90409 Nuernberg, Germany e-mail: schubi(a)suse.de ------------------------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- 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] zypper odds
by Jan Engelhardt 22 Apr '08

22 Apr '08

Hi, I have cleaned the rpm db (manually - since zypper did not let me do it) from any packages I do not want, and given that clean slate, let's begin there: beta1:/home/salestv # zypper in sensors Reading installed packages... The following NEW packages are going to be installed: yast2-trans-en_US yast2-registration suseRegister opensuse-manual_en bundle-lang-common-en bash-completion uuid-runtime sensors readline-doc perl-doc perl-TimeDate orbit2 openobex obex-data-server nss-mdns limal-ca-mgm-perl limal-ca-mgm libtasn1-3 libtasn1 libsoup-2_4-1 libsoup libsensors4 libgvfscommon0 libgphoto2 libgnutls26 libgio-2_0-0 libfuse2 libexif libavahi-glib1 libavahi-core5 libavahi-common3 libavahi-client3 libarchive2 gvfs-fuse gvfs-backends gvfs gtk2-branding-upstream gnome-keyring gconf2 fuse ft2demos checkmedia bluez-libs bash-doc avahi alsa-plugins alsa-oss PolicyKit-doc Overall download size: 29.1 M. After the operation, additional 61.5 M will be used. Continue? [YES/no]: No way does sensors need documentation. Why is this counterproductive setting enabled, and where can it be changed? -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

6 7