[pkg-horde] Bug#515892: Bug#515892: horde3: Nothing works after upgrading from 3.1.3-4etch4 to 3.2.2+debian0-2

Gregory Colpart reg at evolix.fr
Sun Mar 15 13:51:18 UTC 2009

severity 515892 wishlist

Hello, thanks for your report.

On Wed, Feb 18, 2009 at 08:48:50AM +0100, root wrote:
> Since the last upgrade, my horde3 installation is completely
> broken, none of the modules seems to work.  Investigating in my
> box, I've found many problems : first the modules are nearly
> all set to inactive in /etc/horde/horde3/registry.php

All modules are disabled by default for a *new* installation (see
NEWS). But, when you are upgrading, you have the choice to keep
your old registry.php as a conf file. Then I guess you choose to
overwrite your old registry.php.

> the webroot detection that was in the same file has been
> removed and replaced with a hardcoded path which is false in my
> case.

webroot detection is useless with Debian for FHS reason IIRC.
Then, it's hardcoded in registry.php file. If you modify it, you
will have the choice to keep your changes (as a conf file).

> After activating the modules in this file, it appears that the
> different database tables (mysql in my case) used by the
> modules haven't been updated according to the examples found in
> /usr/share/doc/ I'm trying to upgrade them by hand one by one
> but it's a bit boring.

Database upgrades are not automatically done, and you shoud
actually upgrade them by hand for now. I agree that upgrades
could be less boring: ideas/patches welcome :)
I keep this bug open in wishlist.

On Thu, Feb 26, 2009 at 05:35:52PM +0100, tech at mediaforest.net wrote:
> updating database by hand  seemed at first to make horde work
> back, but when using it, it appears that many features are
> broken :
> - All users preferences have been reset,
> - On any message of any account, it's no more possible to "see
> all headers" when clicking it, I always get "Requested message
> not found."
> - Many messages aren't viewable online

Outch. Could you open separate bug report for them? Or even
open bug reports directly in upstream BTS (bugs.horde.org)?

Gregory Colpart <reg at evolix.fr>  GnuPG:1024D/C1027A0E
Evolix - Informatique et Logiciels Libres http://www.evolix.fr/

More information about the pkg-horde-hackers mailing list