BEWARE upgrading Horde System
Marc G. Fournier
scrappy at hub.org
Sat Apr 8 06:28:14 UTC 2006
On Sat, 8 Apr 2006, Thierry Thomas wrote:
> Le Ven 7 avr 06 à 18:38:31 +0200, Marc G. Fournier <scrappy at hub.org>
> écrivait :
>>> The Horde config is backed up to conf.php.previous on every upgrade.
>>> Simply copying this file back to conf.php, checking permissions, then
>>> regenerating the config through the web is enough to get you right back
>>> where you left off (provided you have done any other required upgrade
>> Right, now go upgrade your IMP, or Turba, or Kronolith? And what about
>> changes to registry.php?
>> All that should happen on an upgrade is the .dist files get upgraded, not
>> blindly overwrite any of the .php files that an admin may or may not have
>> modified ... that is why the base distribution has .dist files ...
>> On an initial install, although it does add more work, putting the
>> original .php files in place is cool ... but, for instance, my motd.php
>> files for IMP is now gone, which had a bunch of programming in it to
>> redirect ppl coming in to various places ... now it has a 'Powered by
>> Horde' icon :(
> Which was your previous versions? All modified config/*.php should have
> been saved as config/*.php.previous, and a message should have been
> cp -p $cf $cf.previous
> echo "===> Backing-up..."
> echo "---> $cf has been saved ***"
> echo "---> as $cf.previous ***"
I had seen/found the one in horde/config/conf.php.previous ... totally
overlooked the others ... but, the point is, why overwrite an existing
configuration with a stock one in the first place? None of the other
ports does that ... just upgraded amavisd, and it has a fairly large
config file, and it didn't move *my* config file off to the side to put in
some default one :(
I ended up finding a backup of my old install that was laying around one
of my servers (thank god I hate deleting old files), copying those in
place, and then going through and manually updating my config files
(either through Horde Admin -> Setup area, or using diff ) ... it wasn't
until *after* had gone through this that I clued into the 'previous' files
... casualty of using portupgrade to update ports, most messages like your
above most likely scrolls off the screen faster then one sees it ;(
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy at hub.org Yahoo!: yscrappy ICQ: 7615664
More information about the freebsd-ports