March 2008 - Zypp Development - openSUSE Mailing Lists

[zypp-devel] [REVIEW] granular inter process lock
by Duncan Mac-Vicar Prett 28 Mar '08

28 Mar '08

Hi guys, I had this in my queue since Easter. to make it short, our current global lock sucks, and it will suck more when we get packagekit, zypper and yast running at the same time :-) My prototype has passed the two initial test cases. The idea is a scoped object, that is, to make it work you create it, and once it is out of scope, it releases the lock. Locks are by name. And you can create writer or readers mutex for a named region. The name you give to the mutex will determine which region it will protect, and if you are entering it as reader or writer, and the behavior: wait until free, wait with timeout, or abort if locked. The different behaviors are that for example some operations, like enabling or disabling repos are really short, but probably we don't want to wait for the rpm commit lock to end and abort immediately. So you use like this: process A, the pool creates a reader lock for the pool: InterProcessMutex mutex( "pool", Reader); The repomanager wants to rewrite the solv files, which would screw up if some process have the global pool (usually zypper for some seconds, or YaST while the user has it opened), so the repomanager could do: InterProcessMutex mutex( "pool", Writer, 10); Repomanager will not be able to write while the first mutex is on scope, and will sleep for a total of 10 seconds on 1 seconds intervals, and then will throw if the lock is still there. However if another process just want to query data from the solv files, like a second process accessing the global pool, it will take a second reader lock on "pool" which will coexist nicely with the first one. Reference counting, cleaning etc is done by fcntl locks, so the kernel takes care of most stuff. (it is a direct mapping of the named resources over locks on a file per-resource, plus cleaning an waiting logic) It is not correct, if we for example test a lock for not being locked, and then try to acquire a lock, and just in the middle another process take it first, what we do is we abort mission and re enter the loop to try to acquire again, so it works reasonable, but it does not guarantee order on serving the resource, which is reasonable for the use case I guess. There are some improvements suggested by Michael Andres already, specially in the code path, and I also need more test cases covering more combinations. But I post it here for review / comments. http://svn.opensuse.org/svn/zypp/trunk/libzypp/zypp/base/InterProcessMutex.h (and .cc ) Testcases: http://svn.opensuse.org/svn/zypp/trunk/libzypp/tests/zypp/base/InterProcess… http://svn.opensuse.org/svn/zypp/trunk/libzypp/tests/zypp/base/InterProcess… Cheers Duncan -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

6 5

[zypp-devel] proposal for server side solv files
by Duncan Mac-Vicar Prett 26 Mar '08

26 Mar '08

Hi guys, here is the proposal: we put the .solv file in repodata/something.solv repomd.xml gets extra data: <data type="solv"> <location href="repodata/something.solv.gz"/> <checksum type="sha">eed8ddc83f767f5a959b29e3ec006f53a2ab871d</checksum> <timestamp>1205162318</timestamp> <open-checksum type="sha">e837550df577f334d03d71b4bb1218d6b533e1ae</open-checksum> </data> Advantages: - no need to re-sign the solv file. - we can add version and metadata in the same file. Version information could be stored as: <data type="solv" format-version="7" schema-version="3"> Cons: - need to modify createrepo, but we already do for patches, if we use createrepo. If not, this is not a cons. libzypp workflow: * when probing, probe first for type "solv" (becomes a new type of repos) * look for repomd.xml, * look if there are solv files * download and unpack * if there are not, fallback to yum (this needs to be evaluated wether it is easy). For CDs, we can put there a repodata/repomd.xml with the solv file information only. Opinions? Duncan -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

3 2

[zypp-devel] checking free space
by Josef Reidinger 26 Mar '08

26 Mar '08

Hi, in bnc #331602 user says that zypper write to him that he hasn't enough free space. I look and zypper doesn't check this. But also when I looking I cannot find in libzypp if this is somewhere checked (only use of df function is in making cache). So whole check for enough free space is in rpm program or I overlook something? thanks, Pepa -- 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] Configurability of 'keep downloaded packages'
by Stanislav Visnovsky 22 Mar '08

22 Mar '08

Hi! I'm working on the functionality to keep the downloaded packages on disk, not removing them. This needs to be configurable, of course. I'd like to get your views on how much configurability we need. I see at least the following options: 1) global enable/disable 2) per-repository enable/disable 3) per-access protocol enable/disable (CD, HTTP, FTP, NFS, ...) Any opinions? Stano -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

9 24

[zypp-devel] a more recent zypper for openSUSE 10.2
by Dominique Leuenberger 21 Mar '08

21 Mar '08

Hello, I really love the way ypper works in current factory. I have a VPS (Virtual Private Server), based on 10.2 (yes.. some of them have such a new one.. most still run 9.3 or max 10.1) I would like to upgrade to a more recent zypper there (I don't care much about the yast modules; most of my things I configure in the config files.. so if I break YaST, bad luck ;) the problem I have, though is: In my OBS project home:dimstar, I linked in zypper, libzypp, libsatsolver (and cmake and hicolor-icon-theme) from openSUSE:Factory, to have them built against 10.2 (the factory RPM does not work because of glibc dependencies not bein satisfied) The issue there seems to be that libsatsolver does not compile. Errors: [ 93%] Building C object bindings/ruby/CMakeFiles/satsolverx.dir/libsatsolver_wrap.o /usr/bin/gcc -Dsatsolverx_EXPORTS -Werror -Wall -Wall -Werror -Wall -g -O3 -fPIC -I/usr/src/packages/BUILD/satsolver-0.0.22 -I/usr/src/packages/BUILD/satsolver-0.0.22/src -I/usr/lib/ruby/1.8/i586-linux -I/usr/src/packages/BUILD/satsolver-0.0.22/applayer -I/usr/src/packages/BUILD/satsolver-0.0.22/tools -D_FILE_OFFSET_BITS=64 -DVERSION=\"0.0.22\" -o bindings/ruby/CMakeFiles/satsolverx.dir/libsatsolver_wrap.o -c /usr/src/packages/BUILD/satsolver-0.0.22/bindings/ruby/libsatsolver_wrap.c /usr/src/packages/BUILD/satsolver-0.0.22/bindings/ruby/libsatsolver_wrap.c: In function 'Repo_size': /usr/src/packages/BUILD/satsolver-0.0.22/bindings/ruby/libsatsolver_wrap.c:1793: error: '$self' undeclared (first use in this function) /usr/src/packages/BUILD/satsolver-0.0.22/bindings/ruby/libsatsolver_wrap.c:1793: error: (Each undeclared identifier is reported only once /usr/src/packages/BUILD/satsolver-0.0.22/bindings/ruby/libsatsolver_wrap.c:1793: error: for each function it appears in.) and it continues on like this. You can see the full log at https://build.opensuse.org/package/live_build_log?arch=i586&package=libsats… Any other ideas how else I could get a newer zypper as my preferred PM on 10.2 to run? Dominique -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

5 9

[zypp-devel] Please run the testsuite before checkin!
by Michael Matz 20 Mar '08

20 Mar '08

Hi, On Thu, 20 Mar 2008, zypp-devel(a)opensuse.org wrote: > The build failed. > > See http://yast.suse.de:3333/builds/zypp-trunk/9232 for details. > (only SUSE-internal) > > > CHANGES > ------- > Revision 9231 committed by jreidinger on 2008-03-20 13:57:20 > return more information from checking if metadata need refresh, so user can get better info. (bnc #307249) > M /trunk/libzypp/VERSION.cmake > M /trunk/libzypp/zypp/RepoManager.cc > M /trunk/libzypp/zypp/RepoManager.h This patch broke the testsuite. As a general rule, everyone should run the tests before checkin to SVN (it's as simple as 'cd tests; make; ctest -A' for libzypp). This mail is supposed to be a remainder for this. In the future I'll take the liberty to revert patches that break the testsuite. (Josef: don't feel singled out by this mail, you were just triggering it. This rule applies to everyone, not just you :-) ) > Start processing tests > Test project /root/work/CBUILDS/libzypp/tests > 1/ 30 Testing Arch_test Passed > 2/ 30 Testing Capabilities_test Passed > 3/ 30 Testing CheckSum_test Passed > 4/ 30 Testing Digest_test Passed > 5/ 30 Testing Edition_test Passed > 6/ 30 Testing Fetcher_test Passed > 7/ 30 Testing FileChecker_test Passed > 8/ 30 Testing KeyRing_test Passed > 9/ 30 Testing MediaSetAccess_test Passed > 10/ 30 Testing PathInfo_test Passed > 11/ 30 Testing PoolQuery_test Passed > 12/ 30 Testing ProgressData_test Passed > 13/ 30 Testing PublicKey_test Passed > 14/ 30 Testing RWPtr_test Passed > 15/ 30 Testing RepoInfo_test Passed > 16/ 30 Testing RepoManager_test ***Failed > 17/ 30 Testing RepoStatus_test Passed > 18/ 30 Testing ResKind_test Passed > 19/ 30 Testing TranslatedText_test Passed > 20/ 30 Testing Url_test Passed > 21/ 30 Testing Vendor_test Passed > 22/ 30 Testing Vendor2_test Passed > 23/ 30 Testing Sysconfig_test Passed > 24/ 30 Testing RepomdFileReader_test Passed > 25/ 30 Testing PatchesFileReader_test Passed > 26/ 30 Testing inidict_test Passed > 27/ 30 Testing iniparser_test Passed > 28/ 30 Testing RepoVariables_test Passed > 29/ 30 Testing YUMDownloader_test Passed > 30/ 30 Testing Downloader_test Passed > > 97% tests passed, 1 tests failed out of 30 > > The following tests FAILED: > 16 - RepoManager_test (Failed) > Errors while running CTest Ciao, Michael. -- 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] Out of office
by kkaempf＠suse.de 19 Mar '08

19 Mar '08

Until Tuesday, March 25th, I am on a business trip and might not be able to process mail in a timely manner. In urgent cases, please call me on my cell phone. Klaus -- 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] We're going to loose resolvables of kind 'Language'.
by Michael Andres 18 Mar '08

18 Mar '08

We're going to loose resolvables of kind 'Language'. The sat solver allows to handle language supporting packages the way as e.g. hardware supporting packages, via namespaces. So there is no more need to create those dummy language-resolvables. That's nice because the satpool does not allow to have solvables without a repository. So we don't have to create a dummy repository just to maintain those dummy resolvables. The zypp interface will basically stay the same: void setRequestedLocales( const LocaleSet & locales_r ); LocaleSet getRequestedLocales() const; LocaleSet getAvailableLocales() const; May be we add some convenience methods. -- 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

3 4

[zypp-devel] ignore with solver
by Josef Reidinger 18 Mar '08

18 Mar '08

Hi, due to FATE #303527 I plan add new item to enum Action to mediaRequestCallback. Behavior of this action is remember package which fail to download and throw it from libzypp. Program like zypper catch this exception, say solver that this package don't use and try make new installation plan without problematic package. Maybe IgnoreRequestException can be used, due to it's not used anywhere in zypp (and is userRequest exception). any ideas or comments? Also is KEEP_STATE (in ResStatus) good to say solver that it cannot use this package? Thanks, Pepa -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

4 5

[zypp-devel] eject specific device - change in API needed
by Jan Kupec 12 Mar '08

12 Mar '08

I just commited the following change in the media API: void release(MediaAccessId accessId, const std::string & ejectDev = ""); void release(MediaAccessId accessId, bool eject = false) ZYPP_DEPRECATED; Not a very good idea though. The question is, can i drop the old release() method or should i rename the new one so that there is no ambiguity? With so many changes in the API we already did i'd just drop it. Cheers, jano -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

1 0