Re: CentOS / Blue Quartz update broke YUM?

On Tue, 22 Jan 2008 08:12:29 -0500, seth vidal wrote
> On Tue, 2008-01-22 at 07:55 -0500, Mailing Lists wrote:
> > On Mon, 21 Jan 2008 21:26:14 -0500, seth vidal wrote
> > > On Mon, 2008-01-21 at 20:16 -0500, Mailing Lists wrote:
> > > > Hi,
> > > > 
> > > > I have a CentOS-BlueQuartz box... after the recent major upgrade, YUM broke. I 
> > surfed 
> > > > the archives for BlueQuartz, CentOS & yum but did not see record of my issue.
> > > >
> > > 
> > > I don't know what a 'blue quartz' is but this error:
> > > 
> > Blue Quartz is the Cobalt Replacement GUI
> > 
> > > > result, resultmsgs = do() 
> > > > File "/usr/share/yum-cli/cli.py", line 477, in doCommands 
> > > > return self.updatePkgs() 
> > > > File "/usr/share/yum-cli/cli.py", line 955, in updatePkgs 
> > > > self.doRepoSetup() 
> > > > File "/usr/share/yum-cli/cli.py", line 75, in doRepoSetup 
> > > > self.doSackSetup(thisrepo=thisrepo) 
> > > > File "__init__.py", line 260, in doSackSetup 
> > > > File "repos.py", line 277, in populateSack 
> > > > File "/usr/lib/python2.3/site-packages/sqlitecachec.py", line 40, in getPrimary 
> > > > self.repoid)) 
> > > > TypeError: Parsing primary.xml error: Start tag expected, '<' not found
> > > 
> > > means you have either:
> > > 1. a damaged mirror
> > > 2. or a damaged primary.xml.gz file
> > > 3. some sort of proxy b/t you and them munging this stuff
> > > 
> > > Check up with the repository/distro maintainer, see if they know what's
> > > up.
> > > 
> > I've checked the other lists and no one is complaining about yum failing - so the 
> > repository/distro maintainer is fine...  And I've got no proxy to the internet.
> > 
> > I have the following Repositories set up:
> > CentOS-Base.repo
> > mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=os
> > 
> > BlueQuartz-Base.repo
> > baseurl=http://bluequartz.org/pub/BlueQuartz/5100R/CentOS4/bluequartz/$basearch/
> > 
> > NuOnce.repo
> > baseurl=http://www.nuonce.net/repos/
> > 
> > 
> > I killed /var/cache/yum, backed up & removed all the repos in /etc/yum.repos.d.  I 
put 
> > each one back individually and every one threw the error in primary.xml.
> >
> 
> has your network provider changed recently? Maybe added a proxy?
> 
Nope...  nothing of that sort has changed.  I checked that with your first suggestion.  
Each repo downloads the primary.xml.gz file and a quick scan through it seems like 
everything is OK.