installing Virtualmin 8 and all related packages ✘
[ERROR] Something went wrong. Exiting.
[ERROR] The last few log entries were:
spamassassin-4.0.1-5.el10_0.x86_64
usermin-2.500-1.noarch
webmin-2.202-1.noarch
[2025-11-18 18:42:08 PST] [INFO] Installing dependencies and system packages: [2025-11-18 18:42:08 PST] [INFO] Success.
[2025-11-18 18:44:32 PST] [INFO] Spin pid is: 14257
Error:
Problem: problem with installed package clamav-lib-1.4.3-2.el10_1.x86_64
- package clamav-lib-1.4.3-2.el10_1.x86_64 from @System requires libcrypto.so.3(OPENSSL_3.4.0)(64bit), but none of the providers can be installed
- package clamav-lib-1.4.3-2.el10_1.x86_64 from epel requires libcrypto.so.3(OPENSSL_3.4.0)(64bit), but none of the providers can be installed
- cannot install both openssl-libs-1:3.2.2-16.el10_0.4.x86_64 from baseos and openssl-libs-1:3.2.2-16.el10.x86_64 from @System
- cannot install both openssl-libs-1:3.2.2-16.el10_0.4.x86_64 from baseos and openssl-libs-1:3.2.2-16.el10.x86_64 from baseos
- package openssl-1:3.2.2-16.el10_0.4.x86_64 from baseos requires openssl-libs(x86-64) = 1:3.2.2-16.el10_0.4, but none of the providers can be installed
- cannot install the best candidate for the job
[2025-11-18 18:44:32 PST] [INFO] Installing Virtualmin 8 and all related packages: [2025-11-18 18:44:32 PST] [INFO] Failed with error: 1
Yep, this is a known issue in EPEL on all EL 10 systems using it, and it has nothing to do with the Virtualmin installer.
It’s been around for almost two weeks. I hoped they’d fix it that day, but it seems they don’t test the packages they build for millions of systems. I’ll probably report it later this weekend if they don’t fix it still.
for the last couple of months i have been very successful installing the latest release candidate (and unstable). but only very recently i have been getting those strange EPEL errors mentioned earlier.
could you please direct me to where the epel error was reported? was that link i posted where the error was first reported? that is where i read about RL-10.1 but i was not sure if this is the same error or not.
both of these at least give me a different error: (not sure if this is progress or not?)
Cleaning up software repo metadata
Checking and installing system package updates
Installing dependencies and system packages ✘
[ERROR] Something went wrong. Exiting.
[ERROR] The last few log entries were:
Rocky Linux 10.0 - CRB 423 kB/s | 535 kB 00:01
Rocky Linux 10.0 - Extras 8.5 kB/s | 5.5 kB 00:00
Webmin Prerelease 62 kB/s | 36 kB 00:00
Dependencies resolved.
Nothing to do.
Complete!
[2025-11-24 18:30:57 PST] [INFO] Checking and installing system package updates: [2025-11-24 18:30:57 PST] [INFO] Success.
[2025-11-24 18:32:10 PST] [INFO] Spin pid is: 6660
Error:
Problem: cannot install both cyrus-sasl-lib-2.1.28-27.el10.x86_64 from baseos and cyrus-sasl-lib-2.1.28-29.el10.x86_64 from @System
package cyrus-sasl-gssapi-2.1.28-29.el10.x86_64 from @System requires cyrus-sasl-lib(x86-64) = 2.1.28-29.el10, but none of the providers can be installed
package cyrus-sasl-2.1.28-27.el10.x86_64 from baseos requires cyrus-sasl-lib(x86-64) = 2.1.28-27.el10, but none of the providers can be installed
cannot install the best candidate for the job
conflicting requests
[2025-11-24 18:32:10 PST] [INFO] Installing dependencies and system packages: [2025-11-24 18:32:10 PST] [INFO] Failed with error: 1
however, as per the links you sent, i just tried the following on RL-10.0 and this RL-10.0 installation worked as well:
echo ‘10.0’ > /etc/dnf/vars/releasever ; ## should this be removed afterward?
dnf -y install cyrus-sasl cyrus-sasl-devel ; ## webmin had trouble with this
dnf clean packages ; ## first time on 10.0 this was required for some reason
that is what was suggested in the link you shared. i had seen that fix in a couple of places
do you think it would be better just to go to RL-10.1 since it does not require any sort of fix? i understand that webmin has not been fully tested yet on 10.1. or is that a bad idea?
It doesn’t make much sense to me because I expected Rocky 10.0 to automatically update to 10.1?
And, again, there isn’t an issue for us to fix because we support EL 10 systems in the beta installer; EPEL package dependency issues are not something we can fix.