Bugzilla – Bug 634695
sles10sp3 is unable to handle repofiles generated by obs 2.0
Last modified: 2010-10-12 11:53:45 UTC
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.8) Gecko/20100723 SUSE/3.6.8-1.3 Firefox/3.6.8 Just discovered a problem for the second time, that on sles10sp3 when using zypper or yast to install packages, some packages cannot be resolved by zypper/yast. I had a look in the corresponding primary.xml.gz and noticed, that packages which cannot be found are listed in the xml file this way: [...] </format> </package><package type="rpm"> <name>open-xchange-authentication-ldap</name> [...] when I change that to [...] </format> </package> <package type="rpm"> <name>open-xchange-authentication-ldap</name> [...] manually in the primary.xml.gz in the local cache in /var/lib/zypp/cache/, the package can be found. This is either a bug in obs or a bug in yast/zypper on sles10sp3 or both. Reproducible: Always Steps to Reproduce: 1. 2. 3.
our createrepo-0.9.8 is generating primary.xml files with the package elements on seperate lines, so I suppose we don't have this problem in build.o.o otherwise someone would have reported this.
Obs is running on SLES11 from Novell: choeger@buildservice:~> rpm -qi createrepo Name : createrepo Relocations: (not relocatable) Version : 0.9.8 Vendor: openSUSE Build Service Release : 6.1 Build Date: Mon 19 Apr 2010 09:15:57 PM CEST Install Date: Tue 29 Jun 2010 04:53:05 PM CEST Build Host: build14 Group : System/Packages Source RPM: createrepo-0.9.8-6.1.src.rpm Size : 221375 License: GPLv2+ Signature : DSA/SHA1, Mon 19 Apr 2010 09:16:07 PM CEST, Key ID 85753aa5eefefde9 URL : http://linux.duke.edu/metadata/ Summary : Creates a Common Metadata Repository Description : This utility generates a common metadata repository from a directory of RPM packages. Should I reassign this bug to any other product/component?
problem was not reproducable for Carsten. I may get caused by using --update, he will check the next time.
But still this is a bug on SLES10SP3. Could you please assign it to the correct product and component? I am unable to access sles10 even though we're a partner Novell. That does only seem to work a few days every odd years...
And it can be reproduced easily. Just manually do, what createrepo does: change primary.xml.gz according to my instructions above, just inversely.
However, this is not a createrepo bug, it would by a zypp one. Duncan, do you mind to have a look ?
I would need the original file that causes the problem, attached.
Created attachment 392331 [details] original primary.xml.gz as created by own obs instance
Created attachment 392332 [details] manually fixed primary.xml.gz in local zypp cache
(In reply to comment #3) > problem was not reproducable for Carsten. > > I may get caused by using --update, he will check the next time. It IS caused by the --update code. I removed that now from my local bs_publish and triggered a rebuild. After I did that, the primary index is no longer sles10 incompatible: before: buildservice:/srv/obs/repos/open-xchange-6.18.1-rev4/SLES10 # zcat repodata/primary.xml.gz |grep "package><" </package><package type="rpm"> </package><package type="rpm"> </package><package type="rpm"> </package><package type="rpm"> </package><package type="rpm"> </package><package type="rpm"> </package><package type="rpm"> </package><package type="rpm"> </package><package type="rpm"> </package><package type="rpm"> </package><package type="rpm"> </package><package type="rpm"> </package><package type="rpm"> </package><package type="rpm"> </package><package type="rpm"> </package><package type="rpm"> </package><package type="rpm"> </package><package type="rpm"> </package><package type="rpm"> </package><package type="rpm"> </package><package type="rpm"> </package><package type="rpm"> after: buildservice:/srv/obs/repos/open-xchange-6.18.1-rev4/SLES10 # zcat repodata/primary.xml.gz |grep "package><" Don´t you have that in your obs? That is really annoying... :-(