Changes between Version 1 and Version 2 of Trac Upgrade

02/06/14 20:46:04 (3 years ago)



  • Trac Upgrade

    v1 v2  
    11= Upgrade Instructions = 
    4 A Trac environment sometimes needs to be upgraded before it can be used with a new version of Trac. This document describes the steps necessary to upgrade an environment. 
     5== Instructions == 
    6  '''Note''': ''Environment upgrades are not necessary for minor version releases unless otherwise noted. For example, there's no need to upgrade a Trac environment created with (or upgraded) 0.8.0 when installing 0.8.4 (or any other 0.8.x release).'' 
     7Typically, there are seven steps involved in upgrading to a newer version of Trac: 
    8 == General Instructions == 
     9=== 1. Bring your server off-line 
    10 Typically, there are four steps involved in upgrading to a newer version of Trac: 
     11It 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].  
    12 === Update the Trac Code === 
     13=== 2. Update the Trac Code === #UpdatetheTracCode 
    14 Get the new version of Trac, either by downloading an offical release package or by checking it out from the [ Subversion repository]. 
     15Get the new version as described in TracInstall, or your operating system specific procedure. 
    16 If you're doing a major version upgrade (such as from 0.8 to 0.9), it is ''highly'' recommended that you first remove the existing Trac code. To do this, you need to delete the `trac` directory from the Python `lib/site-packages` directory. 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). 
     17If you already have a 0.11 version of Trac installed via `easy_install`, it might be easiest to also use `easy_install` to upgrade your Trac installation: 
    18 If you have a source distribution, you need to run 
    20 python install 
     20# easy_install --upgrade Trac==0.12 
    23 to install the new version. If you've downloaded the Windows installer, you execute it, and so on. 
     23If you do a manual (not operating system-specific) upgrade, you should also stop any running Trac servers before the installation. Doing "hot" upgrades is not advised, especially on Windows ([trac:#7265]). 
    25 === Upgrade the Trac Environment === 
     25You may also want to remove the pre-existing Trac code by deleting the `trac` directory from the Python `lib/site-packages` directory, or remove Trac `.egg` files from former versions. 
     26The location of the site-packages directory depends on the operating system and the location in which Python was installed. However, the following locations are typical: 
     27 * on Linux: `/usr/lib/python2.X/site-packages` 
     28 * on Windows: `C:\Python2.X\lib\site-packages` 
     29 * on MacOSX: `/Library/Python/2.X/site-packages` 
    27 Unless noted otherwise, upgrading between major versions (such as 0.8 and 0.9) involves changes to the database schema, and possibly the layout of the [wiki:TracEnvironment environment directory]. Fortunately, Trac provides automated upgrade scripts to ease the pain. These scripts are run via [wiki:TracAdmin trac-admin]: 
     31You 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.) 
     33This cleanup is not mandatory, but makes it easier to troubleshoot issues later on, as you won't waste your time looking at code or templates from a previous release that are not being used anymore... As usual, make a backup before actually deleting things. 
     35=== 3. Upgrade the Trac Environment === #UpgradetheTracEnvironment 
     37Environment upgrades are not necessary for minor version releases unless otherwise noted.  
     39After 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]: 
    2941trac-admin /path/to/projenv upgrade 
    3244This command will do nothing if the environment is already up-to-date. 
    34 Note that if you are using a PostgreSQL database, this command will fail with the message that the environment can only be backed up when you use an SQLite database. This means that you will have to backup the repository and the database manually. Then, to perform the actual upgrade, run: 
     46Note that a backup of your database will be performed automatically prior to the upgrade.  
     47This feature is relatively new for the PostgreSQL or MySQL database backends, so if it fails, you will have to backup the database manually. Then, to perform the actual upgrade, run: 
    3649trac-admin /path/to/projenv upgrade --no-backup 
    39 === Update the Trac Documentation === 
     52=== 4. Update the Trac Documentation === #UpdatetheTracDocumentation 
    41 Every [wiki:TracEnvironment Trac environment] includes a copy of the Trac documentation for the installed version. As you probably want to keep the included documentation in sync with the installed version of Trac, [wiki:TracAdmin trac-admin] provides a command to upgrade the documentation: 
     54Every [TracEnvironment Trac environment] includes a copy of the Trac documentation for the installed version. As you probably want to keep the included documentation in sync with the installed version of Trac, [TracAdmin trac-admin] provides a command to upgrade the documentation: 
    4356trac-admin /path/to/projenv wiki upgrade 
    46 Note that this procedure will of course leave your `WikiStart` page intact. 
     59Note that this procedure will leave your `WikiStart` page intact. 
    48 === Restart the Web Server === 
    50 In order to reload the new Trac code you will need to restart your web server (note this is not necessary for [wiki:TracCgi CGI]). 
     62=== 5. Refresh static resources === 
    52 == Specific Versions == 
     64If 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: 
     66trac-admin /path/to/env deploy /deploy/path 
     68this will extract static resources and CGI scripts (`trac.wsgi`, etc) from new Trac version and its plugins into `/deploy/path`. 
    54 The following sections discuss any extra actions that may need to be taken to upgrade to specific versions of Trac. 
     70Some web browsers (IE, Opera) cache CSS and Javascript files aggressively, so you may need to instruct your users to manually erase the contents of their browser's cache, a forced refreshed (`<F5>`) should be enough. 
     72Remove above note once #9936 is fixed. 
    56 == From 0.9.x to 0.10.x == 
     75=== 6. Steps specific to a given Trac version  === 
     76==== Upgrading from Trac 0.12 to Trac 1.0 ==== #to1.0 
    58 Due to some changes in the Wiki syntax, you may notice that certain parts of your pages no longer work as expected: 
    59  * Previously, links to images would result in that image being embedded into the page. Since 0.10, links to images remain plain links. If you want to embed an image in the page, use the `[[Image]]` macro. 
    60  * You can no longer use `%20` in wiki links to encode spaces. Instead, you should quote the name containing spaces (for example, use `wiki:"My page"` instead of `wiki:My%20page`.) 
     78The 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: 
     81tracopt.versioncontrol.svn.* = enabled 
     83The upgrade procedure should take care of this and change the TracIni appropriately, unless you already had the svn components explicitly disabled. 
    62 Several enhancements have been made to the version control subsystem, in particular for the support of scoped repositories has been improved.  
    63 It is recommended that you perform a [TracAdmin#InteractiveMode trac-admin] '''`resync`''' operation to take advantage of these improvements. 
     85Another step in the automatic upgrade will change the way the attachments are stored. If you're a bit paranoid, you might want to take a backup of the `attachments` directory before upgrading (but if you are, you already did a full copy of the environment, no?). In case the `attachments` directory contains some files which are //not// attachments, the last step of the migration to the new layout will fail: the deletion of the now unused `attachments` directory can't be done if there are still files and folders in it. You may ignore this error, but better go have a look to these files, move them elsewhere and remove the `attachments` directory manually to cleanup the environment. The attachments themselves are now all located in your environment below the `files/attachments` directory. 
    65 Also note that the argument list of the [TracAdmin trac-admin] '''`initenv`''' command has changed: there's a new argument for determining the type of version control system. The old usage was: 
    66 {{{ 
    67    initenv <projectname> <db> <repospath> <templatepath> 
    68 }}} 
    69 The new usage is: 
    70 {{{ 
    71    initenv <projectname> <db> <repostype> <repospath> <templatepath> 
    72 }}} 
    73 If you're using any scripts that automate the creation of Trac environments, you will need to update them. If you're using Subversion, specify `svn` for the `<repostype>` argument. 
    75 == From 0.9.3 to 0.9.4 == 
     88==== Upgrading from Trac 0.11 to Trac 0.12 ==== 
    77 There is a bug in Pysqlite 1.x that causes reports using the "%" character for `LIKE` clauses or date formatting to fail.  You will need to use escape the percent characters with another: "%%". 
     90===== Python 2.3 no longer supported ===== 
     91The minimum supported version of python is now 2.4 
    79 == From 0.9.x to 0.9.3 or later == 
     93===== SQLite v3.x required ===== 
     94SQLite 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. 
    81 If you are using plugins you might need to upgrade them. See for further details. 
     96===== PySqlite 2 required ===== 
     97PySqlite 1.1.x is no longer supported. Please install 2.5.5 or later if possible (see [#Tracdatabaseupgrade Trac database upgrade] below). 
    83 == From 0.9-beta to 0.9 == 
     99===== Multiple Repository Support ===== 
     100The latest version includes support for multiple repositories. If you plan to add more repositories to your Trac instance, please refer to TracRepositoryAdmin#Migration. 
    85 If inclusion of the static resources (style sheets, javascript, images) is not working, check the value of the `htdocs_location` in trac.ini. For [wiki:TracModPython mod_python], [wiki:TracStandalone Tracd] and [wiki:TracFastCgi FastCGI], you can simply remove the option altogether. For [wiki:TracCgi CGI], you should fix it to point to the URL you mapped the Trac `htdocs` directory to (although you can also remove it and then [wiki:TracCgi#MappingStaticResources map the static resources]). If you're still having problems after removing the option, check the paths in the `trac/` file and fix them if they're incorrect. 
     102This may be of interest to users with only one repository, since there's now a way to avoid the potentially costly resync check at every request. 
    87 If you've been using plugins with a beta release of Trac 0.9, or have disabled some of the built-in components, you might have to update the rules for disabling/enabling components in [wiki:TracIni trac.ini]. In particular, globally installed plugins now need to be enabled explicitly. See TracPlugins and TracIni for more information. 
     104===== Resynchronize the Trac Environment Against the Source Code Repository ===== 
    89 If you want to enable the display of all ticket changes in the timeline (the “Ticket Details” option), you now have to explicitly enable that in [wiki:TracIni trac.ini], too: 
     106Each [TracEnvironment Trac environment] must be resynchronized against the source code repository in order to avoid errors such as "[ No changeset ??? in the repository]" while browsing the source through the Trac interface: 
    92 [timeline] 
    93 ticket_show_details = true 
     109trac-admin /path/to/projenv repository resync '*' 
    96 == From 0.8.x to 0.9 == 
     112===== Improved repository synchronization ===== 
     113In addition to supporting multiple repositories, there is now a more efficient method for synchronizing Trac and your repositories. 
    98 [wiki:TracModPython mod_python] users will also need to change the name of the mod_python handler in the Apache HTTPD configuration: 
     115While you can keep the same synchronization as in 0.11 adding the post-commit hook as outlined in TracRepositoryAdmin#Synchronization and TracRepositoryAdmin#ExplicitSync will allow more efficient synchronization and is more or less required for multiple repositories. 
     117Note 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. 
     119===== Authz permission checking ===== 
     120The 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). 
     122===== Microsecond timestamps ===== 
     123All 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. 
     125==== Upgrading from Trac 0.10 to Trac 0.11 ==== 
     126===== Site Templates and Styles ===== 
     127The templating engine has changed in 0.11 to Genshi, please look at TracInterfaceCustomization for more information. 
     129If you are using custom CSS styles 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. 
     131===== Trac Macros, Plugins ===== 
     132The 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. 
     134===== For FCGI/WSGI/CGI users ===== 
     135For those who run Trac under the CGI environment, run this command in order to obtain the trac.*gi file: 
    100    from: PythonHandler trac.ModPythonHandler 
    101    to:   PythonHandler trac.web.modpython_frontend 
     137trac-admin /path/to/env deploy /deploy/directory/path 
    104 If you have [ PySQLite] 2.x installed, Trac will now try to open your SQLite database using the SQLite 3.x file format. The database formats used by SQLite 2.8.x and SQLite 3.x are incompatible. If you get an error like ''“file is encrypted or is not a database”'' after upgrading, then you must convert your database file. 
     140This 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. 
    106 To do this, you need to have both SQLite 2.8.x and SQLite 3.x installed (they have different filenames so can coexist on the same system). Then use the following commands: 
    107 {{{ 
    108  $ mv trac.db trac2.db 
    109  $ sqlite trac2.db .dump | sqlite3 trac.db 
    110 }}} 
     142===== Web Admin plugin integrated ===== 
     143If you had the webadmin plugin installed, you can uninstall it as it is part of the Trac code base since 0.11. 
    112 To update multiple database files at once on linux you may use the following command (replace {{{/var/trac}}} withe the location where your trac installtions reside): 
    113 {{{ 
    114  $ find /var/trac/ -iname "trac.db" | xargs -i bash -c "mv {} {}.2; sqlite {}.2 .dump | sqlite3 {};" 
    115 }}} 
     145=== 7. Restart the Web Server === #RestarttheWebServer 
    117 Remember the give the webserver write permission to trac.db. 
     147If you are not running [wiki:TracCgi CGI], reload the new Trac code by restarting your web server. 
    119 After testing that the conversion was successful, the `trac2.db` file can be deleted. For more information on the SQLite upgrade see 
     149== Known Issues == 
    121 == From 0.7.x to 0.8 == 
     151Things you should pay attention to, while upgrading. 
    123 0.8 adds a new roadmap feature which requires additional permissions. While a 
    124 fresh installation will by default grant ROADMAP_VIEW and MILESTONE_VIEW 
    125 permissions to anonymous, these permissions have to be granted manually when 
    126 upgrading: 
    127 {{{ 
    128  $ trac-admin /path/to/projectenv permission add anonymous MILESTONE_VIEW 
    129  $ trac-admin /path/to/projectenv permission add anonymous ROADMAP_VIEW 
    130 }}} 
     153=== Customized Templates 
     155Trac supports customization of its Genshi templates by placing copies of the templates in the `<env>/templates` folder of your [TracEnvironment environment] or in a common location specified in the [[TracIni#GlobalConfiguration| [inherit] templates_dir]] configuration setting. If you choose to do so, be wary that you will need to repeat your changes manually on a copy of the new templates when you upgrade to a new release of Trac (even a minor one), as the templates will likely evolve. So keep a diff around ;-) 
     157The 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 TracDev/ApiChanges pages. 
     159=== !ZipImportError === 
     161Due 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. 
     162See [trac:#7014] for details. 
     164=== Wiki Upgrade === 
     165`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. 
     167=== Trac database upgrade === 
     169A known issue in some versions of 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]. 
     171=== parent dir === 
     172If you use a trac parent env configuration and one of the plugins in one child does not work, none of the children work. 
     174== Related topics 
     176=== Upgrading Python === 
     178Upgrading Python to a newer version will require reinstallation of Python packages: Trac of course; also [ easy_install], if you've been using that.  Assuming you're using Subversion, you'll also need to upgrade the Python bindings for svn. 
     180==== Windows and Python 2.6 ==== 
     182If you've been using !CollabNet's Subversion package, you may need to uninstall that in favor of [ Alagazam], which has the Python bindings readily available (see TracSubversion).  The good news is, that works with no tweaking. 
     184=== Changing Database Backend === 
     185==== SQLite to PostgreSQL ==== 
     187The [ sqlite2pg] script on [] has been written to assist in migrating a SQLite database to a PostgreSQL database 
     189=== Upgrading from older versions of Trac === #OlderVersions 
     191For upgrades from versions older than Trac 0.10, refer first to [trac:wiki:0.10/TracUpgrade#SpecificVersions].