[Kolab-devel] devel Digest, Vol 122, Issue 18

Thu Oct 10 14:00:49 CEST 2013

Hi Jeroen, 

i've performed the following steps, and i've encountered some issues,
perhaps these might be of use to you: 

- Installed a clean CentOS 6.4 on a virtualbox machine 

- Installed kolab from the regular repos, as specified in
http://docs.kolab.org/en-US/Kolab_Groupware/3.0/html/Community_Installation_Guide/chap-Community_Installation_Guide-Installation.html#sect-Community_Installation_Guide-Installation_with_RPM_Packages-Red_Hat_Enterprise_Linux
[3] 

- Performed setup-kolab, which presented a running installation in which
i have added a user and with this user i could log into roundcube and
send mail (or at least, fill the queue, since this is a confined
environment). 

I then performed the following steps with their respective
results/remarks: 

1. Upgrade all packages to the 3.1 version 

Install new OBS repository:
Wget the http://obs.kolabsys.com:82/Kolab:/3.1/CentOS_6/Kolab:3.1.repo
file to /etc/yum.repos.d/ 

yum update 

During the installation, a lot of notices/errors/warnings occurred in
specifically the php based packages: 

Installation php problems during installation of
php-pear-DB-1.7.13-3.el6.noarch & roundcubemail-1.0-7.1.1.noarch:
PHP Warning: function registration failed, duplicate name
new_vectorevent / vectorevent_set / vectorevent_size /
vectorevent_capacity / vectorevent_clear / vectorevent_push / etc
PHP Warning: module kolabformat already loaded in Unknown on line 0
PHP Notice: constant swig_runtime_data_type_pointer already defined 

SQLConnect error in roundcubemail installation 

2. Run setup-kolab imap 

Done without problems 

2.1 Remove squatter:
http://hosted.kolabsys.com/~vanmeeuwen/build/html/administrator-guide/upgrading-from-kolab-3.0.html#the-use-of-squatter

Ran the provided snippet as a .sh script, works. 

3. Run setup-kolab mta 

Done without problems 

4. Run setup-kolab roundcube
4.1 Dont be scared of errors about already existing databases
(improvement might be possible here?) 

There were a lot of notices/errors, but otherwise it ran. 

4.2 Manually check schema updates (improvement might be possible here?)
rpm -ql roundcubemail roundcubemail-plugins-kolab | grep sql 

Checked that output, as far as i can see, last updates were from
may/june, so i left them alone. 

I did run the bin/installto.sh script, as specified in:
http://trac.roundcube.net/wiki/Howto_Upgrade [4] 

Seems the installation/upgrade works. But i got a lot of
errors/warnings, are these possible related to my setup or are these
still an issue with the updateprocedure? 

Best regards, 

Hans de Raad 

---

DevHdR
onderdeel van HaLeNaS v.o.f.

Van Sevenbergestraat 49
2274 PK Voorburg

KvK: 53493753

Tel: +316-83578847

www.hcderaad.nl

On 2013-09-16 12:00, devel-request at lists.kolab.org wrote: 

> Send devel mailing list submissions to
> devel at lists.kolab.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.kolab.org/mailman/listinfo/devel [2]
> or, via email, send a message with subject or body 'help' to
> devel-request at lists.kolab.org
> 
> You can reach the person managing the list at
> devel-owner at lists.kolab.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of devel digest..."
> 
> Today's Topics:
> 
> 1. Re: Upgradepath towards 3.1 (Jeroen van Meeuwen (Kolab Systems))
> 
> List-Post: <mailto:devel at lists.kolab.org>
> Content-Transfer-Encoding: 7bit
> From: "Jeroen van Meeuwen (Kolab Systems)" <vanmeeuwen at kolabsys.com>
> Precedence: list
> MIME-Version: 1.0
> To: devel at lists.kolab.org
> References: <bcaf71684f76650adb02a9c765421af7 at hcderaad.nl>
> <ab8a0c0db53b3e320e0267a0e5b78c4d at hcderaad.nl>
> In-Reply-To: <ab8a0c0db53b3e320e0267a0e5b78c4d at hcderaad.nl>
> Date: Sun, 15 Sep 2013 11:17:26 +0100
> Reply-To: Kolab development coordination <devel at lists.kolab.org>
> Message-ID: <f05cf823087c56ec1d1fbc1a6a589bed at kolabsys.com>
> Content-Type: text/plain; charset=UTF-8;
> format=flowed
> Subject: Re: [Kolab-devel] Upgradepath towards 3.1
> Message: 1
> 
> On 2013-09-14 20:58, de Raad, Hans wrote:
> 
>> Hi Jeroen, thanks again for the clarifications, might i try a quick summary? This to try and find the cleanest possible upgrade path. 1. Upgrade all packages to the devel version 2. Run setup-kolab imap 2.1 Remove squatter: http://hosted.kolabsys.com/~vanmeeuwen/build/html/administrator-guide/upgrading-from-kolab-3.0.html#the-use-of-squatter [1] 3. Run setup-kolab mta 4. Run setup-kolab roundcube 4.1 Dont be scared of errors about already existing databases (improvement might be possible here?) 4.2 Manually check schema updates (improvement might be possible here?) rpm -ql roundcubemail roundcubemail-plugins-kolab | grep sql And by now one would run 3.1? If this is the case, i'd like to offer to create an update script performing these steps.
> 
> That would be great, I would appreciate notes and feedback on what else 
> may need to happen for an upgrade process.
> 
> That said, if we start to iterate over the things we might look at 
> doing;
> 
> - check and optionally prepare various aspects of the system, and
> - setup components (all of them or part of them), and
> - update / upgrade components,
> 
> we might want to start looking at how useful the current setup-kolab.py 
> is exactly. Additionally I can add to this list;
> 
> - a functioning '--yes' that just walks through the preparations and 
> setup with default values,
> - a functioning '--demo' that seeds some sample data in to the 
> environment,
> - a variety of options along the lines of: --with-ldap=openldap, 
> --with-imap=dovecot, --with-sql=postgres.
> 
> So perhaps it is time to design all of that properly.
> 
> Kind regards,
> 
> Jeroen van Meeuwen
> 
> _______________________________________________
> devel mailing list
> devel at lists.kolab.org
> https://lists.kolab.org/mailman/listinfo/devel [2]

Links:
------
[1]
http://hosted.kolabsys.com/~vanmeeuwen/build/html/administrator-guide/upgrading-from-kolab-3.0.html#the-use-of-squatter
[2] https://lists.kolab.org/mailman/listinfo/devel
[3]
http://docs.kolab.org/en-US/Kolab_Groupware/3.0/html/Community_Installation_Guide/chap-Community_Installation_Guide-Installation.html#sect-Community_Installation_Guide-Installation_with_RPM_Packages-Red_Hat_Enterprise_Linux
[4] http://trac.roundcube.net/wiki/Howto_Upgrade
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kolab.org/pipermail/devel/attachments/20131010/9d64a58b/attachment.html>