Today July 17th, 2024 released updated for Webmin GPL from 7.10.0 to 7.20.1 failed.
Steps to Reproduce
Using RHEL 7, try to update the package wbm-virtual-server.noarch 3:7.10.0.gpl-1 to wbm-virtual-server.noarch 3:7.20.1.gpl-1
Update failed with this error in the log
Update Packages
Now updating wbm-virtual-server ..
Installing package(s) with command /bin/yum -y install wbm-virtual-server ..
Loaded plugins: changelog, langpacks, product-id, search-disabled-repos,
: subscription-manager, versionlock
<LINE MASKED FOR PRIVACY>
Resolving Dependencies
--> Running transaction check
---> Package wbm-virtual-server.noarch 3:7.10.0.gpl-1 will be updated
---> Package wbm-virtual-server.noarch 3:7.20.1.gpl-1 will be an update
--> Finished Dependency Resolution
Dependencies Resolved
================================================================================
Package Arch Version Repository Size
================================================================================
Updating:
wbm-virtual-server noarch 3:7.20.1.gpl-1 virtualmin-universal 23 M
Transaction Summary
================================================================================
Upgrade 1 Package
Total download size: 23 M
Downloading packages:
No Presto metadata available for virtualmin-universal
Package wbm-virtual-server-7.20.1.gpl-1.noarch.rpm is not signed
Package wbm-virtual-server-7.20.1.gpl-1.noarch.rpm is not signed
.. install failed!
No packages were installed. Check the messages above for the cause of the error.
Needed end result is that this update complete without error message
Cause
We do not know what cause this challenge. The following are speculations about the cause of this challenge.
Speculation 1. Missing dependency?
As you probably know, RHEL 7 Maipo received security updates and Extended Life-cycle Support (ELS) until June 30, 2028. Sources:
We don’t support any OSes beyond their general EOL. The only way to run RHEL 7 safely at this point is to pay for ELS.
But, we also won’t break it any time soon (though it might break before the four years of ELS, we aren’t testing on RHEL7 anymore). If you switch to our newer repos, you can keep getting updates to Virtualmin packages, but you won’t ever receive an update of the httpd package, as I’m no longer maintaining custom ones. You’ll need to switch to the RHEL httpd package, and you’ll need to switch to an execution mode other than fcgid+suexec. (PHP-FPM is the recommended mode for everyone in almost every circumstance, and switching to it should generally be pretty painless).
The quickest way to initiate the installation of Virtualmin GPL on your server is to log in via SSH using a terminal, and execute the following pre-prepared command:
sudo sh -c "$(curl -fsSL https://software.virtualmin.com/gpl/scripts/virtualmin-install.sh)" -- --bundle LAMP
to [re]Run virtualmin setup-repos if we already have virtualmin/webmin successfully installed?
No! That’s installing Virtualmin. You never install Virtualmin again. You do not want to reinstall anything. You just want to switch to new repos.
Either (if you’re reasonably up to date):
virtualmin setup-repos
As I said above, or you can run the install script with the --setup or -s flag. You can download it and run it, or you can probably do it all in one with:
sudo sh -c "$(curl -fsSL https://software.virtualmin.com/gpl/scripts/virtualmin-install.sh)" -- --setup
Joe - you have been patiently helping me for years and years now. and each year, you may notice a decline in my intelligence, so I thank you for your assistance, as always.
as always, thank you so very much. worked PERFECTLY.
Good morning @Joe This is to confirm that virtualmin setup-repos was successful. Thanks again.
The dnf clean all command would fail though. Because this server is a RHEL 7. As you probably know, dnf is included starting with RHEL 8.
For those facing this challenge on RHEL 7, this command was successful yum clean all. In summary, to resolve this challenge on RHEL 7, we ran virtualmin setup-repos and then yum clean all
We’ll try this. Then share our result here.