Re: Kolab 16 on Debian - upgrade error

Christoph Erhardt <[email protected]> Mon, 12 Nov 2018 10:11:47 +0100

Newsgroups	gmane.comp.kde.devel.kroupware
Message-ID	<1915574.G8ySqt0N9Z__29626.0291863748$1542014297$gmane$org@delle>

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 <[email protected]> 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
> [email protected]
> https://lists.kolab.org/mailman/listinfo/users

_______________________________________________
users mailing list
[email protected]
https://lists.kolab.org/mailman/listinfo/users

signature.asc (application/pgp-signature, 833 B)