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