Koozali.org: home of the SME Server
Obsolete Releases => SME 7.x Contribs => Topic started by: Peasant on January 12, 2011, 11:10:26 PM
-
A few years ago I installed SME Server at a clients, and it has run pretty faultlessly since then. At the time, backup with dar was a contrib, rather than being built in to the base release, so I had to install it as a contrib. Part of this installation process was to exclude sme-backup from updates so that it didn't overwrite the contrib. As I understand things, the contrib will not have been updated along with the rest of the server, so I would now like to revert to the base sme-backup. I still have a copy of the wiki page at the time, and it describes unistalling the contrib, and reinstalling the base rpm. Before diving in and doing this I wanted to check that it is still the right way to go about it:
rpm -e --nodeps e-smith-backup
mkdir -p /newfolder
wget http://mirror.contribs.org/smeserver/releases/7/smeos/i386/SME/RPMS/e-smith-backup-<recent version>
yum localinstall e-smith-backup*.rpm
signal-event post-upgrade
reboot
Check for any orphaned cron jobs and remove them:
rm /etc/cron.d/backupwk
Then remove the Exclude entry for e-smith-backup created when the contrib was installed:
db yum_repositories delprop smeupdates Exclude
expand-template /etc/yum.conf
I'm a bit wary of the last line of the first section of code, thinking it should be signal-event reboot rather than plain reboot
Can someone please confirm this will do the job, or is there a better way to do it?
Thanks in anticipation
-
Part of this installation process was to exclude sme-backup from updates so that it didn't overwrite the contrib.
If the contrib was designed correctly then no settings will ever overwrite each other. I haven't tried the contrib in question so couldn't answer the rest of your question.
-
Thanks for that. As I understand things the contrib was replacing the existing sme-backup with the modified RPM, which included all the functionality of the base one at the time. I think that is why it was necessary to disable updates. The contrib had to be updated manually.
-
Just checked out the server, and it appears to be running the latest version of dar, darlib and e-smith-backup. Is it possible that when the contrib was incorporated into the base that it magically changed things to latest version?
I'll leave alone for the moment, as everything is working as it should.