February 2008 - Zypp Development - openSUSE Mailing Lists

[zypp-devel] Configurability of 'keep downloaded packages'
by Stanislav Visnovsky 22 Mar '08

22 Mar '08

Hi! I'm working on the functionality to keep the downloaded packages on disk, not removing them. This needs to be configurable, of course. I'd like to get your views on how much configurability we need. I see at least the following options: 1) global enable/disable 2) per-repository enable/disable 3) per-access protocol enable/disable (CD, HTTP, FTP, NFS, ...) Any opinions? Stano -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

9 24

[zypp-devel] We're going to loose resolvables of kind 'Language'.
by Michael Andres 18 Mar '08

18 Mar '08

We're going to loose resolvables of kind 'Language'. The sat solver allows to handle language supporting packages the way as e.g. hardware supporting packages, via namespaces. So there is no more need to create those dummy language-resolvables. That's nice because the satpool does not allow to have solvables without a repository. So we don't have to create a dummy repository just to maintain those dummy resolvables. The zypp interface will basically stay the same: void setRequestedLocales( const LocaleSet & locales_r ); LocaleSet getRequestedLocales() const; LocaleSet getAvailableLocales() const; May be we add some convenience methods. -- 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

3 4

[zypp-devel] Verify system feature dropped?
by Katarina Machalkova 07 Mar '08

07 Mar '08

Hi, zypp hackers, while working on ncurses package selector redesign I have found out that yet another thing has been dropped (deprecated/obsoleted/temporarily unavailable) from zypp silently, without communicating this fact to those who are using the feature. In this case, maintainers of package selectors. Facts: FaTE #301178 "Offer 'verify installed package dependencies' functionality in YaST" mandatory/important for SLE10 SP1 important for openSUSE 10.3 Requested by: kkaempf(a)novell.com Project Manager: visnov(a)novell.com (adding those to Cc:) After selecting 'Verify system' entry from package selector menu, solver run should check package dependencies and take appropriate action to restore the consistency of the system (e.g. mark missing packages for installation) However, this never happens, I'm getting false-positive result that all dependencies are correct (which is obviously not true) and this message in the log: Resolver.cc (verifySystem): Will currently not be supported by the SAT-solver Maybe I'm not having the most recent version of SAT-solver and this issue would be already settled if I made fresh svn checkout. In that case you may disregard this e-mail. Anyway, as this feature was mandatory, I believe it should not be dropped without adequate substitute. Moreover, it has been requested for zypper, too (FaTE #301918 - adding jkupec to Cc:). As this is not the first thing dropped/made obsolete from zypp more or less silently, I'd really appreciate if (in the future) we would be informed about such changes and about adequate replacement functionality (if any). Better late, than never at all (finding this out sheerly by accident). Zypp is a library that is used by other applications (package selectors, zypper,...) and without them, it's just dead kilo-lines of code in subversion. frozenB. -- \\\\\ Katarina Machalkova \\\\\\\__o YaST developer __\\\\\\\'/_ & hedgehog painter

3 4

[zypp-devel] collect pending AIs thread
by Duncan Mac-Vicar P. 06 Mar '08

06 Mar '08

Hi guys, I would like to collect in this thread all details that we need to address in the next weeks. You can incrementally reply to this thread and I will put them all together. I start with: - patch and delta rpm creation - fix attributes to take care of translations - integrate patch & pattern concepts (wrap APIs, etc) - fix UIs to support this patches and patterns (including the applet) - enhance downloader to download .solv files - take care of media.1 for media verification (either download it when downloading solv files only, or store it in solv file) -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

9 19

[zypp-devel] Selectables and 'candidate'
by Jan Kupec 01 Mar '08

01 Mar '08

Let's agree on what a candidate is (installation candidate, right?). Is it one of the resolvables (or pool items) of a Selectable considered to be the most suitable to be selected for installation based on current setup of policies? Is it just a hint for the solver about what should be installed in case the user doesn't specifically choose another version? Is the 'candidate' tied to a particular Selectable or is it rather a candidate of multiple Selectables (the whole pool perhaps)? Klaus suggested the term 'candidate' is misleading. Why? If the candidate is for some reason not installable (which will be determined by solving), is there a problem with still calling it a candidate? Candidate != to-be-installed, right? If the answers are positive, the Selectable::candidate() should return the candidate based on current policies and should be used by the UIs to mark it for installation (if user clicked to install the selectable (no specific version)) and by the solver to mark it for installation to satisfy some dependencies. And that's just about it. If not, please correct me. Anything else? I hope i'm not messing things up :O) -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

12 24

[zypp-devel] XML output for zypper
by Jan Kupec 29 Feb '08

29 Feb '08

Hi there! zypper -x (--xmlout) is almost done. The main features (currently in svn, to be in zypper-0.10.2) include: * all output in XML: info, warning, error messages, progress/download progress, prompts, * uniquely identified user dialogs (prompts) * enumerated possible dialog answers (comming soon: prompt help) * query command results as xml data - list-updates (obsoletes the xu command) uses the established update info xml structure from zypp-check-patches/zypper xu - repos - search (TODO) - patches (TODO) - info (TODO) * other special information as xml data - install summary * common types of output (messages, progress) are written using classes derived from Out class (OutNormal, OutXML) so this type of output can easily be changed/extended, new class can be added (e.g. OutColored). Output examples attached. I have left the <update-status> subtree compatible with zypp-check-patches, but i've changed the rest of the xml written by 'zypper --terse xu' [2] (used by the updater applets) a bit as i believe it is only used by the applets so far, which we can adapt. There is an RNC scheme at [0], which will get installed to /usr/share/zypper/$somewhere/xmlout.rnc. I will also update [2] http://en.opensuse.org/Standards/Zypper_Xml after the code freeze. Also there is prompt.h header file at [1] with an enum of the prompt IDs and their description (TODO) which i plan to get installed into /usr/include/zypper/prompt.h. As for zypper commands and options: - I would like to drop the xu command in favor of 'zypper -x lu -t package -t patch'. - Also, i'd like to use the --terse option for other type of machine-readable output (like zypper repos printing the table without header and decoration). For 11.0 it should be just ignored (provided only for rug-compatibility). IMO we can afford dropping these, as they were only used by the updater applets so far (probably :O). XML input is not implemented yet, but eventually will be. So go ahead and play with it, feedback is welcome! Cheers, jano [0] http://svn.opensuse.org/svn/zypp/trunk/zypper/src/output/xmlout.rnc [1] http://svn.opensuse.org/svn/zypp/trunk/zypper/src/output/prompt.h [2] http://en.opensuse.org/Standards/Zypper_Xml

1 0

[zypp-devel] zypper dup shortcoming
by Michael Andres 27 Feb '08

27 Feb '08

As people are encouraged to use 'zypper dup', we get some reports which describe problems arising from the fact that we update the update stack in the running system. After installing the new libzypp, zypper continues the transaction and is still using the old lib. While the new libzypp converts and removes obsoltete locations (like the cache store or the obsolete sql databases) in it's post install script, the zypper running still tries to access these locations. Maybe zypper should check whether the update stack needs an update, and handle this specially. -- 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 5

[zypp-devel] Re: [CruiseControl] zypp-trunk build 8907 failed
by Michael Matz 25 Feb '08

25 Feb '08

Hi, On Mon, 25 Feb 2008, zypp-devel(a)opensuse.org wrote: > The build failed. > > See http://gabbai.suse.de:3333/builds/zypp-trunk/8907 for details. > (only SUSE-internal) > > /usr/include/zypp/ByteCount.h:80: Warning(503): Can't wrap 'operator size_type' unless renamed to a valid identifier. > /usr/include/zypp/repo/RepoType.h:62: Error: '__eq__' is multiply defined in the generated module. > /usr/include/zypp/Pathname.h:154: Error: Previous declaration of '__eq__' Can someone who feels responsible for python PLEASE fix those bloody bindings, which fail to compile since weeks?! Or remove them, or something. It makes no sense to have an automatic compile checker if noone looks at them or fixes bugs exposed there. >From the looks of it it rather seems that SWIG is broken as it thinks that namespace zypp { namespace filesystem { bool operator==( const Pathname & l, const Pathname & r ); }} and namespace zypp { namespace repo { bool operator==(const RepoType & obj1, const RepoType & obj2); }} are the same, which clearly they aren't. I have no idea about SWIG. 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] rpmlib dependencies
by Stefan Schubert 25 Feb '08

25 Feb '08

Hi, while generating testcases I recognized that the pool has rpmlib dependencies. These dependencies will be added to the testcases. Former libzypp parsers (helix paser) have dropped this kind of dependency. How will be managed this in the SAT solver-pool ? P.S.: This code will never be touched by rpmlib dependencies: function : pool_addrelproviders /* make our system solvable provide all unknown rpmlib() stuff */ if (plist.count == 0 && !strncmp(id2str(pool, name), "rpmlib(", 7)) { queue_push(&plist, SYSTEMSOLVABLE); } 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 1

[zypp-devel] Re: [zypp-commit] r8851 - /trunk/libzypp/zypp/sat/Solvable.cc
by Michael Matz 22 Feb '08

22 Feb '08

Hi Duncan (and others), On Thu, 21 Feb 2008, matz(a)svn.opensuse.org wrote: > Author: matz > Date: Thu Feb 21 16:39:05 2008 > New Revision: 8851 > > URL: http://svn.opensuse.org/viewcvs/zypp?rev=8851&view=rev > Log: > We need to add mediadir also in the non-trivial case. This and the last commit to satsolver/tools/repo_rpmmd.c fix a bug in parsing of susetags repos which look like our full trees (i.e. no revisions in the rpm filename), unfortunately it necessarily breaks handling of the media file with already generated SOLV files from yum repos. You need to update those, once this libsatsolv and libzypp is submitted, or already now if you use SVN. Ciao, Michael. -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

3 4