This website is deprecated, and remains online only for historic access to old issues and docs for historic versions of Virtualmin. It has been unmaintained for several years, and should not be relied on for up-to-date information. Please visit www.virtualmin.com instead.
I'm seeing it on my CentOS 5 test system. Are you sure the virtualmin-universal repo is enabled on your system?</div>
Yes. For informational purposes, I haven't changed a thing on my system, other than updating to 3.53 just a few hours to a day prior to you releasing 3.54. I checked my repos, and both virtualmin and virtualmin-universal are enabled (as configured by vmin-pro installation).
After using the <b>yum clean all </b>command, yum sees the 3.54 update, and is able to install it cleanly.
Not sure what triggers this behavior, but I have not ever had to run that prior to 3.53, and I've had this system running for a while (probably approaching a year..).
I'm thinking that ofttimes we get a notification to our servers that the upgrade is there and run into network caching not updating fast enough. Possibly between you and the repo some network cache is serving up old info. Usually later in the day after the notification goes out we're able to update. It's been my practice anyway to see if someone screams before I update all the severs ;-)
Howdy Will,
I'm seeing it on my CentOS 5 test system. Are you sure the virtualmin-universal repo is enabled on your system?
--
Check out the forum guidelines!
<b>Joe wrote:</b>
<div class='quote'>Howdy Will,
I'm seeing it on my CentOS 5 test system. Are you sure the virtualmin-universal repo is enabled on your system?</div>
Yes. For informational purposes, I haven't changed a thing on my system, other than updating to 3.53 just a few hours to a day prior to you releasing 3.54. I checked my repos, and both virtualmin and virtualmin-universal are enabled (as configured by vmin-pro installation).
After using the <b>yum clean all </b>command, yum sees the 3.54 update, and is able to install it cleanly.
Not sure what triggers this behavior, but I have not ever had to run that prior to 3.53, and I've had this system running for a while (probably approaching a year..).
Ah well, at least it's updated! Thanks
Hi Will,
I'm thinking that ofttimes we get a notification to our servers that the upgrade is there and run into network caching not updating fast enough. Possibly between you and the repo some network cache is serving up old info. Usually later in the day after the notification goes out we're able to update. It's been my practice anyway to see if someone screams before I update all the severs ;-)
Dan