Account confirmers, Anti-spam team, Confirmed users, Bureaucrats and Sysops emeriti
4,925
edits
Bugzilla:Moving From CVS To Bazaar: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
== Upgrading from CVS to bzr == | == Upgrading from CVS to bzr == | ||
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. | ||
You can tell if you are in this category by looking in your top-level Bugzilla directory. If there is a subdirectory called "CVS", then your installation is a checkout from CVS. | |||
The procedure is as follows: | The switching procedure is as follows: | ||
=== 1. Update Your Bugzilla To The Latest Point Release === | === 1. 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. Therefore, you need to update your Bugzilla, from CVS, to the latest minor release of your branch. 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: | |||
cvs update -rBUGZILLA-X_Y-STABLE -dP | |||
where X.Y is your Bugzilla version number. Don't forget to run checksetup.pl. | |||
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. | ||
| Line 19: | Line 21: | ||
=== 2. Save Any Local Customizations === | === 2. 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 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. | ||
To generate a patch with all the changes you made, go into your bugzilla/ directory and run this command: | To generate a patch with all the changes you made, go into your bugzilla/ directory and run this command: | ||
| Line 26: | Line 28: | ||
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. | ||
=== 3. Download Code from bzr === | === 3. Download Code from bzr === | ||
| Line 33: | Line 33: | ||
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 : | ||
bzr co bzr://bzr.mozilla.org/bugzilla/ | bzr co bzr://bzr.mozilla.org/bugzilla/X.Y bugzilla-bzr | ||
Replace | 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. | ||
=== 4. Shut Down Bugzilla === | === 4. Shut Down Bugzilla === | ||
| Line 57: | Line 57: | ||
=== 6. Reapply Local Customizations === | === 6. Reapply Local Customizations === | ||
If you recorded any changes to your current Bugzilla installation in step | 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. | ||
Copy patch.diff into the bugzilla-bzr directory and then do: | |||
patch -p0 < patch.diff | patch -p0 < patch.diff | ||
| Line 78: | Line 80: | ||
=== 8. Upgrade Bugzilla === | === 8. Upgrade Bugzilla === | ||
Use your Bugzilla for several days to check that the switch has had no detrimental effects. Then, follow the 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. | ||