From f5de3aebd09b261a65e913c94db557dc565a2745 Mon Sep 17 00:00:00 2001 From: Andrew Ruthven Date: Wed, 21 May 2025 20:29:22 +1200 Subject: Debianize UPGRADING-5.0 Forwarded: not-needed Patch-Name: debianize_UPGRADING-5.0.diff --- docs/UPGRADING-5.0 | 44 +++++++++++++++++++++----------------------- 1 file changed, 21 insertions(+), 23 deletions(-) diff --git a/docs/UPGRADING-5.0 b/docs/UPGRADING-5.0 index a97eb7b3..041bfa1d 100644 --- a/docs/UPGRADING-5.0 +++ b/docs/UPGRADING-5.0 @@ -12,23 +12,26 @@ extension writers, including deprecated code. =head2 Upgrading Recommendations -RT now defaults to a database name of rt5 and an installation root of -/opt/rt5. +RT now defaults to a database name of rt5. If you are upgrading, you will likely want to specify that your database is still named rt4 or even rt3. Alternatively, you could import a backup of your database as rt5 to conform to the new default, although this isn't required. -Upgrading to RT 5 over an existing RT 4 installation (/opt/rt4) is not -recommended and will almost certainly cause issues. Instead, do a fresh -install into /opt/rt5 (or your custom location) for the code portion of the -upgrade. Then import your existing database and run the database upgrade -steps using make upgrade-database. +Upgrading to RT 5 over an existing RT 4 installation is not recommended and +will almost certainly cause issues. In Debian installing RT 5 will install to +new locations. -We recommend this approach because of the large number of changes to the code -base for this major release. We moved some things to new locations and old -files are not removed as part of the upgrade process. These old files will -still be detected by RT in some cases and will cause issues. +If you aren't using dbconfig to manage your database, refer to +/usr/share/doc/request-tracker5/NEWS.Debian.gz for details on how to upgrade +your database. You may want to copy it to a new database first. + +We take the approach of installing to new locations to allow running RT 4 and +RT 5 side-by-side on Debian and also because of the large number of changes to +the code base for this major release. We moved some things to new locations and +old files are not removed as part of the upgrade process. If RT 5 was installed +over the top of RT 4 then these old files will still be detected by RT in some +cases and will cause issues. Installing a fresh code base will also allow you to evaluate your local modifications and configuration changes as you migrate to 5.0. If you have @@ -123,11 +126,7 @@ the previous behavior. =item * -RT can now run with GnuPG 2.2. On install or upgrade, it requires the updated -version of L. C will test for the correct version. -RT should also still run with GnuPG 1.4.x. It is not supported for GnuPG versions -2.0 or 2.1. On some Linux systems, you may need to add a new repo to get an -updated GnuPG package with some version of 2.2. +RT can now run with GnuPG 2.2 or 2.4. =item * @@ -175,7 +174,7 @@ are described below. =item RT::Extension::ConfigInDatabase If you previously used L -as an extension, run the F utility +as an extension, run the F utility after completing all the other upgrade steps from the F. This will migrate your existing configuration to the new core RT tables. @@ -226,7 +225,7 @@ options added for AssetSQL and the new asset query builder. =item RT::Authen::Token If you previously used L -as an extension, run the F utility +as an extension, run the F utility after completing all the other upgrade steps from the F. This will migrate your existing tokens to the new core RT tables. @@ -388,7 +387,7 @@ If you use groups in ticket roles, it's likely your CachedGroupMembers table has a large number of now unnecessary records and these can hurt performance. To delete these extra records run the following script: - /opt/rt5/etc/upgrade/shrink-cgm-table + /usr/share/request-tracker5/etc/upgrade/shrink-cgm-table Depending on how many records your system has, this may take a while to run. After you run this, you may have significantly reduced the number of records @@ -498,8 +497,7 @@ RT 4.4.6 and earlier use the Perl GraphViz module for interfacing with the graph library for generating ticket link graphs. That module has been deprecated so we have replaced it with the GraphViz2 module. -Systems using C<--enable-graphviz> will be prompted to install the Perl -GraphViz2 module when upgrading. +This is installed on Debian when installing the request-tracker5 package. =item * New C<$EmailDashboardInlineCSS> option for dashboard email @@ -511,8 +509,8 @@ CSS. We have found this reduces the size of the dashboard emails significantly and can help with rendering in some email clients. To use this new feature, you must install the optional Perl module -L, version 4018 or later, then enable the feature in -your RT configuration. +L, available on Debian as the libcss-inliner-perl package, then +enable the feature in your RT configuration. =item * ModifyLoginRedirect callback in Logout.html moved