April 2008 - Zypp Development - openSUSE Mailing Lists

[zypp-devel] New solver call : resolveQueue
by Stefan Schubert 11 Mar '09

11 Mar '09

Hi, apart from the solver call "resolvePool" ( collect all transactions from the pool, solving this transactions and writing the result back to pool) the solver can work off a given request queue too: /** * Resolve package dependencies: * * The solver works off the given queue and writes back the solution * to pool. * * Returns "true" on success (i.e., if there were no problems that * need user interaction) and "false" if there were problems. In * the latter case, use problems() and later applySolutions() * below. **/ bool resolveQueue (solver::detail::SolverQueueItemList & queue); The queue can have elements which are described in the following classes: base class: SolverQueueItem.h SolverQueueItemDelete.h SolverQueueItemInstall.h SolverQueueItemLock.h SolverQueueItemInstallOneOf.h SolverQueueItemUpdate.h Known problems: - The update and InstallOneOf request does not work correctly. - The error messages are too abstract now for the user. (Jano, you can start implementation now :-) ) Greetings Stefan -- ******************************************************************************* 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

6 12

[zypp-devel] Locks wiki
by Josef Reidinger 06 May '08

06 May '08

Hi, I create wiki page[1] about locks format. Please fill info about solvattr which i don't know. One interesting thing is, that locks accept everything from knowid from sat-solver, because I pass string with attribute to poolquery and poolquery fill this string to dataiterator which know it. so also much undocumented attributes work (e.g. provides or evr). Pepa [1] http://en.opensuse.org/Libzypp/Locksfile -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

5 10

[zypp-devel] upgrade - removing unmaintained packages?
by Ladislav Slezak 06 May '08

06 May '08

Hi all, zypp::UpgradeOptions() had 'delete_unmaintained' flag for removing unmaintained packages. But it's gone now. Why? How can we remove unmaintained packages now? The reason is: "gcc42 is explicitly not obsoleted, but only people that explicitly want to keep it should be able to do so" and "and any kind of package obsolete would do hard erase it" Coolo suggested adding a fixed list ("gcc42"...) somewhere into yast (probably into control.xml file). But maintaining a fixed list is wrong solution IMO... Should I implement the behavior in pkg-bindings level or is it possible to put it back to libzypp? What did the option do exactly? Thanks in advance Lada -- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

4 7

[zypp-devel] libzypp download failover - server side implemented
by Dr. Peter Poeml 02 May '08

02 May '08

Hi, I have implemented a text mirror list for libzypp, which is returned for requests containing the rfc 2295 header shown below. I slightly changed the format. The returned mime type is application/mirrorlist-txt. A Vary header is set on the header for proper caching. % curl -sH "Accept-Features: mirrorlist-txt" 'http://download.opensuse.org/distribution/10.3/repo/oss/suse/repodata/prima…' | head -6 # mirrorlist-txt version=1.0 # url baseurl_len mirrorid region:country power http://ftp.tu-chemnitz.de/pub/linux/opensuse/distribution/10.3/repo/oss/sus… 45 39 EU:de 100 http://download.uni-hd.de/ftp/pub/linux/opensuse/distribution/10.3/repo/oss… 49 41 EU:de 100 http://opensuse.intergenia.de/distribution/10.3/repo/oss/suse/repodata/prim… 30 75 EU:de 100 http://widehat.opensuse.org/distribution/10.3/repo/oss/suse/repodata/primar… 28 97 EU:de 50 I have updated http://en.opensuse.org/Libzypp/Failover accordingly. Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development

2 1

[zypp-devel] new zypper search?
by Jan Kupec 02 May '08

02 May '08

2 5

[zypp-devel] Re: [zypp-commit] r9893 - in /trunk/zypper: doc/zypper.8 src/zypper-main.cc src/zypper-main.h src/zypper-utils.cc src/zypper.cc src/zypper.h
by Michael Matz 30 Apr '08

30 Apr '08

Hi Jano, On Tue, 29 Apr 2008, jkupec(a)svn.opensuse.org wrote: > + line_read = ::readline ("zypper> "); One remark that came to my mind while reading the patch: gdb is another program that uses readline to handle its input, resembling shell input. It uses this as prompt: (gdb) <CURSOR> (i.e. "(gdb) ", including the separating space). I kind of like this prompt because it doesn't use any character I'm used to seeing in normal shell prompts (I'm aware of people changing their $PS1, but they often don't use parentheses). In particular the '>' character is sometimes used to introduce the normal shell command prompt, so 'zypper> ' "feels" like a shell prompt when I'm on a machine called zypper. That's partly by design of course, after all it _is_ a prompt; it's just that you can't give your normal shell command into it (not even things like "$((1 + 2))") so it seems sensible to differentiate between them also by slight visual differences. I know that this certainly makes bugzilla reports easier to read when the commenter copy&pastes something from the terminal which includes such prompts; it's clearly distinguishable from shell. So perhaps it would be a nice convention to make all prompts from programs (in comparison to a shell) read "(programname) ". zypper could be used to hammer such convention into users brains :-) What do you think? Ciao, Michael. -- 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] zypp::PoolQueryResult - Helper class to collect (not only) PoolQuery results.
by Michael Andres 29 Apr '08

29 Apr '08

Added class zypp::PoolQueryResult /** Helper class to collect (not only) PoolQuery results. * * \note Unfortunately PoolQuery::begin might throw. Exceptions * are caught and the query is treated as empty. * * PoolQueryResult maintains a set of sat::Solvable. You can * add/remove solvables to/from the set defined by: * * \li a single sat::Solvable * \li a single PoolItem * \li a PoolQuery * \li an other PoolQueryResult * \li any iterator pair with value_type sat::Solvable * or PoolItem or PoolQuery or any type that fits * operator+=. * * The class is a sat::SolvIterMixin, so you can iterate the result * not just as sat::Solvable, but also as PoolItem or * ui::Selectable. * * \code * // Constructed from PoolItem iterator pair * PoolQueryResult result( pool.byKindBegin<Package>(), pool.byKindEnd<Package>() ); * MIL << result.size() << endl; * * { * // Removing a PoolQuery result * PoolQuery q; * q.addAttribute( sat::SolvAttr::name, "[a-zA-Z]*" ); * q.setMatchGlob(); * result -= q; * MIL << result.size() << endl; * } * MIL << result << endl; * * // Removing a range of sat::Solvables * sat::WhatProvides poviders( Capability("3ddiag") ); * result -= PoolQueryResult( poviders.begin(), poviders.end() ); * * // packages not starting with a letter, except 3ddiag * MIL << result << endl; * \endcode */ -- 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] new PoolItem/ResObject call isRelevant()
by Stefan Schubert 29 Apr '08

29 Apr '08

Hi, this is interesting for all UIs concerning package handling. This call gives an answer to "Is this PoolItem/ResObject interesting for user and should it be shown ?" /** Returns true if the solvable is relevant which means e.G. for patches * that at least one package of the patch is installed. */ bool isRelevant() const; Greetings Stefan -- ******************************************************************************* 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

4 6

[zypp-devel] (kein Betreff)
by haenel 29 Apr '08

29 Apr '08

-- 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] r9847 - in /trunk/sat-solver/src: repo.h repodata.c
by Michael Schroeder 28 Apr '08

28 Apr '08

On Sun, Apr 27, 2008 at 06:32:40PM -0000, matz(a)svn.opensuse.org wrote: > Author: matz > Date: Sun Apr 27 20:32:40 2008 > New Revision: 9847 > > URL: http://svn.opensuse.org/viewcvs/zypp?rev=9847&view=rev > Log: > I promised this to Jano; skipping kinds in matcher when a flag is specified. EEEk! Don't promise such things! There is no "kind" in the satsolver... Micha. -- Michael Schroeder mls(a)suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- 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] [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

[zypp-devel] zypper 11.0-7.1 Backport
by Günther J. Niederwimmer 22 Apr '08

22 Apr '08

Hello, is this known ? zypper up -t package Reading installed packages. No additional space will be used or freed after the operation. Continue? [YES/no] : don't correct working ?: It can't find / install the packages that listed from zypper lu -t package -- mit freundlichen Grüßen / best Regards Günther J. Niederwimmer -- 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] Test of boost::replace_all
by Josef Reidinger 22 Apr '08

22 Apr '08

I use in some place boost function replace all. I see in zypper, that this function jano implement. So I test which is faster and also contain gsub from zypp String which is not in place (so must copy result). Due to result I add janpo's implementation to zypp and replace all boost::replace_all I attach test source. Here is result (10000 and 10000000 loops): zypper gsub boost user time: 9 system time: 0 jano replace_all boost user time: 7 system time: 0 boost replace_all boost user time: 84 system time: 0 jreidinger@zofie:~/tmp/testing> jreidinger@zofie:~/tmp/testing> g++ test.cc jreidinger@zofie:~/tmp/testing> ./a.out 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 Pepa

2 2

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

22 Apr '08

Marcus Meissner wrote: > On Tue, Apr 22, 2008 at 01:36:16PM +0200, Jan Kupec wrote: >> 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. > > An alternative would be to just do a dummy call to PackageKit for refreshing > via dbus? AFAIK, the choice is either a PackageKit backend for the applets, or zypper. It probably doesn't make much sense to mix these two. > > But we are fine even with above setuid refresh approach. We would like > to look at the sources though, once done. Sure. j. -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

1 0

[Fwd: Re: [zypp-devel] very weird zypper behaviour]
by Stefan Schubert 22 Apr '08

22 Apr '08

-------- Original-Nachricht -------- Betreff: Re: [zypp-devel] very weird zypper behaviour Datum: Tue, 22 Apr 2008 12:58:17 +0200 Von: Stefan Schubert <schubi(a)suse.de> An: Stephan Kulow <coolo(a)suse.de> Referenzen: <200804172137.56843.coolo(a)suse.de> <200804211116.51154.coolo(a)suse.de> <480C5CE9.3090402(a)suse.de> <200804211149.44322.coolo(a)suse.de> Stephan Kulow schrieb: > Am Montag, 21. April 2008 schrieb Stefan Schubert: > >> A good argument :-) . Send me the testcase..... >> >> > Export/tc/libltdl > > Greetings, Stephan > Libzypp deptestomatic parse the dependency and generates a capability: 2008-04-22 12:48:51 <1> waerden(26327) [zypp] SATResolver.cc(resolvePool):672 Requires libltdl == 3 2008-04-22 12:48:51 <1> waerden(26327) [zypp] SATResolver.cc(solving):458 Starting solving.... While the SAT solver deptestomatic takes the name only: queue_push( &(pd->trials), SOLVER_INSTALL_SOLVABLE_PROVIDES ); queue_push( &(pd->trials), str2id( pd->pool, name, 1 ) ); Greetings Stefan -- ******************************************************************************* 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) -- ******************************************************************************* 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] .repo files product_dir -> path
by Lukas Ocilka 22 Apr '08

22 Apr '08

Hi, There is a bug 379051 - "During update missing old repositories for upgrade" in bugzilla. The reason seems to be that the .repo file has changed since 10.3 product_dir=/ -> path=/ Did anyone change the product_dir key to path or am I wrong? Thx Lukas -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- Ano, ano. Moudry rozkaz. Sam jsem nemel v tech gratulacich jasno.

2 3