Hi, What's the difference and can we just use: Code: branchname=141.00beta01 cd /usr/local/src rm -rf centminmod* git clone -b ${branchname} --depth=1 https://github.com/centminmod/centminmod.git centminmod cd centminmod ./centmin.sh to replace the 140.00beta01? Thanks !
I followed this and didn't have any issues. I was running 140.00beta01 and upgraded to 141.00beta01 with no issues.
Thanks for your reply... Probably it get's first some updates? But does the OS is important and we may not use it on specific OS versions like Centos 7, Almalinux 8,9 Rocky Linux etc?
Centmin Mod 141.00beta01 is solely for EL10 development and testing but is backwards compatible with EL7, EL8, EL9 OSes https://community.centminmod.com/th...0-rocky-linux-10-compatibility-worklog.29603/ Yes you can those manual commands to switch to any Centmin Mod branch usually.
Since following the code replacement instructions for 140.00beta01, running cmupdate shows the following: Code (Text): root@server:~#cmupdate From https://github.com/centminmod/centminmod * branch 140.00beta01 -> FETCH_HEAD From https://github.com/centminmod/centminmod * branch 140.00beta01 -> FETCH_HEAD Is that expected?
restored friendlier messages Code (Text): cmupdate ------------------------------------- Updating Centmin Mod code ------------------------------------- * 141.00beta01 Checking for updates on origin/141.00beta01 ... From https://github.com/centminmod/centminmod * branch 141.00beta01 -> FETCH_HEAD Already up to date with origin/141.00beta01 at fcee543. Latest commit: fcee543 (2026-05-20) wrap cmupdate latest-commit line to fit 80-col terminals in 141.00beta01 ------------------------------------- Updated Centmin Mod code -------------------------------------
Great, and one other point regarding the new compact fancy DMOTD - is this message necessary: Code (Text): [!!] ! Older branch (140.00beta01) — newer: 132.00stable or 141.00beta01 (threads/25572) Also, the new cmupdate output states Updating... and Updated... even when everything is already up to date.
Yeah update fixed a bug which now shows this message as actually intended, so yes message is meant to show now the bug is fixed. But will re-word it