December 2009 - Zypp Development - openSUSE Mailing Lists

[zypp-devel] zypper miscounting when DownloadInAdvance used
by Jano Kupec 16 Dec '09

16 Dec '09

Hi there! When you switch on DownloadInAdvance, the DownloadResolvableReport is still call, even if the package is already in cache. This causes this callback is called twice for each package, and zypper has no good way of counting the so-far-downloaded packages. I see no easy way of avoiding this for 11.2. The information that the package is available in cache is buried deep in the call stack in Fetcher::Impl: target::TargetImpl::commit(with PackageCache) target::CommitPackageCache::get target::CommitPackageCache::sourceProvidePackage TargetImpl::RepoProvidePackage::operator() DownloadResolvableReport sent from here -. repo::PackageProvider::providePackage <-----------' repo::PackageProvider::doProvidePackage repo::Impl::RepoMediaAccess::provideFile Fetcher::start Fetcher::Impl::start Fetcher::Impl::provideToDest Fetcher::Impl::provideFromCache The way i see it, we'll need to add bool Fetcher::isCached public method and improve repo::PackageProvider to be able to use Fetcher::isCached before it calls any callback (well, in fact, it should report DownloadResolvableReport::gotFromCache). Maybe add bool repo::PackageProvider::provideFromCache and only use the current code flow if this returns false. Or (maybe even better) we should completely avoid calling repo::PackageProvider and get the files from cache in somewhat more direct way (e.g. by remembering the paths of files already provided by previous calls to PackageProvider during the download phase), if possible. Any ideas? (BTW, in the meantime i'll fix zypper by blindly resetting the counter when it reaches the expected number of packages to download.) https://bugzilla.novell.com/show_bug.cgi?id=545295 -- 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)---

2 5

[zypp-devel] [ANNOUNCE] ZYpp source repositories on gitorious.org/opensuse
by Duncan Mac-Vicar Prett 11 Dec '09

11 Dec '09

The ZYpp repositories previously published at git.opensuse.org repositories are now available on http://gitorious.org/opensuse http://gitorious.org/opensuse/sat-solver http://gitorious.org/opensuse/libzypp http://gitorious.org/opensuse/zypper http://gitorious.org/opensuse/zypp-utils (previously zypp/tools) http://gitorious.org/opensuse/libzypp-bindings http://gitorious.org/opensuse/libzypp-testsuite http://gitorious.org/opensuse/zypp-dialogsolver http://gitorious.org/opensuse/cmpi-zypp http://gitorious.org/opensuse/zypp-zmd-backend (previously zypp/backend) There is an initial opensuse-zypp team defined with access to those repositories. To switch you only need to edit your .git/config origin remote If before it was git@git.opensuse.org:projects/zypp/zypper.git Now it would be: git@gitorious.org:opensuse/zypper.git The repositories in git.opensuse.org are still accessible, but you can't push to them anymore. They will stay there until no repositories are left on that machine. Gitorious provides feeds for each repository pushes, and per each branch commits. To make it easier to follow the overall project, I have created this feed which merges various feeds and make the titles more similar to the old mails: http://pipes.yahoo.com/pipes/pipe.info?_id=36dc1dc1c0380cca92df9ddaa5b6e26d In the next days we will look for a solution to mail those feed updates to the commits mailing list. -- Duncan Mac-Vicar P. - Engineering Manager, YaST SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- 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] JFYI: zypp-*-obs-submitt on Hudson changed.
by Michael Andres 09 Dec '09

09 Dec '09

Hi. - I changed the zypp-*-obs-submitt script on Hudson not to submitt to obs://zypp:Head (or older branches), if specfile, changesfile AND TARBALL CONTENT are unchanged. In the past we submitted to often, because 'diff' reported two tarballs as being (binary) different , even if their content was actually the same. Blame me if something broke. - Users of osc-plugin-overview (git branch master) will recognize that for obssr:// no longer only new submitt requests are listed. If there is no new request pending, the last one accepted is shown. Together with the change on Hudson we can now see whether a package needs to be submitted by comparing the obs revisions, even if the package version is unchanged. This of course requires that we $ osc overview 11sp1 ** 11sp1 ** +--------------+--------------+--------------+--------------+ | package | obs://zypp:H | obssr://SUSE | ibs://SUSE:S | | | ead | :SLE-11:SP1 | LE-11-SP1:GA | +==============+==============+==============+==============+ | libsatsolver | 0.14.11 | 0.14.11 | 0.14.10 | | | rev 408 | rev 408 | rev 1 | | | | #26013 (NEW) | | +--------------+--------------+--------------+--------------+ | libzypp | 6.27.1 | 6.27.1 | 6.27.0 | | | rev 599 | rev 599 | rev 3 | | | | #26047 (NEW) | | +--------------+--------------+--------------+--------------+ | zypper | 1.2.15 | 1.2.14 | 1.2.14 | | | rev 416 | rev 414 | rev 3 | | | | #25620 | | +--------------+--------------+--------------+--------------+ | libzypp- | 0.5.3 | 0.5.3 | 0.5.2 | | bindings | rev 90 | rev 90 | rev 3 | | | | #26014 (NEW) | | +--------------+--------------+--------------+--------------+ | libqdialogso | 1.3.0 | 1.3.0 | 1.3.0 | | lver1 | rev 590 | rev 558 | rev 1 | | | | #24027 | | +--------------+--------------+--------------+--------------+ | libzypp- | 4.2.11 | 4.2.11 | 4.2.11 | | testsuite- | rev 4 | rev 4 | rev 2 | | tools | | #25625 | | +--------------+--------------+--------------+--------------+ -- 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] <libzypp-bindings> master : fix lib intall path on x86_64
by Klaus Kaempf 01 Dec '09

01 Dec '09

* Michael Andres <ma(a)suse.de> [Dec 01. 2009 14:29]: > > FIND_PACKAGE(PythonInterp REQUIRED) > -EXECUTE_PROCESS(COMMAND ${PYTHON_EXECUTABLE} -c "from sys import stdout; from distutils import sysconfig; stdout.write(sysconfig.get_python_lib())" OUTPUT_VARIABLE PYTHON_LIB_PATH) > +EXECUTE_PROCESS(COMMAND ${PYTHON_EXECUTABLE} -c "from sys import stdout; from distutils import sysconfig; stdout.write(sysconfig.get_python_lib(1))" OUTPUT_VARIABLE PYTHON_LIB_PATH) Thats not completely accurate. You need two pathes: 1. PYTHON_LIB_PATH - for generic Python files (all .py files) 2. PYTHON_ARCH_PATH - for arch-specific files (all .so files) Swig usually generates two binding files. One .so file with a 'raw' api and one .py file to make the raw api usable. 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

1 0