ddkilzer@apple.com | 8040bb0 | 2017-03-21 16:27:49 +0000 | [diff] [blame^] | 1 | .. _upgrading-with-a-tarball: |
| 2 | |
| 3 | Upgrading with a Tarball |
| 4 | ######################## |
| 5 | |
| 6 | If you are unable (or unwilling) to use Git, another option is to obtain a |
| 7 | tarball of the latest version from our website and upgrade your Bugzilla |
| 8 | installation using that. |
| 9 | |
| 10 | Without a source code management system to help you, the process may be |
| 11 | trickier. |
| 12 | |
| 13 | .. include:: upgrading-with-1.inc.rst |
| 14 | |
| 15 | As you are using a tarball and not an SCM, it's not at all easy to see if |
| 16 | you've made local code customizations. You may have to use institutional |
| 17 | knowledge, or download a fresh copy of your *current* version of Bugzilla |
| 18 | and compare the two directories. If you find that you have, you'll need |
| 19 | to turn them into a patch file, perhaps by diffing the two directories, |
| 20 | and then reapply that patch file later. If you are customizing Bugzilla |
| 21 | locally, please consider |
| 22 | :ref:`rebasing your install on top of git <migrating-from-a-tarball>`. |
| 23 | |
| 24 | .. _upgrade-files-tarball: |
| 25 | |
| 26 | Getting The New Bugzilla |
| 27 | ======================== |
| 28 | |
| 29 | Download a copy of the latest version of Bugzilla from the |
| 30 | `Download Page <http://www.bugzilla.org/download/>`_ into a separate |
| 31 | directory (which we will call :file:`bugzilla-new`) alongside your existing |
| 32 | Bugzilla installation (which we will assume is in a directory called |
| 33 | :file:`bugzilla`). |
| 34 | |
| 35 | Copy Across Data and Modules |
| 36 | ============================ |
| 37 | |
| 38 | Copy the contents of the following directories from your current installation |
| 39 | of Bugzilla into the corresponding directory in :file:`bugzilla-new/`: |
| 40 | |
| 41 | .. code-block:: none |
| 42 | |
| 43 | lib/ |
| 44 | data/ |
| 45 | template/en/custom (may or may not exist) |
| 46 | |
| 47 | You also need to copy any extensions you have written or installed, which are |
| 48 | in the :file:`extensions/` directory. Bugzilla ships with some extensions, |
| 49 | so again if you want to know if any of the installed extensions are yours, |
| 50 | you may have to compare with a clean copy of your current version. You can |
| 51 | disregard any which have a :file:`disabled` file - those are not enabled. |
| 52 | |
| 53 | Lastly, copy the following file from your current installation of Bugzilla |
| 54 | into the corresponding place in :file:`bugzilla-new/`: |
| 55 | |
| 56 | .. code-block:: none |
| 57 | |
| 58 | localconfig |
| 59 | |
| 60 | This file contains your database password and access details. |
| 61 | |
| 62 | Swap The New Version In |
| 63 | ======================= |
| 64 | |
| 65 | Now we swap the directories over. From the directory containing the |
| 66 | :file:`bugzilla` and :file:`bugzilla-new` directories, run: |
| 67 | |
| 68 | :command:`mv bugzilla bugzilla-old` |
| 69 | |
| 70 | :command:`mv bugzilla-new bugzilla` |
| 71 | |
| 72 | :command:`cd bugzilla` |
| 73 | |
| 74 | .. include:: upgrading-with-2.inc.rst |