| SYSTEM INFORMATION | |
|---|---|
| Operating system: | Ubuntu Linux 18.04.5 |
| Webmin version: | 1.973 |
| Virtualmin version: | 6.16 |
| Related products version: | RECOMMENDED |
Follow-up of
Is there any progress?
It is too painfull replacing MariaDB back to MySQL after the unwanted change by a mistaken Virtuamin upgrade.
I followed this advice from ILia which look the simplest:
- Putting this package on hold, like
apt-mark hold virtualmin-lamp-stack(however this will prevent running upgrades from UI as Webmin Software Packages Updates module uses-yparam with package name individually to upgrade a package, however, when package that is on hold is getting changed, upgrade will not work automatically (thankfully) unless additional param--allow-change-held-packagesis passed). In other words future package upgrades could only be done using console by runningapt-get upgradecommand;
I then updating all 138 packages from the webmin UI excluding the virtualmin-lamp-stack package.
This did not break the server, and all updates disappeared including the virtualmin-lamp-stack package.
I dared to reboot the server, and everything is still working.
Now, I understand that the virtualmin-lamp-stack package will not be updated anymore, preventing unwanted revert to MySQL.
-
Will future updates show up in Webmin, or will I need to run apt-get update/upgrade periodically?
-
What will not be upgraded by the
apt-get upgradecommand? Will Apache, PHP and Mariadb still upgraded? What about Webmin and Virtualmin? -
Will Webmin/virtualmin be eventually fixed to keep MariaDB if it is used instead of MySQL?
Thanks for help.