Zimbra 10.1.16 Released - Please Post Your Patch/Upgrade Results Here

[adrian.gibanel.btactic]

Release Notes:
https://wiki.zimbra.com/wiki/Zimbra_Releases/10.1.16

Please post your patching and/or upgrading results here.

---

( This is a very small summary. Check the release notes above for the complete changes. )

• Many security fixes
• Ubuntu 24 Support (Beta)
• New Zimbra NE Backup Restore v2 available with enhanced deduplication and improved compression.

---

Please take this thread as a Network Edition only release. ZCS FOSS builds feedback in this thread are usually not useful because the FOSS version might not be ready to be built because of embargos or previous or current versions. (Explanation.)

[adrian.gibanel.btactic]

• Ubuntu 24 Support (Beta)

If you take a look at Zimbra NE downloads page you can see that download filename is zcs-NETWORK-10.1.0_BETA_4848.UBUNTU24_64.20260106140815.tgz.

I was actually expecting something like zcs-NETWORK-10.1.16_BETA_4848.UBUNTU24_64.20260106140815.tgz given that 10.1.0 is a rather old version that might not be prepared to work with Ubuntu 24.04.

What's funny is that we already have zm-build's 10.1.0.beta tag from when 10.1.0 was initially tested as beta... so they cannot push that tag again because it would be overwritten.

So I'm not sure how to replicate this in order to try to build Ubuntu 24.04 FOSS... unless I just use 10.1.15 tags (10.1.16 tag is embargoed as it was expected).

My current hyphotesis is that they used (with additional changes to include NE stuff) something similar to:

Code: Select all

git clone --depth 1 --branch 10.1.16 git@github.com:Zimbra/zm-build.git
cd zm-build
ENV_CACHE_CLEAR_FLAG=true ./build.pl --ant-options -DskipTests=true --git-default-tag=10.1.16,10.1.15,10.1.14,10.1.13,10.1.12,10.1.10,10.1.9,10.1.8,10.1.7,10.1.6,10.1.5,10.1.4,10.1.3,10.1.2,10.1.1,10.1.0,10.1.0.beta --build-release-no=10.1.0 --build-type=FOSS --build-release=LIBERTY --build-release-candidate=BETA --build-no 4848 --build-thirdparty-server=files.zimbra.com --no-interactive

.
so in other words:

- --build-release-no=10.1.0 enforces that the filename has 10.1.0 on it.
- --git-default-tag=10.1.16,10.1.15,10.1.14,10.1.13,10.1.12,10.1.10,10.1.9,10.1.8,10.1.7,10.1.6,10.1.5,10.1.4,10.1.3,10.1.2,10.1.1,10.1.0,10.1.0.beta enforces that actual 10.1.16 version is used which it's updated to support Ubuntu 24.04
- --build-release-candidate=BETA ensures BETA in the filename (I already support this seamlessly in zimbra-foss-builder when selected tag has 'beta' on its name.)

It would be nice if someone from Synacor would shed some light on this.

[umashankar.avagadda]

Build Ubuntu 24.04 Beta

Code: Select all

git clone --depth 1 --branch 10.1.16 git@github.com:Zimbra/zm-build.git
cd zm-build
ENV_CACHE_CLEAR_FLAG=true ./build.pl --ant-options -DskipTests=true --git-default-tag=10.1.16,10.1.15,10.1.14,10.1.13,10.1.12,10.1.11,10.1.10,10.1.9,10.1.8,10.1.7,10.1.6,10.1.5,10.1.4,10.1.3,10.1.2,10.1.1,10.1.0 --build-release-no=10.1.0 --build-type=FOSS --build-release=LIBERTY --build-release-candidate=BETA --build-no 4848 --build-thirdparty-server=files.zimbra.com --no-interactive

[adrian.gibanel.btactic]

Build Ubuntu 24.04 Beta

Code: Select all

git clone --depth 1 --branch 10.1.16 git@github.com:Zimbra/zm-build.git
cd zm-build
ENV_CACHE_CLEAR_FLAG=true ./build.pl --ant-options -DskipTests=true --git-default-tag=10.1.16,10.1.15,10.1.14,10.1.13,10.1.12,10.1.11,10.1.10,10.1.9,10.1.8,10.1.7,10.1.6,10.1.5,10.1.4,10.1.3,10.1.2,10.1.1,10.1.0 --build-release-no=10.1.0 --build-type=FOSS --build-release=LIBERTY --build-release-candidate=BETA --build-no 4848 --build-thirdparty-server=files.zimbra.com --no-interactive

Thank you @umashankar.avagadda !

BTW... Could you please take care of: CVE-2025-68645 fix missing !!! from ZCS FOSS 10.0.18. in a similar way to what you did with ZCS FOSS 10.1.8?

Thank you.

[umashankar.avagadda]

Build Ubuntu 24.04 Beta

Code: Select all

git clone --depth 1 --branch 10.1.16 git@github.com:Zimbra/zm-build.git
cd zm-build
ENV_CACHE_CLEAR_FLAG=true ./build.pl --ant-options -DskipTests=true --git-default-tag=10.1.16,10.1.15,10.1.14,10.1.13,10.1.12,10.1.11,10.1.10,10.1.9,10.1.8,10.1.7,10.1.6,10.1.5,10.1.4,10.1.3,10.1.2,10.1.1,10.1.0 --build-release-no=10.1.0 --build-type=FOSS --build-release=LIBERTY --build-release-candidate=BETA --build-no 4848 --build-thirdparty-server=files.zimbra.com --no-interactive

Thank you @umashankar.avagadda !

BTW... Could you please take care of: CVE-2025-68645 fix missing !!! from ZCS FOSS 10.0.18. in a similar way to what you did with ZCS FOSS 10.1.8?

Thank you.

Done.

[jzzr]

Hello,

Patch installed on Redhat 8, multi-server. Tests performed with classic webmail, mailbox sharing, IMAP, CalDAV, CardDav, ActiveSync.
No issues to report.

As usual, no information on the criticality level of security fixes to assess the urgency of the patch.

Regards

[BradC]

I did a few test upgrades from 10.1.15 on Ubuntu 20.04 LTS to 10.1.16 on Ubuntu 24.04 LTS. A few glitches in the upgrade, but I'm sure they'll iron that out in the wash. Once it's installed and running it seems ok.

[Lostaff]

Hello,

Zimbra NE Patch 10.1.16 (from 10.1.14) installed on Ubuntu 22.04.5 LTS multi-server.
Until now no issues to report.

Regards

[adrian.gibanel.btactic]

As usual, no information on the criticality level of security fixes to assess the urgency of the patch.

They seemed to start in 10.1.14 release but unfortunately that was only once.

In any case what I wanted to add here is that the email announcement for 10.1.16 has on it:


Patch Security Severity: High
Deployment Risk: High

.

Whether they have reused an older sent email (as it has happened other times) and this is a leftover it's open to speculation.

[Klug]

Maybe the deployment risk is linked to the new backup system?