Hi Ok, good. I was not aware of that. Should I contact the release team or will you do that?
Best regards, // Ola On Sun, Aug 10, 2008 at 03:11:25AM +0200, Gregory Colpart wrote: > 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 <[EMAIL PROTECTED]> GnuPG:1024D/C1027A0E > Evolix - Informatique et Logiciels Libres http://www.evolix.fr/ > -- --- Inguza Technology AB --- MSc in Information Technology ---- / [EMAIL PROTECTED] Annebergsslingan 37 \ | [EMAIL PROTECTED] 654 65 KARLSTAD | | http://inguza.com/ Mobile: +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --------------------------------------------------------------- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
