[commits] [Wiki] created: OpenSuse16LeapUpdateFromAlphaNotes

boekhorstb1 wikiguest at horde.org
Wed Oct 7 13:33:46 UTC 2026


dc6614599d7a6767a1d256383af89e27  Wed, 07 Oct 2026 13:33:46 +0000

Created page: https://wiki.horde.org/OpenSuse16LeapUpdateFromAlphaNotes

# Update to H6 from H6 alpha

Current Horde version and Opensuse Version:
- Horde 6.0.0-RC7
- openSUSE Leap 16.0

Update to:
- Horde 6.2.1
- openSUSE Leap 16.0

There are a few helpful links that could help in case you get stuck  
(this is for setting things up from scratch):
- my previous tutorial [setup h6 on opensuse from scratch](./setup_h6.md)
- the [hordectl github  
repository](https://github.com/horde/hordectl/blob/FRAMEWORK_6_0/doc/INSTALL_HORDE.md) contains very useful documentation that is not readily available in the horde  
wiki.

## Requirements

- composer v2
- apache2
- mariadb (used version: 11.8.8-160000.1.1, should work on newest)
- PHP 8.4 with cli, fpm, mysql, xml (note this means xmlreader and  
xmlwriter for OpenSuse), mbstring, curl, gd, intl, bcmath, zip  
extensions.
- unzip

You need to setup php 8.4 first, then install all the required  
packages as follows (also run this command to update the packages if  
you do not want to perform a complete system update):

```
$ zypper in php8-cli php8-fpm php8-mysql php8-xmlreader php8-xmlwriter  
php8-mbstring php8-curl php8-gd php8-intl php8-bcmath php8-zip \
             php-composer2 \
             apache2 \
             mariadb \
             unzip
```

NOTE: You can do a systemupgrade as well, i.e.:

```
sudo zypper refresh && sudo zypper update
```

## Create backups

Create a backup of your horde directory and DB. At least duplicate the  
Horde working dir to somehwere safe.

NOTE:
- If you use hordectl in Horde, your configurations might be overwritten.
Normally hordectl will create a `conf.bak.php` file. But better be  
save than sorry. So at least backup the `var/` directory inside your  
horde parent directory (for me this will be  
`/srv/www/horde-deployment`).
- composer.lock contains your state of horde. So back that up too.

## Update with composer

First try the direct approach and run this (after you created the  
necessary backups):

```
# cd /srv/www/horde-deployment
# composer update
```

Update the Database:

```root
su wwwrun -s /bin/bash -c  
"/srv/www/horde-deployment/vendor/bin/horde-db-migrate up"
```

Set permissions again:

```root
chown -R wwwrun:www /srv/www/horde-deployment
chmod -R 775 /srv/www/horde-deployment
```

Restart apache2:

```
systemctl restart apache2
```





More information about the commits mailing list