search

maldua / zimbra-foss-builder

Zimbra FOSS Builder
GNU General Public License v3.0
13 stars 3 forks source link

zimbra-patch support? #14

Open akanellis opened 2 days ago

akanellis commented 2 days ago

Hello all,

Is there a proper way to build zimbra-patch zimbra-mta-patch etc packages like the ones Zimbra is building for updating using a repo? They are still building these packages like they did with v8 version but for the network edition only.

adriangibanelbtactic commented 2 days ago

zimbra-patch, zimbra-mta-patch are not needed for the latest versions.

You just need to install a new FOSS version and that's it.

In any case zimbra-patch , zimbra-mta-patch et al. it's an arkane way of updating Zimbra (probably the core NE packages) that they are still using. Not sure why they can't do exactly the same thing thanks to regular packages.

akanellis commented 2 days ago

If you need to maintain large amount of FOSS zimbra servers, those patch packages are amazing because if you have them in a repo, you can keep all up to date with just yum update which is automated. Now you need to ./install.sh on each server to push updates.

They still make those packages if you look at https://wiki.zimbra.com/wiki/Zimbra_Releases/10.0.11 down at the bottom they list the patch packages for the Network edition.

And they are basically the packages from the FOSS builds but they also run the whole upgrade script which among others makes updates on the ldap scheme, make changes according to new features etc.

It would be amazing if there was a proper way to make those packages for easy mass updates.

adriangibanelbtactic commented 2 days ago

If you need to maintain large amount of FOSS zimbra servers, those patch packages are amazing because if you have them in a repo, you can keep all up to date with just yum update which is automated. Now you need to ./install.sh on each server to push updates.

I know.

They still make those packages if you look at https://wiki.zimbra.com/wiki/Zimbra_Releases/10.0.11 down at the bottom they list the patch packages for the Network edition.

That's right.

And they are basically the packages from the FOSS builds but they also run the whole upgrade script which among others makes updates on the ldap scheme, make changes according to new features etc.

Are you sure about them being packages from the FOSS builds?

And are you sure that they do not run an small upgrade script instead of the whole upgrade script (zmsetup) ?

It would be amazing if there was a proper way to make those packages for easy mass updates.

Yeah, well, the idea is to push the currently built packages for the tgz installer onto a repo of its own. I think it should be equivalent to what you describe (Just doing yum update or apt update && apt dist-upgrade but I'm not sure. You would have to do the beta-testing for it. This would be needed to do, probably, in a project of its own.

If you are quite interested in it please create a new issue regarding tgz installer packages repo so that we don't forget about it.

Regarding the packages that are not in the tgz installer but in the Synacor Zimbra repo we can also build them if we know how. Please check the stalled repo: https://github.com/maldua/zimbra-foss-packages-builder/tree/dev-v001 and this forum thread: Zimbra/packages repo - Documentation improvement request.

akanellis commented 2 days ago

Yeah, well, the idea is to push the currently built packages for the tgz installer onto a repo of its own. I think it should be equivalent to what you describe (Just doing yum update or apt update && apt dist-upgrade but I'm not sure. You would have to do the beta-testing for it. This would be needed to do, probably, in a project of its own.

I have already done that. Meaning I maintain a rhel8 and rhel7 repo for my own servers with all the packages from the .tgz. Doing yum update on test vm servers, only installed new software but did not run any upgrade scripts and also leaves zimbra crashed showing error 500 pages until you restart it. So zmcontrol -v shows the latest version, but the ldap scheme is not updated. If you run ./install.sh afterwards, you will see how it will still recognize it as a upgrade from the previous version and at some point performs ldap scheme upgrade. So this is not gonna work, thus why I was thinking of the *-patch packages.

I will experiment at some point creating those packages myself or at least create a dummy rpm package that only runs the upgrade script.