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 think the reason for the confusion is that there is a 5.04 release of virtualmin-base -- which is not Virtualmin, but is the prerequisites. And I think this was all to fix some issues with prerequisites in CentOS, particularly for clamd.
Aha, that would indeed explain it! Thanks cruiskeen, that's exactly it. Joe pushed out an update to virtualmin-base to handle some dependencies that should be included, as well as to address an issue with ProFTPd that was sometimes occurring during the installation.
That package doesn't affect Virtualmin itself though, just some things relating to it's dependencies.
Thank you. But still, is there a reason not to announce it, and even for not making it available with new version of Virtualmin? Its part of the system. I really fear what happened with the theme hack, where untested theme was released.
That's a valid request. I don't usually announce virtuamin-base releases, unless the release changes something that would effect users.
First up: virtualmin-base is not Virtualmin; Virtualmin is a package called "wbm-virtual-server", and I always announce those releases and include a changelog.
virtualmin-base is a package that depends on other packages, and bundles the postinstall setup script. Once Virtualmin is installed upgrades don't run the postinstall script, and would only ever change dependencies. This release had a typo bug fix (on some CentOS versions, though it was already fixed on some) and removed dependencies on clamav-scanner and clamav-scanner-systemd (which are things that are unique to CentOS 7, and so shouldn't have been in this package for CentOS 5 and 6. This change is invisible to users who already have Virtualmin installed. It prevented running the installation on older CentOS versions, but didn't effect CentOS 7.
Anyway, I understand your caution and concern and I'll start posting a news item about virtualmin-base updates, as well. They almost never happen, so it's not a big deal to post about them. (Before I rolled 5.0, we would sometimes go years between virtualmin-base updates.)
Howdy,
Hmm, where is it that you're seeing Virtualmin 5.0.4? To my knowledge that hasn't been put into any of the Virtualmin software repositories.
-Eric
But it is there: It is offered for CentOS based systems but not for Debian based ones. So what has been changed? Regards, Kai
I think the reason for the confusion is that there is a 5.04 release of virtualmin-base -- which is not Virtualmin, but is the prerequisites. And I think this was all to fix some issues with prerequisites in CentOS, particularly for clamd.
There is not a 5.04 Virtualmin yet.
Aha, that would indeed explain it! Thanks cruiskeen, that's exactly it. Joe pushed out an update to virtualmin-base to handle some dependencies that should be included, as well as to address an issue with ProFTPd that was sometimes occurring during the installation.
That package doesn't affect Virtualmin itself though, just some things relating to it's dependencies.
-Eric
Thank you. But still, is there a reason not to announce it, and even for not making it available with new version of Virtualmin? Its part of the system. I really fear what happened with the theme hack, where untested theme was released.
That's a valid request. I don't usually announce virtuamin-base releases, unless the release changes something that would effect users.
First up: virtualmin-base is not Virtualmin; Virtualmin is a package called "wbm-virtual-server", and I always announce those releases and include a changelog.
virtualmin-base is a package that depends on other packages, and bundles the postinstall setup script. Once Virtualmin is installed upgrades don't run the postinstall script, and would only ever change dependencies. This release had a typo bug fix (on some CentOS versions, though it was already fixed on some) and removed dependencies on clamav-scanner and clamav-scanner-systemd (which are things that are unique to CentOS 7, and so shouldn't have been in this package for CentOS 5 and 6. This change is invisible to users who already have Virtualmin installed. It prevented running the installation on older CentOS versions, but didn't effect CentOS 7.
Anyway, I understand your caution and concern and I'll start posting a news item about virtualmin-base updates, as well. They almost never happen, so it's not a big deal to post about them. (Before I rolled 5.0, we would sometimes go years between virtualmin-base updates.)
--
Check out the forum guidelines!
thanks