| Summary | No patch from 3.2-rc4 to 3.2 FINAL |
| Queue | Horde Base |
| Queue Version | 3.2 |
| Type | Bug |
| State | Not A Bug |
| Priority | 1. Low |
| Owners | |
| Requester | nick.maynard (at) alumni (dot) doc (dot) ic (dot) ac (dot) uk |
| Created | 07/31/2008 (6186 days ago) |
| Due | |
| Updated | 07/31/2008 (6186 days ago) |
| Assigned | |
| Resolved | 07/31/2008 (6186 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
the steps necessary to convert existing data, and you always should
check your configuration files for new settings. So you just need to
uncompress the new version, compare your configuration files to the
default ones and update them, and test it.
The reason for not providing a patch is that there are a lot of new
binary files (images and translations) between 3.1.x and 3.2, and
patches don't cover those - making the patch a worse upgrade than a
fresh tarball since you need the tarball afterall.
seems reasonable from a administrator's point of view to assume that
the intention of the Horde developers is that there is an upgrade
route via patches.
If this is not the case, it should be noted that there is no
explanation of what to do in the UPGRADE document either.
As a administrator of 3.1.x, now there is a 3.2 release I desire to
upgrade to it. I have not been able to find complete documentation on
any method to do so.
This bug is basically the following: there is no documented upgrade
route. If possible, it would be highly advantageous to provide
administrators with this. Otherwise, a multi-hour reinstall will be
required.
State ⇒ Not A Bug
Priority ⇒ 1. Low
Priority ⇒ 3. High
Type ⇒ Bug
Summary ⇒ No upgrade route from 3.2-rc4 to 3.2 FINAL
Queue ⇒ Horde Base
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
My Horde is currently at 3.1.4. I can upgrade (via patches) to 3.1.8
or 3.2-rc4, but not to 3.2 Final or beyond.
This effectively means there is no way to upgrade Horde 3.1.x to 3.2.x
without performing a fresh install.