October 2008 - Zypp Development - openSUSE Mailing Lists

[zypp-devel] Re: [zypp-commit] r11408 - /trunk/libzypp/zypp/repo/PackageDelta.cc
by Michael Andres 20 Oct '08

20 Oct '08

On Monday 20 October 2008 15:30:48 kkaempf(a)svn.opensuse.org wrote: > Log: > fix Dataiterator_init call > > Modified: > trunk/libzypp/zypp/repo/PackageDelta.cc > > Modified: trunk/libzypp/zypp/repo/PackageDelta.cc > URL: > http://svn.opensuse.org/viewcvs/zypp/trunk/libzypp/zypp/repo/PackageDelta.c >c?rev=11408&r1=11407&r2=11408&view=diff > =========================================================================== >=== --- trunk/libzypp/zypp/repo/PackageDelta.cc (original) > +++ trunk/libzypp/zypp/repo/PackageDelta.cc Mon Oct 20 15:30:48 2008 > @@ -36,7 +36,7 @@ > { > MIL << "creating deltarpm from repo " << repo.alias() << ", id " << > extraid << endl; > > ::Dataiterator di; > > - ::dataiterator_init(&di, repo.get(), extraid, 0, 0, 0); > + ::dataiterator_init(&di, NULL, repo.get(), extraid, 0, 0, 0); Don't fix it that way. dataiterator_init segfaults with a NULL 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 4

[zypp-devel] satsolver: dataiterator_init needs Pool and Repo, why ?
by Klaus Kaempf 20 Oct '08

20 Oct '08

Why does dataiterator_init() need a Pool and a Repo pointer ? The Pool pointer is already inside the Repo structure. Klaus --- 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

4 5

[zypp-devel] Simulating web access in test cases
by Duncan Mac-Vicar Prett 17 Oct '08

17 Oct '08

Since we have had lot of bugs that happen only on http access and not on direct file access, I wanted to have this testable as well. I have committed a embedded web server for testcases, it is not very stable yet because I had to do some boost threads magic, but it already helps Fetcher testcase to test http access. you use it something like:: /** * * Starts a webserver to simulate remote transfers in * testcases * * \code * #include "WebServer.h" * * BOOST_AUTO_TEST_CASE(Foo) * { * * WebServer web((Pathname(TESTS_SRC_DIR) + "/datadir").c_str() ); * web.start(); * * MediaSetAccess media( Url("http://localhost:9099"), "/" ); * * // do something with the url * * * web.stop(); * * \endcode */ -- 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] Some changes related to writing zypp test cases.
by Michael Andres 17 Oct '08

17 Oct '08

Hi!. Some changes related to writing zypp test cases. zypp-trunk rev. 11223: - added tests/data/openSUSE-11.1 containing raw susetags metadata. Keeping .solv files in svn is somewhat inconvenient, as you must rebuild them if something in satsolver changes. - added tests/include as location for includes that might be used in multiple testcases. - added tests/include/TestSetup.h to ease building a test environment below some tempdir. Currently supports easy setup of Target, RepoManager and loading data (raw metadata and .solv files) into the pool. That's how it currently looks like: #include "TestSetup.h" BOOST_AUTO_TEST_CASE(WhatProvides) { TestSetup test( Arch_x86_64 ); // use x86_64 as system arch test.loadTarget(); // initialize and load target test.loadRepo( TESTS_SRC_DIR"/data/openSUSE-11.1" ); This is all you need to setup Target, RepoManager below some temp directory and load the raw metadata into the pool. In case you want to setup the system below some fix directory, use: TestSetup test( "/tmp/mydir", Arch_x86_64 ); You directory is used as it is and not removed at the end. Feel free to add whatever helps you writing testcases. -- 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 2

[zypp-devel] Re: [zypp-commit] r11377 - in /trunk/libzypp/zypp: RepoManager.cc RepoManager.h
by Duncan Mac-Vicar Prett 17 Oct '08

17 Oct '08

jkupec(a)svn.opensuse.org wrote: > Author: jkupec > Date: Thu Oct 16 17:59:17 2008 > New Revision: 11377 > > URL: http://svn.opensuse.org/viewcvs/zypp?rev=11377&view=rev > Log: > - repository license methods added to RepoManager (bnc #372386) > > Modified: > trunk/libzypp/zypp/RepoManager.cc > trunk/libzypp/zypp/RepoManager.h > All the 10.1 to 10.2 refactoring was to move that stuff out of repository classes. Similar functions are in : http://svn.opensuse.org/svn/zypp/trunk/libzypp/zypp/repo/RepoProvideFile.h -- 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] r11300 - /trunk/libzypp/cmake/modules/ZyppCommon.cmake
by Michael Andres 14 Oct '08

14 Oct '08

On Saturday 11 October 2008 13:01:47 dmacvicar(a)svn.opensuse.org wrote: > Author: dmacvicar > Date: Sat Oct 11 13:01:47 2008 > New Revision: 11300 > > URL: http://svn.opensuse.org/viewcvs/zypp?rev=11300&view=rev > Log: > use more standard spec.in than spec.cmake It's been consistent. Why now a mixture of .cmake and .in? ./doc/autodoc/Doxyfile.cmake ./VERSION.cmake ./libzypp.pc.cmake ./package/libzypp-rpmlint.cmake but ./libzypp.spec.in -- 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] JFYI: 'the big solv data change' - satsolver and zypp are currently broken
by Michael Andres 09 Oct '08

09 Oct '08

Hi! The latest satsolver in svn::trunk is broken, and libzypp is already adapted to the new interfaces. So currently everything compiles, but creation of solvfiles frequently fails. And maybe other things too. AFAIK revision 11278 is the last stable one. -- 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] Enabled distupgrade of the SAT solver
by Stefan Schubert 07 Oct '08

07 Oct '08

Hi, I have enabled the distupgrade of the SAT solver. In order to use the old distupgrade you can set the environment variable ZYPP_NO_SAT_UPDATE. But this should be used as fallback only :-) This variable will can be used until the old distupgrade mechanism will be removed from libzypp. I will send an EMAIL when this happens. 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

4 6

[zypp-devel] Re: [softwaremgmt] zypper-0.12.7 update/list-updates now defaults to --type package
by Duncan Mac-Vicar Prett 06 Oct '08

06 Oct '08

Susanne Oberhauser wrote: > Duncan Mac-Vicar Prett <dmacvicar(a)suse.de> writes: > > A patch can trigger the installation of a pacakge that wasn't on > your system before, can't it? > No > Sometimes the newest package is not good for everybody, and patches > allow you to be selective on when to update a package and when not to > update it. > > No. Patch just conflict with the last version with the problem, so selecting the "patch" it will select the latest version of the packages (from the same vendor). If you are selecting an specific version of a package, then you are not operating over patches anymore. Also, making a patch require an exact version of the package would have no sense for a dependency solver, as then updating to a newer version of the package would break the patch, unless a new patch obsoletes it, which would be quite a lot of work and confusion. > For example, when it comes to drivers, patches can allow you to select > specific package versions for specific hardware versions, using the > modalias, while the packages overclaim they were good for everything. > Also no. Patches did not had different packages for different hardware. It is the solver that selects the packages based on the modalias. modalias has nothing to do with patches. > Basically I think the package update is best for those repos that do > not provide patches. > Technically, unless you select a patch manually, a full system "update" is no real difference between packages and patches since patches are not installed. The result of applying all patches has to be the same as the result of updating all packages. As I said, it is just a different view. > So why did I ask wether they can be done both at the same time? > Again, it is no difference. > To update all packages and to also get all additional changes that are > triggered by the patches. > > Those changes are zero AFAIK now. Scripts could had been a reason, but now scripts are in packages too... > However the most important thing to me is to tell in repos.d/*.conf > wether to do package or patch updates per default on this or that > repo, I have use cases for that. The other one (patches and packages > in one run) to me is less important. > Again, it is just a different view on the system. The content is the same. Duncan -- 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] Some changes related to libzypp autodocs (doxygen)
by Michael Andres 02 Oct '08

02 Oct '08

Hi! @Revision: 11232 I removed the mostly unsudes doxygen files from the source tree (/libzypp/zypp/@DOXYGEN) and created a new place where to create documentation pages that should be included in the autodocs: /libzypp/doc/autoinclude/ You'll find a README and some examples there. Basically, to write a related page, create a file and include a doxygen comment block like this: --[MyTopic.doc]----- /** \page MyTopic A documentation for MyTopic. Leading text. \section sec1 An example section This page contains the subsections \ref subsection1 and \ref subsection2. For more info see page \ref page2. \subsection subsection1 The first subsection Text. \subsection subsection2 The second subsection More text. */ /** \page page2 Another page Even more info. */ ------------------------------ (..I know - it's doxygen ;) If you want your page to appear somewhere else than in 'Related Pages', use \subpage to create the link. E.g. from within the main page (Mainpage.doc): --[Mainpage.doc]----- /** \mainpage Welcome to libzypp More info about this: - \subpage MyTopic */ ------------------------------ Just in case someone really writes a bigger set of pages, and wants to run doxygen without scanning the sourcetree: In doc/autodoc/Doxyfile.cmake change -INPUT = @ZYPP_DOCINCLUDE_DIR@ @ZYPP_SOURCE_DIR@ +INPUT = @ZYPP_DOCINCLUDE_DIR@ and use 'make doc_forced' to force rebuilding the autodocs. -- 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