Hi all, Following a report on users@ about not-up-to-date ovirt-release36.rpm in $subject, I had a look, then did: # pwd /var/www/html/pub/yum-repo # mkdir bck-2016-07-05 # mv ovirt-release36.rpm bck-2016-07-05 && ln -s ../ovirt-3.6/rpm/el7/noarch/ovirt-release36.rpm # mv ovirt-release36-snapshot.rpm bck-2016-07-05 && ln -s ../ovirt-3.6/rpm/el7/noarch/ovirt-release36-snapshot.rpm # mv ovirt-release-master.rpm bck-2016-07-05 && ln -s ../ovirt-master-snapshot/rpm/el7/noarch/ovirt-release-master.rpm # mv ovirt-release40-snapshot.rpm bck-2016-07-05 && ln -s ../ovirt-4.0-snapshot/rpm/el7/noarch/ovirt-release40-snapshot.rpm # mv ovirt-release40.rpm bck-2016-07-05 && ln -s ../ovirt-4.0/rpm/el7/noarch/ovirt-release40.rpm # ls -l ovirt-release* -rw-r--r--. 1 root root 6408 Jul 28 2014 ovirt-release33.rpm -rw-r--r--. 1 root root 7968 Sep 9 2014 ovirt-release34.rpm -rw-r--r--. 2 root root 13904 Nov 10 2015 ovirt-release35.rpm lrwxrwxrwx. 1 root root 47 Jul 5 19:39 ovirt-release36.rpm -> ../ovirt-3.6/rpm/el7/noarch/ovirt-release36.rpm lrwxrwxrwx. 1 root root 56 Jul 5 19:41 ovirt-release36-snapshot.rpm -> ../ovirt-3.6/rpm/el7/noarch/ovirt-release36-snapshot.rpm lrwxrwxrwx. 1 root root 47 Jul 5 19:48 ovirt-release40.rpm -> ../ovirt-4.0/rpm/el7/noarch/ovirt-release40.rpm lrwxrwxrwx. 1 root root 65 Jul 5 19:46 ovirt-release40-snapshot.rpm -> ../ovirt-4.0-snapshot/rpm/el7/noarch/ovirt-release40-snapshot.rpm lrwxrwxrwx. 1 root root 64 Jul 5 19:44 ovirt-release-master.rpm -> ../ovirt-master-snapshot/rpm/el7/noarch/ovirt-release-master.rpm Also, I noticed we have there repodata, i.e. this is a yum repo itself. If it's indeed used as one anywhere, the above will break it - because the symlinks will automatically change during releases or nightly builds, and the repo metadata will not be updated. Is it indeed used? If so, we should probably do something about this - either revert my change and have something else that copies the files (and runs createrepo), or something else that runs createrepo frequently/as needed. Best, -- Didi