Packages (https://github.com/Zimbra/packages) are available for FOSS, so you need to use Zimbra's package repository, even if you are using FOSS.What you are looking for is: https://github.com/Zimbra/packages which let's you build the additional packages. You would, of course, need a way to convert those compiled binary packages onto a repo if you want to an experience similar to the original ZCS OSE 8.8.15.jered,When running a FOSS build, install.sh asks: "Use Zimbra's package repository?"
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?
Have you received any feedback on this detrimental matter?
I ran an upgrade from 8.8.15p45 FOSS to 10.0.6 FOSS using a build created with the help of @ianw1974 's helpful github page.
Hearing that FOSS was no longer going to receive patches via zimbra's repo and the server being offline at the time, I answered NO to 'Use Zimbra's package repository?'.
The upgrade completed successfully and all services ran as expected.
After reading your post I added back zimbra's repo and cert to find that
zimbra-ldap-components (1.0.26-1zimbra8.8b1.20.04 -> 3.0.2-1zimbra10.0b1.20.04)
zimbra-osl (1.0.10-1zimbra8.7b1.20.04 -> 3.0.0-1zimbra10.0b1.20.04)
zimbra-core-components (2.0.26-1zimbra8.8b1.20.04 -> 4.0.2-1zimbra10.0b1.20.04)
packages still needed to be updated.
Clearly FOSS will still require zimbra's repos to manually upgrade via personal builds.
I searched but couldn't find a recommended best practice for upgrading via personal builds or any mention of zimbra 10 FOSS lifecycle.
Statistics: Posted by umashankar.avagadda — Sat Feb 03, 2024 3:41 am