I've tried to set up a local repo on a server (alecto) using
reposync. This part seems to go OK and the the target directory (/repo) gets populated.
I did this so I could update multiple VMs running CentOS without hammering my Internet connection.
The problem is that when using 'yum update' on the VMs, it fails on most (not all) packages, apparently looking for older versions of that package than is installed in the /repo directory. For example, it looks to install
zlib-1.2.7-17 when the version in
zlib-1.2.7-18. I have no idea where it gets the idea that the -17 version should be used.
There is only one repo defined in the VM's
/etc/yum.repos.d directory - alecto.repo and that contains:
[alecto] name=Local network repo on Alecto baseurl=ftp://192.168.1.110/ enabled=1 gpgcheck=0
It's not the FTP setup - some installations work (eg
yum install pigz) and it's possible that they work because their version number doesn't change very often.
createrepo on all the reposync'ed directories and I have cleared out all
yum caches on the VM.
My question is: What the heck is going on? Failing that: where does
yum get the version numbers of what it thinks it needs to install?
I have been beating my head against a wall for two days now and could really use some help.