Revert a patch upgrade

To downgrade a patch that you have installed on your TeamForge site, get the rpm file containing the previous patch and use the yum package manager to apply it.

  1. Get the rpm file for the patch you want. You may have saved it locally. If not, your CollabNet representative can help.
    The patch installer file is named TeamForge-installer-<major-release>.<minor-release>. <revision>.<patch-level>-<build-number>.<architecture>.rpm.

    For example, the patch 2 installer for TeamForge 5.4 on all platforms might be named TeamForge-installer-5.4.0.2-181.noarch.rpm.

  2. Stop CollabNet TeamForge.
    Note: If your site is running on multiple machines, stop all the machines.
    • /etc/init.d/collabnet stop all
  3. Unpack the patch installer.
    • rpm -ivh <patch installer file>
    For example:
    • rpm -ivh TeamForge-installer-5.4.0.1-181.noarch.rpm
    The rpm package deposits the patch installer in the appropriate directory under your main TeamForge install directory.
  4. Change to the install directory for the patch you want to revert to. For example:
    • cd /opt/collabnet/teamforge-installer/5.4.0.1
  5. Run the patch installer.
    • yum install TeamForge-installer-<package-number> -y
    For example:
    • yum install TeamForge-installer-<5.4.0.1> -y
  6. Update your Apache configuration, keeping the existing settings around in case you need to roll back any changes.
    1. Back up the existing Apache configuration file.
      • On Red Hat 5.4:
        • cd /etc/httpd/conf
        • cp httpd.conf httpd.conf.backup
      • On SuSE 11.x:
        • cd /etc/apache2
        • mv httpd.conf httpd.conf_old
        • cp httpd.conf.cn_new httpd.conf
    2. Review the new httpd.conf.cn_new or apache2 file that was created by the install process. This is an Apache web server configuration file that combines any existing web server configuration with directives specific to CollabNet TeamForge.
    3. When you are satisfied that the new configuration file meets all your networking requirements, rename it so it becomes the active version.
      • On Red Hat 5.4: mv httpd.conf.cn_new httpd.conf
      • On SuSE 11.x:
        • cd /etc/sysconfig/
        • mv apache2 apache2_old
        • cp apache2.cn_new apache2
  7. Recreate the runtime environment.
    • ./install.sh -V -r -d <SITE_DIR>
  8. Start CollabNet TeamForge.
    • On Red Hat or CentOS:
      • /etc/init.d/httpd start (On CentOS, you may need to start Apache manually: /sbin/chkconfig --level 2345 httpd on)
      • /etc/init.d/postgresql start
      • /etc/init.d/collabnet start
    • On SuSE:
      • /etc/init.d/apache2 start
      • /etc/init.d/postgresql start
      • /etc/init.d/collabnet start
  9. Verify that the patch was reverted.
    1. Log onto the site as a site administrator.
    2. On the Admin tab, click System Tools.
    3. Click Build Information and observe which patches are present.
Note: If a TeamForge 5.4 patch includes a Subversion 1.6.x upgrade, that upgrade is not reverted when you revert the patch. This is because all versions of Subversion 1.6.x are compatible.