Update form openSUSE Leap 15.6 to 16.0

WalterH · 2026-04-13T16:12:44+00:00

openSUSE 15.6 is nearly at the end of its life cycle. The Grommunio developers have resolved the dependency issues for the openSUSE 16.0 packages, so it is t...

Duese6

@externa1
From this side it looks like the original appliance setup might be a factor.
Older legacy/BIOS-based appliances seem to behave differently than newer UEFI/EFI installs during the 15.6 → 16.0 upgrade.
So the difference may be less about community vs. supported, and more about how the system was originally installed.

Duese6

crpb
One question regarding the repository setup:
Is OSS + non‑OSS currently sufficient for Leap 16.0, or should an update repository be expected as well?
On Leap 15.6 the /update repo played an important role, so I just want to confirm this is expected behavior for 16.0 at the moment.

crpb

crpb update opensuse repositories

click in the link above, it is all explained

Duese6

Hi,

someone else got this SuSE Package Signing Errors?
Is there any way to "fix" this? Or just ignore it.

WalterH

Duese6 This is explained in: "13. Distribution update to openSUSE 16.0" last sentence.

Duese6

I removed the expired GPG key (gpg-pubkey-39db7c82-5f68629b) using

rpm -e gpg-pubkey-39db7c82-5f68629b

and then refreshed the repositories with

zypper ref

If there is a better or recommended approach, please let me know. 😅

Andy

WalterH I have the openSUSE repositories in the file /etc/zypp/repos.d/bas.repo.

Same here with the single repo

crpb Or even easier

Therefore I will try this after clone my VM, will see.

Andy

As I have Communityversion, I use the first 4 lines

rm /etc/zypp/repos.d/*
zypper addrepo http://cdn.opensuse.org/distribution/leap/16.0/repo/non-oss openSUSE:repo-non-oss
zypper addrepo http://cdn.opensuse.org/distribution/leap/16.0/repo/oss openSUSE:repo-oss
zypper addrepo --enable --refresh --no-keep-packages 'https://download.grommunio.com/community/openSUSE_Leap_16.0' grommunio

localhost:~ # zypper lr
Die Repository-Prioritäten sind ohne Effekt. Alle aktivierten Repositorys teilen sich die gleiche Priorität.

# | Alias                 | Name                  | Enabled | GPG Check | Refresh
--+-----------------------+-----------------------+---------+-----------+--------
1 | grommunio             | grommunio             | Ja      | ( p) Ja   | Ja
2 | openSUSE:repo-non-oss | openSUSE:repo-non-oss | Ja      | ( p) Ja   | Nein
3 | openSUSE:repo-oss     | openSUSE:repo-oss     | Ja      | ( p) Ja   | Nein
localhost:~ #

Andy

But I´m not sure, if that all, because in Leap 15.6 it was more

localhost:~ # cat /etc/zypp/repos.d/*.repo | more
[grommunio]
enabled=1
autorefresh=1
baseurl=https://download.grommunio.com/community/openSUSE_Leap_16.0
keeppackages=0
[openSUSE:repo-non-oss]
enabled=1
autorefresh=0
baseurl=http://cdn.opensuse.org/distribution/leap/16.0/repo/non-oss
[openSUSE:repo-oss]
enabled=1
autorefresh=0
baseurl=http://cdn.opensuse.org/distribution/leap/16.0/repo/oss
localhost:~ #

And is autorefresh=0 maybe better autorefresh=1 or is okay with 0?

Duese6

Andy

Hi.

I use autorefresh=1 so repository metadata is always up to date automatically.

So mine (base.repo) looks like

[openSUSE:repo-non-oss]
enabled=1
autorefresh=1
baseurl=https://cdn.opensuse.org/distribution/leap/16.0/repo/non-oss
keeppackages=0

[openSUSE:repo-oss]
enabled=1
autorefresh=1
baseurl=https://cdn.opensuse.org/distribution/leap/16.0/repo/oss
keeppackages=0

Andy

Also unclear is if the plymouth-start.service must be started. The jitsi-jicofo.service is down since a long time.

localhost:~ # systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● jitsi-jicofo.service loaded failed failed JItsi COnference FOcus
● plymouth-start.service masked failed failed plymouth-start.service

Legend: LOAD → Reflects whether the unit definition was properly loaded.
ACTIVE → The high-level unit activation state, i.e. generalization of SUB.
SUB → The low-level unit activation state, values depend on unit type.

2 loaded units listed.
Sie haben neue Post in /var/mail/root.
localhost:~ #

Duese6

Hi.

As a final step of my Leap 15.6 → 16.0 migration tests, I wanted to verify that the complete Let’s Encrypt renewal and deploy workflow actually works on a grommunio appliance.
For testing purposes, I deliberately placed an older (but still valid) certificate so that certbot is definitely inside the renewal window. The goal was not to debug certbot itself, but to make sure the full grommunio deploy path (certbot → nginx stop/start → deploy hook) really runs.
It turned out that on Leap 16.0 the certbot binary symlinks may be missing:
/etc/alternatives/certbot -> /usr/bin/certbot-3.13
/usr/bin/certbot -> /etc/alternatives/certbot

Creating the symlinks manually fixed the issue:
sudo ln -sf /usr/bin/certbot-3.13 /etc/alternatives/certbot
sudo ln -sf /etc/alternatives/certbot /usr/bin/certbot

After that, grommunio-certbot-renew.service runs correctly and the renewal/deploy workflow completes without issues.
Just wanted to share this in case someone else runs into a renewal job that silently skips due to a missing /usr/bin/certbot.

grommunio99

Duese6 thats a very good point!
https://www.reddit.com/r/openSUSE/comments/1ogukop/certbotletsencrypt_on_opensuse_leap_16/
looks like we will get problems in the future as there will be no package for certbot any more.

THE_FRICKLER

ich habe heute meine community Appliance genau nach der "grünen" Anleitung von 15.6 auf 16.0 gehoben. Mit Redis ergab es ein Problem. zypper in redis hat es behoben.
Danke Walter

grommunio99

thx @WalterH - the upgrade instruction worked almost great.
Just one question, after the upgrade was completed
I only had one repository active:

# | Alias                 | Name                  | Enabled | GPG Check | Refresh
--+-----------------------+-----------------------+---------+-----------+--------
1 | grommunio             | grommunio             | Ja      | (r ) Ja   | Ja

I added the others again with

zypper addrepo http://cdn.opensuse.org/distribution/leap/16.0/repo/oss openSUSE:repo-oss
zypper addrepo http://cdn.opensuse.org/distribution/leap/16.0/repo/non-oss openSUSE:repo-non-oss

But i'm note sure what you mean with this sentence:
"This repository list includes both oss and non-oss repositories, but the oss repository has not been renamed 'base':"

My current repo config looks like this:

sudo zypper lr
[sudo] Passwort für root:
Die Repository-Prioritäten sind ohne Effekt. Alle aktivierten Repositorys teilen sich die gleiche Priorität.

# | Alias                 | Name                  | Enabled | GPG Check | Refresh
--+-----------------------+-----------------------+---------+-----------+--------
1 | grommunio             | grommunio             | Ja      | (r ) Ja   | Ja
2 | openSUSE:repo-non-oss | openSUSE:repo-non-oss | Ja      | (r ) Ja   | Nein
3 | openSUSE:repo-oss     | openSUSE:repo-oss     | Ja      | (r ) Ja   | Nein

I think its fine?

WalterH

It's easier to read if you format the code as code.
I've also noticed that the openSUSE repositories sometimes disappear during the update. The list of repositories is fine. You just need to enable auto-refresh.

1of16

grommunio99
just use https://github.com/acmesh-official/acme.sh

Duese6

I noticed that only grommunio-imapsync-2.229-lp160.4.1.noarch being installed.
The newer grommunio-imapsync-2.314-lp160.x package cannot be installed because it requires perl(IO::Socket::INET6), which does not seem to be available on Leap 16.
On Leap 15.6 this dependency was present, so the newer version installs fine there.
Has anyone else observed the same behavior on Leap 16, or found a clean way to install the newer imapsync package?

Andy

Don´t know, maybe here

https://community.grommunio.com/d/2635-grommunio-imapsync-opensuse-leap-160

With Leap 16, which commands must be use to reinstall Grommunio Files (NC)?

Duese6

Andy

Hi, did you uninstall grommunio-files during setup (e.g. Solution 3: deinstallation of grommunio-files-31.0.13-lp156.1.1.noarch)?

I did the same on my first test system. Later I reinstalled it using zypper in grommunio-files, but that also required choosing “break php8-imagick-3.7.0-bp156.4.5.x86_64 by ignoring some of its dependencies”.

This worked for me. But accessing /files returned a 500 error because the original configuration was missing.
I restored the configuration directly from an older snapshot (/var/lib/grommunio-files/config/config.php).

EddieA

I didn't see, but is there a timeline on a new ISO with this version of OpenSUSE.

I'm currently trying out grommunio, so it wouldn't be a hardship for me to start over and it would be a cleaner route.

« Previous Page Next Page »