I was successfully able to install Ian's 10.0.5 build, but have a question of how the Zimbra package repos for packages that aren't part of the distribution build will be treated going forward. In particular, I did a regular system update (dnf update) today, and was surprised to see the updated OpenJDK get pulled in, which is (nominally) part of 10.0.6 content.
When running a FOSS build, install.sh asks: "Use Zimbra's package repository?"
Answering Yes (on RHEL) adds repo specs:Answering "No" doesn't, and I assume the install will fail if you do not have a similar repo configured, which isn't provided by a third-party build. The third-party build includes 27 packages as part of its bundle, but my machine has 223 packages with "zimbra" in the name, the rest being fetched from the above Zimbra repos. These are almost all open source components (Postfix, Amavis, ClamAV, nginx, MariaDB, etc), but builds that Zimbra has pinned to known-good versions or patched (which are all forked on GitHub, but are not cloned and rebuilt as part of a zm-build afaict).
As part of FOSS participation, is Zimbra going to continue to make these repos and packages available, or are we also going to have to start rebuilding the entire constellation of support packages as well?
When running a FOSS build, install.sh asks: "Use Zimbra's package repository?"
Answering Yes (on RHEL) adds repo specs:
Code:
[zimbra]name=Zimbra RPM Repositorybaseurl=https://repo.zimbra.com/rpm/87/rhel8gpgcheck=1enabled=1[zimbra-1000-oss]name=Zimbra New RPM Repositorybaseurl=https://repo.zimbra.com/rpm/1000/rhel8gpgcheck=1enabled=1As part of FOSS participation, is Zimbra going to continue to make these repos and packages available, or are we also going to have to start rebuilding the entire constellation of support packages as well?
Statistics: Posted by jered — Wed Dec 20, 2023 8:33 pm