Sophie

Sophie

distrib > Mageia > 7 > i586 > by-pkgid > 4e237fd705495e1e21ef20696443e053 > files > 999

bugzilla-5.0.4-3.mga7.noarch.rpm


<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml">
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <title>3.11. Upgrading &#8212; Bugzilla 5.0.4 documentation</title>
    <link rel="stylesheet" href="../_static/bugzilla.css" type="text/css" />
    <link rel="stylesheet" href="../_static/pygments.css" type="text/css" />
    <script type="text/javascript">
      var DOCUMENTATION_OPTIONS = {
        URL_ROOT:    '../',
        VERSION:     '5.0.4',
        COLLAPSE_INDEX: false,
        FILE_SUFFIX: '.html',
        HAS_SOURCE:  true,
        SOURCELINK_SUFFIX: '.txt'
      };
    </script>
    <script type="text/javascript" src="../_static/jquery.js"></script>
    <script type="text/javascript" src="../_static/underscore.js"></script>
    <script type="text/javascript" src="../_static/doctools.js"></script>
    <link rel="shortcut icon" href="../_static/favicon.ico"/>
    <link rel="search" title="Search" href="../search.html" />
    <link rel="next" title="3.11.1. Upgrading with Git" href="upgrading-with-git.html" />
    <link rel="prev" title="3.10. Moving Bugzilla Between Machines" href="moving.html" /> 
  </head>
  <body>
    <div class="related" role="navigation" aria-label="related navigation">
      <h3>Navigation</h3>
      <ul>
        <li class="right" style="margin-right: 10px">
          <a href="upgrading-with-git.html" title="3.11.1. Upgrading with Git"
             accesskey="N">next</a></li>
        <li class="right" >
          <a href="moving.html" title="3.10. Moving Bugzilla Between Machines"
             accesskey="P">previous</a> |</li>
        <li class="nav-item nav-item-0"><a href="../index.html">Bugzilla 5.0.4 documentation</a> &#187;</li>
          <li class="nav-item nav-item-1"><a href="index.html" accesskey="U">3. Installation and Maintenance Guide</a> &#187;</li> 
      </ul>
    </div>  

    <div class="document">
      <div class="documentwrapper">
        <div class="bodywrapper">
          <div class="body" role="main">
            
  <div class="section" id="upgrading">
<span id="id1"></span><h1>3.11. Upgrading<a class="headerlink" href="#upgrading" title="Permalink to this headline">ΒΆ</a></h1>
<p>You can upgrade Bugzilla from any version to any later version in one go -
there is no need to pass through intermediate versions unless you are changing
the method by which you obtain the code along the way.</p>
<div class="admonition warning">
<p class="first admonition-title">Warning</p>
<p class="last">Upgrading is a one-way process. You cannot &quot;downgrade&quot; an
upgraded Bugzilla. If you wish to revert to the old Bugzilla
version for any reason, you will have to restore your system
from a backup. Those with critical data or large installations may wish
to test the upgrade on a development server first, using a copy of the
production data and configuration.</p>
</div>
<p>Bugzilla uses the Git version control system to store its code. A modern
Bugzilla installation consists of a checkout of a stable version of the code
from our Git repository. This makes upgrading much easier. If this is
already true of your installation, see <a class="reference internal" href="upgrading-with-git.html#upgrading-with-git"><span class="std std-ref">Upgrading with Git</span></a>.</p>
<p>Before Git, we used to use Bazaar and, before that, CVS. If your installation
of Bugzilla consists of a checkout from one of those two systems, you need to
upgrade in three steps:</p>
<ol class="arabic simple">
<li>Upgrade to the latest point release of your current Bugzilla version.</li>
<li>Move to Git while staying on exactly the same release.</li>
<li>Upgrade to the latest Bugzilla using the instructions for <a class="reference internal" href="upgrading-with-git.html#upgrading-with-git"><span class="std std-ref">Upgrading with Git</span></a>.</li>
</ol>
<p>See <a class="reference internal" href="migrating-from-bzr.html#migrating-from-bazaar"><span class="std std-ref">Migrating from Bazaar</span></a> or <a class="reference internal" href="migrating-from-cvs.html#migrating-from-cvs"><span class="std std-ref">Migrating from CVS</span></a> as appropriate.</p>
<p>Some Bugzillas were installed simply by downloading a copy of the code as
an archive file (&quot;tarball&quot;). However, recent tarballs have included source
code management system information, so you may be able to use the Git, Bzr
or CVS instructions.</p>
<p>If you aren't sure which of these categories you fall into, to find out which
version control system your copy of Bugzilla recognizes, look for the
following subdirectories in your root Bugzilla directory:</p>
<ul class="simple">
<li><code class="file docutils literal"><span class="pre">.git</span></code>: you installed using Git - follow <a class="reference internal" href="upgrading-with-git.html#upgrading-with-git"><span class="std std-ref">Upgrading with Git</span></a>.</li>
<li><code class="file docutils literal"><span class="pre">.bzr</span></code>: you installed using Bazaar - follow <a class="reference internal" href="migrating-from-bzr.html#migrating-from-bazaar"><span class="std std-ref">Migrating from Bazaar</span></a>.</li>
<li><code class="file docutils literal"><span class="pre">CVS</span></code>: you installed using CVS - follow <a class="reference internal" href="migrating-from-cvs.html#migrating-from-cvs"><span class="std std-ref">Migrating from CVS</span></a>.</li>
<li>None of the above: you installed using an old tarball - follow
<a class="reference internal" href="migrating-from-a-tarball.html#migrating-from-a-tarball"><span class="std std-ref">Migrating from a Tarball</span></a>.</li>
</ul>
<p>It is also possible, particularly if your server machine does not have and
cannot be configured to have access to the public internet, to upgrade using
a tarball. See <a class="reference internal" href="upgrading-with-a-tarball.html#upgrading-with-a-tarball"><span class="std std-ref">Upgrading with a Tarball</span></a>.</p>
<p>Whichever path you use, you may need help with
<a class="reference internal" href="upgrading-customizations.html#upgrading-customizations"><span class="std std-ref">Upgrading a Customized or Extended Bugzilla</span></a>.</p>
<div class="toctree-wrapper compound">
<ul>
<li class="toctree-l1"><a class="reference internal" href="upgrading-with-git.html">3.11.1. Upgrading with Git</a></li>
<li class="toctree-l1"><a class="reference internal" href="migrating-from-bzr.html">3.11.2. Migrating from Bazaar</a></li>
<li class="toctree-l1"><a class="reference internal" href="migrating-from-cvs.html">3.11.3. Migrating from CVS</a></li>
<li class="toctree-l1"><a class="reference internal" href="migrating-from-a-tarball.html">3.11.4. Migrating from a Tarball</a></li>
<li class="toctree-l1"><a class="reference internal" href="upgrading-with-a-tarball.html">3.11.5. Upgrading with a Tarball</a></li>
<li class="toctree-l1"><a class="reference internal" href="upgrading-customizations.html">3.11.6. Upgrading a Customized or Extended Bugzilla</a></li>
</ul>
</div>
<p>Bugzilla can automatically notify administrators when new releases are
available if the <span class="param">upgrade_notification</span> parameter is set.
Administrators will see these notifications when they access the Bugzilla home
page. Bugzilla will check once per day for new releases. If you are behind a
proxy, you may have to set the <span class="param">proxy_url</span> parameter accordingly. If
the proxy requires authentication, use the
<span class="paramval">http://user:pass&#64;proxy_url/</span> syntax.</p>
<hr class="docutils" />
<p>This documentation undoubtedly has bugs; if you find some, please file
them <a class="reference external" href="https://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&amp;component=Documentation">here</a>.</p>
</div>


          </div>
        </div>
      </div>
      <div class="sphinxsidebar" role="navigation" aria-label="main navigation">
        <div class="sphinxsidebarwrapper">
            <p class="logo"><a href="../index.html">
              <img class="logo" src="../_static/bugzilla.png" alt="Logo"/>
            </a></p>
  <h4>Previous topic</h4>
  <p class="topless"><a href="moving.html"
                        title="previous chapter">3.10. Moving Bugzilla Between Machines</a></p>
  <h4>Next topic</h4>
  <p class="topless"><a href="upgrading-with-git.html"
                        title="next chapter">3.11.1. Upgrading with Git</a></p>
<div id="searchbox" style="display: none" role="search">
  <h3>Quick search</h3>
    <form class="search" action="../search.html" method="get">
      <div><input type="text" name="q" /></div>
      <div><input type="submit" value="Go" /></div>
      <input type="hidden" name="check_keywords" value="yes" />
      <input type="hidden" name="area" value="default" />
    </form>
</div>
<script type="text/javascript">$('#searchbox').show(0);</script>
        </div>
      </div>
      <div class="clearer"></div>
    </div>
    <div class="related" role="navigation" aria-label="related navigation">
      <h3>Navigation</h3>
      <ul>
        <li class="right" style="margin-right: 10px">
          <a href="upgrading-with-git.html" title="3.11.1. Upgrading with Git"
             >next</a></li>
        <li class="right" >
          <a href="moving.html" title="3.10. Moving Bugzilla Between Machines"
             >previous</a> |</li>
        <li class="nav-item nav-item-0"><a href="../index.html">Bugzilla 5.0.4 documentation</a> &#187;</li>
          <li class="nav-item nav-item-1"><a href="index.html" >3. Installation and Maintenance Guide</a> &#187;</li> 
      </ul>
    </div>
    <div class="footer" role="contentinfo">
      Created using <a href="http://sphinx-doc.org/">Sphinx</a> 1.6.6.
    </div>
  </body>
</html>