Re: new metadata format for repositories

[Jim Cornette <cornette insight rr com>]

seth vidal wrote:
> > I was trying to update a lot of packages through both up2date and 
> > through yum. I still am having problems with the noarch rpms. The rpms 
> > start to download, then stall up2date or kill yum. Below is a list of 
> > the files that I am having problems with downloading.
>
>
> I'm very confused - what does this have to do with the metadata work?

I am under the impression that the metadata work is to resolve conflicts 
and to download the proper programs, libs and whatever is needed to 
generate a common repository for yum, apt, up2date or whatever method is 
used to retrieve the rpm, deb or whatever other packaging format is 
needed to accomplish the above mission.

Two methods of progam retrieval have failed that are using the yum 
format. These seem to be noarch rpms. My hope was that the repodata 
files might shine some light upon what this is caused by with the yum repos.

My system is a fully developmental rawhide version that I installed by 
ftp on January 4th sucessfully. If this problem is caused by metadata 
errors, I was wondering if any work generated by the common metadata 
project could be enhanced by information regarding the inadequacies 
within the yum metadata formatted files.

> > automake14-1.4p6-8.noarch.rpm
> > automake-1.8.2-1.noarch.rpm
> > docbook-style-xsl-1.64.1-5.noarch.rpm
> > ghostscript-7.07-17.i386.rpm
> > ghostscript-fonts-8.11-1.noarch.rpm
> > gnome-icon-theme-1.1.5-1.noarch.rpm
> > gnome-vfs2-2.5.5-2.i386.rpm
> > gnome-vfs2-devel-2.5.5-2.i386.rpm
> > hwdata-0.103-1.noarch.rpm
> > repodata
> > system-config-language-1.1.5-1.noarch.rpm
> > system-config-samba-1.2.2-1.noarch.rpm
> > system-config-users-1.2.8-1.noarch.rpm
>
>
> setup multiple mirrors in your /etc/yum.conf
>
> [someserver]
> name=myserver
> baseurl = url://server/bar/path
>           url://otherserver/bar/path
>           url://stillotherserver/bar/path
>
> etc etc

Why would the shortcoming seem to only effect the noarch files? My 
system is up2date now after the local repos were added. I'll add some 
fallover urls to the file and see if the problem with noarch rpms is 
still present or goes away.

> > The ghostscripts downloaded alright. The noarch stalled. I then tried 
> > out the generation script for the standardized repodata on these files. 
> > The generation went successful. It generated the below files within the 
> > repodata directory.
>
>
> cool
>
>
> > 29437 Jan 20 21:08 filelists.xml.gz
> > 21249 Jan 20 21:08 other.xml.gz
> >  5689 Jan 20 21:08 primary.xml.gz
> >   666 Jan 20 21:08 repomd.xml
>
>
> those sizes seem about right on average.
>
> -sv

I hope this common format is put into action soon. I like the idea and 
can foresee the versatility the standardization will add to program 
packaging installations.

Now for deb, rpm or whatever program packager to co-exist within the 
Linux systems and not conflict.

Jim