2 commits - Installation_Guide/en-US Testing_Reference/en-US
Jeroen van Meeuwen
vanmeeuwen at kolabsys.com
Fri Jan 7 15:46:14 CET 2011
Installation_Guide/en-US/Obtaining_Kolab_Software.xml | 270 ++++++++++++------
Testing_Reference/en-US/Test_Suite_000-Overview.xml | 4
2 files changed, 185 insertions(+), 89 deletions(-)
New commits:
commit 2d0c6d98a710295ea75d57abdd50b7f938c6c086
Author: Jeroen van Meeuwen (Kolab Systems) <vanmeeuwen at kolabsys.com>
Date: Fri Jan 7 14:44:37 2011 +0000
- Move the volatile repository information up further
- Expand on the actual start of the installation procedure
- Add a troubleshooting the apt package manager section
- Start on the RPM packages side of things as well
diff --git a/Installation_Guide/en-US/Obtaining_Kolab_Software.xml b/Installation_Guide/en-US/Obtaining_Kolab_Software.xml
index dff14cd..23107eb 100644
--- a/Installation_Guide/en-US/Obtaining_Kolab_Software.xml
+++ b/Installation_Guide/en-US/Obtaining_Kolab_Software.xml
@@ -173,6 +173,21 @@ $ <userinput>sha1sum -c SHA1SUMS</userinput></screen>
deb-src http://mirror.kolabsys.com/pub/debian/kolab-&PRODUCT_VERSION;/ squeeze release updates</screen>
</para>
+ <important>
+ <title>Debian Volatile (Updates) Repositories</title>
+ <para>
+ It is critically important to consider also enabling the so-called volatile repository for your Debian version, to enable updates for components such as <application>clamav</application>.
+ </para>
+ <para>
+ To enable the volatile repository for Debian Lenny, include the following line in <filename>/etc/apt/sources.list</filename>:
+ </para>
+ <para>
+
+<screen>deb http://volatile.debian.org/debian-volatile stable/volatile main</screen>
+
+ </para>
+
+ </important>
</step>
<step>
@@ -188,24 +203,32 @@ Pin-Priority: 501</screen>
</para>
</step>
+ <step>
+ <para>
+ Start the installation of the base package as follows:
+ </para>
+ <para>
- </procedure>
+<screen># <userinput>apt-get install kolabd</userinput></screen>
- <important>
- <title>Debian Volatile Repositories</title>
- <para>
- It is critically important to consider also enabling the volatile repository for your Debian version, to enable updates for components such as <application>clamav</application>.
- </para>
- <para>
- To enable the volatile repository for Debian Lenny, include the following line in <filename>/etc/apt/sources.list</filename>:
- </para>
- <para>
+ </para>
-<screen>deb http://volatile.debian.org/debian-volatile stable/volatile main</screen>
+ </step>
+ <step>
+ <para>
+ When asked to confirm you want to install the package and its dependencies, press Enter.
+ </para>
- </para>
+ </step>
+ <step>
+ <para>
+ When asked to confirm you want to continue installing the packages of which the integrity nor source can be securely verified, press y then Enter.
+ </para>
+
+ </step>
+
+ </procedure>
- </important>
</section>
@@ -243,114 +266,187 @@ Pin-Priority: 501</screen>
</section>
+ <section id="sect-Installation_Guide-Installation_with_APT_Packages-Troubleshooting_the_APT_Package_Manager">
+ <title>Troubleshooting the APT Package Manager</title>
+ <section id="sect-Installation_Guide-Troubleshooting_the_APT_Package_Manager-Broken_Packages">
+ <title>Broken Packages</title>
+ <para>
+ If you get an error similar to, for example:
+ </para>
+ <para>
- </section>
-
- <section id="sect-Installation_Guide-Obtaining_Kolab_Software-Installation_with_RPM_Packages">
- <title>Installation with RPM Packages</title>
- <para>
- para
- </para>
-
- </section>
-
- <section id="sect-Installation_Guide-Obtaining_Kolab_Software-Repository_Configuration">
- <title>Repository Configuration</title>
- <section id="sect-Installation_Guide-Repository_Configuration-Community_Edition">
- <title>Community Edition</title>
- <para>
- TODO: Insert notice about the community edition.
- </para>
-
- </section>
+<screen>test90-1:~# apt-get install kolabd
+Reading package lists... Done
+Building dependency tree
+Reading state information... Done
+Some packages could not be installed. This may mean that you have
+requested an impossible situation or if you are using the unstable
+distribution that some required packages have not yet been created
+or been moved out of Incoming.
+The following information may help to resolve the situation:
+
+The following packages have unmet dependencies:
+ kolabd: Depends: postfix (>= 2.4) but it is not going to be installed
+ Depends: postfix-ldap (>= 2.4) but it is not going to be installed
+E: Broken packages</screen>
- <section id="sect-Installation_Guide-Repository_Configuration-Enterprise_Edition">
- <title>Enterprise Edition</title>
- <para>
- TODO: Insert benefit of purchasing subscriptions to enterprise editions.
- </para>
- <para>
- TODO: Insert procedure to <emphasis>obtain</emphasis> mirror client certificate per system, and under what conditions excemptions are being made for a wildcard or customer cert.
- </para>
- <para>
- TODO: Describe exporting and using as browser cert.
- </para>
- <section id="sect-Installation_Guide-Enterprise_Edition-Enterprise_Edition_on_APT_based_Systems">
- <title>Enterprise Edition on APT-based Systems</title>
+ </para>
<para>
- TODO: Describe the exact procedure to enable the secure communications.
+ The error is not caused by broken packages, but a broken package manager that cannot install <application>exim</application> and <application>postfix</application> in parallel.
</para>
+ <formalpara id="form-Installation_Guide-Broken_Packages-Solution">
+ <title>Solution</title>
+ <para>
+ First remove any non-postfix MTA you may have installed, which in a default Debian installation is probably <application>exim</application>.
+ </para>
+
+ </formalpara>
<para>
- TODO: Describe the exact procedure to prioritize Kolab Systems packages over any other.
+ To remove <application>exim</application>, execute the following with superuser privileges:
</para>
+ <para>
- </section>
+<screen># <userinput>apt-get remove exim4 exim4-base exim4-config exim4-daemon-light</userinput></screen>
- <section id="sect-Installation_Guide-Enterprise_Edition-Enterprise_Edition_on_RPM_based_Systems">
- <title>Enterprise Edition on RPM-based Systems</title>
+ </para>
<para>
- TODO: Describe the exact procedure to enable the secure communications.
+ Then continue installing Kolab:
</para>
<para>
- TODO: Describe the exact procedure to prioritize Kolab Systems packages over any other.
+
+<screen># <userinput>apt-get install kolabd</userinput></screen>
+
</para>
</section>
- <section id="sect-Installation_Guide-Enterprise_Edition-Debian_Squeeze">
- <title>Debian Squeeze</title>
- <procedure>
- <step>
+
+ </section>
+
+
+ </section>
+
+ <section id="sect-Installation_Guide-Obtaining_Kolab_Software-Installation_with_RPM_Packages">
+ <title>Installation with RPM Packages</title>
+ <para>
+ RPM packages are being provided for the following Linux distributions and versions:
+ </para>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <formalpara id="form-Installation_Guide-Installation_with_RPM_Packages-CentOS">
+ <title>CentOS</title>
<para>
- For the supported, certified enterprise version of Kolab &PRODUCT_VERSION; software packages for Debian Squeeze, add the following two lines to <filename>/etc/apt/sources.list</filename>:
+ <simplelist>
+ <member>CentOS 5, until approximately Q1 2014</member>
+ <member>CentOS 6, until approximately Q4 2017</member>
+
+ </simplelist>
+
</para>
- <para>
-<screen>deb http://mirror.kolabsys.com/debian/kolab-&PRODUCT_VERSION;/ squeeze release updates
-deb-src http://mirror.kolabsys.com/debian/kolab-&PRODUCT_VERSION;/ squeeze release updates</screen>
+ </formalpara>
+ </listitem>
+ <listitem>
+ <formalpara id="form-Installation_Guide-Installation_with_RPM_Packages-Fedora">
+ <title>Fedora</title>
+ <para>
+ As Fedora is a development platform, and not a server platform, it suffices to say all current versions of Fedora are supported for as long as the lifecycle of the Fedora distribution lasts (e.g. approximately 13 months).
</para>
- </step>
+ </formalpara>
- </procedure>
+ </listitem>
+ <listitem>
+ <formalpara id="form-Installation_Guide-Installation_with_RPM_Packages-Red_Hat_Enterprise_Linux">
+ <title>Red Hat Enterprise Linux</title>
+ <para>
+ <simplelist>
+ <member>Red Hat Enterprise Linux 5 (Tikanga), until approximately Q1 2014</member>
+ <member>Red Hat Enterprise Linux 6 (Santiago), until approximately Q4 2017</member>
+ </simplelist>
- </section>
+ </para>
+
+ </formalpara>
+
+ </listitem>
+
+ </itemizedlist>
+ </para>
+ <section id="sect-Installation_Guide-Installation_with_RPM_Packages-CentOS">
+ <title>CentOS</title>
+ <para>
+ For the instructions on installing Kolab on CentOS, please refer to the instructions in <xref linkend="sect-Installation_Guide-Installation_with_RPM_Packages-Red_Hat_Enterprise_Linux" />.
+ </para>
</section>
- <section id="sect-Installation_Guide-Repository_Configuration-Red_Hat_Enterprise_Linux_5">
- <title>Red Hat Enterprise Linux 5</title>
- <procedure>
- <step>
- <para>
- Obtain the <application>-release</application>
- </para>
+ <section id="sect-Installation_Guide-Installation_with_RPM_Packages-Red_Hat_Enterprise_Linux">
+ <title>Red Hat Enterprise Linux</title>
+ <para>
+ The Kolab software repositories for Red Hat Enterprise Linux ship two so-called <literal>-release</literal> packages. The <literal>kolab-&PRODUCT_VERSION;-community-release</literal> package contains the configuration for the stable software channels, e.g. <emphasis>release</emphasis> and <emphasis>updates</emphasis>.
+ </para>
+ <para>
+ Depending on the version of Red Hat Enterprise Linux, install the following package:
+ </para>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="http://mirror.kolabsys.com/pub/redhat/kolab-/el5/development/x86_64/kolab--community-release-5-6.el5.kolab.noarch.rpm">Enterprise Linux 5</ulink>
+ </para>
- </step>
- <step>
- <para>
- TODO: Security and Integrity verification instructions
- </para>
+ </listitem>
- </step>
- <step>
- <para>
- TODO: Install instructions
- </para>
+ </itemizedlist>
- </step>
- <step>
- <para>
- Verification instructions
- </para>
+ </para>
+ <para>
+ To test the installation of the repository configuration, please execute:
+ </para>
+ <para>
- </step>
+<screen># <userinput>yum repolist</userinput>
+(...snip...)
+kolab-&PRODUCT_VERSION;
+kolab-&PRODUCT_VERSION;-updates
+(...snip...)</screen>
- </procedure>
+ </para>
+ <para>
+ Note that the output is abbreviated for clarity. The output may actually include the description of the repository, and the number of packages available. Optionally, to see which repositories have been configured though not enabled, also execute:
+ </para>
+ <para>
+<screen># <userinput>yum repolist all</userinput>
+(...snip...)
+kolab-&PRODUCT_VERSION;
+kolab-&PRODUCT_VERSION;-debuginfo
+kolab-&PRODUCT_VERSION;-source
+kolab-&PRODUCT_VERSION;-updates
+kolab-&PRODUCT_VERSION;-updates-debuginfo
+kolab-&PRODUCT_VERSION;-updates-source
+kolab-&PRODUCT_VERSION;-updates-testing
+kolab-&PRODUCT_VERSION;-updates-testing-debuginfo
+kolab-&PRODUCT_VERSION;-updates-testing-source
+(...snip...)</screen>
+
+ </para>
+ <para>
+ Note that the output is abbreviated for clarity. The output may actually include the description of the repository, whether the repository is enabled by default or not, and the number of packages available
+ </para>
+
+ </section>
+
+ <section id="sect-Installation_Guide-Installation_with_RPM_Packages-Fedora">
+ <title>Fedora</title>
+ <para>
+ para
+ </para>
</section>
commit e305db16680b47ab9fad35f6014da0f89dca6b1b
Author: Jeroen van Meeuwen (Kolab Systems) <vanmeeuwen at kolabsys.com>
Date: Thu Jan 6 17:47:46 2011 +0000
Clarify where these settings actually come from
diff --git a/Testing_Reference/en-US/Test_Suite_000-Overview.xml b/Testing_Reference/en-US/Test_Suite_000-Overview.xml
index ae5038e..d5ceaf2 100644
--- a/Testing_Reference/en-US/Test_Suite_000-Overview.xml
+++ b/Testing_Reference/en-US/Test_Suite_000-Overview.xml
@@ -27,13 +27,13 @@
<itemizedlist>
<listitem>
<para>
- As Cyrus Administrator, deletes all mailboxes relevant to the test cases included using the configured users in <literal>testing/users</literal>.
+ As Cyrus Administrator, deletes all mailboxes relevant to the test cases included using the configured users in section <literal>testing</literal>, key <literal>users</literal> from the configuration file specified on the command-line, or the default configuration file <filename>/etc/kolab/kolab.conf</filename>.
</para>
</listitem>
<listitem>
<para>
- Creates the top-level mailboxes for the users configured in <literal>testing/users</literal>.
+ Creates the top-level mailboxes for the users configured in section <literal>testing</literal>, key <literal>users</literal> from the configuration file specified on the command-line, or the default configuration file <filename>/etc/kolab/kolab.conf</filename>.
</para>
</listitem>
More information about the commits
mailing list