2015-06-01 21:36 keltezéssel, Steve Ankeny írta:
What's missing when we see the following?
The following packages have been kept back:
libldb-dev libldb1 libmapi0 libmapiproxy0 libmapistore0 libnss-winbind
libpam-winbind libsmbclient libwbclient0 openchangeproxy
openchangeserver
python-ldb python-ocsmanager python-samba samba samba-common
samba-common-bin samba-dev samba-dsdb-modules samba-libs
samba-vfs-modules
smbclient sogo sogo-activesync sogo-openchange winbind
0 upgraded, 0 newly installed, 0 to remove and 26 not upgraded.
And, I presume 'sql-update-2.2.17_to_2.3.0.sh' is part of the SOGo
packages?
... or the postinstall script will detect and run it automatically?
On 06/01/2015 02:51 PM, Ludovic Marcotte wrote:
Upgrading to v2.3.0
Run the shell
scriptsql-update-2.2.17_to_2.3.0.shorsql-update-2.2.17_to_2.3.0-mysql.sh(if
you use MySQL).
This will grow the "participant states" field of calendar quick
tables to a larger size and add the the "c_description" column to
calendar quick tables.
Moreover, if you are using a multi-domain configuration, make sure
the keys for your domains match the email domains you have defined.
I don't clearly understand the red part...
Example, if I have...
domains = {
*domain1*= {
SOGoMailDomain = "*domain1.tld*";
SOGoUserSources = (
{
...
}
);
};
*domain2*= {
SOGoMailDomain = "*domain2.tld*";
SOGoUserSources = (
{
...
}
);
};
};
... then I need to rename keys from domainX to domainX.tld before upgrading?
--
users@sogo.nu
https://inverse.ca/sogo/lists
