Yes with one caveat. There is what is commonly called third party repository and Zimbra is currently providing these updates which arrive via the package mgmt for your distribution. Examples of what is in here are nginx, openssl, ldap, etc, etc. Then there is the stuff the community is building which is from Zimbra's public github which installs via the install.sh command. That is for both new installs and updates. Ian's scripts and builds are an example of this. I don't believe we have anyone building all the 3rd party yet. I believe there is one FOSS build that attempts to use repositories for their updates but I think it was ubuntu based and I have not tried it as we are RHEL 8 here. I also only run the network version in production so am participating in the FOSS to learn how it all works. I tried to list various projects here: https://wiki.zimbra.com/wiki/JDunphy-Co ... d_ProjectsI had a question for those running the FOSS builds, when it comes time to patch them, do we have to run through the upgrade/install process each time, or will it pull patches from the zimbra repos? I have yet to test that process and just want to make sure I have a path to maintain a patched version.
An addition point in case it isn't understood - There are FOSS builds based on tags (Zimbra will tag parts of the system in github and their build.pl script is smart enough to use the newest tag up to the tag specified) and what is referred to as the development branch. Ian's are the latest from development that is shared on github. Adrian's Maldua builds are based on tag builds. Zimbra has spent a lot of effort recently reworking documentation and the build scripts so that building by tags is possible and from my experimentation seems to work every time now. Unfortunately, that brings us to another caveat with mixing FOSS builds and tag build during updates. Sometimes if you are using the latest FOSS development version, the schema can be newer or contain new components that will be in the next release of Zimbra. If you attempted to upgrade your FOSS development build to a FOSS tag build there could be a potential for problems. FOSS Development builds are probably better thought of as date based builds and the tag builds are based on a closer approximation to the NETWORK versioning... 10.0.8, 8.8.15 P40, etc.
Having said that, it isn't clear to me that the NETWORK builds and the FOSS tag builds have every patch even if they claim the same version number... I would think the development version might have more patches but then you are getting a lot of other stuff that is incoming as they say. We have a few questions in these boards about this but I don't believe it has been answered completely what is going on with how they are managing their private repositories used in the NETWORK builds and the public repositories for builds that the FOSS community is using. If anyone has more information, please share.
Disclaimer: I do not run FOSS but that is my understanding of how it fits together.
HTH,
Jim
Statistics: Posted by JDunphy — Fri Jun 14, 2024 1:52 pm