July 2007 - Zypp Development - openSUSE Mailing Lists

[zypp-devel] Product type handling
by Jiri Srain 03 Aug '07

03 Aug '07

Hi! As I stated today during the meeting, please, update following way the source parsers in ZYPP: For SuSEtags add to the content file TYPE base for the base product; if not present, it is an add-on product For YUM, we already have in the metadata definition attribute type { text }, which should have values "base" or "add-on"; the parser itself has nandling this attribute commented out. The zypp::Product::category should return the type of the product. Since we broke even source-code compatibility of the library as whole anyway, it may make sense to rename it to zypp::Product::type to be consistent with the metadata. Thanks in advance! Jiri -- Regards, Jiri Srain YaST Team Leader --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain(a)suse.cz Lihovarska 1060/12 tel: +420 284 028 959 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz

2 1

[zypp-devel] Re: [zypp-commit] r6311 - zypper-sources.cc - base urls iterator
by Jan Kupec 01 Aug '07

01 Aug '07

dmacvicar(a)svn.opensuse.org wrote: > Author: dmacvicar > Date: Mon Jul 30 23:42:43 2007 > New Revision: 6311 > > URL: http://svn.opensuse.org/viewcvs/zypp?rev=6311&view=rev > Log: > dont use baseUrls (deprecated, perhaps we remove it) > use the url iterator Let's keep baseUrls(), it's handy for the application to store the set of urls and then work with it if appropriate. Example use case: when initializing repos (checking if to refresh for those with autorefresh enabled), if the app finds out the repo is invalid, it can disable it in its internal set and ignore it for the rest of the operation. But for list repos operation, as is the case below, it is appropriate to use the iterator which always works with data of the *.repo files. Jano > Modified: > trunk/zypper/src/zypper-sources.cc > > Modified: trunk/zypper/src/zypper-sources.cc > URL: http://svn.opensuse.org/viewcvs/zypp/trunk/zypper/src/zypper-sources.cc?rev… > ============================================================================== > --- trunk/zypper/src/zypper-sources.cc (original) > +++ trunk/zypper/src/zypper-sources.cc Mon Jul 30 23:42:43 2007 > @@ -123,10 +123,8 @@ > tr << repo.type().asString(); > tr << repo.alias(); > > - std::set<Url> urls; > - urls = repo.baseUrls(); > - for ( RepoInfo::urls_const_iterator uit = urls.begin(); > - uit != urls.end(); > + for ( RepoInfo::urls_const_iterator uit = repo.baseUrlsBegin(); > + uit != repo.baseUrlsEnd(); > ++uit ) > { > tr << (*uit).asString(); > -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

3 3

[zypp-devel] Re: [zypp-commit] r6258 - /trunk/zypper/doc/zypper.8
by Jan Kupec 01 Aug '07

01 Aug '07

Hi Klaus, kkaempf(a)svn.opensuse.org wrote: > Author: kkaempf > Date: Fri Jul 27 16:37:21 2007 > New Revision: 6258 > > URL: http://svn.opensuse.org/viewcvs/zypp?rev=6258&view=rev > Log: > update manpage for '--from-repo' > > +\fI\--from-repo\fR <repository_alias> > +Limit to updates available from named repository > +.TP this is planned for almost all commands (incl. search, install), not only for update. One reason is for rug compatibility (alias --catalog) and other reason is that it is generally a good thing. But what about naming it just --repo or --repository instead of --from-repo? Jano -- 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] Qt widget for showing solver results.
by Stefan Schubert 31 Jul '07

31 Jul '07

Hi, as I have promised in our last meeting I would like to provide more information about the solver QT widget. This modal QDialog widget shows a solver result in a grafical tree in which the user can navigate and can get the information "who has installed whom and why". A screenshot how it looks like can be found here: ~schubi/Export/solvertree/solver.jpg I have made a package and checked in into autobuild: libqdialogsolver1 libqdialogsolver1-devel The interface is quite simple: #ifndef QZYPPSOLVERDIALOG_H #define QZYPPSOLVERDIALOG_H #include <qdialog.h> #include "zypp/solver/detail/Resolver.h" class SolverTree; /////////////////////////////////////////////////////////////////// // // CLASS NAME : QZyppSolverDialog // /** * Modal QDialog class which shows the solver result in * a graphical view. */ class QZyppSolverDialog : public QDialog{ Q_OBJECT protected: zypp::solver::detail::Resolver_Ptr resolver; SolverTree *solvertree; public: /** Constructor * \param Resolver pointer of a valid solver run */ QZyppSolverDialog(zypp::solver::detail::Resolver_Ptr r = NULL); /** ctor */ ~QZyppSolverDialog(); /** Selecting one item in the solvertree * \param \ref item which will be selected */ void selectItem(const zypp::PoolItem_Ref item); private: QZyppSolverDialog& operator = (const QZyppSolverDialog &zyppSolverDialog); QZyppSolverDialog(const QZyppSolverDialog &zyppSolverDialog); }; #endif HuHa, is there any possibility of making a button in the QT-UI ? :-) This is the first working version. Improvements, suggestions, wishes 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

3 4

[zypp-devel] media change callback problems
by Jan Kupec 31 Jul '07

31 Jul '07

Hi, i think we have two problems with media MediaChangeReport::requestMedia() callback: 1) the callback mixes request for another media from media set (where the media are physically changeable CD/DVD) and request for another URL 2) with the refactored libzypp we have no means to change the URL as we did before. The URL edit box has no effect now in YaST dialogs due to this fact. (zypper didn't have this implemented so far.) This is again because we don't have repositories globally associated with media access, and there is nothing like simple redirect(media, newurl) call now. I guess 1) can be solved easily by splitting the requestMedia() into e.g. requestMediaFromSet() and problem(), where requestMediaFromSet() would be called only for changeable media (after a guess whether the error can be caused by wrong media number) and problem() would be called for all media types on real error (where requestMediaFromSet() did not help). This way the UI can display more appropriate message like "Please, insert media labeled 'openSUSE 10.3' #2 into the drive..." for requestMediaFromSet() and "An error occured: ...." for problem(). But for 2) i don't know. Ideas? BTW: I've made a change to the callback so that it is called for CDs/DVDs only, but thanx to Michael i've realized the problem is a little bit more complex. Should i revert that change for now? It should be reverted at least if we decide not to solve the above problems for now. 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]
by Di Pe 31 Jul '07

31 Jul '07

Hi, I am using zypper 0.83 on opensuse 10.2, have a custom repository and installed a new version of sqlite. Everything works fine but when I try to downgrade to sqlite 3.38 using the 10.2 repository: / # zypper in --catalog dvd sqlite Reading repository buildsvc... Reading repository fhcrc... Reading repository update... Reading repository dvd... Reading RPM database... skipping package 'sqlite' (already installed) Summary: Nothing to do. I could uninstall and reinstall sqlite but guess that would really mess up zypper. Not sure if there is any other way to do this but I think this would be a really useful feature. thanks dipe -- We've Got Your Name at http://www.mail.com! Get a FREE E-mail Account Today - Choose From 100+ Domains -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

3 3

[zypp-devel] tribool ... (Fwd)
by Martin Vidner 30 Jul '07

30 Jul '07

Michael is not subscribed, forwarding... ----- Forwarded message from Michael Meeks <michael.meeks(a)novell.com> ----- Subject: tribool ... From: Michael Meeks <michael.meeks(a)novell.com> To: zypp-devel(a)opensuse.org Cc: Ricardo Cruz <rpmcruz(a)alunos.dcc.fc.up.pt> Organization: Novell, Inc. X-Mailer: Evolution 2.6.0 Date: Mon, 23 Jul 2007 08:55:13 +0100 Hi guys, So - I learned something fun, interesting and new this morning (at the cost of an hour or so) - it was the joys of the tribool: if (available_obj != NULL && !available_obj->repository().info().enabled()) { In normal usage, by the power of sequence points, this sort of thing works nicely (and indeed, it used to work before the API re-hash I think). Unfortunately, with a tri-bool around this becomes a mess, sequence points are no longer your friend: return false && !(zypp::ResObject::constPtr(NULL)->repository().info().enabled()) ? 1 : 0; SEGV's immediately - try it as a return from main() ;-) it compiles to: return tribool.operator&& (false, <segv'ing-code>) Now the fix is 'obvious' - simply split it into 2 if's, or add a '(bool)' cast to what appears to be a bool anyway ;-) but it's pretty sickeningly non-obvious to the casual user. Also, will it survive a future maintainer's desire for cleaner code without "all these odd / redundant casts in it" ? Urgh, Michael. -- michael.meeks(a)novell.com <><, Pseudo Engineer, itinerant idiot -- 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: Qt widget for showing solver results.
by Stefan Schubert 30 Jul '07

30 Jul '07

Stephan Kulow schrieb: > Am Donnerstag 26 Juli 2007 schrieb Stefan Schubert: > > >> This is the first working version. Improvements, suggestions, wishes are >> VERY welcome. >> > Looks nice. This uses graphviz? I'm afraid this does not fit in either the > instsys nor the CD. So if you add the button, it should only appear if you > can satisfy the dependencies. > Thanks. Yes, it uses graphiviz. This could become a problem with inst-sys but not in the running system. Greetings Stefan > But it would definitely easy debugging such problems also for e.g. factory > users. > > Greetings, Stephan > > -- ******************************************************************************* 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] Exception history
by Michael Andres 27 Jul '07

27 Jul '07

(In SVN) Class Exception now offers a history list of message strings. These messages should describe what lead to the exception. The Exceptions message itself is NOT included in the history. History access: /** Iterator pointing to the most recent message. */ HistoryIterator historyBegin() const { return _history.begin(); } /** Iterator pointing behind the last message. */ HistoryIterator historyEnd() const { return _history.end(); } /** Whether the history list is empty. */ bool historyEmpty() const { return _history.empty(); } /** The size of the history list. */ HistorySize historySize() const { return _history.size(); } History maintainance: /** Store an other Exception as history. */ void remember( const Exception & old_r ); /** Add some message text to the history. */ void addHistory( const std::string & msg_r ); Example: Rethrow, remembering an old exception: try { .... } catch( const Exception & olderr_r ) { ZYPP_CAUGHT( olderr_r ) HighLevelException newerr( "Something failed." ); newerr.rember( olderr_r ); ZYPP_THROW( newerr ); } Print exception and history if available: Exception error; dumpRange( ERR << error << endl, err.historyBegin(), err.historyEnd(), "", "History:\n - ", "\n - ", "\n", "" ); Todo: Check and adjust existing code to remember previois Exceptions. -- 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

2 3

[zypp-devel] zypper development wiki page
by Jan Kupec 27 Jul '07

27 Jul '07

For all who wish to participate in zypper development, i have set up a wiki page at: http://en.opensuse.org/Zypper/Development Feel free to edit it as needed. Cheers, Jano -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

1 0