Bugzilla – Bug 155701
installation source doesn't provide patches
Last modified: 2006-03-09 09:23:55 UTC
There is testing YUM repository which should provide the patches for testing update tools: https://armstrong.suse.de/download/Code/10/update/i386 However, after adding this service to my zmd, I can't retrieve list of patches from it (the XML-RPC call zmd.packsys.get_patches returns empty list). I still didn't get an answer if the problem is at the repository definition or in ZMD. Last report from Harald: > If ZMD is able to get yum-sources it could work. You also should see one > patch in the meanwhile. There are some smaller quirks in the patch, i > try to solve right now using the input by Klaus.
Created attachment 71518 [details] log from zmd ("/usr/local/sbin/zmd -n") (The three calls were for service list, catalog list and patches list.)
Looking at the logs, it fetches the XML from Friday. Looking at armstrong: -rw-r--r-- 1 root root 747176 Mar 3 16:04 other.xml -rw-r--r-- 1 root root 1363 Mar 6 10:06 patch-aaa_base-1235.xml -rw-r--r-- 1 root root 281 Mar 3 16:05 patches.xml -rw-r--r-- 1 root root 16749 Mar 3 16:04 primary.xml -rw-r--r-- 1 root root 1222 Mar 3 16:05 repomd.xml It is from Friday - this files are fixed by Klaus AFAICS. If they are correct I can't really say, but to my best knowledge Klaus has checked them with libzypp backend. Adding Tambet as we need also knowledge about ZMD. Tambet, could help us on this.
Did you use latest zmd and libzypp packages from last night ? If yes, please provide /var/log/zmd-messages.log and /var/log/zmd-backend.log
Created attachment 71545 [details] /usr/local/var/log/zmd-messages.log zypp-zmd-backend is from STABLE zmd from STABLE still reports "error : Attempt to serialize data containing null reference" - which was already fixed (bug #154715). I'm using zmd from subversion (in /usr/local).
Created attachment 71546 [details] /var/log/zmd-backend.log gzipped
Looks like the patch file is wrong 2006-03-07 13:41:08 <0> gorgon(27030) [yum] YUMSourceImpl.cc(createResolvables):435 Reading file /usr/local/var/cache/zmd/web/files/armstrong.suse.de/download/Code/10/update/i386/repodata/patch-aaa_base-1235.xml 2006-03-07 13:41:08 <5> gorgon(27030) [base] Exception.cc(log):83 YUMPatchParser.cc(process):60 THROW: YUMPatchParser.cc(process):60: XML parser error: null pointer check failed 2006-03-07 13:41:08 <3> gorgon(27030) [yum] YUMSourceImpl.cc(createResolvables):461 Cannot read patch metadata
Klaus or Jiri, could please check again? Or provide a mechanism to test myself? Added Rudi to CC, as he is coding the engine creating these files. If found in patch-aaa_base-1235.xml the following to lines and removed the latter, as I expect it an error: <plainrpm arch="i586" filename="aaa_base-10.0.42-57.i586.rpm" downloadsize="311342" md5sum="" buildtime="1141055104"/> <plainrpm arch="i586" filename="" downloadsize="" md5sum="" buildtime="1141055104"/> I should be "patchrpm" I think, but in the generated file by autobuild, the patchrpm tag is also empty. It looks like it has been edited manuaelly, so it shouldn't be a problem of the engine, the engine just creates an empty patchrpm-tag. Reassigning to Klaus for another validation run Is the "md5sum" attribute mandatory or optional, could it be empty at all? I added the "external" md5sum of aaa_base-10.0.42-57.i586.rpm.
With current libzypp, armstrong.suse.de/download/Code/10/update/i386 looks just fine: Found 7 resolvables 5 packages 0 selections 0 patterns 1 patches 0 scripts 0 messages 1 atoms 0 products
But I'm still not able to read them. I've installed libzypp and libzypp-zmd-devel from stable and new zmd (zypp branch) from sources. Still no patches seen. ad comment #7: I use a ruby script using XML-RPC to test it; I don't know if there's other way, rug probably still doesn't support patches.
Tabmet, are you able to see the list of patches from this source, using zmd.packsys.get_patches call?
Created attachment 71699 [details] zmd-backend.log
Yes. >>> server.zmd.packsys.get_patches ("") [{'status': 0, 'category': 'recommended', 'name': 'aaa_base', 'type': 3, 'installed': False, 'version': '1235-0', 'summary': '', 'arch': 'noarch', 'id': 844}]
Looks like I am doomed :-( This must mean I am using zmd a wrong way. Tambet, is it correct to use zmd from zmd-zypp branch?
Created attachment 71781 [details] test script Could you please try to run this script? I hope you need only 'ruby' package installed. It is necessary to set correct values of secret (line 105) and prefix, where deviceid file should be found (line 101). The scripts only lists services, catalogs and patches. The call for adding the service is commented.
I tested with latest zmd from https://svn.provo.novell.com/svn/nrm/avenger/branches/zypp/zmd and libzypp-zmd-backend-0.0.8-36 and libzypp-0.0.8-36 packages. I can't run the test: tambet@164-99-120-83:~> ruby ./test.ruby ./test.ruby:3:in `require': no such file to load -- digest_auth (LoadError) from ./test.ruby:3 tambet@164-99-120-83:~>
Created attachment 71792 [details] lib needed to run the script sorry, forgot the library (just put it in the same dir)
tambet@164-99-120-83:~/foo> ruby ./test.ruby ./digest_auth.rb:25:in `gen_auth_header': private method `gsub' called for nil:NilClass (NoMethodError) from ./test.ruby:21:in `set_auth' from /usr/lib/ruby/1.8/xmlrpc/client.rb:320:in `initialize' from /usr/lib/ruby/1.8/xmlrpc/client.rb:357:in `new2' from ./test.ruby:115:in `initialize' from ./test.ruby:195 I don't feel that's the most productive usage of my time.
That's very nice from you. I could say similar things about my attemps to get zmd and zypp working without the possibility to use properly built rpm package :-(
I'm sorry, but building packages is not my job. I'm sorry, but debugging your scripts that never even get to the point where service addition gets called is not my job.
This bug (as a bug of repo is fixed after comment #8); setting back to FIXED. Now I'm finaly able to see the list of patches using XML-RPC (reinstalling machine, zmd from svn, libzypp from stable helped - I think the reason might have been in some old zmd cache). So this problem seems also solved.