[pkg-horde] Bug#493885: Bug#493885: horde3: update to 3.2.1+debian0-2 causes imp to fail

[Gregory Colpart]

Hi,

On Tue, Aug 05, 2008 at 08:52:31PM +0200, Ola Lundqvist wrote:
> 
> I think we should consider this bug as a serious or important bug.
> This would mean that all existing installations of horde3 (from
> stable for example) will have all the applications disabled
> when they upgrade.
> 
> I know that this is simply an effect of the configuration file handling
> and that people have not edited the file before in combination with
> that the default value for the file has been updated. I think the
> change is good, but we need to make something about this...
> 
> Do you think it would be possible to "automatically make the
> configuration file edited" so that the configuration file handling
> function detect the file as changed and ask the admin if it should
> be replaced or not. I do not know at which stage the configuration
> files are replaced.
> 
> What do you think?

(A short answer because I've a slow Internet connection)

I think "it's not a bug" because I was aware of these effects.
See debian/NEWS:
--8<--
  * All Horde components are now inactive by default! If you want to use a
    component (IMP, Turba, Kronolith, etcetera.): configure it and active it
    in /etc/horde/horde3/registry.php file (set 'status' => 'active').
--8<--
We should also add this information in release notes for Lenny.

If you find a nice way to deal with upgrade with no change in
registry.php file, it could be interessant.

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