OX6:UpdatingOXPackages: Difference between revisions

From Open-Xchange
No edit summary
 
(50 intermediate revisions by 9 users not shown)
Line 1: Line 1:
== Updating Open-Xchange Server packages ==
= Updating Open-Xchange Server packages =


This article describes how to update Open-Xchange Server packages from one service pack to another.
This article describes how to update Open-Xchange Server packages from one service pack to another.


'''What is written here only applies to Open-Xchange Server Service Pack levels SP4 and newer!'''
== How to get updates? ==
 
=== How to get updates? ===


Open-Xchange Server 6 updates can be accessed by customers with a valid license for
Open-Xchange Server 6 updates can be accessed by customers with a valid license for
Line 12: Line 10:
* OX HE
* OX HE


Have a look at the article:
You need to configure the [[OXReportClient]].
[http://sdb.open-xchange.com/node/65 How to create an OXAccount and unlock Keys within the License Database]
 
for more information about how to create an account in the [http://ldb.open-xchange.com LDB].
'''Please note: The update to v6.22 is only supported from an installed version 6.20.7 or later. If you have an earlier version of Open-Xchange Server 6 installed, please update to the latest release of v6.20 before attempting an update to v6.22.'''
 
= Updating Open-Xchange Server Packages 6.20.x =


=== What Service Pack do I have installed? ===
== Installing Updates ==


The service pack can be determined in checking the version number of the <tt>open-xchange</tt> package. The second digit relates to the SP version. The following table shows a list of package versions and the corresponding SP number:
A new service pack usually introduces new packages and requires configuration changes. To get all required new packages and configuration changes, the following '''must''' be done when installing updates.


{| border="1" cellspacing="0" cellpadding="5" align="center"
=== On Debian based distributions ===
! Package version
! SP Version
|-
| 6.4
| SP3
|-
| 6.6
| SP4
|-
| 6.8
| SP5
|-
|}


If the second digit is an odd number (e.g. 6.3, 6.5 or 6.7), you have a beta or snapshot version installed.
Add the following entry to <tt>/etc/apt/sources.list.d/open-xchange.list</tt>


==== How to determine the version number? ====
deb http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/updates/backend/DebianJessie/ /
===== On Debian based distributions =====
deb http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/updates/frontend/DebianJessie/ /


Run
Then run
 
$ apt-get update


  $ dpkg -l open-xchange
  $ apt-get dist-upgrade


The following output should appear:
If you want to see, what apt-get is going to do without actually doing it, you can run:


  Desired=Unknown/Install/Remove/Purge/Hold
  $ apt-get dist-upgrade -s
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name              Version            Description
+++-==================-==================-====================================================
ii  open-xchange      6.6.0-1            Open-Xchange server scripts and configuration


===== On RPM based distributions =====
{{RestartAfterUpdate}}


Run
=== On RPM based distributions ===


$ rpm -q open-xchange
==== RHEL6/CentOS6 ====


The following output should appear:
Add the following entry to <tt>/etc/yum.repos.d/ox.repo</tt>:


  open-xchange-6.6.0-1.1
  [ox-updates]
name=Open-Xchange Updates
baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/updates/backend/RHEL6/
baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/updates/frontend/RHEL6/
gpgkey=http://software.open-xchange.com/oxbuildkey.pub
enabled=1
gpgcheck=1
metadata_expire=0m


=== Installing Updates ===
 
and run
 
$ yum update
 
$ yum upgrade
 
{{RestartAfterUpdate}}
 
==== RHEL7/CentOS7 ====
 
Add the following entry to <tt>/etc/yum.repos.d/ox.repo</tt>:
 
[ox-updates]
name=Open-Xchange Updates
baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/updates/backend/RHEL7/
baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/updates/frontend/RHEL7/
gpgkey=http://software.open-xchange.com/oxbuildkey.pub
enabled=1
gpgcheck=1
metadata_expire=0m
 
 
and run
 
$ yum update
 
$ yum upgrade
 
{{RestartAfterUpdate}}
 
= Updating Open-Xchange Server Packages 6.22.x =
 
== Installing Updates ==


A new service pack usually introduces new packages and requires configuration changes. To get all required new packages and configuration changes, the following '''must''' be done when installing updates.
A new service pack usually introduces new packages and requires configuration changes. To get all required new packages and configuration changes, the following '''must''' be done when installing updates.


==== On Debian based distributions ====
=== On Debian based distributions ===
 
Add the following entry to <tt>/etc/apt/sources.list.d/open-xchange.list</tt>
 
deb http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/updates/backend/DebianJessie/ /
deb http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/updates/frontend/DebianJessie/ /


To ensure, that all required configuration file changes will be applied to the Open-Xchange packages, you need to leave the original files as they are and the <tt>postinst</tt> mechanism will automatically apply all necessary changes.
Then run


You can do that in answering all the questions like e.g. this
$ apt-get update


  Configuration file `/opt/open-xchange/etc/groupware/system.properties'
  $ apt-get dist-upgrade
  ==> Modified (by you or by a script) since installation.
  ==> Package distributor has shipped an updated version.
    What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version
    N or O  : keep your currently-installed version
      D    : show the differences between the versions
      Z    : background this process to examine the situation
  The default action is to keep your current version.
*** system.properties (Y/I/N/O/D/Z) [default=N] ?


with the default answer "N".
If you want to see, what apt-get is going to do without actually doing it, you can run:


If you don't want to do that every time, you could tell apt-get to answer this question for you, just cut and paste the following command in a shell as root user:
$ apt-get dist-upgrade -s


cat<<EOF > /etc/apt/apt.conf.d/01oxupdater
{{RestartAfterUpdate|release=6.22}}
DPkg::options {"--force-confold";};
EOF


''Note: This change will apply to ALL packages you are going to update in the future, not only Open-Xchange packages.
=== On RPM based distributions ===
''


Add the following entry to <tt>/etc/apt/sources.list</tt>
==== RHEL6/CentOS6 ====


  $ deb http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/updates/DebianEtch /
Add the following entry to <tt>/etc/yum.repos.d/ox.repo</tt>:
 
[ox-updates-backend]
name=Open-Xchange Updates
baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/updates/backend/RHEL6/
gpgkey=http://software.open-xchange.com/oxbuildkey.pub
enabled=1
gpgcheck=1
metadata_expire=0m
[ox-updates-frontend]
name=Open-Xchange Updates
baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/updates/frontend/RHEL6/
gpgkey=http://software.open-xchange.com/oxbuildkey.pub
enabled=1
gpgcheck=1
metadata_expire=0m
 
 
and run
 
$ yum update
 
  $ yum upgrade
 
{{RestartAfterUpdate|release=6.22}}
 
==== RHEL7/CentOS7 ====
 
Add the following entry to <tt>/etc/yum.repos.d/ox.repo</tt>:
 
[ox-updates-backend]
name=Open-Xchange Updates
baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/updates/backend/RHEL7/
gpgkey=http://software.open-xchange.com/oxbuildkey.pub
enabled=1
gpgcheck=1
metadata_expire=0m
[ox-updates-frontend]
name=Open-Xchange Updates
baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/updates/frontend/RHEL7/
gpgkey=http://software.open-xchange.com/oxbuildkey.pub
enabled=1
gpgcheck=1
metadata_expire=0m
 
and run
 
$ yum update
 
$ yum upgrade
 
{{RestartAfterUpdate|release=6.22}}
 
= Updating older supported versions of Open-Xchange Server Packages 6.22.x =
 
== Installing Updates ==
 
A new service pack usually introduces new packages and requires configuration changes. To get all required new packages and configuration changes, the following '''must''' be done when installing updates.
 
=== On Debian based distributions ===
If you want to update an older version of Open-Xchange Server v6 to the latest maintenance release, add the following entry to <tt>/etc/apt/sources.list.d/open-xchange.list</tt>. Replace VERSION with the version you are using (e.g. 6.22.6, 6.22.7). See [[AppSuite:Version_Support_Commitment]] for the currently supported versions. Also, make sure that your repository configuration points at the versioned base installation repositories (instead of using the <tt>6.22/stable</tt> symlink.)
 
deb http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/VERSION/updates/backend/DebianJessie/ /
deb http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/VERSION/updates/frontend/DebianJessie/ /


Then run
Then run
Line 109: Line 191:
  $ apt-get dist-upgrade -s
  $ apt-get dist-upgrade -s


==== On RPM based distributions ====
{{RestartAfterUpdate|release=6.22}}
 
=== On RPM based distributions ===


===== RHEL5 =====
==== RHEL6/CentOS6 ====


Add the following entry to <tt>/etc/yum.repos.d/ox.repo</tt>:
If you want to update an older version of Open-Xchange Server v6 to the latest maintenance release, add the following entry to <tt>/etc/yum.repos.d/ox.repo</tt>. Replace VERSION with the version you are using (e.g. 6.22.6, 6.22.7). See [[AppSuite:Version_Support_Committment]] for the currently supported versions. Also, make sure that your repository configuration points at the versioned base installation repositories (instead of using the <tt>6.22/stable</tt> symlink.)


  [ox-updates]
  [ox-updates-backend]
name=Open-Xchange Updates
baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/VERSION/updates/backend/RHEL6/
gpgkey=http://software.open-xchange.com/oxbuildkey.pub
enabled=1
gpgcheck=1
metadata_expire=0m
[ox-updates-frontend]
  name=Open-Xchange Updates
  name=Open-Xchange Updates
  baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/updates/RHEL5/
  baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/VERSION/updates/frontend/RHEL6/
gpgkey=http://software.open-xchange.com/oxbuildkey.pub
  enabled=1
  enabled=1
  gpgcheck=0
  gpgcheck=1
metadata_expire=0m
 
 
and run
 
$ yum update
 
$ yum upgrade
 
{{RestartAfterUpdate|release=6.22}}
 
==== RHEL7/CentOS7 ====


If you want to update an older version of Open-Xchange Server v6 to the latest maintenance release, add the following entry to <tt>/etc/yum.repos.d/ox.repo</tt>. Replace VERSION with the version you are using (e.g. 6.22.6, 6.22.7). See [[AppSuite:Version_Support_Committment]] for the currently supported versions. Also, make sure that your repository configuration points at the versioned base installation repositories (instead of using the <tt>6.22/stable</tt> symlink.)
[ox-updates-backend]
name=Open-Xchange Updates
baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/VERSION/updates/backend/RHEL7/
gpgkey=http://software.open-xchange.com/oxbuildkey.pub
enabled=1
gpgcheck=1
metadata_expire=0m
[ox-updates-frontend]
name=Open-Xchange Updates
baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/VERSION/updates/frontend/RHEL7/
gpgkey=http://software.open-xchange.com/oxbuildkey.pub
enabled=1
gpgcheck=1
metadata_expire=0m


and run
and run
Line 128: Line 250:
  $ yum upgrade
  $ yum upgrade


{{RestartAfterUpdate|release=6.22}}


===== SLES10 =====
==== SLES12 ====


Add the updates repository to the repository list:
If you want to update an older version of Open-Xchange Server v6 to the latest maintenance release, add the following entries to the repository list. Replace VERSION with the version you are using (e.g. 6.22.6, 6.22.7). See [[AppSuite:Version_Support_Committment]] for the currently supported versions. Also, make sure that your repository configuration points at the versioned base installation repositories (instead of using the <tt>6.22/stable</tt> symlink.)


  $ zypper sa http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/updates/SLES10/ OXUPDATES
  $ zypper ar http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/VERSION/updates/backend/SLE_12/ UPDATESBACKEND
$ zypper ar http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/VERSION/updates/frontend/SLE_12/ UPDATESFRONTEND


and run
and run


  $ zypper up -y -t package
  $ zypper dup -r UPDATESBACKEND
$ zypper dup -r UPDATESFRONTEND
 
 
You might need to run
 
$ zypper ref
 
to update the repository metadata before running ''zypper up''.
 
{{RestartAfterUpdate|release=6.22}}
 


''Note: package is not the name of a package, but an option, so just copy and paste the complete line.''
[[Category: OX6]]

Latest revision as of 10:31, 21 November 2019

Updating Open-Xchange Server packages

This article describes how to update Open-Xchange Server packages from one service pack to another.

How to get updates?

Open-Xchange Server 6 updates can be accessed by customers with a valid license for

  • OX SE
  • OX HE

You need to configure the OXReportClient.

Please note: The update to v6.22 is only supported from an installed version 6.20.7 or later. If you have an earlier version of Open-Xchange Server 6 installed, please update to the latest release of v6.20 before attempting an update to v6.22.

Updating Open-Xchange Server Packages 6.20.x

Installing Updates

A new service pack usually introduces new packages and requires configuration changes. To get all required new packages and configuration changes, the following must be done when installing updates.

On Debian based distributions

Add the following entry to /etc/apt/sources.list.d/open-xchange.list 

deb http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/updates/backend/DebianJessie/ /
deb http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/updates/frontend/DebianJessie/ /

Then run 

$ apt-get update

$ apt-get dist-upgrade

If you want to see, what apt-get is going to do without actually doing it, you can run: 

$ apt-get dist-upgrade -s

After the new packages are installed, the groupware and admin process needs a restart: 

$ /etc/init.d/open-xchange-groupware restart
$ /etc/init.d/open-xchange-admin restart

NOTE: Please take care, that you do not restart Open-Xchange during the process where it updates it's database. A database update can happen after installing minor or major updates. As soon as the first user tries to log in to the system or if any provisioning action is done, this update starts.

On RPM based distributions

RHEL6/CentOS6

Add the following entry to /etc/yum.repos.d/ox.repo: 

[ox-updates]
name=Open-Xchange Updates
baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/updates/backend/RHEL6/
baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/updates/frontend/RHEL6/
gpgkey=http://software.open-xchange.com/oxbuildkey.pub
enabled=1
gpgcheck=1
metadata_expire=0m


and run 

$ yum update

$ yum upgrade

After the new packages are installed, the groupware and admin process needs a restart: 

$ /etc/init.d/open-xchange-groupware restart
$ /etc/init.d/open-xchange-admin restart

NOTE: Please take care, that you do not restart Open-Xchange during the process where it updates it's database. A database update can happen after installing minor or major updates. As soon as the first user tries to log in to the system or if any provisioning action is done, this update starts.

RHEL7/CentOS7

Add the following entry to /etc/yum.repos.d/ox.repo: 

[ox-updates]
name=Open-Xchange Updates
baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/updates/backend/RHEL7/
baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/updates/frontend/RHEL7/
gpgkey=http://software.open-xchange.com/oxbuildkey.pub
enabled=1
gpgcheck=1
metadata_expire=0m


and run 

$ yum update

$ yum upgrade

After the new packages are installed, the groupware and admin process needs a restart: 

$ /etc/init.d/open-xchange-groupware restart
$ /etc/init.d/open-xchange-admin restart

NOTE: Please take care, that you do not restart Open-Xchange during the process where it updates it's database. A database update can happen after installing minor or major updates. As soon as the first user tries to log in to the system or if any provisioning action is done, this update starts.

Updating Open-Xchange Server Packages 6.22.x

Installing Updates

A new service pack usually introduces new packages and requires configuration changes. To get all required new packages and configuration changes, the following must be done when installing updates.

On Debian based distributions

Add the following entry to /etc/apt/sources.list.d/open-xchange.list 

deb http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/updates/backend/DebianJessie/ /
deb http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/updates/frontend/DebianJessie/ /

Then run 

$ apt-get update

$ apt-get dist-upgrade

If you want to see, what apt-get is going to do without actually doing it, you can run: 

$ apt-get dist-upgrade -s

After the new packages are installed, the server process needs a restart: 

$ /etc/init.d/open-xchange restart

NOTE: Please take care, that you do not restart Open-Xchange during the process where it updates it's database. A database update can happen after installing minor or major updates. As soon as the first user tries to log in to the system or if any provisioning action is done, this update starts.

On RPM based distributions

RHEL6/CentOS6

Add the following entry to /etc/yum.repos.d/ox.repo: 

[ox-updates-backend]
name=Open-Xchange Updates
baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/updates/backend/RHEL6/
gpgkey=http://software.open-xchange.com/oxbuildkey.pub
enabled=1
gpgcheck=1
metadata_expire=0m

[ox-updates-frontend]
name=Open-Xchange Updates
baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/updates/frontend/RHEL6/
gpgkey=http://software.open-xchange.com/oxbuildkey.pub
enabled=1
gpgcheck=1
metadata_expire=0m


and run 

$ yum update

$ yum upgrade

After the new packages are installed, the server process needs a restart: 

$ /etc/init.d/open-xchange restart

NOTE: Please take care, that you do not restart Open-Xchange during the process where it updates it's database. A database update can happen after installing minor or major updates. As soon as the first user tries to log in to the system or if any provisioning action is done, this update starts.

RHEL7/CentOS7

Add the following entry to /etc/yum.repos.d/ox.repo: 

[ox-updates-backend]
name=Open-Xchange Updates
baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/updates/backend/RHEL7/
gpgkey=http://software.open-xchange.com/oxbuildkey.pub
enabled=1
gpgcheck=1
metadata_expire=0m

[ox-updates-frontend]
name=Open-Xchange Updates
baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/updates/frontend/RHEL7/
gpgkey=http://software.open-xchange.com/oxbuildkey.pub
enabled=1
gpgcheck=1
metadata_expire=0m

and run 

$ yum update

$ yum upgrade

After the new packages are installed, the server process needs a restart: 

$ /etc/init.d/open-xchange restart

NOTE: Please take care, that you do not restart Open-Xchange during the process where it updates it's database. A database update can happen after installing minor or major updates. As soon as the first user tries to log in to the system or if any provisioning action is done, this update starts.

Updating older supported versions of Open-Xchange Server Packages 6.22.x

Installing Updates

A new service pack usually introduces new packages and requires configuration changes. To get all required new packages and configuration changes, the following must be done when installing updates.

On Debian based distributions

If you want to update an older version of Open-Xchange Server v6 to the latest maintenance release, add the following entry to /etc/apt/sources.list.d/open-xchange.list. Replace VERSION with the version you are using (e.g. 6.22.6, 6.22.7). See AppSuite:Version_Support_Commitment for the currently supported versions. Also, make sure that your repository configuration points at the versioned base installation repositories (instead of using the 6.22/stable symlink.) 

deb http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/VERSION/updates/backend/DebianJessie/ /
deb http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/VERSION/updates/frontend/DebianJessie/ /

Then run 

$ apt-get update

$ apt-get dist-upgrade

If you want to see, what apt-get is going to do without actually doing it, you can run: 

$ apt-get dist-upgrade -s

After the new packages are installed, the server process needs a restart: 

$ /etc/init.d/open-xchange restart

NOTE: Please take care, that you do not restart Open-Xchange during the process where it updates it's database. A database update can happen after installing minor or major updates. As soon as the first user tries to log in to the system or if any provisioning action is done, this update starts.

On RPM based distributions

RHEL6/CentOS6

If you want to update an older version of Open-Xchange Server v6 to the latest maintenance release, add the following entry to /etc/yum.repos.d/ox.repo. Replace VERSION with the version you are using (e.g. 6.22.6, 6.22.7). See AppSuite:Version_Support_Committment for the currently supported versions. Also, make sure that your repository configuration points at the versioned base installation repositories (instead of using the 6.22/stable symlink.) 

[ox-updates-backend]
name=Open-Xchange Updates
baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/VERSION/updates/backend/RHEL6/
gpgkey=http://software.open-xchange.com/oxbuildkey.pub
enabled=1
gpgcheck=1
metadata_expire=0m

[ox-updates-frontend]
name=Open-Xchange Updates
baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/VERSION/updates/frontend/RHEL6/
gpgkey=http://software.open-xchange.com/oxbuildkey.pub
enabled=1
gpgcheck=1
metadata_expire=0m


and run 

$ yum update

$ yum upgrade

After the new packages are installed, the server process needs a restart: 

$ /etc/init.d/open-xchange restart

NOTE: Please take care, that you do not restart Open-Xchange during the process where it updates it's database. A database update can happen after installing minor or major updates. As soon as the first user tries to log in to the system or if any provisioning action is done, this update starts.

RHEL7/CentOS7

If you want to update an older version of Open-Xchange Server v6 to the latest maintenance release, add the following entry to /etc/yum.repos.d/ox.repo. Replace VERSION with the version you are using (e.g. 6.22.6, 6.22.7). See AppSuite:Version_Support_Committment for the currently supported versions. Also, make sure that your repository configuration points at the versioned base installation repositories (instead of using the 6.22/stable symlink.) 

[ox-updates-backend]
name=Open-Xchange Updates
baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/VERSION/updates/backend/RHEL7/
gpgkey=http://software.open-xchange.com/oxbuildkey.pub
enabled=1
gpgcheck=1
metadata_expire=0m

[ox-updates-frontend]
name=Open-Xchange Updates
baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/VERSION/updates/frontend/RHEL7/
gpgkey=http://software.open-xchange.com/oxbuildkey.pub
enabled=1
gpgcheck=1
metadata_expire=0m

and run 

$ yum update

$ yum upgrade

After the new packages are installed, the server process needs a restart: 

$ /etc/init.d/open-xchange restart

NOTE: Please take care, that you do not restart Open-Xchange during the process where it updates it's database. A database update can happen after installing minor or major updates. As soon as the first user tries to log in to the system or if any provisioning action is done, this update starts.

SLES12

If you want to update an older version of Open-Xchange Server v6 to the latest maintenance release, add the following entries to the repository list. Replace VERSION with the version you are using (e.g. 6.22.6, 6.22.7). See AppSuite:Version_Support_Committment for the currently supported versions. Also, make sure that your repository configuration points at the versioned base installation repositories (instead of using the 6.22/stable symlink.) 

$ zypper ar http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/VERSION/updates/backend/SLE_12/ UPDATESBACKEND
$ zypper ar http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/6.22/VERSION/updates/frontend/SLE_12/ UPDATESFRONTEND

and run 

$ zypper dup -r UPDATESBACKEND
$ zypper dup -r UPDATESFRONTEND


You might need to run 

$ zypper ref

to update the repository metadata before running zypper up.

After the new packages are installed, the server process needs a restart: 

$ /etc/init.d/open-xchange restart

NOTE: Please take care, that you do not restart Open-Xchange during the process where it updates it's database. A database update can happen after installing minor or major updates. As soon as the first user tries to log in to the system or if any provisioning action is done, this update starts.

Retrieved from "https://wiki.open-xchange.com/wiki/index.php?title=OX6:UpdatingOXPackages&oldid=25064"