March 2009 - Zypp Development - openSUSE Mailing Lists

[zypp-devel] zypp.conf: Hint which media to prefer when installing packages (download vs. CD).
by Michael Andres 31 Mar '09

31 Mar '09

Hi! <libzypp> master: I'd like to add this option to zypp.conf: ## ## Hint which media to prefer when installing packages (download vs. CD). ## ## Valid values: download, volatile ## Default value: download ## ## Note that this just a hint. First of all the solver will choose the 'best' ## package according to its repos proiority, version and architecture. But if ## there is a choice, we will prefer packages from the desired media. ## ## Packages available loacaly are always prefered. The question is whether ## you prefer packages being downloaded via FTP/HTTP/HTTPS (download), rather ## than being prompted to insert a CD/DVD (volatile), in case they are available ## on both media. ## ## Name | Priority | URI ## openSUSE-11.1 99 dvd:/// ## openSUSE-11.1-Oss 99 http://download.opensuse.org/distribution/11.1/repo/oss ## ## In the above example 2 repositories with similar content are used. Rather ## than raising the priority of one of them to 'prefer' a certain media, you ## should use the same priority for both and set download.media_preference ## instead. ## ## download.media_preference = download The media preference will be passed to the solver in form of sub-priorities. This will make the solver prefer packages from a specific media, within a set of equal prioritized repos. Comments? -- 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] find/use fastest mirror?
by PGNet 30 Mar '09

30 Mar '09

using, zypper dup with, e.g., a repo @, http://download.opensuse.org/repositories/KDE:/KDE4:/Factory:/Desktop/openS… i understand the redirectors 'pick' a mirror for me. occassionally, a really slow mirror is picked, e.g., Retrieving: http://download.opensuse.org/repositories/KDE:/KDE4:/Factory:/Desktop/openS… [done (3.6 K/s)] poking along @ just a few K/s ... is is possible to find/specify "fastest mirror" in zypper? i'm looking for functionality similar to that in yum, http://wiki.centos.org/PackageManagement/Yum/FastestMirror thanks. -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

2 5

[zypp-devel] Re: [opensuse] Zypper segmentation fault
by Jan Kupec 30 Mar '09

30 Mar '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Γαβριήλ Παπαδάκης wrote: > This is my first post, so please forgive me for not describing correctly the > situation. My home workstation (OpenSuSE 10.3 32bit) has been receiving fairly > regularly, albeit manually (every 2-3 days) the official updates, except for the kernel related > ones. I admit having several OBS repositories enabled, as well as Packman, > Gtk:STABLE and KDE:Backports. I try to be careful about updating major > infrastructure, always checking the list of packages to be upgraded or > installed, refreshing the repos before any updating takes place, > not using any updaterapplet and going mostly through yast2. Yesterday, trying > to launch any software management app through yast resulted in the window > taken down. Trying the cli greeted me with this: > > PENTIUM:/var/log # zypper lr > Repository 'openSUSE BuildService - Wine CVS Builds' is up to date. > Segmentation fault > YaST got signal 11 at YCP file /usr/share/YaST2/clients/repositories.ycp:761 > /sbin/yast2: line 386: 12277 Segmentation fault $ybindir/y2base $module > "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2QT_ARGS Did we release some 10.3 update recently? - -- cheers, jano Ján Kupec YaST team - ---------------------------------------------------------(PGP)--- Key ID: 637EE901 Fingerprint: 93B9 C79B 2D20 51C3 800B E09B 8048 46A6 637E E901 - ---------------------------------------------------------(IRC)--- Server: irc.freenode.net Nick: jniq Channels: #zypp #yast #suse #susecz - ---------------------------------------------------------(EOF)--- -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAknQp8kACgkQgEhGpmN+6QHvoQCfdUjA9/yu6xx52rVMvg5iQqM3 NfgAn30T2/l8D/JHHC/PKZNxJZ2bxWsR =+mJ9 -----END PGP SIGNATURE----- -- 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] sat-solver and solvable:mediadir
by Jan Blunck 30 Mar '09

30 Mar '09

I found out that the satsolver Python bindings return a bool object ("True") if solvable:mediadir is not existing in the solv file. This happens with the solv files generated from buildservice repositories like http://download.opensuse.org/repositories/home:/janblunck/openSUSE_Factory/. Is solvable:mediadir a required field and therefore a bug in repo2solv? Thanks, Jan -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

4 9

[zypp-devel] git.opensuse.org/projects/zypp/*- Rebase origin/SuSE-SLE-10-SP3-Branch?
by Michael Andres 25 Mar '09

25 Mar '09

Hi! About one year ago SuSE-SLE-10-SP3-Branch was created, but AFAIK not used for zypp. All development took place in the SP2 branch. The same is probably true for zypper and the other zypp/ projetcs. Instead of backporting all the SP2 fixes, can't we rebase the SuSE-SLE-10-SP3-Branch to the current SuSE-SLE-10-SP2-Branch, and continue from there? So we don't lose any of the stuff we did for SP2. Now: x SuSE-SLE-10-SP2-Branch | x x SuSE-SLE-10-SP3-Branch |/ x After rebase: | x SuSE-SLE-10-SP3-Branch / x SuSE-SLE-10-SP2-Branch | x | x We should do this before we start to work on SP3. Objections? -- 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] Regarding Google Summer Of Code Project
by sarguru 22 Mar '09

22 Mar '09

I am a B.Tech Information Technology (IV semester) student from National Institute Of Technology , Jaipur,India.I am interested in a project titled Configuration and Package Management Rollback . I have been using linux for quite a lot of time from now on and i have been sing open suse for almost a couple of years. I have found two or three ideas to proceed with the project including using LVM snapshots/making a separate directory(not usual/usr/bin or sbin ) and keeping the old configuration files when the update is done(for package management) etc., Even though the project doesnt involve heavy coding work i fel this is the project of high importance of degree of usefulness that it may provide people. I want to contact people who are working on related projects / potential mentors for the project(since the name of the mentor is not up in the list). Please mail me the possibility of this project being selected/things you require from me and so on. Thanks. Sargurunathan M Department Of Computer Engineering, Malviya National Institute Of Technology, Jaipur, India. -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ -- 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 needed (zypp) solver API additions
by Jan Kupec 18 Mar '09

18 Mar '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! I've put together the following list of things that would be nice to have in libzypp API. These are needed by command line apps like zypper or ruby/python scripts using the bindings, since they typically do not select packages to install by pointing at one particular package from a list of available (GUI/TUI way), but rather by package name or capability plus some preferences like repo, arch, version. Also, because of this, a command line app either needs a feedback from solver about the requested operation, or it needs to get a clue whether the operation will succeed in advance. Example: either: request to install package with given name, solve, get feedback from solver that the package is already installed, tell the user or: check whether the best package is already installed (no update candidate is available), and either tell the user it already is, or tell the solver to install it. More complex example would be bnc #482307: there is a higher version of a package available, but in repo with lower priority. In GUI, if you wondered why it does not upgrade a package, you could check the Versions tab, and you could click to choose the version. In CLI, e.g. when you do 'zypper up foo' it should tell you "no update candidate for foo found" plus a hint "foo x.y.z is available in repository 'bar' which has priority X. Use 'zypper in foo-x.y.z' or whatever to install that package.". The following could help. The list: (notes below) - --------- a) install package with given name (1), plus optionaly: - enforce specific version (2) - enforce specific repo (2) - enforce specific arch (3) - force the operation: if appropriate package is already installed, reinstall it, considering given version/repo/arch preferences (meaning even if specified version is already installed, reinstall; evein if better version that the specified is installed, downgrade; etc - we should before make a list of all cases before implementing). b) install pacakge with given capability, plus optionaly: - enforce specific version (we have this) - enforce specific repo - enforce specific arch (4) - force the operation (like above) c) update package with given name (7), plus optionaly: - enforce specific repo - adjust update policy (vendor change, arch change, etc.) d) find the best package with given name (5) - plus the options available in a)? e) find update candidate for given installed package having the same arch, plus optionally: - having any compatible arch - from specified repo - regardless of priorities - regardless of vendor - maybe other policies f) Install srcpackage _without_ build deps (6) - with specified version - from specified repo g) Remove a package by name (8) - plus enforce specific version (for multiversion packages) h) Remove a pattern - needs to be defined - could be something like remove all packages required[/recommended/suggested] by the pattern. If a), b), c), f), g) are provided, d) and e) are needed as the hint, to give the user feedback. Anything else? If you agree to have these in libzypp, i'd like to help implementing them, of course, since this is quite a lot of work but it would move the burden from zypper to libzypp. But more than that, it would allow to add these to libzypp testsuite, and it would make the functionality available to ruby/python via bindings. Notes: (1) Currently zypper chooses the best package by itself and does ResStatus::setToBeInstalled(zypp::ResStatus::USER). It could use The new solver API (SolverQueueItemInstall + resolveQueue(), but that currently lacks the other capabilities - forcing arch/version/repo, and one has to be carefull not to mix resolvePool() and resolveQueue()). (2) Currently zypper needs to do this by itself (3) Currently zypper would need to do this by itself (not implemented) (4) Currently zypper appends .arch to the capability name to do this (5) Something like Selectable::candidate(), but that's rather GUI/TUI specific. We need also a method that would return the best no matter what is already "transacting" or installed. (6) Currently it automatically drags the build deps in, apps need to use ZYpp::installSrcPackage(srcpkg) (7) Similarly like in (1), SolverQueueItemUpdate could be enhanced? (8) SolverQueueItemRemove seems to do this, but does not allow to choose name/capability, and version. BTW: do we have a list of solver policies somewhere (else than the satsolver source code :O) and a list of possible ways to change them? - -- cheers, jano Ján Kupec YaST team - ---------------------------------------------------------(PGP)--- Key ID: 637EE901 Fingerprint: 93B9 C79B 2D20 51C3 800B E09B 8048 46A6 637E E901 - ---------------------------------------------------------(IRC)--- Server: irc.freenode.net Nick: jniq Channels: #zypp #yast #suse #susecz - ---------------------------------------------------------(EOF)--- -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkm3p9UACgkQgEhGpmN+6QG0igCeL8AdKBNBUTDBhxCKzG/CHJsV ADoAn2dra8hKgEV/ZNCNux/MLiLgyvfo =JrwM -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

4 8

[zypp-devel] [PATCH 1/3] Let Solver.solve() return a bool in Python
by Jan Blunck 18 Mar '09

18 Mar '09

Let the Python binding return a bool from Solver.solve() as described in the documentation. Signed-off-by: Jan Blunck <jblunck(a)suse.de> --- bindings/python/tests/solvable.py | 5 +++-- bindings/solver.i | 5 +++++ 2 files changed, 8 insertions(+), 2 deletions(-) diff --git a/bindings/python/tests/solvable.py b/bindings/python/tests/solvable.py index d25a389..7c53659 100644 --- a/bindings/python/tests/solvable.py +++ b/bindings/python/tests/solvable.py @@ -76,9 +76,10 @@ class TestSequenceFunctions(unittest.TestCase): transaction = self.pool.create_transaction() transaction.install( solv1 ) - solver = self.pool.create_solver( self.pool.create_repo( "system" ) ) + solver = self.pool.create_solver() # self.pool.debug = 255 - solver.solve( transaction ) + res = solver.solve( transaction ) + assert res.__class__.__name__ == 'bool', res.__class__.__name__ # solver.each_to_install { |s| # puts "Install #{s}" # } diff --git a/bindings/solver.i b/bindings/solver.i index 768793d..ea9c3c3 100644 --- a/bindings/solver.i +++ b/bindings/solver.i @@ -785,6 +785,11 @@ typedef struct solver {} Solver; %typemap(out) int solve "$result = $1 ? Qtrue : Qfalse;"; #endif +#if defined(SWIGPYTHON) +%typemap(out) int solve { + $result = PyBool_FromLong((long) ($1 ? 1 : 0)); +} +#endif /* * Solve the given Transaction * -- 1.6.1.3 -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

3 17

[zypp-devel] Code 11 libzypp and patches.xml
by Michael Schroeder 17 Mar '09

17 Mar '09

Hi Zypp folks, can someone think of any reason why we still look at patches.xml when reading repositories? We can't handle "old style" patches with atoms anyway, so wouldn't it be safer to just ignore them? See the disaster with the ATI and NVidea Repos... Cheers, Michael. -- Michael Schroeder mls(a)suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- 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] [PATCH] Add pool iterate testcase
by Jan Blunck 17 Mar '09

17 Mar '09

This is a replacement for the removed testcase from commit 1d7329e8c21e125b10b910684665af891f44af6e. Signed-off-by: Jan Blunck <jblunck(a)suse.de> --- bindings/python/tests/solvable.py | 4 ++++ 1 files changed, 4 insertions(+), 0 deletions(-) diff --git a/bindings/python/tests/solvable.py b/bindings/python/tests/solvable.py index 141368f..8a7bdaa 100644 --- a/bindings/python/tests/solvable.py +++ b/bindings/python/tests/solvable.py @@ -39,6 +39,10 @@ class TestSequenceFunctions(unittest.TestCase): solv = list(self.pool.providers( 'product:openSUSE' )) assert len(solv) == 1, len(solv) + def test_iterate_pool(self): + for s in self.pool: + assert str(s.pool()) == str(self.pool) + def test_creation(self): repo = self.pool.create_repo( 'test' ) assert repo -- 1.6.1.3 -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

1 0