Kolab 16 on Debian - upgrade error

[Daniel Hoffend]

Hi Christoph

I'm semi okay with your idea. This this has a couple drawbacks: Not 
every roundcubemail configuration file would get created by setup-kolab.

The way to go would be:
- defaults.php stays defaults.php
- config.php gets renamed to config.php.dist (.dist for distribution is 
a common suffix afaik)
- same applies to <plugin>.php in the roundcubemail-plugins-kolab 
package
- in the debian/postinst section we should do a test if config.php 
doesnt exist, cp config.php.dist config.php to ensure we have a complete 
configuration.

This way the initial installation gets a full valid configuration and 
during an upgrade you don't get asked if you want to replace your 
existing configuration.

But the default answer (if you want to replace a file) is indeed to keep 
your existing configuration. Even if you run apt-get upgrade in 
non-interactive mode, it will preserve your configuration unless you as 
admin do an error and select the wrong option manually!

But on the other hand: I like to have the notification if something has 
changed, because otherwise you don't notice if a plugin has updated 
their config syntax or introduced new options. But I can understand the 
risk. In the end it's a user/admin error and it shows how got your 
backup is

--
Regards
Daniel


Am 2018-11-12 10:11, schrieb Christoph Erhardt:
> Yep, the situation has been like this for quite some time: 
> roundcubemail
> includes a bunch of default configuration files and the end user must 
> be
> careful not to have their Kolab-generated configuration overwritten on 
> every
> upgrade.
> 
> But APT *did* ask politely before overwriting the file, defaulting to 
> "no",
> didn't it? ;-)
> 
> That said, I don't really see a striking reason for us to ship a 
> default
> configuration file in the first place if that file subsequently gets
> overwritten by "setup-kolab". So we might as well drop it from the 
> package, or
> we could rename it to something like "config.inc.php.default".
> 
> Any strong opinions? :-)
> 
> Best regards,
> Christoph
> 
> On Sunday, 11 November 2018 11:56:20 CET hede wrote:
>> On Fri, 9 Nov 2018 11:54:27 +0100 Gelpi Andrea <liste at gelpi.it> wrote:
>> > After the update roudcube said it cannot contact the db any more.
>> 
>> Same here. I didn't dig further into it but it seems the new config 
>> changes
>> some storage keys which renders roundcube unable to read old stored
>> secrets!?
>> 
>> Second: the whole local config was removed / replaced with some stale
>> default. No SQL Password, LDAP, etc. "setup-kolab roundcube" should be 
>> able
>> to repair this one.
>> _______________________________________________
>> users mailing list
>> users at lists.kolab.org
>> https://lists.kolab.org/mailman/listinfo/users
> _______________________________________________
> users mailing list
> users at lists.kolab.org
> https://lists.kolab.org/mailman/listinfo/users