Skip to content

Releases: ianw1974/zimbra-build-scripts

v1.2.1

11 Oct 08:36
3db2430
Compare
Choose a tag to compare

Added support for building Zimbra 10.1.x on EL9 distros.

v1.2.0

01 Oct 09:23
1f8d711
Compare
Choose a tag to compare
  • Builds for 10.1.0.
  • Ubuntu 22.04 now supported for 10.1.0 and higher (do not attempt to build Zimbra 9.0.0)

v1.1.8

07 May 15:29
8ac9c4d
Compare
Choose a tag to compare

Bump version and disable patch for disabling libphp.so as no longer required. This is because Zimbra have commited the missing components for PHP to their branches as previously they had the libphp.so module loading in the config, when the module didn't exist.

v1.1.6

02 Apr 16:40
f34de6f
Compare
Choose a tag to compare

Ubuntu 18.04 Deprecated, plus some additional fixes for building Zimbra.

v1.1.5

25 Jan 10:25
5672c23
Compare
Choose a tag to compare

This release fixes Zimbra 9.0.0 builds and the nginx.conf.main.template file with the appropriate uid/gid that is required.

v1.1.4

31 Oct 22:39
457a336
Compare
Choose a tag to compare

New in this release:

  • config.build.10 updated release number from 10.0.0 to 10.0.5
  • added automatic update of build number in config.build - using the current yearly quarter and last two digits of current year, eg: 0423.

v1.1.3

12 Aug 16:29
e1575f8
Compare
Choose a tag to compare

Fixes:

  • Oracle Linux failed to build due to missing dependency which pulled in OpenJDK-11 instead of OpenJDK 1.8. Dependency added to stop this from happening.
  • Patch introduced to fix missing dependency package net-tools as the Zimbra Installer requires it as it still uses the legacy tools of ifconfig and netstat. This fix saves people having to remember to install this dependency first, before running the Zimbra installer.
  • New function --cleanup to cleanup the system after the build has been finished. This originally was forced at the beginning of the build process, but in some circumstances, like today when Github connectivity was being temperamental it meant having to clone everything from zero again. By only cleaning the .staging directory at the beginning of the build process, we at least still have the previously cloned repositories locally, and can re-run the script to continue the build process from more or less the point when the connectivity issues stopped the build process from cloning/downloading from GitHub. The new function means we have to now manually run --cleanup to completely cleanup the system after an initial build and again prior to wanting to build a new Zimbra build in the future.

v1.1.2

31 Jul 11:16
e000a20
Compare
Choose a tag to compare

Addresses a few issues with building Zimbra 9 from develop branch:

  • Fixes jetty.xml and jetty.xml.in so that it doesn't include onlyoffice configuration - this is because onlyoffice is available for Zimbra 10
  • Fixes repositories so that Zimbra 9 repositories are used instead of Zimbra 10.

v1.1.1

11 Jul 19:39
cac9e1d
Compare
Choose a tag to compare

Version bump:

  • Removed config.build from repository.
  • Script requires copying config.build.9 or config.build.10 to config.build
  • Help updated to show step copying build file mentioned above
  • Build function will exit if config.build doesn't exist

The .gitignore file will now work properly since config.build no longer exists in the repository. This means it won't cause any problems for future pulls, or show that there is an uncommitted change.

v1.1.0

06 Nov 15:01
f2df537
Compare
Choose a tag to compare

Zimbra have fixed their repositories, so it's now possible to install the built Ubuntu 20.04 packages.

This release re-adds build support for Ubuntu 20.04 (previously packages could be built, but due to lack of packages in Zimbra repositories it couldn't be installed - see #10).