Changes between Version 1 and Version 2 of TracUpgrade

Timestamp:

2015-04-01T12:42:00Z (10 years ago)

Author:

trac

Comment:

--

TracUpgrade

@@ -1 @@
-= Upgrade Instructions =
+= Upgrade Instructions
 [[TracGuideToc]]
 [[PageOutline(2-4,,inline,unnumbered)]]
 
-== Instructions ==
+== Instructions
 
 Typically, there are seven steps involved in upgrading to a newer version of Trac:
@@ -9 +9 @@
 === 1. Bring your server off-line
 
-It is not a good idea to update a running server: the server processes may have parts of the current packages cached in memory, and updating the code will likely trigger [#ZipImportError internal errors]. 
-
-=== 2. Update the Trac Code === #UpdatetheTracCode
+It is not a good idea to update a running server: the server processes may have parts of the current packages cached in memory, and updating the code will likely trigger [#ZipImportError internal errors].
+
+Although a database backup will be implicitly created by default when upgrading the environment, it is always a good idea to perform a full backup of the environment using the [TracBackup hotcopy] command before beginning.
+
+=== 2. Update the Trac Code #UpdatetheTracCode
 
 Get the new version as described in TracInstall, or your operating system specific procedure.
@@ -17 +19 @@
 If you already have a 0.12 version of Trac installed via `easy_install`, it might be easiest to also use `easy_install` to upgrade your Trac installation:
 
-{{{
-# easy_install --upgrade Trac==1.0
+{{{#!sh
+easy_install --upgrade Trac==1.0
 }}}
 
@@ -31 +33 @@
 You may also want to remove the Trac `cgi-bin`, `htdocs`, `templates` and `wiki-default` directories that are commonly found in a directory called `share/trac`. The exact location depends on your platform. This cleanup is not mandatory, but makes it easier to troubleshoot issues later on, as your installation is uncluttered by code or templates from a previous release that is not used anymore. As usual, make a backup before actually removing things.
 
-=== 3. Upgrade the Trac Environment === #UpgradetheTracEnvironment
+=== 3. Upgrade the Trac Environment #UpgradetheTracEnvironment
 
 Environment upgrades are not necessary for minor version releases unless otherwise noted. 
 
 After restarting, Trac should show the instances which need a manual upgrade via the automated upgrade scripts to ease the pain. These scripts are run via [TracAdmin trac-admin]:
-{{{
+{{{#!sh
 trac-admin /path/to/projenv upgrade
 }}}
@@ -44 +46 @@
 Note that a backup of your database will be performed automatically prior to the upgrade. 
 This feature is relatively new for PostgreSQL or MySQL databases, so if it fails, you will have to backup the database manually. Then, to perform the actual upgrade, run:
-{{{
+{{{#!sh
 trac-admin /path/to/projenv upgrade --no-backup
 }}}
@@ -51 +53 @@
 
 By default, every [TracEnvironment Trac environment] includes a copy of the Trac documentation for the installed version. However, to keep the included documentation in sync with the installed version of Trac, use the following [TracAdmin trac-admin] command to upgrade the documentation:
-{{{
+{{{#!sh
 trac-admin /path/to/projenv wiki upgrade
 }}}
@@ -57 +59 @@
 Note that this procedure will leave your `WikiStart` page intact.
 
-=== 5. Refresh static resources ===
+=== 5. Refresh static resources
 
 If you have set up a web server to give out static resources directly (accessed using the `/chrome/` URL) then you will need to refresh them using the same command:
-{{{
+{{{#!sh
 trac-admin /path/to/env deploy /deploy/path
 }}}
@@ -70 +72 @@
 }}}
 
-=== 6. Steps specific to a given Trac version  ===
-
-==== Upgrading from Trac 0.12 to Trac 1.0 ==== #to1.0
-
-===== Python 2.4 no longer supported =====
+=== 6. Steps specific to a given Trac version
+
+==== Upgrading from Trac 0.12 to Trac 1.0 #to1.0
+
+===== Python 2.4 no longer supported
 Upgrade Python to at least 2.5, but not 3.0.
 
 ===== Subversion components not enabled by default for new installations
 The Trac components for Subversion support are no longer enabled by default. To enable the svn support, you need to make sure the `tracopt.versioncontrol.svn` components are enabled, for example by setting the following in the TracIni:
-{{{
+{{{#!ini
 [components]
 tracopt.versioncontrol.svn.* = enabled
@@ -91 +93 @@
 Prior to 1.0, the owner field of new tickets always defaulted to `[ticket] default_owner` when the value was not empty. If the value was empty, the owner field defaulted to to the Component's owner. In 1.0 and later, the `default_owner` must be set to `< default >` to make new tickets default to the Component's owner. This change allows the `default_owner` to be set to an empty value if no default owner is desired.
 
-==== Upgrading from Trac 0.11 to Trac 0.12 ====
-
-===== Python 2.3 no longer supported =====
+==== Upgrading from Trac 0.11 to Trac 0.12
+
+===== Python 2.3 no longer supported
 The minimum supported version of Python is now 2.4.
 
-===== SQLite v3.x required =====
+===== SQLite v3.x required
 SQLite v2.x is no longer supported. If you still use a Trac database of this format, you'll need to convert it to SQLite v3.x first. See [trac:PySqlite#UpgradingSQLitefrom2.xto3.x] for details.
 
-===== [trac:PySqlite] 2 required =====
+===== [trac:PySqlite] 2 required
 [trac:PySqlite] 1.1.x is no longer supported. Please install 2.5.5 or later if possible, see [#Tracdatabaseupgrade Trac database upgrade] below.
 
-===== Multiple Repository Support =====
+===== Multiple Repository Support
 The latest version includes support for multiple repositories. If you plan to add more repositories to your Trac instance, please refer to TracRepositoryAdmin#Migration.
 
 This may be of interest to users with only one repository, since there is now a way to avoid the potentially costly resync check at every request.
 
-===== Resynchronize the Trac Environment Against the Source Code Repository =====
+===== Resynchronize the Trac Environment Against the Source Code Repository
 
 Each [TracEnvironment Trac environment] must be resynchronized against the source code repository in order to avoid errors such as "[trac:#6120 No changeset ??? in the repository]" while browsing the source through the Trac interface:
 
-{{{
+{{{#!sh
 trac-admin /path/to/projenv repository resync '*'
 }}}
 
-===== Improved repository synchronization =====
+===== Improved repository synchronization
 In addition to supporting multiple repositories, there is now a more efficient method for synchronizing Trac and your repositories.
 
@@ -122 +124 @@
 Note that if you were using the `trac-post-commit-hook`, ''you're strongly advised to upgrade it'' to the new hook documented in the above references and [TracWorkflow#Howtocombinethetracopt.ticket.commit_updaterwiththetestingworkflow here], as the old hook will not work with anything else than the default repository and even for this case, it won't trigger the appropriate notifications.
 
-===== Authz permission checking =====
+===== Authz permission checking
 The authz permission checking has been migrated to a fine-grained permission policy. If you use authz permissions (aka `[trac] authz_file` and `authz_module_name`), you must add `AuthzSourcePolicy` in front of your permission policies in `[trac] permission_policies`. You must also remove `BROWSER_VIEW`, `CHANGESET_VIEW`, `FILE_VIEW` and `LOG_VIEW` from your global permissions with `trac-admin $ENV permission remove` or the "Permissions" admin panel.
 
-===== Microsecond timestamps =====
+===== Microsecond timestamps
 All timestamps in database tables, except the `session` table, have been changed from "seconds since epoch" to "microseconds since epoch" values. This change should be transparent to most users, except for custom reports. If any of your reports use date/time columns in calculations (e.g. to pass them to `datetime()`), you must divide the values retrieved from the database by 1'000'000. Similarly, if a report provides a calculated value to be displayed as a date/time (i.e. with a column named "time", "datetime", "changetime", "date", "created" or "modified"), you must provide a microsecond timestamp, that is, multiply your previous calculation with 1'000'000.
 
-==== Upgrading from Trac 0.10 to Trac 0.11 ====
-===== Site Templates and Styles =====
+==== Upgrading from Trac 0.10 to Trac 0.11
+===== Site Templates and Styles
 The templating engine has changed in 0.11 to Genshi, please look at TracInterfaceCustomization for more information.
 
 If you are using custom CSS or modified templates in the `templates` directory of the TracEnvironment, you will need to convert them to the Genshi way of doing things. To continue to use your style sheet, follow the instructions at TracInterfaceCustomization#SiteAppearance.
 
-===== Trac Macros, Plugins =====
+===== Trac Macros, Plugins
 The Trac macros will need to be adapted, as the old-style wiki-macros are not supported anymore due to the drop of [trac:ClearSilver] and the HDF. They need to be converted to the new-style macros, see WikiMacros. When they are converted to the new style, they need to be placed into the plugins directory instead and not wiki-macros, which is no longer scanned for macros or plugins.
 
-===== For FCGI/WSGI/CGI users =====
+===== For FCGI/WSGI/CGI users
 For those who run Trac under the CGI environment, run this command in order to obtain the trac.*gi file:
-{{{
+{{{#!sh
 trac-admin /path/to/env deploy /deploy/directory/path
 }}}
@@ -145 +147 @@
 This will create a deploy directory with the following two subdirectories: `cgi-bin` and `htdocs`. Then update your Apache configuration file `httpd.conf` with this new `trac.cgi` location and `htdocs` location.
 
-===== Web Admin plugin integrated =====
+===== Web Admin plugin integrated
 If you had the [trac:WebAdmin] plugin installed, you can uninstall it as it is part of the Trac code base since 0.11.
 
@@ -174 +176 @@
 There are some significant caveats in this, such as accepting a ticket sets it to 'assigned' state, and assigning a ticket sets it to 'new' state. So you will probably want to migrate to "basic" workflow; [trac:source:trunk/contrib/workflow/migrate_original_to_basic.py contrib/workflow/migrate_original_to_basic.py] may be helpful. See TracWorkflow for a detailed description of the new basic workflow.
 
-=== 7. Restart the Web Server === #RestarttheWebServer
+===== Global Configuration
+In versions prior to 0.11, the global configuration was by default located in `$prefix/share/trac/conf/trac.ini` or `/etc/trac/trac.ini`, depending on the distribution. You may want to specify that file to inherit from when upgrading.  Literally, when upgrading you have to add an `[inherit]` section to your project's `trac.ini` file. Additionally, you have to move your customized templates and common images from `$prefix/share/trac/...` to the new location.
+
+=== 7. Restart the Web Server #RestarttheWebServer
 
 If you are not running [wiki:TracCgi CGI], reload the new Trac code by restarting your web server.
 
-== Known Issues ==
+== Known Issues
 
 === Customized Templates
@@ -186 +191 @@
 The preferred way to perform TracInterfaceCustomization is to write a custom plugin doing an appropriate `ITemplateStreamFilter` transformation, as this is more robust in case of changes: we usually won't modify element `id`s or change CSS `class`es, and if we have to do so, this will be documented in the [trac:TracDev/ApiChanges] pages.
 
-=== !ZipImportError ===
+=== !ZipImportError
 
 Due to internal caching of zipped packages, whenever the content of the packages change on disk, the in-memory zip index will no longer match and you'll get irrecoverable !ZipImportError errors. Better anticipate and bring your server down for maintenance before upgrading.
 See [trac:#7014] for details.
 
-=== Wiki Upgrade ===
+=== Wiki Upgrade
 `trac-admin` will not delete or remove default wiki pages that were present in a previous version but are no longer in the new version.
 
-=== Trac database upgrade ===
+=== Trac database upgrade
 
 A known issue in some versions of [trac:PySqlite] (2.5.2-2.5.4) prevents the trac-admin upgrade script from successfully upgrading the database format. It is advised to use either a newer or older version of the sqlite python bindings to avoid this error. For more details see ticket [trac:#9434].
 
-=== Parent dir ===
+=== Parent dir
 If you use a Trac parent env configuration and one of the plugins in one child does not work, none of the children will work.
 
 == Related topics
 
-=== Upgrading Python ===
+=== Upgrading Python
 
 Upgrading Python to a newer version will require reinstallation of Python packages: Trac itself of course, but also [http://pypi.python.org/pypi/setuptools easy_install], if you've been using that. If you are using Subversion, you'll also need to upgrade the Python bindings for svn.
 
-==== Windows and Python 2.6 ====
+==== Windows and Python 2.6
 
 If you've been using !CollabNet's Subversion package, you may need to uninstall that in favor of [http://alagazam.net/ Alagazam], which has the Python bindings readily available, see [trac:TracSubversion]. That package works without tweaking.
 
-=== Changing Database Backend ===
+=== Changing Database Backend
 
 The [http://trac-hacks.org/wiki/TracMigratePlugin TracMigratePlugin] on [http://trac-hacks.org trac-hacks.org] has been written to assist in migrating between SQLite, MySQL and PostgreSQL databases.
 
-=== Upgrading from older versions of Trac === #OlderVersions
+=== Upgrading from older versions of Trac #OlderVersions
 
 For upgrades from versions older than Trac 0.10, refer first to [trac:wiki:0.10/TracUpgrade#SpecificVersions].