Page MenuHomePhorge

New Kolab install broken on Ubuntu 22.04
Closed, ResolvedPublic

Description

Hello Community

first thanks for you effort over the years.
The support for Ubuntu 18.04 will end march this year and I'm currently looking into upgrade my kolab-installation accordiningly.

Throughout the last year the packages for 20.04 and 22.04 appears in the repositories but are not installable. (I've seen there is a plesk version running on 20.04 ...)

The following packages have unmet dependencies:
 kolab : Depends: kolab-cli but it is not installable
         Depends: kolab-conf but it is not installable
         Depends: kolab-imap but it is not going to be installed
         Depends: kolab-mta but it is not going to be installed
         Depends: kolab-saslauthd but it is not installable
         Depends: kolab-server but it is not installable
         Depends: kolab-webclient but it is not going to be installed
         Depends: kolab-webadmin but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

Are there plans to support the new ubuntu lts version or do i have to switch to another distribution?

Details

Ticket Type
Task

Event Timeline

ghane lowered the priority of this task from Needs Triage to Low.Jan 30 2023, 12:06 PM
ghane subscribed.

work is in progress

This is like T7247 (deb packaging)

ghane triaged this task as Normal priority.Jan 30 2023, 3:05 PM
ghane added a project: Architecture & Design.

Hello

a little feedback from my side. While using https://mirror.apheleia-it.ch/repos/Kolab:/16:/Testing/Ubuntu_22.04 as source, I was able to install the kolab-packages. So the dependencies are solved. Only one strange thing comes up: the 389-ds package depends on cockpit-389-ds and therefore enforces cockpit to be installed... but this seems to comes from upstream

besides that: roundcube is unable to connect to the LDAP. ErrorMessage: LDAP Error: Could not connect to any LDAP server, last tried localhost

I double checked this via LDAP search -> ldap is available and queryable. cyrus-imap is also able to connect and query, i'm able to successfully connect and query to cyrus-imap

one other quirk: for some reason i have to create /var/lock/dirsrv/slapd-deepdraft and /var/run/dirsrv all the time prior to start 389/dirsrv. In ubuntu booth folders are mapped to a tmpfs. seems something is missing in the startup-scripts

PS: this is currently only used in a test-environment

machniak claimed this task.