Account confirmers, Anti-spam team, Confirmed users, Bureaucrats and Sysops emeriti
4,925
edits
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{draft}} | {{draft}} | ||
This page applies to people whose installation of Bugzilla is a checkout from CVS, and who wish to upgrade from 4.0 or earlier to Bugzilla 4.2 or newer. Bugzilla 4.2 and later are not available in our CVS repository, only our Bazaar (bzr) repository. Therefore, you will need to change your installation over to pull from bzr before upgrading to 4.2. | This page applies to people whose installation of Bugzilla is a checkout from CVS, and who wish to upgrade from 4.0 or earlier to Bugzilla 4.2 or newer. Bugzilla 4.2 and later are not available in our CVS repository, only our Bazaar (bzr) repository. Therefore, you will need to change your installation over to pull from bzr before upgrading to 4.2. | ||
| Line 10: | Line 7: | ||
The switching procedure is as follows: | The switching procedure is as follows: | ||
== | == Update Your Bugzilla To The Latest Point Release == | ||
The aim when switching is to switch between two identical versions of Bugzilla, to minimise the risk of conflict or problems. (The upgrade to 4.2 can then happen as a separate step.) For simplicity, therefore, you should make sure you are on the latest point release for your version, by updating Bugzilla (from CVS). The instructions on doing that are [http://www.bugzilla.org/download/#cvs on the Bugzilla website]. You should use the update command of the following form: | The aim when switching is to switch between two identical versions of Bugzilla, to minimise the risk of conflict or problems. (The upgrade to 4.2 can then happen as a separate step.) For simplicity, therefore, you should make sure you are on the latest point release for your version, by updating Bugzilla (from CVS). The instructions on doing that are [http://www.bugzilla.org/download/#cvs on the Bugzilla website]. You should use the update command of the following form: | ||
| Line 20: | Line 17: | ||
You should then use your Bugzilla for a day or two to make sure it's all still working fine. | You should then use your Bugzilla for a day or two to make sure it's all still working fine. | ||
== | == Save Any Local Customizations == | ||
If you have customizations to your Bugzilla, and you made them by changing the Bugzilla code itself (rather than using the Extension system), you will have to keep a copy of those changes. If you made no changes, or all changes are contained into extensions, jump to step 3. If you aren't sure, do the below, and see if patch.diff has non-zero size. | If you have customizations to your Bugzilla, and you made them by changing the Bugzilla code itself (rather than using the Extension system), you will have to keep a copy of those changes. If you made no changes, or all changes are contained into extensions, jump to step 3. If you aren't sure, do the below, and see if patch.diff has non-zero size. | ||
| Line 30: | Line 27: | ||
The file patch.diff will contain all the changes you made to your current installation. | The file patch.diff will contain all the changes you made to your current installation. | ||
== | == Download Code from bzr == | ||
Download a copy of your current version of Bugzilla from the bzr repository into a separate directory. You will need a copy of the bzr program. All Linux installations have it; have a look in your package manager. For instance, Fedora 16 has bzr-2.4.2-1.fc16.i686.rpm. On Windows, you can download it from http://bazaar.canonical.com; The standalone application is recommended, which has a name like bzr-2.4.2-1-setup.exe. Once bzr is installed, run this command to download Bugzilla : | Download a copy of your current version of Bugzilla from the bzr repository into a separate directory. You will need a copy of the bzr program. All Linux installations have it; have a look in your package manager. For instance, Fedora 16 has bzr-2.4.2-1.fc16.i686.rpm. On Windows, you can download it from http://bazaar.canonical.com; The standalone application is recommended, which has a name like bzr-2.4.2-1-setup.exe. Once bzr is installed, run this command to download Bugzilla : | ||
| Line 38: | Line 35: | ||
Replace X.Y with the version number of your current Bugzilla, e.g. 3.6. "bugzilla-bzr" is the name of the local directory into which the source code will be downloaded. | Replace X.Y with the version number of your current Bugzilla, e.g. 3.6. "bugzilla-bzr" is the name of the local directory into which the source code will be downloaded. | ||
== | == Shut Down Bugzilla == | ||
At this point, you should shut down Bugzilla to stop anyone changing the data you are about to copy. Go into the administrative interface and put an appropriate message into the "shutdownhtml" parameter. | At this point, you should shut down Bugzilla to stop anyone changing the data you are about to copy. Go into the administrative interface and put an appropriate message into the "shutdownhtml" parameter. | ||
== | == Copy Across Data and Modules == | ||
Copy the contents of the following directories from your current installation of Bugzilla into the corresponding directory in bugzilla-bzr/: | Copy the contents of the following directories from your current installation of Bugzilla into the corresponding directory in bugzilla-bzr/: | ||
| Line 56: | Line 53: | ||
Because your two versions of Bugzilla are the same, this should all work fine. | Because your two versions of Bugzilla are the same, this should all work fine. | ||
== | == Reapply Local Customizations == | ||
If you recorded any changes to your current Bugzilla installation in step 2, then you have to apply patch.diff you created earlier to your new installation. If you made no changes, you can jump to the next step. If you are on Windows and you don’t have patch.exe, you can download it from http://gnuwin32.sourceforge.net/packages/patch.htm. Once downloaded, you must copy patch.exe into the Windows directory. | If you recorded any changes to your current Bugzilla installation in step 2, then you have to apply patch.diff you created earlier to your new installation. If you made no changes, you can jump to the next step. If you are on Windows and you don’t have patch.exe, you can download it from http://gnuwin32.sourceforge.net/packages/patch.htm. Once downloaded, you must copy patch.exe into the Windows directory. | ||
| Line 66: | Line 63: | ||
The patch should apply cleanly because you have exactly the same version of Bugzilla in both directories. | The patch should apply cleanly because you have exactly the same version of Bugzilla in both directories. | ||
== | == Swap The New Version In == | ||
Rename your old Bugzilla directory to bugzilla-cvs, and rename your bugzilla-bzr directory to whatever name your Bugzilla directory had. Run checksetup.pl to confirm that all is well. | Rename your old Bugzilla directory to bugzilla-cvs, and rename your bugzilla-bzr directory to whatever name your Bugzilla directory had. Run checksetup.pl to confirm that all is well. | ||
| Line 75: | Line 72: | ||
./checksetup.pl | ./checksetup.pl | ||
== | == Re-enable Bugzilla == | ||
Go into the administrative interface and clear the contents of the "shutdownhtml" parameter. | Go into the administrative interface and clear the contents of the "shutdownhtml" parameter. | ||
== | == Upgrade Bugzilla == | ||
Use your Bugzilla for several days to check that the switch has had no detrimental effects. Then, follow the [Bugzilla:Bzr#Updating_to_a_Newer_Release|normal instructions] for upgrading a bzr install of Bugzilla to the latest version. | Use your Bugzilla for several days to check that the switch has had no detrimental effects. Then, follow the [Bugzilla:Bzr#Updating_to_a_Newer_Release|normal instructions] for upgrading a bzr install of Bugzilla to the latest version. | ||