April 2008 - Zypp Development - openSUSE Mailing Lists

[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

[zypp-devel] allowvirtualconflicts and allowselfconflicts
by Stefan Schubert 21 Apr '08

21 Apr '08

Hi, these flags will be provided by the SAT solver. How should this be handled by libzypp ( ZConfig, setting on the fly,....) ? Suggestions are VERY welcome :-) 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

2 2

[zypp-devel] keeping old kernel packages
by Dr. Peter Poeml 21 Apr '08

21 Apr '08

Hi, stupid question, how do I avoid that zypper removes the installed kernel packages (when updating)? The following packages are going to be REMOVED: kernel-default kernel-default kernel-default kernel-default kernel-default kernel-default I need to keep those. Thanks, Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development

6 15

[zypp-devel] very weird zypper behaviour
by Stephan Kulow 21 Apr '08

21 Apr '08

Hi, the live cds are broken since today and I debugged it a bit and the zypper behaviour below kiwi is _very_ weird. I patched kiwi to call --debug-solver and I get e.g. <addReq name="libltdl = 3"/> in the zypper command line it was zypper libltdl-3 Who splits the package name? Interestingly enough not all package names. But also "ghostscript = x11" is installed. Greetings, Stephan -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

5 12

[zypp-devel] libzypp work during beta phase
by Duncan Mac-Vicar Prett 18 Apr '08

18 Apr '08

- Satisfied products and patterns - Better display of "installed" patterns and patches (reduce icons) Patch: - needs reboot? -> how? - affects package manager (should we calculate it?) - does repo2solv parse the right languages? -> should the logic be there or should the caller specify which ones? - delta rpms What else? -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

5 6

[zypp-devel] how foo-branding-myvendor can conflict with any foo-branding-*?
by Stanislav Brabec 16 Apr '08

16 Apr '08

Hallo. To provide a solution for branding packages, I need a conflict, where any of foo-branding-myvendor packages conflicts with any of all other packages with name foo-branding-*. All these packages provide the same files, but the complete list of packages, which will provide it, is not known in time of packaging. For example: gimp-branding-openSUSE will conflict with gimp-branding-SLED. But both have to conflict with gimp-branding-Flocke, gimp-branding-Flower or gimp-branding-Spring, which may be created by a third party. And each of them has to conflict with each another. There are two recent ideas: 1) Each of them will provide and conflict with gimp-branding It works in libzypp (self conflicts are ignored), but break in rpm level. [Bug 379338] weird package conflict related to kdebase4-workspace-branding https://bugzilla.novell.com/show_bug.cgi?id=379338 2) Do nothing. It works in rpm (file conflicts are sufficient), but does not work in libzypp. Is there any other solution for this problem? -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 966, +49 911 740538747 190 00 Praha 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

6 22