June 2012 - Zypp Development - openSUSE Mailing Lists

[zypp-devel] deptestomatic.multi and srcpackage
by Cristian Morales Vega 21 Jun '12

21 Jun '12

Trying to understand the output of "osc whatdependson" I want to use deptestomatic.multi with the <graphic/> tag to see the dependency tree. To generate the .xml file I run "zypper --disable-system-resolvables in --debug-solver hamster-applet", that gives me a "trial" with this line: <install channel="oss" kind="package" name="hamster-applet" arch="noarch" version="2.91.2" release="4.1.2" status="U_Tu_"/> The problem is that when I try to change it for <install channel="src_oss" kind="srcpackage" name="hamster-applet" arch="noarch" version="2.91.2" release="4.1.2" status="U_Tu_"/> I get a "Can't find kind: srcpackage:'hamster-applet' in source 'src_oss': no such name/kind". I tried different versions, <install channel="src_oss" kind="srcpackage" name="hamster-applet" arch="noarch" version="2.91.2" release="4.1.2"/> <install channel="src_oss" kind="srcpackage" name="hamster-applet"/> But doesn't help. Any idea of what I should do to make it work? Thanks. -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: zypp-devel+owner(a)opensuse.org

1 0

[zypp-devel] RFC: Adding a cache of service metadata (bnc#765308)
by Martin Vidner 20 Jun '12

20 Jun '12

Hi, (proposed) short version: in the future (not including SLE11-SP2) repo services will be cached, so if you expect a service to change (SP migration?), call "zypper refs". Discussion, please comment (Wagon, SUSE Manager, hello): As you know, zypp takes packages from *repositories*, and the package/repo metadata is cached: without autorefresh, the cache is refreshed only explicitly by zypper refresh (ref). With autorefresh (and unless overriden by --no-refresh) , we contact the server to update one or more metadata files BUT only if some time has elapsed since we last contacted the server (5 minutes by default). Zypp also knows *services*, which essentially are server-defined mutable lists of repositories. They too have an autorefresh attribute and respect --no-refresh. However, they do not have the timed cache like above. For interactive usage it is only a minor annoyance since you usually have only one service (nu.novell.com) so there is only one round trip. But as soon as you use Chef which checks many packages individualy with a "zypper info" call, the latencies add up. Therefore I've proposed to add a service cache. Michael has pointed out that some use cases rely on the service not being cached, namely the migration to a next service pack, which we implement by installing a product and relying on nu.novell.com to give us a new set of repos. With the service cache, those use cases would need an explicit service cache invalidation AKA zypper service-refresh (refs). I think that should be done in the long term, and in the short term (SLE11 SP2) the service cache would be disabled by default. Regarding how to control the service cache: a) zypp.conf has an option repo.refresh.delay, so we could add service.refresh.delay b) a CLI option '--allow-service-cache <sec>' I prefer (a) for symmetry and it seems that (b) per-run config is not needed, otherwise users would request --allow-repo-cache already. -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu

5 6

[zypp-devel] led display Suppliers shared photos with you
by led display Suppliers 10 Jun '12

10 Jun '12

Dear Mr/Miss, Still be puzzling about looking for best led display supplier? Now it will be miles easier working with KEROSA! Here you can find competitive price and excellent quality with a best mix. We"ve been in led display career for many years. We know your market and your country well. Our business is flexible which something is more likely to be a friend chat. We never waste your time. Our conversation will be very efficient base on our good communication. Please reply as soon as possible .if you are working on some led display project. We are ready to make you a satisfied offer! Samuel Shezhen Krosa Techology Co.,Ltd. Address: Building 3,Park,Guanguang road,Bao"an District,Shenzhen,China. post 518000

1 0

[zypp-devel] Refreshing of Repositories and GPG Keys
by Saurabh Sood 06 Jun '12

06 Jun '12

Hi, I need to refresh the repository metadata, in case a repository has been added. I am currently using this line rman.refreshMetadata(repoinfo,zypp::RepoManager::RefreshIfNeeded); where rman is an object of zypp::RepoManager. Is this right, or something else needs to be done? Also, I could not get how to get the GPG keys for the particular repository if it exists. I have currently avoided the check for GPG keys. Regards,. Saurabh -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: zypp-devel+owner(a)opensuse.org

3 3

[zypp-devel] Initialisation of Target
by Saurabh Sood 04 Jun '12

04 Jun '12

Hi, I am stuck at trying to initialise the target, so as to proceed with the installation of packages. I am getting a null zypp::ui::Selectable::Ptr, when I use zypp::ui::Selectable::get(). Because of this, I am not able to carry out installation of packages. Also, I did not understand what parameter is to be passed ti initialiseTarget. My Code : https://github.com/openSUSE/one-click-installer/blob/master/playground/pars… Regards,. Saurabh -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: zypp-devel+owner(a)opensuse.org

2 1