On 11 April 2011 09:23, James Hogarth <[email protected]> wrote: > Had a mail from someone asking for help about this so though I'd float > it to the list archives in case others encounter it. > > CentOS 5.6 was released Friday and some of the 5.5 /updates/ are now > of course in the 5.6 /os/ (base) area. Openssl was specifically > mentioned but others are likely to be there as well. > > The md5sum for these differs since they were built different days on > different hosts. > > Spacewalk-repo-sync makes use of NVREA of course to determine what to > sync from upstream and consequently won't see the new package after > the symlink change in upstream yum to point /5/ at /5.6/ instead of > /5.5/ ... > > The consequence is new kickstarts might see discrepancies in checksums > reported by the distro media versus the channels and have trouble > installing. > > It's worth it at this point for those using CentOS5 to clear out their > base channel and /updates/ channel and repopulate from the media and > the /updates/ repo from an appropriate mirror. > > The same is likely to occur when SL make the release of 5.6 and do a > similar switch. > > Hope this helps anyone else encountering this....
yes - and its something similar to this that caused my 'spacewalk 1.3 - rhnpush - error' thread. packages with the same name but different checksums in the base and updates 5.6 repo. _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
