<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
<html><body style='font-family: Verdana,Geneva,sans-serif'>
<p>Hi Jeroen,</p>
<p>i've performed the following steps, and i've encountered some issues, perhaps these might be of use to you:</p>
<p>- Installed a clean CentOS 6.4 on a virtualbox machine</p>
<p>- Installed kolab from the regular repos, as specified in <a href="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">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</a></p>
<p>- 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).</p>
<p>I then performed the following steps with their respective results/remarks:</p>
<p>1. Upgrade all packages to the 3.1 version</p>
<p><br />Install new OBS repository:<br />Wget the http://obs.kolabsys.com:82/Kolab:/3.1/CentOS_6/Kolab:3.1.repo file to /etc/yum.repos.d/</p>
<p>yum update</p>
<p>During the installation, a lot of notices/errors/warnings occurred in specifically the php based packages:</p>
<p><br />Installation php problems during installation of php-pear-DB-1.7.13-3.el6.noarch & roundcubemail-1.0-7.1.1.noarch:<br />PHP Warning: function registration failed, duplicate name new_vectorevent / vectorevent_set / vectorevent_size / vectorevent_capacity / vectorevent_clear / vectorevent_push / etc<br />PHP Warning: module kolabformat already loaded in Unknown on line 0<br />PHP Notice: constant swig_runtime_data_type_pointer already defined</p>
<p>SQLConnect error in roundcubemail installation</p>
<p><br />2. Run setup-kolab imap</p>
<p>Done without problems</p>
<p><br />2.1 Remove squatter:<br />http://hosted.kolabsys.com/~vanmeeuwen/build/html/administrator-guide/upgrading-from-kolab-3.0.html#the-use-of-squatter</p>
<p>Ran the provided snippet as a .sh script, works.</p>
<p><br />3. Run setup-kolab mta</p>
<p>Done without problems</p>
<p><br />4. Run setup-kolab roundcube<br />4.1 Dont be scared of errors about already existing databases<br />(improvement might be possible here?)</p>
<p>There were a lot of notices/errors, but otherwise it ran.</p>
<p><br />4.2 Manually check schema updates (improvement might be possible here?)<br />rpm -ql roundcubemail roundcubemail-plugins-kolab | grep sql</p>
<p>Checked that output, as far as i can see, last updates were from may/june, so i left them alone.</p>
<p>I did run the bin/installto.sh script, as specified in: <a href="http://trac.roundcube.net/wiki/Howto_Upgrade">http://trac.roundcube.net/wiki/Howto_Upgrade</a></p>
<p>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?</p>
<p>Best regards,</p>
<p>Hans de Raad</p>
<p> </p>
<div>
<pre>---<br />
DevHdR
onderdeel van HaLeNaS v.o.f.
Van Sevenbergestraat 49
2274 PK Voorburg
KvK: 53493753
Tel: +316-83578847
www.hcderaad.nl</pre>
</div>
<p>On 2013-09-16 12:00, devel-request@lists.kolab.org wrote:</p>
<blockquote type="cite" style="padding-left:5px; border-left:#1010ff 2px solid; margin-left:5px"><!-- html ignored --><!-- head ignored --><!-- meta ignored -->
<pre>Send devel mailing list submissions to
<a href="mailto:devel@lists.kolab.org">devel@lists.kolab.org</a>
To subscribe or unsubscribe via the World Wide Web, visit
<a href="https://lists.kolab.org/mailman/listinfo/devel">https://lists.kolab.org/mailman/listinfo/devel</a>
or, via email, send a message with subject or body 'help' to
<a href="mailto:devel-request@lists.kolab.org">devel-request@lists.kolab.org</a>
You can reach the person managing the list at
<a href="mailto:devel-owner@lists.kolab.org">devel-owner@lists.kolab.org</a>
When replying, please edit your Subject line so it is more specific
than "Re: Contents of devel digest..."
</pre>
<br />
<pre>Today's Topics:
1. Re: Upgradepath towards 3.1 (Jeroen van Meeuwen (Kolab Systems))
</pre>
<br />
<pre>List-Post: <mailto:<a href="mailto:devel@lists.kolab.org">devel@lists.kolab.org</a>>
Content-Transfer-Encoding: 7bit
From: "Jeroen van Meeuwen (Kolab Systems)" <<a href="mailto:vanmeeuwen@kolabsys.com">vanmeeuwen@kolabsys.com</a>>
Precedence: list
MIME-Version: 1.0
To: <a href="mailto:devel@lists.kolab.org">devel@lists.kolab.org</a>
References: <<a href="mailto:bcaf71684f76650adb02a9c765421af7@hcderaad.nl">bcaf71684f76650adb02a9c765421af7@hcderaad.nl</a>>
<<a href="mailto:ab8a0c0db53b3e320e0267a0e5b78c4d@hcderaad.nl">ab8a0c0db53b3e320e0267a0e5b78c4d@hcderaad.nl</a>>
In-Reply-To: <<a href="mailto:ab8a0c0db53b3e320e0267a0e5b78c4d@hcderaad.nl">ab8a0c0db53b3e320e0267a0e5b78c4d@hcderaad.nl</a>>
Date: Sun, 15 Sep 2013 11:17:26 +0100
Reply-To: Kolab development coordination <<a href="mailto:devel@lists.kolab.org">devel@lists.kolab.org</a>>
Message-ID: <<a href="mailto:f05cf823087c56ec1d1fbc1a6a589bed@kolabsys.com">f05cf823087c56ec1d1fbc1a6a589bed@kolabsys.com</a>>
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:</pre>
<blockquote type="cite" style="padding-left:5px; border-left:#1010ff 2px solid; margin-left:5px">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: <a href="http://hosted.kolabsys.com/~vanmeeuwen/build/html/administrator-guide/upgrading-from-kolab-3.0.html#the-use-of-squatter">http://hosted.kolabsys.com/~vanmeeuwen/build/html/administrator-guide/upgrading-from-kolab-3.0.html#the-use-of-squatter</a> 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.</blockquote>
<pre>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
</pre>
<br />
<pre>_______________________________________________
devel mailing list
<a href="mailto:devel@lists.kolab.org">devel@lists.kolab.org</a>
<a href="https://lists.kolab.org/mailman/listinfo/devel">https://lists.kolab.org/mailman/listinfo/devel</a><span style="font-family: Verdana, Geneva, sans-serif;"><span style="white-space: normal;">
</span></span></pre>
</blockquote>
</body></html>