August 2008 - Zypp Development - openSUSE Mailing Lists

[zypp-devel] Re: [zypp-commit] r10844 - /trunk/sat-solver/tools/repo_products.c
by Michael Schroeder 21 Aug '08

21 Aug '08

On Wed, Aug 13, 2008 at 04:06:31PM -0000, kkaempf(a)svn.opensuse.org wrote: > Author: kkaempf > Date: Wed Aug 13 18:06:31 2008 > New Revision: 10844 > > URL: http://svn.opensuse.org/viewcvs/zypp?rev=10844&view=rev > Log: > provide solvable:installtime for product solvables > [...] > if (!s) > { > + struct stat st; > + > s = pool_id2solvable(pool, repo_add_solvable(repo)); > repodata_extend(data, s - pool->solvables); > handle = repodata_get_handle(data, s - pool->solvables - repo->start); > + if (!fstat(fileno(fp), &st)) > + { > + repodata_set_num(data, handle, SOLVABLE_INSTALLTIME, st.st_ctime); That's the last inode change time. Don't you mean "st.st_mtime"? 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 3

[zypp-devel] Problems with dependencies on files
by Lorenzo Villani 21 Aug '08

21 Aug '08

Today, while trying to install openjdk on fedora using zypper, it gave me the following error: # sudo zypper in java-1.6.0-openjdk java-1.6.0-openjdk-devel maven2 Reading installed packages... Problem: nothing provides /usr/lib/security/classpath.security needed by java-1.5.0-gcj-1.5.0.0-21.fc9.i386 Solution 1: do not ask to install a solvable providing maven2 Choose the above solution using '1' or cancel using 'c' [1/C]: C And I had to install those packages using yum :( PS: That file on fedora is provided by libgcj-4.3.0-8 Regards -- Lorenzo Villani Blog: http://blog.binaryhelix.net -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

4 3

[zypp-devel] repodata.c - clarification
by Roberto Mannai 21 Aug '08

21 Aug '08

Hi I'm writting a patch about the bug: https://bugzilla.novell.com/show_bug.cgi?id=399239 - "YaST's software installation modules should show disk space modification". The patch would be an append in the tooltip on the "Free space" column in the disk usage widget, like "Used XX GB - Installing x MB" or " - Removing x MB". When the user makes a selection for install / removal, I keep a counter of disk usage delta. However I saw that for some packages, the variable zypp::DiskUsageCounter::MountPoint.pkg_size returns 0. Going deeper I saw that "repodata_search" method in "repodata.c" returns in this instruction: for (kp = keyp; (k = *kp++) != 0; ) if (data->keys[k].name == keyname) break; if (k == 0) return; So, for packages like "kernel-rt", "miro" and "kernel-source", I have k == 0, going on no disk usage is computed (no call to pool.c - solver_fill_DU_cb). I'm using the revision 10814 on svn. A quick test case is selecting the "kernel-source" for installation: the disk usage bar does not change (nor the percentage). Is this behaviour wanted (for some condition on Repodata objects) or is it a bug? Is this related to https://bugzilla.novell.com/show_bug.cgi?id=375104 ? Best regards Roberto Mannai -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

2 4

[zypp-devel] Re: [yast-devel] repodata.c - clarification
by Stanislav Visnovsky 20 Aug '08

20 Aug '08

Hi! I believe zypp-devel is the proper mailing list for this. Stano Dňa Saturday 16 August 2008 16:06:33 Roberto Mannai ste napísal: > Hi > I'm writting a patch about the bug: > https://bugzilla.novell.com/show_bug.cgi?id=399239 - "YaST's software > installation modules should show disk space modification". The patch > would be an append in the tooltip on the "Free space" column in the > disk usage widget, like "Used XX GB - Installing x MB" or " - Removing > x MB". When the user makes a selection for install / removal, I keep a > counter of disk usage delta. > > However I saw that for some packages, the variable > zypp::DiskUsageCounter::MountPoint.pkg_size returns 0. Going deeper I > saw that "repodata_search" method in "repodata.c" returns in this > instruction: > > for (kp = keyp; (k = *kp++) != 0; ) > if (data->keys[k].name == keyname) break; > if (k == 0) return; > > So, for packages like "kernel-rt", "miro" and "kernel-source", I have > k == 0, going on no disk usage is computed (no call to pool.c - > solver_fill_DU_cb). I'm using the revision 10814 on svn. > > A quick test case is selecting the "kernel-source" for installation: > the disk usage bar does not change (nor the percentage). > > Is this behaviour wanted (for some condition on Repodata objects) or > is it a bug? Is this related to > https://bugzilla.novell.com/show_bug.cgi?id=375104 ? > > Best regards > Roberto Mannai -- 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] .solv files
by Peter Poeml 18 Aug '08

18 Aug '08

Hi, I noticed a new file type on mirrors, a repo.solv file. http://ftp.nux.ipb.pt/pub/dists/opensuse/repositories/Apache:/Modules/Apach… It turned up in the build service, but I assume it could also turn up in distro or update trees. I need to know how to handle these files and would appreciate some details about them. I suppose they should be treated like .xml files resp. .xml.gz files in the build service tree, because they are probably regenerated each time the repo metadata is recreated? It is explained here http://www.mirrorbrain.org/files/talks/download-infra.pdf (page 55) why this is important to know. Just a note: in general, it is very helpful to notify ftpadmin when new kind of content is created, since the content needs to be distributed appropriately. Things that you do at metadata level can have significant effects on our infrastructure and how it serves our users :-) Thanks, Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development

3 3

[zypp-devel] ui::Selectable in pkg-bindings
by Ladislav Slezak 15 Aug '08

15 Aug '08

Hi all, I'd like to switch pkg-bindings internal implementation to ui::Selectable, this change will solve some problems related to selection of the right solvable and will unify behavior of pkg-bindings with packager widgets and zypper. There is one major problem with Selectables: they exclusively work on ResStatus::USER level which is OK for yast UI but not usable for pkg-bindigs which use ResStatus::APPL_HIGH, ResStatus::USER is used only in some cases. The reason is that changes made by user have higher priority than changes done by yast scripts, so user is able to override yast changes if it's needed. It seems that the ui::Selectable API must be enhanced, any idea? -- 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

3 5

[zypp-devel] New: ZYpp::getTarget and Target::assertRootPrefix
by Michael Andres 15 Aug '08

15 Aug '08

JFYI: New methods class ZYpp: /** Same as \ref target but returns NULL if target is not * initialized, instead of throwing. */ Target_Ptr zypp::getTarget() const; class Target: /** Return the path prefixed by the target root, unless * it already is prefixed. */ Pathname Target::assertRootPrefix( const Pathname & path_r ) const { return Pathname::assertprefix( root(), path_r ); } So if you have a Pathname mypath; and want to prefix it with the targets root, in case the target is already initialized: Target_Ptr target( getZYpp()->getTarget() ); if ( target ) mypath = target->assertRootPrefix( mypath ); -- 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] New ui::Selectable methods...
by Michael Andres 12 Aug '08

12 Aug '08

JFYI: enum Fate { TO_DELETE = -1, UNMODIFIED = 0, TO_INSTALL = 1 }; /** */ bool setFate( Fate fate_r ); /** Set the item to be installed (new- or re-install). */ bool setToInstall() { return setFate( TO_INSTALL ); } /** Take care the item gets installed if it is not. */ bool setInstalled(); /** Take care the item gets installed if it is not, or is older. */ bool setUpToDate(); /** Set the item to be deleted (must be installed). */ bool setToDelete() { return setFate( TO_DELETE ); } /** Take care the item gets deleted if it is installed. */ bool setDeleted(); /** Set the item to stay unmodified. */ bool unset() { return setFate( UNMODIFIED ); } Some new status methods. They may be sometimes easier to use, as they do not always distinguish whether installed objects are present, like the ui::Staus does. E.g: unset() // thate care the item says as it is. The same with ui::Sataus: setStatus( hasInstalledObj() ? S_KeepInstalled : S_NoInst ) setDeleted() vs. ( ! hasInstalledObj() || setStatus( S_Del ) ) setInstalled() vs. ( hasInstalledObj() || setStatus( S_Install ) ) -- 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] new workflow / libzypp-bindings
by Jan-Simon Möller 11 Aug '08

11 Aug '08

Hi! I successfully compiled the libzypp-bindings now. As stated in a previous mail, the examples are outdated. I'm no trying to fix it, but got stuck: E.g.: list-available-resolvables.py bails out at Z.addResolvables(...) I started coding a bit about my use-case: Read repo from local server, display installable items. Its much like the list-available-resolvables.py - just a remote-repo. It should look like: import zypp Z = zypp.ZYppFactory_instance().getZYpp() repoManager = zypp.RepoManager() #possibly set PATH to some /tmp/foo (won't touch installed system!) # myurl1 = zypp.Url("http://192.168.10.247/home:/user/standard/") # right ? repo1 = repoManager.addRepository(?????) # hmm syntax inside () ??? repo2 = repo3 = repos = repoManager.knownRepositories() for repo in repos: if not repo.enabled() continue if not repo.isCached(repo): repoManager.buildCache(repo) # # substitute for Z.addResolvables() !! print "Available" # ... and so on Any help appreciated! Best regards Jan-Simon -- 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] libzypp-bindings - examples out-of date ?
by Jan-Simon Möller 08 Aug '08

08 Aug '08

Hi! The examples for the libzypp-bindings seem broken, or not up-to-date with the current implementation. Could please someone look at it ? For external devs its more or less the first entry-point! Best regards Jan-Simon -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

3 8