August 2011 - Zypp Development - openSUSE Mailing Lists

[zypp-devel] libzypp-bindings: callbacks support Python
by Zhang, Qiang Z 13 Sep '11

13 Sep '11

Hi Klaus and all, Does callbacks works for python in libzypp-bindings? I have just used the test code(swig/python/tests/commit_callbacks.py), but it seems don't work and CommitReceiver have never been called. Do you know what's the root cause? Thanks In advance. Qiang

2 13

[zypp-devel] libzypp-bindings: More API support
by Zhang, Qiang Z 02 Sep '11

02 Sep '11

Hi all, We would like to use more python API in libzypp-bindings, such as PoolQuery, and I have tried to import the related API to libzypp, but fails. Here's the patch I used to import PoolQuery API: --- diff -uNr libzypp-bindings-0.5.8/swig/PoolQuery.i libzypp-bindings-0.5.8.new/swig/PoolQuery.i --- libzypp-bindings-0.5.8/swig/PoolQuery.i 1970-01-01 08:00:00.000000000 +0800 +++ libzypp-bindings-0.5.8.new/swig/PoolQuery.i 2011-08-30 13:19:41.067491333 +0800 @@ -0,0 +1 @@ +%include <zypp/PoolQuery.h> diff -uNr libzypp-bindings-0.5.8/swig/zypp.i libzypp-bindings-0.5.8.new/swig/zypp.i --- libzypp-bindings-0.5.8/swig/zypp.i 2011-08-30 13:18:41.251366083 +0800 +++ libzypp-bindings-0.5.8.new/swig/zypp.i 2011-08-30 13:48:54.900428645 +0800 @@ -59,6 +59,7 @@ #include "zypp/Resolver.h" #include "zypp/pool/GetResolvablesToInsDel.h" +#include "zypp/PoolQuery.h" #include "zypp/Product.h" using namespace boost; @@ -159,6 +160,7 @@ %include "TmpPath.i" %include "Resolver.i" %include "ZConfig.i" +%include "PoolQuery.i" %ignore zypp::ZYpp::setTextLocale; %ignore zypp::ZYpp::getTextLocale; --- But, I have got the following build error. ########### /home/abuild/rpmbuild/BUILD/libzypp-bindings-0.5.8/swig/python/libzypp_python.cc: In function 'PyObject* _wrap___lshift__(PyObject*, PyObject*)': /home/abuild/rpmbuild/BUILD/libzypp-bindings-0.5.8/swig/python/libzypp_python.cc:122672: error: redefinition of 'PyObject* _wrap___lshift__(PyObject*, PyObject*)' /home/abuild/rpmbuild/BUILD/libzypp-bindings-0.5.8/swig/python/libzypp_python.cc:107956: error: 'PyObject* _wrap___lshift__(PyObject*, PyObject*)' previously defined here /home/abuild/rpmbuild/BUILD/libzypp-bindings-0.5.8/swig/python/libzypp_python.cc: In function 'PyObject* _wrap_dumpOn(PyObject*, PyObject*)': /home/abuild/rpmbuild/BUILD/libzypp-bindings-0.5.8/swig/python/libzypp_python.cc:122718: error: redefinition of 'PyObject* _wrap_dumpOn(PyObject*, PyObject*)' /home/abuild/rpmbuild/BUILD/libzypp-bindings-0.5.8/swig/python/libzypp_python.cc:122336: error: 'PyObject* _wrap_dumpOn(PyObject*, PyObject*)' previously defined here /home/abuild/rpmbuild/BUILD/libzypp-bindings-0.5.8/swig/python/libzypp_python.cc: In function 'PyObject* _wrap_ZYppFactoryException_locker_pid(PyObject*, PyObject*)': /home/abuild/rpmbuild/BUILD/libzypp-bindings-0.5.8/swig/python/libzypp_python.cc:123604: warning: 'pid_t zypp::ZYppFactoryException::locker_pid() const' is deprecated (declared at /usr/include/zypp/ZYppFactory.h:33) ########### Do you have any comments? Thanks In advance. Qiang

4 4

[zypp-devel] next-gen API for package management?
by Duncan Mac-Vicar P. 01 Sep '11

01 Sep '11

ZYpp API is a toolkit. It provides not only the package management API but all the classes and components like a LEGO set. In this regard, its goals as an API are very similar to LLVM. This makes the API complex to wrap in scripting languages, both technically and from the user point of view: the wrapped API does not make much sense for simple tasks. However, we have seen the need for a simple client API that encapsulates all the knowledge there. Ideally this would be a simple API, comparable to what zypper offers, or what PackageKit offers. This API could actually be used by zypper and the PackageKit backend, which would serve as a good testbed for its usefulness. The API could be done in plain C, exposing only opaque structs keeping the ZYpp data and some API to do operations, but avoiding exposing other types that would conflict with scripting languages own stdlibs (Pathname, Date, etc), so restricting itself to basic types only. Having a simple C API would allow for easy binding: you can use swig, ffi, interpreter own API, etc. If we follow conventions like class_methodname(class *, args).. etc bindings get easier... Now, how this API would look like? Lets collect use cases. Where possible I would prefer actual client code examples in C, python, etc together with the use case (only usecases could lead to a committee-taste API). -- Duncan Mac-Vicar P. - http://www.suse.com/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5, 90409 Nürnberg, Germany -- 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] How to implement "zypper pattern-info tablet" using libzypp-bindings
by Zhang, Qiang Z 31 Aug '11

31 Aug '11

Hi all, Sorry to disturb you again. We want to use libzypp-bindings to get package list for special pattern, just as the function of 'zypper pattern-info'. But fails with some unexpected error. Error 1: Code: pool = myZypp.pool() # pool of packages group = "tablet" pattern = pool.byIdentBegin (zypp.ResKind.pattern, group)# this would trigger the following error: File "/usr/lib/python2.6/site-packages/zypp.py", line 3084, in byIdentBegin def byIdentBegin(self, *args): return _zypp.ResPool_byIdentBegin(self, *args) NotImplementedError: Wrong number of arguments for overloaded function 'ResPool_byIdentBegin'. Possible C/C++ prototypes are: byIdentBegin(zypp::ResPool const *,zypp::ResPool::ByIdent const &) byIdentBegin(zypp::ResPool const *,zypp::ResKind,zypp::IdString) byIdentBegin(zypp::ResPool const *,zypp::ResKind,C_Str const &) byIdentBegin(zypp::ResPool const *,zypp::PoolItem const &) byIdentBegin(zypp::ResPool const *,zypp::sat::Solvable) byIdentBegin(zypp::ResPool const *,zypp::IdString) In fact, my arguments are correct. Error 2: Code for item in pool: # iterate over the pool msg = "" if zypp.isKindPattern(item) and str(item.name()) == "tablet": msg += str(item.name()) pattern= zypp.asKindPattern(item) contents = pattern.contents(); # This code will trigger the following error: swig/python detected a memory leak of type 'zypp::sat::SolvableSet *', no destructor found. Attached are two c++ code to implement this function, and one python code. Thanks in advance Qiang

1 0

[zypp-devel] multiarch/noarch not working with repomd repos
by T.C. Hollingsworth 23 Aug '11

23 Aug '11

I'm trying to get zypper & friends working on Fedora but I have run into a little snag. For some reason, zypper can't find noarch & i686 (I'm on x86_64) packages. It seems to be parsing the metadata correctly because repomd2solv shows them and zypper can install them if I force the arch in zypp.conf. I assumed the problem is somewhere in the repomd parsing logic, as I'd imagine people would be yelling quite loudly if noarch didn't work on openSUSE. ;-) But, that just seems to parse it and pass it off to the satsolver code, and I've looked everywhere from Arch.cc to PoolImpl.cc and everything looks like it should be handling this just fine. I also wanted to check if there was a regression somewhere, but I can't use anything much older than current git because the stable openSUSE branches don't support RPM 4.9. Thanks a lot, T.C. -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

2 2