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

[zypp-devel] Re: [zypp-commit] r6229 - /trunk/zypper/zypper.spec.cmake
by Klaus Kaempf 27 Jul '07

27 Jul '07

* jkupec(a)svn.opensuse.org <jkupec(a)svn.opensuse.org> [Jul 26. 2007 15:41]: > Author: jkupec > Date: Thu Jul 26 15:41:02 2007 > New Revision: 6229 > > URL: http://svn.opensuse.org/viewcvs/zypp?rev=6229&view=rev > Log: > - cmake added to build dependencies > - added versions to build deps Why ? > > Modified: > trunk/zypper/zypper.spec.cmake > > Modified: trunk/zypper/zypper.spec.cmake > URL: http://svn.opensuse.org/viewcvs/zypp/trunk/zypper/zypper.spec.cmake?rev=622… > ============================================================================== > --- trunk/zypper/zypper.spec.cmake (original) > +++ trunk/zypper/zypper.spec.cmake Thu Jul 26 15:41:02 2007 > @@ -11,9 +11,8 @@ > # norootforbuild > > Name: @PACKAGE@ > -BuildRequires: libzypp-devel >= 3.11.9 > -BuildRequires: gcc-c++ pkg-config boost-devel gettext-devel > -BuildRequires: readline-devel > +BuildRequires: libzypp-devel >= 3.11.9 boost-devel >= 1.33.1 gettext-devel >= 0.16 readline-devel >= 5.2 > +BuildRequires: gcc-c++ >= 4.2 cmake >= 2.4.6 pkg-config >= 0.21 This means that one cannot compile zypper on openSUSE 10.2 any more :-( 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] download area at commit
by Duncan Mac-Vicar Prett 26 Jul '07

26 Jul '07

Some background. - every media opened can have its own mount point. - before, every soure kept its media opened while the source obj was in memory - SourceManager had a method that iterates over all living Sources, changing the attach point of their medias. This was used by pkg bindings. Now: - Medias are not used till refresh or commit, they are not part of the source, and there is not 1:1 repo <-> media access relation. - There is a function MediaManager::setAttachPrefix(const Pathname) which changes the prefix for the future opened medias (not the attached ones). It means: - as we dont open the medias till commit, and MoveDownloadArea() in bindings is called just before commit, it should be safe to use just MediaManager::setAttachPrefix in the MoveDownloadArea() func. - MoveDownLoad area gets /instdir + /var/tmp as parameter. I am not sure if MediaManager::setAttachPrefix includes the tmpdir again. So, if I am correct, all the change needed would be: #include <zypp/media/MediaManager.h> YCPValue PkgModuleFunctions::SourceMoveDownloadArea (const YCPString & path) { try { y2milestone( "Moving download area of all sources to %s", path->value().c_str()) ; media::MediaManager manager; manager.setAttachPrefix(path->value()); } catch (zypp::Exception & excpt) { _last_error.setLastError(excpt.asUserString()); y2error("Pkg::SourceMoveDownloadArea has failed: %s", excpt.msg().c_str() ); return YCPBoolean(false); } y2milestone( "Download areas moved"); return YCPBoolean(true); } Comments? -- Duncan Mac-Vicar Prett Novell :: SUSE R&D, Maxfeldstr. 5, 90409 Nürnberg 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] r6227 - /trunk/zypper/src/zypper-misc.cc
by Klaus Kaempf 26 Jul '07

26 Jul '07

* mvidner(a)svn.opensuse.org <mvidner(a)svn.opensuse.org> [Jul 26. 2007 13:55]: > Author: mvidner > Date: Thu Jul 26 13:55:40 2007 > New Revision: 6227 > > URL: http://svn.opensuse.org/viewcvs/zypp?rev=6227&view=rev > Log: > Install not by package name but by capability, if the string > contains one of =<> (FATE 301956). > (not working yet, probably a libzypp bug: #294727) Yes, it muzst be fixed in the solver API. Currently it throws away all 'extra dependencies'. I have a patch in preparation though ... Klaus -- 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] r6216 - in /trunk/zypper: package/zypper.changes src/zypper-misc.cc src/zypper.cc
by Duncan Mac-Vicar P. 26 Jul '07

26 Jul '07

On Wednesday 25 July 2007 05:07:42 pm kkaempf(a)svn.opensuse.org wrote: > Author: kkaempf > Date: Wed Jul 25 17:07:42 2007 > New Revision: 6216 > > URL: http://svn.opensuse.org/viewcvs/zypp?rev=6216&view=rev > Log: > - implement '--best-effort' for "list updates" > adapt output columns appropriately (in best-effort mode, zypper > does not know the repository, version, or architecture since the > dependency solver will determine it later.) > - make "list update" output handling more robust > - r6216 I don't understand much the best-effort thing. Can you ellaborate? -- 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] solver testsuite is running again.
by Stefan Schubert 25 Jul '07

25 Jul '07

Hi, all solver tests are working again now. I have disabled source,target and parser cause I do not know if they are still needed anymore. 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

1 0

[zypp-devel] Announcing CruiseControl
by J. Daniel Schmidt 24 Jul '07

24 Jul '07

Hi zypp developers, You might have seen some eMails with a strange subject "[CruiseControl] libzypp-something build failed" on zypp-commit(a)opensuse.org. So here is the explanation: I set up a CruiseControl server for libzypp. CruiseControl is a service that regularly checks the SVN repository (currently 2 minutes) for new checkins and in case of a change rebuilds the project. If the build fails, CruiseControl sends a notification eMail to zypp-commit(a)opensuse.org. This should lead to "Continuos Integration"[1]. Sorry to all external people - the following is only available internally! SUSE-internal developers can also monitor the build status and request rebuilds via a web interface: http://cit32.suse.de:3333/ You may also add your own project to CruiseControl and let it rebuild on every svn checkin. Connect to the machine via SSH as user "ccrb" (default password). Go to the directory /CI/ccrb . Use the folling command to add a new project: $ ./cruise add project-name -u http://svn.somewhere.org/project-name Eg. this command adds the refactoring branch of libzypp to CruiseControl (this branch is unused now - so please do not add it): $ ./cruise add libzypp-refactoring-10_3 -u http://svn.opensuse.org/svn/zypp/branches/REFACTORING-10_3/libzypp Your new project is located at: /CI/ccrb/projects/project-name In there open the file cruise_config.rb and change it according to your needs. If the build process requires a script also provide it in the same directory. Find example configurations in /CI/config_examples. Please note: The machine is a VMware machine - so please use icecream to build your projects. Please send any questions and recommendations to me. [1] http://www.martinfowler.com/articles/continuousIntegration.html Ciao, Daniel -- J. Daniel Schmidt <jdsn(a)suse.de> SUSE Linux Products GmbH Research & Development Maxfeldstr. 5 GF: Markus Rex, HRB 16746 (AG Nürnberg) D-90409 Nürnberg -- 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] media handling
by Duncan Mac-Vicar Prett 24 Jul '07

24 Jul '07

my media verifier branch was merged andd commited. I re-enabled zypper media callbacks and tested with a CD set. Ladislav, can you check the pkg-bindngs callback is enabled and with the same signature? 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] [PATCH] repo media handling and verifiers for review
by Duncan Mac-Vicar P. 23 Jul '07

23 Jul '07

This patch does the following: - Adds a RepoMediaAccess class, which contains a modified version of the old function repo::provideFile as a member. - The old function is modified, to just instanciate a RepoMediaAccessClass, provide the file and return. The class allows to be instanciated once at begining of commit and passed to PackageProvider. It can serve file request from multiple repositories, and keeps MediaSetAccess objects for different urls, it sets the verifiers automatically, and reset them if a diiferent repo access the same url other repo used before. That means, any repo can provide any file from any url, and only one media will be opened per url. FAQ: - Why not implement it in MediaManager (automatic remember of opened medias) A: ask Marius :-P Please comment, otherwise I will merge my local branch commits to svn trunk asap (we need this) Duncan

1 1

[zypp-devel] Re: [zypp-commit] r6153 - /trunk/zypper/src/zypper.cc
by Duncan Mac-Vicar Prett 23 Jul '07

23 Jul '07

On Monday 23 July 2007 14:34:24 tgoettlicher(a)svn.opensuse.org wrote: > Author: tgoettlicher > Date: Mon Jul 23 14:34:24 2007 > New Revision: 6153 > > URL: http://svn.opensuse.org/viewcvs/zypp?rev=6153&view=rev > Log: > Added "xml-updates" to help command Wouldn't it be more clean/elegant to either add a --xml swtch to the existing list-updates command, or a global switch --xml-output which affects all commands, than adding a new command? Cheers Duncan -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

3 2

[zypp-devel] JFYI: TmpFile/TmpDir::makeSibling( Pathname )
by Michael Andres 23 Jul '07

23 Jul '07

To avoid rename across filesystem boundaries, temp. dirrectories/files should be created as sibling of the target location: dest: /var/lib/somefile temp: /var/lib/somefile.XXXXX Classes TmpDir and TmpFile allow to specify the desired name/location, but most code simply uses the dafault /var/tmp. I added static TmpDir makeSibling( const Pathname & sibling_r ); static TmpFile makeSibling( const Pathname & sibling_r ); as a convenience wrapper for TmpDir/TmpFile( sibling_r.dirname(), sibling_r.basename() ); maybe it helps using better temp locations. -- 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] libzypp in alpha 6 feedback
by Martin Schlander 20 Jul '07

20 Jul '07

I've played a little with alpha 6 - dvd install of x86_64. Generally the new libzypp fully lives up to the high expectations that have been built up - the start up speed and the low ram usage is really a blessing. Almost too good to be true. Of course there are some issues, and I must admit I'm too lazy to add each one to bugzilla while it's still so immature, so I'm just gonna run through 'em quickly here on the list. During installation I do custom partitioning, after that when I return to the "installation Settings" there's suddenly a red text stating that there are dependency issues with the package selection that require manual attention. Among some of the things that reported conflicts were openoffice-kde. I just quickly chose to ignore all the conflicts and moved on, before looking at the matter closer. After installation I added factory to the yast inst src module and then added factory non-oss with zypper. Both worked, but adding with the yast module seemed much slower, which is funny since it wasn't supposed to do anything except add the url / create the repo-file - a y2base-proces seemed to be using quite a lot of cpu while this went on. The DVD wasn't available as installation source after installation, which is of course usually the case. Dunno if this is intended. I didn't add any online sources during installation. In YaST inst-src module the repos seemed to default to being disabled and with autorefresh off. If I turned enable + refresh on manually, they would be off again next time inst-src module is started. Adding repos, refreshing, installing and searching with zypper was extremely pleasurable. Testing integration between sw_single and libzypp seemed impossible as sw_single would say on startup "No installation sources found, only displaying installed packages". While at the same time zypper was working well with the installation sources. -- 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] New repository filter in YaST ncurses - request for testing ;-)
by Katarina Machalkova 19 Jul '07

19 Jul '07

Hello! I've added a new feature to YaST ncurses UI - a list of all available repositories + related filtering of packages according to which repository they belong to. You may know this filter well from Qt UI, in ncurses it's brand new. Since no 'class recycling' could be used ;-) (I've written entirely new class for the filter from scratch) and since new zypp repository handling code has been used (and I'm not a zypp developer), I'd like to ask you for trying and testing this feature. If you do so, please report any segfaults ;-) missing repository information, even ugly dialog layout to me (in Bugzilla, assign to kmachalkova). The first one reporting a bug will receive a beer (or a chocolate, if (s)he prefers that) ;-) How to test: just install new yast2-ncurses 2.15.21and go to Filter->Repositories Thanks frozenB. P.S. Code review is also welcome, the whole thing is pretty well commented and documented -- \\\\\ 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] libzypp and shared library policy
by Duncan Mac-Vicar Prett 18 Jul '07

18 Jul '07

After merging the branch into trunk, and preparing for submission, I got a failure from rpmlint, that we dont follow library policy. http://en.opensuse.org/Packaging/RpmLint http://en.opensuse.org/Packaging/Shared_Library_Packaging_Policy According to the policy, the package name should be libzypp$NUMBER where $NUMBER is the soname. We use right now a special way to create the soname from the package name. So we can avoid increasing the major version when we make interface incompatible changes. For now, I just cheated over rpmlint and I am trying to get the package built for submission, but this has to be fixed somehow. -- Duncan Mac-Vicar Prett Novell :: SUSE R&D, Maxfeldstr. 5, 90409 Nürnberg 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] ZYPP status call - 2007-07-17
by Ladislav Slezak 17 Jul '07

17 Jul '07

Participants: Jiri, Jano, Lada, Lukas, Martin, Michal, Stano, Klaus, Duncan, Michael, Edith, Coolo Old AIs: -------- - UI status - all there UIs (ncurses, qt are gtk) are building in autobuild (ncurses and qt have been submitted today) - Creation of /etc/zypp/repos.d directory - fixed - Media change support - still TODO, currently only one installation medium is supported - Base/add-on product flags - still TODO - Pattern names, packages sizes - should be already fixed Status/problems: ---------------- - Memory leaks - Stano reported severe memory leaks during installation, installation on a 512MB system failed (out of memory) - MoveDownloadArea - conclusion of the discussion is to automatically move the download area in libzypp with possibility to set the path from the application. (Needed in the first installation stage to download packages to the target partition instead to the RAM disk.) - There is no automatic testing in pkg-bindings. Because of missing functionality it's postponed later. - Crash in inst_source has been fixed, online update (YOU) needs more testing - Lukas reported a lock-up when more than one product is registered. Further steps: -------------- - Implement new pkg-bindings to use the new libzypp features (esp. in the installation source manager) (AI: lslezak) - Implement new Progress callbacks with support for "tick" events (AI: lslezak) - QA - we need to test the changes (AI: edith) - All changes should be documented on a wiki page, it's very important for the QA team to get the overview what needs to be tested (AI: duncan) - Documentation (manuals) must be checked and updated (cooperation with Docu team) - Release notes should contain a small notice about the change. - Refresh policy - no conclusion yet, will be discussed on zypp-devel@ The next meeting: ----------------- - Not scheduled yet, we will decide when the first Alpha6 build is available to get the current status. -- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Prague 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

1 0

Fwd: Re: [zypp-devel] ZYPP goes alpha6 -> merging back to TRUNK today?
by Jiri Srain 16 Jul '07

16 Jul '07

Just forwarding to the list... Jiri ---------- Předaná zpráva ---------- Subject: Re: [zypp-devel] ZYPP goes alpha6 -> merging back to TRUNK today? Date: pondělí 16 červenec 2007 11:30 From: Stephan Kulow <coolo(a)suse.de> To: Jiri Srain <jsrain(a)suse.cz> Cc: Michael Andres <ma(a)suse.de>, dmacvicar(a)suse.de, jkupec(a)suse.cz, Andreas Jaeger <aj(a)suse.de>, Klaus Kaempf <kkaempf(a)suse.de> Am Montag 16 Juli 2007 schrieb Jiri Srain: > Hi! > > Dne pondělí 16 červenec 2007 11:17 Michael Andres napsal(a): > > Hi! > > > > Looks like we have some solver enhancements developed in TRUNK. If we > > don't want to loose them again, we should consider merging back the > > refactoring branch into trunk (or vice versa). > > AFAIK the final decission whether to go or not go for Alpha6 has not been > made yet. We should merge refactoring branch to trunk immediatelly after > this decission is made (provided it is possitive). I gave my go on early saturday after testing the beta DVD. Greetings, Stephan -- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) ------------------------------------------------------- -- 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

1 0

[zypp-devel] ZYPP goes alpha6 -> merging back to TRUNK today?
by Michael Andres 16 Jul '07

16 Jul '07

Hi! Looks like we have some solver enhancements developed in TRUNK. If we don't want to loose them again, we should consider merging back the refactoring branch into trunk (or vice versa). Today. -- 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 1

[zypp-devel] ZYPP status call minutes 2007-07-11
by Edith Parzefall 11 Jul '07

11 Jul '07

Participants: Jiri, Jano, Lada, Michal, Klaus, Duncan, Michael, Edith Old AIs: -------- - list of missing functions in package bindings available - qt UI tested and working - ncurses: AI: Katarina, Gabi, Stefan H. to discuss today - test of package bindings, beta not building on all architectures currently. Check if correct libzypp is checked in. AI: Duncan check callbacks, with help of Klaus - parser call backs fixed for YUM, to do for SUSEtags (ma, not necessarily before alpha 6) - commit callbacks: unchanged, nothing to be done. - source creation should basically work, one known bug left to fix. - memory consuption should be fine. Status/open issues: ------------------- Michael: - SuSEtags: share tags, no descriptions or licenses can be displayed with multi-arch sources. - media handling needs intensive testing (AI: Duncan, Michael) - seperate list of source packages needed (not A6, but 10.3) Duncan: - help with parser bug - check media handling works Jiri: - test installation workflow, problems are to be expected, send report by the end of the day. Jano: - bug in package bindings, - test installation workflow. Lada: - product handling, use media products parser problem: only works for products under / not those in the product directory. - check with autobuild team if it has to be that way. Outlook: - Go/no-go decision after installation workflow tests. Check with aj, when the results are available. - Media handling most crucial at the moment. -- 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] pkg-bindings status
by Ladislav Slezak 11 Jul '07

11 Jul '07

Changes in pkg-bindings ----------------------- - Adapted to the latest libzypp (changes in OnMediaLocation) - List of RepoInfo objects is used as the internal status of all installation sources (instead of Repository) - Implemented Pkg::SourceCreate/SourceScan, but there are still problems on the libzypp side - submitted yast2-pkg-bindings-2.15.23 to BETA TODO ==== Missing Pkg:: functions (not implemented) ----------------------------------------- PkgMediaNames() PkgMediaSizes() PkgMediaCount() SourceReleaseAll() SourceSaveAll() SourceFinishAll() SourceMoveDownloadArea() TargetDisableSources() SourceMediaData() SourceProvideFile() SourceProvideOptionalFile() SourceProvideDir() SourceChangeUrl() Missing Functionality --------------------- SourceGeneralData() - doesn't return key "product_dir" in the map SourceDelete() - remove resolvables if they have loaded from the source SourceCreate() - use source type and product directory parameters Testing ------- Automatic testing is currently not possible, the test code (in pkg-bindings/testsuite/devel) haven't been ported to libzypp, that would be an extra work. Overall Status ============== There are missing too many essential Pkg:: functions, I'm afraid that we won't have ready pkg-bindings which can install system by tomorrow evening :-( -- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Prague 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

5 5

[zypp-devel] Callbacks and reports proposal
by Duncan Mac-Vicar Prett 10 Jul '07

10 Jul '07

I have been trying different approaches for progress reporting Here is one of my proposals: New report ProgressReport struct ProgressReport : public callback::ReportBase { virtual void start( const ProgressData &/*task*/ ) virtual bool progress( const ProgressData &/*task*/ ) virtual void finish( const ProgressData &/*task*/ ) }; Most of the methods of ZYpp time consuming tasks accept a ProgressData function, so if you reuse a ZYpp parser in a small program, you can setup your own progress callback. The idea is that RepoManager functions use an ProgressReportAdaptor internally that appart of sending the progress to the user callback, it also sends it to the global ProgressReport. The reports get the complete progress object, and from it they can get a unique runtime id for the task, text, and progress value. I just implemented the receiver for ZYpper like this: struct ProgressReportReceiver : public zypp::callback::ReceiveReport<zypp::ProgressReport> { virtual void start( const zypp::ProgressData &data ) { display_progress ( data.name() , data.min() ); } virtual bool progress( const zypp::ProgressData &data ) { display_progress ( data.name() , data.val() ); return true; } virtual void finish( const zypp::ProgressData &data ) { display_progress ( data.name() , data.max() ); } }; The nice thing is, with this we could remove all Source*Reports. Only internal reports like media change and download needs to be kept. Internally, ZYpp uses ProgressData and CombinedProgress data to produce quite nice estimates for progress. If you like the idea, I would add later (next week?) an Error class (or use Exception), a Message class, and provide in the same report perhaps some generic user interaction like continue-cancel, press-ok, etc. -- Duncan Mac-Vicar Prett Novell :: SUSE R&D, Maxfeldstr. 5, 90409 Nürnberg 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] Extending pattern definition
by Jiri Srain 09 Jul '07

09 Jul '07

Hi! In order to allow workflows bound to patterns we need to extend the pattern definition on the media as well as the database and in-memory representation of a pattern. We need following tags: "workflow_file" : string // file describing the workflow on the media "workflow_file_checksum" : the same as other checksums "workflow_order" : string // to allow ordering, string for better extendibility (the names can be adapted to fit attribute naming schema) The suggestions for the SuSEtags metadata format are =Wkf =WkfCSum (if not specified in content file) =WkfOrd ZYPP is not required to process this data anyhow (maybe except the checksum?), all that's needed is to deliver the data to YaST. The update of package bindings will be trivial. The document is (inside Novell network) available at http://users.suse.cz/~locilka/PatternsAndAddOnsWithWorkflows/proposal-2007-… Duncan, Jano, is it possible to get this implemented for 10.3? -- 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

5 18

[zypp-devel] pkg-bindings - how to test/help
by Ladislav Slezak 09 Jul '07

09 Jul '07

Hi all, here is a short summary how to install/test the new pkg-bindings from the SVN repository: 1. svn co http://svn.opensuse.org/svn/yast/branches/REFACTORING-10_3/pkg-bindings/ 2. make -f Makefile.cvs 3. make 4. sudo make install 5. test - start e.g. 'yast2 inst_sources' or any other yast module Notes: - It requires the latest libzypp (from REFACTORING branch) and yast development packages - It installs into /usr prefix ! - There are missing functions (see the status mail) -- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Prague 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

1 0

[zypp-devel] Re: [zypp-commit] r5933 - in /branches/REFACTORING-10_3/libzypp/zypp: RepoInfo.cc RepoInfo.h
by Klaus Kaempf 09 Jul '07

09 Jul '07

* dmacvicar(a)svn.opensuse.org <dmacvicar(a)svn.opensuse.org> [Jul 09. 2007 14:57]: > Author: dmacvicar > Date: Mon Jul 9 14:57:21 2007 > New Revision: 5933 > > URL: http://svn.opensuse.org/viewcvs/zypp?rev=5933&view=rev > Log: > > provide numeric id on run time for RepoInfo, useful > for YaST, useless for the rest of the world. Please keep a list of those things (e.g. http://en.opensuse.org/Libzypp/Refactoring/Cleanup or a DEPRECATED comment in the .cc or .h file) so we can address them in the future. Klaus -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

3 2

[zypp-devel] ZYPP status call minutes 2007-07-09
by Jiri Srain 09 Jul '07

09 Jul '07

New AIs: Lada: create list of missing functionality in PkgBindings ASAP HuHa: test package selector in Qt Gabi/someone else: test package selector in NCurses Lada: post information how to test pkg bindings me: check failing packages in Beta with their maintainers Status: - callbacks for source handlings are done - some work done on SuSEtags parsing - sources during update - Duncan will take care later (not urgent now) - variables in URL - discussion about which ones to support, no result - root for target will be specified as it is now for 10.3 (while initializing target) - ZYPP locking - will be kept as it is for 10.3 - PkgBindings: - SourceCreate WIP, other bindings almost ready - hopefully ready by the end of day - Lada will write short status today - in case of any problem raise the flag ASAP -- 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] Submitted libzypp-3.11.1 and yast2-qt-2.15.6 to BETA
by Michael Andres 09 Jul '07

09 Jul '07

yast2-qt-2.15.6 in BETA is ready to be tested. Esp. the former InstSource view - now 'repository'. -- 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 1

[zypp-devel] class functions!!!! Polluted APIs
by Duncan Mac-Vicar Prett 06 Jul '07

06 Jul '07

Some notes on adding functons to classes. Schubi ran nto a problem today where the testsuite pass on his system but failed into the autobuild environment, because target was not able to create the directories in /var/lib/zypp (non-root), while in schubi's machine this directories already existed. The reason was, in a piece of code of the test suite, the target was initialized, to use the getResolvablesToInsDel function. Accessing the target in the testsuite is sick. Because the installed resolvables come from a xml file, and not on the system target, you don't want to make the testsuite results to depend on the host system installed programs. So as long you access the target and you should't you should realze the function you are calling it is in the wrong place. Lets check the function. void TargetImpl::getResolvablesToInsDel ( const ResPool pool_r, TargetImpl::PoolItemList & dellist_r, TargetImpl::PoolItemList & instlist_r, TargetImpl::PoolItemList & srclist_r ) const { pool::GetResolvablesToInsDel collect( pool_r ); MIL << "GetResolvablesToInsDel: " << endl << collect << endl; dellist_r.swap( collect._toDelete ); instlist_r.swap( collect._toInstall ); srclist_r.swap( collect._toSrcinstall ); } So, the function does not access any TargetImpl data, so _why_ is it in the class? Unless you have workflow classes (or facades) you don't need to have the function in the class. Look this function. It operates on the pool data, and it is const, so you can safely have it in the pool, without touching its contents. But having it in Target (with no reason ) means you have to init the target before using it, and lot of things happen during target init. The worst part, the comment on the functon docs: /** JUST FOR TESTSUITE */ /** Sort according to prereqs and media numbers */ If it was only needed by the testsuite, why not just using zypp/pool/GetResolvablesToInsDel.h directly, after all the other function just copies the lists from the collected functor, why not doing that in the testsuite itself? I removed the functon from Target interfaces, Schubi modified the testsuite to use GetResolvablesToInsDel.h directly. So, if you can't find a place where to put a function it, just make it a global function in a namespace, you will at least avoid initializing an object just to use that functon!. -- Duncan Mac-Vicar Prett Novell :: SUSE R&D, Maxfeldstr. 5, 90409 Nürnberg 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] Submitting libzypp-3.11.0 to BETA
by Michael Andres 05 Jul '07

05 Jul '07

- Package::location is now returns an OnMediaLocation - ResObject::archivesize() renamed to downloadSize() At least the above requires changes to zypper, kg-bindings and the UIs. - Allow to iterate all Repositories that contribute Resolvables to the Pool. - MediaSetAccess::provideDir added - remove useless url check - add old-api-style wrapper - Add MediaProducts class - revision 5892 - version 3.11.0 -- 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: [yast-devel] [RFC] QueryBuilder and (Resolvable)Query
by Michael Andres 05 Jul '07

05 Jul '07

On Tue, Jul 03, Katarina Machalkova wrote: > Hola! > > > A 'Selectable(Package,glibc)' will contain at most ONE installed, > > and all available glibc packages. ;( > > > > There is no difference, unless more than one version of a package > > is installed. In that case there are as many Selectables as there > > are versions installed. Each Selectable links to only ONE installed > > but to ALL available versions. > > > > Unfortunately we support this (e.g. multiple kernel versions being > > installed at the same time). > > My apologies for the dumb question *), but if the concept of selectables has > so many drawbacks, why did we decided to use it? Why didn't we switch to > PoolItems instead? Can anyone (Michael, HuHa,...) comment on that in some > human-readable, easy-to-understand way? Historical. You may remember the first libzypp was a bit late, so there was little time to migrate the UI from using the old y2pm to zypp. In the old y2pm the status information was kept in a 'Selectable'. This was possible, because the old y2pm neither supported multiple installed nor multiple available versions. There was at most one installed and one available item and the status. Now we may have multiple installed and multiple available versions. And each item has it's individual status. We tried to find some 'Selectable' that allowed to reuse as much of the existing UI code as possible. An Item that mangles the individual stati into one UI-status. And we found one, but it has some drawbacks. The concept of a "Selectable" is right. An easy view and access to the pool. Pkg-bindings and zypper would like to use something like this as well. Changing (fixing) the ui::Selectable will lead to changes at the UI. But it would allow us to bring PoolItems and Selectables closer together. Or we had to invent something in parallel to the ui::Selectable for Pkg-bindings and zypper. -- 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] ZYpp and name conventions
by Duncan Mac-Vicar Prett 05 Jul '07

05 Jul '07

zypp::CheckSum OnMediaLocaton::checksum() ResObject::mediaNr() OnMediaLocaton::medianr() ResObject::licenseToConfirm() data::Packagebase::repositoryLocation::filepath OnMediaLocation::filename data::Packagebase::repositoryLocation::fileSize OnMediaLocation::downloadsize Not counting that I fixed OnMediaLocation and PackageDelta to use set* for setters instead of the getter naming they where using. What is the purpose of naming everything different, sometimes capitalizing, sometimes not, sometimes everything downcase, sometimes underscores. It just makes everything non-intuitive. Also every developer needs a reference card to know what fileSize, downloadsize, archvesize etc is. We _have to define_ some naming convention. Ths language is not easy to refactor. Some interesting read... http://doc.trolltech.com/qq/qq13-apis.html Duncan -- 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] pkg-bindings in BETA - status
by Ladislav Slezak 04 Jul '07

04 Jul '07

Hi all, I just have submitted yast2-pkg-bindings to BETA. Many bindings have partial or empty implementation and it's completely untested. But it at least compiles and we should be able to see really failing packages in BETA (the failures which are not caused by dependency to pkg-bindings). It needs the latest libzypp from SVN, it might be still failing in autobuild until libzypp is submitted. If anybody is interested in fixing/improving pkg-bindings just check it out from http://svn.opensuse.org/svn/yast/branches/REFACTORING-10_3/pkg-bindings/ Look for '#warning', 'TODO' and 'FIXME' strings for missing functionality. (BTW I'll be out of office until the next Monday.) Ladislav -- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Prague 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

1 0

[zypp-devel] ResPool now provides an iterator to visit all repositories
by Michael Andres 04 Jul '07

04 Jul '07

JFYI: (branches/REFACTORING-10_3) ResPool now provides an iterator to visit all repositories, that contibute Resolvables to the pool: size_type knownRepositoriesSize() const; repository_iterator knownRepositoriesBegin() const; repository_iterator knownRepositoriesEnd() const; (*repository_iterator is type Repository). -- 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] Important open issues inside zypp
by Michael Andres 04 Jul '07

04 Jul '07

Important open issues inside zypp: - The repo handling needs intense testing. Bugs I experienced last week show, that the code compiles but needs testing. RepoManager failed to create required directories. Several exceptions due to malformed URLs created from pathnames. And there's only little information in the log; too few milestones and error messages. - Still not all resolvables stored in the cache are recreated and fed into the pool. Diskusage data is not yet parsed and stored in the DB. - Providing packages in commit incl. support for patch and delta rpms? Duncan provided code for this, I don't know the status. - Some progress reports are not yet connected to the callbacks. And we need of course feedback from pkg-bindings, to see what's missing to launch the repositories and get the resolvable data into the pool. -- 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 3

[zypp-devel] Init of ZYpp configuration and root
by Duncan Mac-Vicar P. 03 Jul '07

03 Jul '07

Hi We have to think about the sequence and layers of configuration to make it consistent this time. I list the requirements that come to my mind - the most important cfg option is the root where you are operating on. In former times this was a Target option, and I think it still is (????) - known repositories raw metadata path, binary cache path, system architecture, etc, needs to be easily configurable/overridable. A zypp.conf file (ini file) would be a nice way to do it. So we have to determine the workflow: - when to set the target root - when do we read values from the config file - do we append the root to every value or is every value absolute, etc Duncan -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

4 7

[zypp-devel] Re: [yast-devel] [RFC] QueryBuilder and (Resolvable)Query
by Jan Kupec 02 Jul '07

02 Jul '07

Stefan Hundhammer wrote: > On Friday 29 June 2007 15:14, Jan Kupec wrote: >> Here is my proposal of a new libzypp API for various metadata queries. >> It should be useful for YaST package managers, zypper, YaST online >> update and maybe others. Pease see attached QueryBuilder.h file and >> comment on the design and usability. >> >> QueryBuilder is meant to build an sqlite query for libzypp's metadata >> cache database and to be used by >> ResolvableQuery::query(QueryBuilder,ProcessingFunctor) function (or >> other Query class) to do complex resolvable data queries. Result of >> these queries will be processed by ProcessingFunctor (read on). >> >> The reason to create such an API is to have a convenient API for coding >> various kinds of user queries, so that apps using libzypp don't have to >> code the functionality by themselves by traversing the resolvable pool. > > That's a nice API for querying resolvables. Will there be a counterpart for > querying selectables (which is what the UI needs), too? Sure! Note the comment in parenthesis after the code example: (the functor is function<bool( const data::RecordId &, data::ResObject_Ptr )> we can provide one which would use Selectables (or NameKindProxy) for yast as well) I hope it will be doable in a resource-sparing way. Maybe by adding name and kind to the 'order by' clause of the query so that the resolvables belonging to one selectable can be collected as the result is read. Anyway, the data::RecordId should probably better be hidden, so the functions might look like: function<bool(const zypp::Resolvable::Ptr &)> and function<bool(const zypp::ui::Selectable::Ptr &)> for YaST j. -- 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] Playing with sqlite cache
by Duncan Mac-Vicar P. 02 Jul '07

02 Jul '07

The cached RepoImpl sets the cache to something bigger, but CacheStore just used the default. For a sets of small repos plus 10.2 repo, playing with the sqlite3 cache size changed writing (done during parsing) times: default (2000) 30.122s 8000 0m25.415s 10000 24.443s 15000 23.567 20000 23.529 You can see the curve has an optimum at 10 M or 15 M (is it worth to use 5 mb to save 1 more second?) but this value should depend on the amount of data you write. It would be cool we could optimize this value on runtime depending on the situation. Duncan -- 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] Yast package to be ordered by date
by Lassi Väätämöinen 02 Jul '07

02 Jul '07

Hi all! Here's my idea of making Yast even more user friendly with apparently rather small tweak(?) http://idea.opensuse.org/content/ideas/order-packages-in-yast-by-date Cheers, -Lassi -- 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] use case question: repository setup rpm.
by Michael E Brown 02 Jul '07

02 Jul '07

I have some questions regarding repository setup for zypp. I know the "zypper service-add ..." stuff, and I currently have the Dell public repositories bootstrap script use this in the script. I was looking to improve this, though. For yum setup, the setup is simply this: drop a "dell.repo" file in /etc/yum.repos.d/. This is quite nice for the simple reason that it is something that RPM manages to do exceedingly well. I have a "dell-unsupported-repository-1-1.noarch.rpm" that I use for this purpose. The other nice thing about this is that I can very easily manage the transition from config to config. For example, if I make a change to the repository layout, I can release updated repository RPMs with the new configs. As I normally will make the old and new layouts compatible, I can simply wait a period of time before removing the backwards compatibility (either symlinks or http redirects, etc). This makes things nice and easy to manage from my side. For zypper, I dont see a nice way to update the client's configs easily via RPM. I tried to do the "zypper service-add ..." inside the RPM %post, but all I managed to do was hang zypper when the RPM was updated as part of a zypper upgrade. What is a good way to handle this situation? Is there something that can be added to the next version to address this? Note: All my testing was carried on on SLES10 and SLES10 SP1. Thanks, Michael Brown Maintainer, Dell unofficial yum repos Dell, Inc -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

2 2