April 2008 - Zypp Development - openSUSE Mailing Lists

[zypp-devel] kernel-default dependencies
by Matt Barringer 16 Apr '08

16 Apr '08

Hello, When doing a dependency resolution for kernel-default (just kernel-default, nothing else) on 10.3 using the satsolver, the decision is to install 60 packages or so, including bundle-lang-common-en, which doesn't look like a requirement by any package. This occurs both with a solv file my code built, and the one using the libzypp testsuite. Am I doing something wrong? That seems like quite a lot of dependencies. Thanks, Matt -- 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] pkg-bindings broken again ;(
by Stephan Kulow 15 Apr '08

15 Apr '08

Hi, We can't release Beta1 with that bug: 2008-04-15 14:17:15 <1> linux(2606) [YCP] clients/runlevel_proposal.ycp:26 Runlevel proposal started 2008-04-15 14:17:15 <1> linux(2606) [YCP] clients/runlevel_proposal.ycp:27 Arguments: ["MakeProposal", $["force_reset":false, "language_changed":fals e]] 2008-04-15 14:17:15 <1> linux(2606) [Pkg] clients/runlevel_proposal.ycp:194 Pkg Builtin called: IsSelected 2008-04-15 14:17:15 <1> linux(2606) [Pkg] Package.cc(IsSelected):474 Tag xorg-x11 is not selected to install 2008-04-15 14:17:15 <1> linux(2606) [YCP] clients/runlevel_proposal.ycp:203 x11_setup_needed: true, x11_selected: false, vnc: false, ssh false, force d: '' 2008-04-15 14:17:15 <1> linux(2606) [YCP] clients/runlevel_proposal.ycp:263 Runlevel proposal: $["preformatted_proposal":"<ul>\n<li>3: Full multiuser with network</li></ul>"] https://bugzilla.novell.com/show_bug.cgi?id=380141 Greetings, Stephan -- 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] question about solver behavior
by Josef Reidinger 14 Apr '08

14 Apr '08

Hi, I have few question about solver. I test zypper in one bug (not related and fixed) and find this behavior. Is it correct? (I done refresh before tests) first try - normal 3ddiag (output snipped) zypper -vvvv in --force-resolution off 3ddiag 0 items locked Force resolution: No Resolving dependencies... The following package is going to be upgraded: 3ddiag-0.740-85.x86_64 (Main Repository (OSS)) same result with force on...but in both case I have in repo newer package. Is correct if solver doesn't try newer? zypper -vvvv in --force-resolution on 3ddiag 0 items locked Force resolution: Yes Resolving dependencies... The following package is going to be upgraded: 3ddiag-0.740-85.x86_64 (Main Repository (OSS)) Now force off and the newest version of package zypper -vvvv in --force-resolution on -C 3ddiag=0.742 0 items locked Force resolution: Yes Resolving dependencies... The following packages are going to be upgraded: yast2-hardware-detection-2.16.1-26.x86_64 (factory) kio_sysinfo-11.0-75.x86_64 (factory) hwinfo-devel-14.11-5.x86_64 (factory) hwinfo-14.11-5.x86_64 (factory) 3ddiag-0.742-10.x86_64 (factory) The following packages are going to be REMOVED: kdebase3-SuSE-10.3-152.x86_64 (@System) sax2-gui-8.1-258.x86_64 (@System) sax2-8.1-258.x86_64 (@System) and with force-resolution off zypper -vvvv in --force-resolution off -C 3ddiag=0.742 Verbosity: 4 Non-option program arguments: '3ddiag=0.742' Initializing Target Checking whether to refresh metadata for factory Reading installed packages... 0 items locked Force resolution: No Resolving dependencies... The following packages are going to be upgraded: zypper-0.10.4-12.x86_64 (factory) yast2-qt-2.16.33-8.x86_64 (factory) yast2-pkg-bindings-2.16.22-4.x86_64 (factory) yast2-perl-bindings-2.16.5-2.x86_64 (factory) yast2-ncurses-2.16.20-7.x86_64 (factory) yast2-hardware-detection-2.16.1-26.x86_64 (factory) yast2-core-2.16.41-2.x86_64 (factory) spamassassin-3.2.4-19.x86_64 (factory) <snip> too much package </snip> 3ddiag-0.742-10.x86_64 (factory) The following NEW packages are going to be installed: yast2-ycp-ui-bindings-2.16.39-7.x86_64 (factory) yast2-libyui-2.16.39-7.x86_64 (factory) yast2-core-devel-2.16.41-2.x86_64 (factory) libsatsolver-devel-0.0.24-2.x86_64 (factory) libblocxx6-2.1.0.342-5.x86_64 (factory) libblocxx-devel-2.1.0.342-5.x86_64 (factory) frozen-bubble-server-2.1.0-138.x86_64 (factory) ( looks like my linux like playing :) yast2-theme-openSUSE-Oxygen-2.16.17-16.noarch (factory) desktop-data-openSUSE-11.0-36.noarch (factory) bundle-lang-kde-ar-11.0-86.noarch (factory) The following packages are going to be REMOVED: desktop-data-SuSE-10.3-88.noarch (@System) blocxx-devel-1.0.0-79.x86_64 (@System) CheckHardware-0.1-1088.x86_64 (@System) perl-IO-Zlib-1.06-13.x86_64 (@System) perl-IO-Compress-Zlib-2.005-16.x86_64 (@System) perl-IO-Compress-Base-2.005-17.x86_64 (@System) perl-Compress-Zlib-2.005-13.x86_64 (@System) perl-Compress-Raw-Zlib-2.005-17.x86_64 (@System) perl-Archive-Tar-1.32-18.x86_64 (@System) liby2util-devel-2.14.0-65.x86_64 (@System) liby2util-2.14.0-65.x86_64 (@System) so is it correct or bug to report? Maybe I am only misunderstood what is force-resolution Pepa -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

4 4

[zypp-devel] Switch to new locks api
by Josef Reidinger 14 Apr '08

14 Apr '08

Libzypp uses new locking api now. You can find it in Locks.h. Works everything except unlock, which I hope implement today. few notes about functions - supported is reading and writing locks to file (default is file specified in zypp.conf). - loadLock append to locks available, if someone find useful setting new locks instead appending (something like restore old locks for frontend) it can be added. - addLock locks all result of query and also store this query for later save, also Selectabable can be locked, it uses optimally query to lock - saving locks must frontend explicit call - saving locks rewrite locks file (as unwanted side effect remove all comments) - existEmptyLocks and removeEmptyLocks is functions to maintance locks. First say if exist some locks which doesn't lock anything and second clean it. (ask for each lock by callback) - if locksfile.apply (see zypp.conf) is on (default) then after start of zypp locks is loaded and applied overview of new file format structure is 'attribute: value', locks (queries) separated by empty line attribute can be global_string (see addString for PoolQuery), string_type (values can be exact, substring, regex, glob), repo (repo allias), kind (Resolvable kind), require_all (if all attribute must match), case_sensitive (search case sensitive), install_status( values can be all, installed, not-installed) and all SolvAttributes with replaced colon ( s/:/_/g ). for example look [0]. default locks file path is /etc/zypp/locks Pepa [0] http://svn.opensuse.org/svn/zypp/trunk/libzypp/tests/zypp/data/PoolQuery/sa… -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

4 4

[zypp-devel] selecting patches by issue
by Duncan Mac-Vicar Prett 14 Apr '08

14 Apr '08

Patches now have bugzilla and security metadata. I already added support for displaying them in the user interface. However I am thinking on zypper now. An user may want to say zypper "install the fix for bugzlla 3223". We have 2 ways to implement this, and I would like to hear your feedback: - use the current metadata to search for the issue and mark packages for install. This will need some "look" code in each application. - Use the solver, and during parsing inject something like provides:fix(bugzilla:23444) when filling the repodata. Then applications could inject a requires in the solver fix(bugzilla:23444) and just solve. I dont't know the consequences of this. - Any other idea? Duncan -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

6 10

[zypp-devel] issues with installed patterns and product
by Duncan Mac-Vicar Prett 14 Apr '08

14 Apr '08

I am trying to fix zypp-query-pool used by registration. I now show "i" as installed using isInstalled for Packages and isSatisfied for patterns. There are two problems. When looking installed (satisfied ) patterns on my machine: i|pattern|xgl|10.3-159|i586 i|pattern|xgl|10.3-159|x86_64 I see satisfied both architectures. When looking for satisfied products, I see none: |product|openSUSE-FTP|10.3|noarch|| |product|openSUSE-FTP-NonOSS|10.3|noarch|| because product depends on patterns, which are never installed, and product.isSatisfied will not return true if the patterns are satisfied or? Duncan -- 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] r9549 - /trunk/sat-solver/src/solver.c
by Klaus Kaempf 11 Apr '08

11 Apr '08

* mlschroe(a)svn.opensuse.org <mlschroe(a)svn.opensuse.org> [Apr 11. 2008 18:51]: > Author: mlschroe > Date: Fri Apr 11 18:51:41 2008 > New Revision: 9549 > > URL: http://svn.opensuse.org/viewcvs/zypp?rev=9549&view=rev > Log: > - change schubi debugging > - add some comments to internal create_decisions_obsoletesmap() > function. > should really make it static, as all uses in applayer code are > broken. I hope nobody uses the applayer. Well, the bindings are using the applayer. And its my intention to use the bindings to push 'how to use sat-solver' upstream. Klaus -- 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: [zypp-commit] r9533 - in /trunk/libzypp/zypp: ZConfig.cc ZConfig.h
by Michael Matz 11 Apr '08

11 Apr '08

Hi Klaus, On Fri, 11 Apr 2008, kkaempf(a)svn.opensuse.org wrote: > Author: kkaempf > Date: Fri Apr 11 13:34:38 2008 > New Revision: 9533 > > URL: http://svn.opensuse.org/viewcvs/zypp?rev=9533&view=rev > Log: > add updateScriptsPath (non-configurable because it doesn't make sense) It does, namely with installation into directories. There it's even required. 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] sat-solver and python
by Martin Vidner 11 Apr '08

11 Apr '08

I needed to compile sat-solver (because it provides necessary api but is not in autobuild yet...) and this patch was necessary for an unknown reason... -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu

2 1

[zypp-devel] SolvIterMixin: Adding PoolItem_iterator and Selectable_iterator
by Michael Andres 11 Apr '08

11 Apr '08

I just added a class SolvIterMixin (zypp/sat/SolvIterMixin.h). Classes providing a sat::Solvable iterator - i.e methods begin() and end() returning an iterator pointing to sat::Solvable - may derive from it to add additional iterators. by now: // value_type sat::Solvable (the same as the derived class' begin/end) Solvable_iterator solvableBegin() const Solvable_iterator solvableEnd() const // value_type PoolItem PoolItem_iterator poolItemBegin() const PoolItem_iterator poolItemEnd() const // value_type ui::Selectable::Ptr Selectable_iterator selectableBegin() const Selectable_iterator selectableEnd() const (The Selectable_iterator will soon be enhanced to avoid multiple visits of the same Selectable, because multiple Solvables/PoolItems refer to the same Selectable.) The intention is that all classes providing a collection of solvables (Queries, Pattern/Patch contents, ...) offer this interface. To use SolvIterMixin derive from it and pass the class and the iterator type as template argument: * namespace detail * { * class WhatProvidesIterator; * } * * class WhatProvides * : public SolvIterMixin<WhatProvides,detail::WhatProvidesIterator> * { * public: * typedef detail::WhatProvidesIterator const_iterator; * * // Iterator pointing to the first Solvable. * const_iterator begin() const; * * // Iterator pointing behind the last Solvable. * const_iterator end() const; * * }; @PoolQuery: The Mixin requires begin/end being const methods, and the ResultIterator must be defined outside class PoolQuery. Once this is fixed, PoolQuery could add the SolvIterMixin interface. -- 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 1