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
m (moved Bugzilla:CvsToBzr to Bugzilla:Moving From CVS To Bazaar: Better name) |
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 Bugzilla 4.0 or earlier to Bugzilla 4.2 or later. Bugzilla 4.2 and up are not available | This page applies to people whose installation of Bugzilla is a checkout from the CVS version control system, and who wish to upgrade from Bugzilla 4.0 or earlier to Bugzilla 4.2 or later. Bugzilla 4.2 and up are not available from our legacy CVS repository, only our Bazaar (bzr) repository. Therefore, you will need to change your installation over to pull code from bzr before upgrading beyond 4.0. | ||
You can tell if you need to follow these instructions by looking in your top-level Bugzilla directory. If there is a subdirectory called "CVS", then your installation is a checkout from CVS. | You can tell if you need to follow these instructions by looking in your top-level Bugzilla directory. If there is a subdirectory called "CVS", then your installation is a checkout from CVS. | ||
| Line 9: | Line 9: | ||
== Update Your Bugzilla To The Latest Point Release == | == 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 aim when switching is to switch between two identical versions of Bugzilla, to minimise the risk of conflict or problems. Any upgrade, e.g. to 4.2, can then happen as a separate step, using the improved merge algorithms in bzr rather than those in CVS. It is recommended that you switch while using the latest point release for your version. You can update to the latest point release using 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: | ||
cvs update -rBUGZILLA-X_Y-STABLE -dP | cvs update -rBUGZILLA-X_Y-STABLE -dP | ||
where X.Y is your Bugzilla version number. Don't forget to run checksetup.pl afterwards. | where X.Y is your Bugzilla version number (e.g. 3.6). Don't forget to run checksetup.pl afterwards. | ||
You should then | You should then test your Bugzilla carefully, or just use it for a day or two, to make sure it's all still working fine. | ||
== Save Any Local Customizations == | == Save Any Local Customizations == | ||
| Line 25: | Line 25: | ||
cvs diff -puN > patch.diff | cvs diff -puN > patch.diff | ||
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. If it's empty, then you didn't make any local code customizations. | ||
== Download Code from bzr == | == 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; | 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; search your package manager for "bzr". On Windows, you can download it from [http://bazaar.canonical.com Canonical]; 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/X.Y bugzilla-bzr | bzr co bzr://bzr.mozilla.org/bugzilla/X.Y bugzilla-bzr | ||