November 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] [bnc 450001] Disable signed repos if the user does not trust the key?
by Michael Andres 04 Dec '08

04 Dec '08

Hi. Disable signed repos if the user does not trust the key? It's IMO a valid request as the user actively prevents the repo from being used. Or shall we continue to nag the user about trusting the key on every refresh? The question is whether this default should be implemented in libzypp, or if it is something the application should explicitly ask for: Trust key? [ ] Once [ ] Always (import) [X] No [X] not now (ask again on next refresh) [ ] maybe later (disable the repository) [ ] never (delete the repository) Or shall we introduce some zconf option RepoWithUntrustedKey = [nag|disable|delete] -- 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

5 8

[zypp-devel] Re: [yast-devel] Nürnberg YaST team meeting 2008-11-25
by Katarina Machalkova 26 Nov '08

26 Nov '08

> - long discussion about non installed (satisfied) patterns/patches, and how > they confuse users. > - at least 4 bugs open about the topic > - need to do something about it, either adapt the concept or the user > interface (sorry for cross-posting, but this is both yast and zypp issue) Is there any (reasonable) output of that discussion, to let others know as well? I mean, the whole concept of patterns in user interface is ... somehow flawed, or better, no clear policies what is the correct behaviour supposed to be are defined (see also: https://bugzilla.novell.com/show_bug.cgi?id=437162#c9 and follow-up). At least, I've been unable to find any, maybe I just don't know where to look. And I'm not currently talking only about setting correct pattern status, but also about correct transitions between the states and propagating pattern status changes to related packages ('pattern content'). I'd be really happy if we finally got down to defining some reasonable concept we can stick to when it comes to patterns and UI. frozenB. -- \\\\\ Katarina Machalkova \\\\\\\__o YaST developer __\\\\\\\'/_ & hedgehog painter -- 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: [Bug 447684] zypper dup no updating all packages? however zypper up does
by Jan Kupec 24 Nov '08

24 Nov '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 bugzilla_noreply(a)novell.com wrote: > --- Comment #2 from Michael Andres <ma(a)novell.com> 2008-11-21 11:48:55 MST --- > > The second one is not necessarily a bug, because the solver uses different > policies in 'dup' and 'up'. I suppose this will confuse several people, as > they don't know what's the command they want to use. And as the zypper output > is not very versbose, it's not that obvious why those packages were not > considered in 'dup'. The question is what should zypper show to make it obvious. It would need some additional info from the solver, currently it just gets which packages are going to be installed and which removed - no hit why. Or is there something more? - -- cheers, jano Ján Kupec YaST team - ---------------------------------------------------------(PGP)--- Key ID: 637EE901 Fingerprint: 93B9 C79B 2D20 51C3 800B E09B 8048 46A6 637E E901 - ----------------------------------------------------------------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkkqa+8ACgkQgEhGpmN+6QFIpgCfXMmSQZjUuSx+dbZkm0dlRZ55 l1wAniUoaNF8QlZ6LU3weWdnZq/hEr64 =21bY -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

3 4

[zypp-devel] Re: [zypp-commit] r11775 - in /trunk/sat-solver: src/knownid.h tools/repo_products.c
by Michael Matz 21 Nov '08

21 Nov '08

Hi, On Fri, 21 Nov 2008, dmacvicar(a)svn.opensuse.org wrote: > Log: > go away repokey > > --- trunk/sat-solver/src/knownid.h (original) > +++ trunk/sat-solver/src/knownid.h Fri Nov 21 17:12:29 2008 > @@ -166,8 +166,6 @@ > KNOWNID(PRODUCT_URL_TYPE, "product:url:type"), > KNOWNID(PRODUCT_FLAGS, "product:flags"), > KNOWNID(PRODUCT_PRODUCTLINE, "product:productline"), > -/* this has to be obsoleted */ > -KNOWNID(PRODUCT_UPDATEREPOKEY, "product:updaterepokey"), > KNOWNID(PRODUCT_REGISTER_TARGET, "product:regtarget"), > KNOWNID(PRODUCT_REGISTER_RELEASE, "product:regrelease"), This is for example one instance of a binary incompatible change. If we want to be serious about stability in the future we need to watch out for these things. (In this case the problem is, that this all defines an enum, hence numbers with a name and an association between those numbers and the strings. The change above assigns to all strings behind the removed item a number one less than before. So binary programs that e.g. used PRODUCT_REGISTER_TARGET to lookup attributes will now look for string "product:regrelease") This doesn't yet matter with just the static library, when the applications are also recompiled with the new header. Ciao, Michael. -- 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] Real time documentation now available
by Duncan Mac-Vicar Prett 21 Nov '08

21 Nov '08

We have cleaned up the main pages of [libzypp][1] and [satsolver][2], mainly to introduce a new feature. Since today, there is developer documentation generated on every svn build from our cruise control system (continuous build), available for trunk and branches. ZYpp documentation has already qute some articles and the API is very good documented, still, it will be enhanced in the following months to take advantages of having the documentation always available. SP2 branch documentation will be available soon. For satsolver, we have moved the existing documentation into the Related pages of the generated documentation (which already contains very useful articles) and we will do every possible effort to document the API too (which is almost empty right now :-/ ). Duncan [1]: http://en.opensuse.org/Libzypp [2]: http://en.opensuse.org/Package_Management/Sat_Solver -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

5 4

[zypp-devel] [PATCH] Perl satsolver bindings: testing identical()
by Olaf Dabrunz 20 Nov '08

20 Nov '08

Here is a Perl test script for the identical() function in the bindings. --- /dev/null 2007-09-21 21:12:45.000000000 +0200 +++ bindings/perl/tests/identical.pl 2008-11-20 20:11:25.000000000 +0100 @@ -0,0 +1,61 @@ +#!/usr/bin/perl + +# +# providers.pl +# +# Test the identical() function +# +# + +use lib '../../../build/bindings/perl'; + +use satsolver; + +# Open Solvable file +# open(F, "gzip -cd tmp/primary.gz |") || die; + +# Create Pool and Repository +my $pool = new satsolver::Pool; +# use x86_64, as this will consider both x86_64 and i?86 packages +$pool->set_arch( 'x86_64' ); +my $repo1 = $pool->create_repo('test_x86_64') || die; + +# Add Solvable to Repository +$repo1->add_solv ("../../testdata/os11-beta5-x86_64.solv"); + +# Create another Repository +my $repo2 = $pool->create_repo('test_biarch') || die; + +# Add Solvable to Repository +$repo2->add_solv ("../../testdata/os11-biarch.solv"); + +# Create dependencies to provides table +$pool->prepare(); + +# Print how much we have +print "\"" . $repo1->name() . "\" size: " . $repo1->size() . "\n"; +print "\"" . $repo2->name() . "\" size: " . $repo2->size() . "\n"; + +# Find a Solvable in the x86_64 Repo +my $solvname = "aaa_base"; +my $solvable1 = $repo1->find($solvname); +die if not defined $solvable1; + +print "\n" . $repo1->name() . ": found: " . $solvable1->string() . "\n"; + +# Find Providers of this Solvable in the biarch Repo +print "\nFinding providers in the biarch repo for $solvname\n"; +foreach my $solvable2 ($pool->providers($solvname)) { + print "--\n"; + next if not defined $solvable2; + + if ($solvable1->identical($solvable2)) { + printf("identical: %s and %s\n", + $solvable1->string(), + $solvable2->string()); + } else { + printf("different: %s and %s\n", + $solvable1->string(), + $solvable2->string()); + } +} -- Olaf Dabrunz (od/odabrunz) 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] zypp; Added support for loading helix repos from testcases.
by Michael Andres 19 Nov '08

19 Nov '08

JFYI: For testing or evaluating solver testcases, libzypp now suports loading of helix files. Some convenience was added to TestSetup. This is what you need to load all repos from a solver testcase into the pool: #include "TestSetup.h" BOOST_AUTO_TEST_CASE(test) { TestSetup test( Arch_x86_64 ); test.loadTestcaseRepos( "/suse/ma/BUGS/153548/YaST2/solverTestcase" ); -- 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] Added zypp::Glob - Find pathnames matching a pattern.
by Michael Andres 19 Nov '08

19 Nov '08

JFYI: I added a small wrapper around ::glob. It's available in zypp/Glob.h. You can easily collect multiple patterns and iterate the result. Glob glob( Glob::_BRACE ); glob.add( "/somewhere/solverTestcase/ *{.xml,.xml.gz}" ); glob.add( "/somewhere/else/a*" ); for_( it, glob.begin(), glob.end() ) ... There is also a static Glob::collect method that sends the result to some container. The containers value type must be constructible from a const char*: std::list<Pathname> plist; Glob::collect( "/somewherre/solverTestcase/*{.xml,.xml.gz}", Glob::_BRACE, std::back_inserter( plist ) ); -- 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] Re: [zypp-commit] r11712 - in /trunk/sat-solver: ./ doc/ doc/autodoc/ doc/autoinclude/
by Michael Schroeder 19 Nov '08

19 Nov '08

On Wed, Nov 19, 2008 at 08:55:08AM -0000, dmacvicar(a)svn.opensuse.org wrote: > Author: dmacvicar > Date: Wed Nov 19 09:55:07 2008 > New Revision: 11712 > > URL: http://svn.opensuse.org/viewcvs/zypp?rev=11712&view=rev > Log: > lets try to make this a documented project > > Added: > trunk/sat-solver/doc/CMakeLists.txt > trunk/sat-solver/doc/autodoc/ > trunk/sat-solver/doc/autodoc/CMakeLists.txt > trunk/sat-solver/doc/autodoc/Doxyfile.cmake > trunk/sat-solver/doc/autoinclude/ > trunk/sat-solver/doc/autoinclude/History.doc > trunk/sat-solver/doc/autoinclude/Mainpage.doc > Modified: > trunk/sat-solver/CMakeLists.txt Eeek, doxygen in the satsolver? I'm not sure if I really like that. This is not libzypp, after all. I prefer standard nroff man pages. Cheers, Michael. -- 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

3 2