Kopano Core & Archiver 8.3.0 final is now available

Wiz

@fbartels Yes, I am aware of this commit as I spent several hours yesterday scrambling over the KCs and commits trying to figure out what happened, however, after reverting the changes made in the commit I was still facing problems with mapi.so so it is something else.

I’ve created support ticket KS-37572 for this particular purpose and would appreciate having it escalated internally on a priority basis as z-push and collab are down.

fbartels

@Wiz I have forwarded your message to our support.

Hi,

I also see this certificate error on Debian 7:

Ign https://download.kopano.io ./ Translation-en
Ign https://download.kopano.io ./ Translation-en
Err https://download.kopano.io ./ Packages
  server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
Err https://download.kopano.io ./ Packages
  server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
Err https://download.kopano.io ./ Packages
  server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
W: Failed to fetch https://download.kopano.io/supported/core:/final/Debian_7.0/./Packages  server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none

W: Failed to fetch https://download.kopano.io/supported/webapp:/final/Debian_7.0/./Packages  server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none

W: Failed to fetch https://download.kopano.io/supported/mdm:/final/Debian_7.0/./Packages  server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none

E: Some index files failed to download. They have been ignored, or old ones used instead.

Any ideas how to sove this error?

Walter

Hi,

uptate to V 8.3.0 on SLES 12, is not possible, zypper always reports “Nothing to do.”

# zypper in kopano-server-packages
Refreshing service 'SUSE_Linux_Enterprise_Server_12_SP1_x86_64'.
Refreshing service 'SUSE_Linux_Enterprise_Software_Development_Kit_12_SP1_x86_64'.
Refreshing service 'Web_and_Scripting_Module_12_x86_64'.
Loading repository data...
Reading installed packages...
'kopano-server-packages' is already installed.
No update candidate for 'kopano-server-packages-8.2.1.531-8.1.x86_64'. The highest available version is already installed.
Resolving package dependencies...

Nothing to do.

Download center provides version 8.3.0.

Any ideas how to fix this issue?

I already found the solution for SLES12SP1, “Auto Refresh” was disabled.

klausade

@WalterHof You could work around this with the following line, in eiter /etc/apt/apt.conf or a file in /etc/apt.cond./
Acquire::https::download.kopano.io::Verify-Peer “false”;

I wish Kopano would just fix their end. I don’t recommend this fix, setting verify-peer to false is not the way to go.

HPH_ZForum

Hello,
I’ve got to say, that on UCS 4.1 this is a complete mess with the repo enabled. I’ve completely lost the clue on what version is provided through which channel.
Something is in “App Center-Aktualisierungen”, something in “Paket-Aktualisierungen”.

"Es sind App Center-Aktualisierungen verfügbar.

Kopano Core: Version 8.1.1.10-8.1-2 kann auf 8.1.1.10-8.1-3 aktualisiert werden
Kopano WebApp: Version 3.2.0.335-19.1 kann auf 3.2.0.335-19.1-2 aktualisiert werden
Z-Push for Kopano: Version 2.3.5 kann auf 2.3.6 aktualisiert werden"

The “Paket-Aktualisierungen” sometimes show something, sometimes they don’t. Klicking on “Install” sometimes does something, sometimes it doesn’t.

What should be the correct, latest Version for Core, WebApp and Z-Push now for UCS 4.1?

HPH_ZForum

@fbartels is it possible, that the UCS appcenter does not reflect the updated versions of Kopano Core installed through “Paket-Aktualisierungen”?
Since Kopano Deskapp is stating “Kopano Core: 8.3.0-1042”, while UCS is still on 8.1.1.10-8.1-2 and offers 8.1.1.10-8.1-3.

@klausade it seams, kopano repaired this issue. Today I upgraded to 8.3.0 on Debian 7 without this errors.

klausade

@WalterHof yes I know. I reported this as a bug, and it got resolved today.