From owner-freebsd-ports@FreeBSD.ORG Sat Apr 8 06:28:14 2006 Return-Path: X-Original-To: freebsd-ports@FreeBSD.org Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1180B16A402; Sat, 8 Apr 2006 06:28:14 +0000 (UTC) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8DBF143D48; Sat, 8 Apr 2006 06:28:13 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (unknown [200.46.204.144]) by hub.org (Postfix) with ESMTP id BB0F462C89F; Sat, 8 Apr 2006 03:28:13 -0300 (ADT) X-Virus-Scanned: by amavisd-new at hub.org Received: from hub.org ([200.46.204.220]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id nECHem5RX2Bg; Sat, 8 Apr 2006 03:28:04 -0300 (ADT) Received: from ganymede.hub.org (blk-222-82-85.eastlink.ca [24.222.82.85]) by hub.org (Postfix) with ESMTP id 9A08762C898; Sat, 8 Apr 2006 03:28:12 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id E658F3AC3B; Sat, 8 Apr 2006 03:28:19 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id D0B42371CC; Sat, 8 Apr 2006 03:28:19 -0300 (ADT) Date: Sat, 8 Apr 2006 03:28:19 -0300 (ADT) From: "Marc G. Fournier" To: Thierry Thomas In-Reply-To: <20060407220515.GH30751@graf.pompo.net> Message-ID: <20060408032316.B947@ganymede.hub.org> References: <20060407032220.W947@ganymede.hub.org> <1144391457.23833.6.camel@shumai.marcuscom.com> <20060407133620.C947@ganymede.hub.org> <20060407220515.GH30751@graf.pompo.net> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1744749939-1144477699=:947" Cc: freebsd-ports@FreeBSD.org Subject: Re: BEWARE upgrading Horde System X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Apr 2006 06:28:14 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-1744749939-1144477699=:947 Content-Type: TEXT/PLAIN; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Sat, 8 Apr 2006, Thierry Thomas wrote: > Le Ven 7 avr 06 =E0 18:38:31 +0200, Marc G. Fournier > =E9crivait=A0: >>> 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 >>> steps). >> >> 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, no= t >> blindly overwrite any of the .php files that an admin may or may not hav= e >> 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 > displayed: > > cp -p $cf $cf.previous > echo "=3D=3D=3D> Backing-up..." > echo "---> $cf has been saved ***" > echo "---> as $cf.previous ***" I had seen/found the one in horde/config/conf.php.previous ... totally=20 overlooked the others ... but, the point is, why overwrite an existing=20 configuration with a stock one in the first place? None of the other=20 ports does that ... just upgraded amavisd, and it has a fairly large=20 config file, and it didn't move *my* config file off to the side to put in= =20 some default one :( I ended up finding a backup of my old install that was laying around one=20 of my servers (thank god I hate deleting old files), copying those in=20 place, and then going through and manually updating my config files=20 (either through Horde Admin -> Setup area, or using diff ) ... it wasn't=20 until *after* had gone through this that I clued into the 'previous' files= =20 =2E.. casualty of using portupgrade to update ports, most messages like you= r=20 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@hub.org Yahoo!: yscrappy ICQ: 7615664 --0-1744749939-1144477699=:947--