[Spacewalk-list] Yum/Cache, problems yumming latest nightly build, primary.sqlite.bz2 missing reference to latest build

[Bushby, Bruce (London)(c)]

Thanks Josh!!  That confirms my suspicions, after all my wgets, browser
refreshes etc, my repomd.xml file has different checksums to yours, and
your primary.sqlite
Db lists the latest versions.

[root at space12 spacewalk]# grep -A5 -B1 primary.sqlite repomd.xml
  <data type="primary_db">
    <location href="repodata/primary.sqlite.bz2"/>
    <checksum
type="sha">e7b665ddeaaf6ceba3f3b0d3eb1b1777937eeae0</checksum>
    <timestamp>1264156270</timestamp>
    <open-checksum
type="sha">69b4c86b84d17e1bb727f7910670610e21e9799d</open-checksum>
    <database_version>10</database_version>
  </data>
[root at space12 spacewalk]#

 Thanks for confirming!! I'll get onto the network people and request
open/no-cache access.....I can already hear their wailing :)

Regards
Bruce



-----Original Message-----
From: spacewalk-list-bounces at redhat.com
[mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Joshua Roys
Sent: 27 January 2010 17:39
To: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] Yum/Cache, problems yumming latest nightly
build, primary.sqlite.bz2 missing reference to latest build

On 01/27/2010 11:53 AM, Bushby, Bruce (London)(c) wrote:
> Could this be an issue with the "repomd.xml" file? I used wget to pull

> down the file and I also downloaded it via my browser.....the files 
> are identical....repomd.xml is also identical if I let yum download
it.

What does this give you:
$ grep -A5 -B1 primary.sqlite repomd.xml

I get:
   <data type="primary_db">
     <location href="repodata/primary.sqlite.bz2"/>
     <checksum
type="sha">c1765cd9415ead3efa00725bf5e167346787b172</checksum>
     <timestamp>1264588143</timestamp>
     <open-checksum
type="sha">0aaac0a0d3d5480bd3b0624328d56453b06c28ed</open-checksum>
     <database_version>10</database_version>
   </data>

Those sha1sums should match the sha1sum of primary.sqlite{,.bz2}

> sqlite> select * from packages where name like 'spacewalk-backend'
> ...> ;
> 19|08a936beffe28571c0ac1936e5c39ec04bf0e558|spacewalk-backend|noarch|0
> 19|08a936beffe28571c0ac1936e5c39ec04bf0e558|spacewalk-backend|noarch|.
> 19|08a936beffe28571c0ac1936e5c39ec04bf0e558|spacewalk-backend|noarch|8
> 19|08a936beffe28571c0ac1936e5c39ec04bf0e558|spacewalk-backend|noarch|.
> 19|08a936beffe28571c0ac1936e5c39ec04bf0e558|spacewalk-backend|noarch|3
> 19|08a936beffe28571c0ac1936e5c39ec04bf0e558|spacewalk-backend|noarch|5
> 19|08a936beffe28571c0ac1936e5c39ec04bf0e558|spacewalk-backend|noarch||
> 19|08a936beffe28571c0ac1936e5c39ec04bf0e558|spacewalk-backend|noarch|0
> 19|08a936beffe28571c0ac1936e5c39ec04bf0e558|spacewalk-backend|noarch||
> 19|08a936beffe28571c0ac1936e5c39ec04bf0e558|spacewalk-backend|noarch|1
> 19|08a936beffe28571c0ac1936e5c39ec04bf0e558|spacewalk-backend|noarch|.
> 19|08a936beffe28571c0ac1936e5c39ec04bf0e558|spacewalk-backend|noarch|f
> 19|08a936beffe28571c0ac1936e5c39ec04bf0e558|spacewalk-backend|noarch|c
> 19|08a936beffe28571c0ac1936e5c39ec04bf0e558|spacewalk-backend|noarch|1
> 19|08a936beffe28571c0ac1936e5c39ec04bf0e558|spacewalk-backend|noarch|2
> 19|08a936beffe28571c0ac1936e5c39ec04bf0e558|spacewalk-backend|noarch||
> 19|08a936beffe28571c0ac1936e5c39ec04bf0e558|spacewalk-backend|noarch|C
> 19|08a936beffe28571c0ac1936e5c39ec04bf0e558|spacewalk-backend|noarch|o
> 19|08a936beffe28571c0ac1936e5c39ec04bf0e558|spacewalk-backend|noarch|m
> 19|08a936beffe28571c0ac1936e5c39ec04bf0e558|spacewalk-backend|noarch|m
> 19|08a936beffe28571c0ac1936e5c39ec04bf0e558|spacewalk-backend|noarch|o
> 19|08a936beffe28571c0ac1936e5c39ec04bf0e558|spacewalk-backend|noarch|n
...

Also, I get:

sqlite> select location_href from packages where name =
'spacewalk-backend' ;
spacewalk-backend-0.8.37-1.fc12.noarch.rpm

If you still can't get the right repomd.xml/primary.sqlite.bz2, there's
definitely a cache in the way.

Josh


**********************************************************************
 Please consider the environment before printing this email or its attachments.
The contents of this email are for the named addressees only.  It contains information which may be confidential and privileged.  If you are not the intended recipient, please notify the sender immediately, destroy this email and any attachments and do not otherwise disclose or use them. Email transmission is not a secure method of communication and Man Investments cannot accept responsibility for the completeness or accuracy of this email or any attachments. Whilst Man Investments makes every effort to keep its network free from viruses, it does not accept responsibility for any computer virus which might be transferred by way of this email or any attachments. This email does not constitute a request, offer, recommendation or solicitation of any kind to buy, subscribe, sell or redeem any investment instruments or to perform other such transactions of any kind. Man Investments reserves the right to monitor, record and retain all electronic communications through its network to ensure the integrity of its systems, for record keeping and regulatory purposes. 
Visit us at: www.maninvestments.com 
TG0908
**********************************************************************