Changes between Version 2 and Version 3 of TracUpgrade


Ignore:
Timestamp:
05/16/13 07:34:23 (16 months ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracUpgrade

    v2 v3  
    11= Upgrade Instructions = 
    22[[TracGuideToc]] 
     3[[PageOutline(2-4,,inline,unnumbered)]] 
    34 
    45== Instructions == 
     
    67Typically, there are seven steps involved in upgrading to a newer version of Trac: 
    78 
    8 === 1. Update the Trac Code === #UpdatetheTracCode 
     9=== 1. Bring your server off-line 
     10 
     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 
     13=== 2. Update the Trac Code === #UpdatetheTracCode 
    914 
    1015Get the new version as described in TracInstall, or your operating system specific procedure. 
    1116 
    12 If you already have a 0.11 version of Trac installed via `easy_install`, it might be the easiest to use it also to upgrade you Trac installation. 
     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: 
    1318 
    1419{{{ 
    15 # easy_install --upgrade Trac==0.12b1 
     20# easy_install --upgrade Trac==0.12 
    1621}}} 
    17 (once beta1 is released, that is) 
    1822 
    19 If you do a manual (not operating system specific) upgrade, you should also stop any running Trac server before the installation. Doing "hot" upgrades is not advised, especially not on Windows ([trac:ticket:7625 #7265]). 
     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]). 
    2024 
    21 You 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 .eggs from former versions. 
    22 The location of the site-packages directory depends on the operating system, and the location in which Python was installed. However, the following locations are common: 
     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: 
    2327 * on Linux: `/usr/lib/python2.X/site-packages` 
    2428 * on Windows: `C:\Python2.X\lib\site-packages` 
    2529 * on MacOSX: `/Library/Python/2.X/site-packages` 
    2630 
    27 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). 
     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.) 
    2832 
    29 This cleanup is not mandatory, but it 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. 
     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. 
    3034 
    31 === 2. Upgrade the Trac Environment === #UpgradetheTracEnvironment 
     35=== 3. Upgrade the Trac Environment === #UpgradetheTracEnvironment 
    3236 
    3337Environment upgrades are not necessary for minor version releases unless otherwise noted.  
     
    4650}}} 
    4751 
    48 === 3. Update the Trac Documentation === #UpdatetheTracDocumentation 
     52=== 4. Update the Trac Documentation === #UpdatetheTracDocumentation 
    4953 
    5054Every [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: 
     
    5357}}} 
    5458 
    55 Note that this procedure will of course leave your `WikiStart` page intact. 
     59Note that this procedure will leave your `WikiStart` page intact. 
    5660 
    57 === 4. Resynchronize the Trac Environment Against the Source Code Repository === 
     61 
     62=== 5. Refresh static resources === 
     63 
     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: 
     65{{{ 
     66trac-admin /path/to/env deploy /deploy/path 
     67}}} 
     68this will extract static resources and CGI scripts (`trac.wsgi`, etc) from new Trac version and its plugins into `/deploy/path`. 
     69 
     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. 
     71{{{#!comment 
     72Remove above note once #9936 is fixed. 
     73}}} 
     74 
     75=== 6. Steps specific to a given Trac version  === 
     76==== Upgrading from Trac 0.12 to Trac 1.0 ==== #to1.0 
     77 
     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: 
     79{{{ 
     80[components] 
     81tracopt.versioncontrol.svn.* = enabled 
     82}}} 
     83The upgrade procedure should take care of this and change the TracIni appropriately, unless you already had the svn components explicitly disabled. 
     84 
     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. 
     86 
     87 
     88==== Upgrading from Trac 0.11 to Trac 0.12 ==== 
     89 
     90===== Python 2.3 no longer supported ===== 
     91The minimum supported version of python is now 2.4 
     92 
     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. 
     95 
     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). 
     98 
     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. 
     101 
     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. 
     103 
     104===== Resynchronize the Trac Environment Against the Source Code Repository ===== 
    58105 
    59106Each [TracEnvironment Trac environment] must be resynchronized against the source code repository in order to avoid errors such as "[http://trac.edgewall.org/ticket/6120 No changeset ??? in the repository]" while browsing the source through the Trac interface: 
     
    63110}}} 
    64111 
    65 === 5. Refresh static resources === 
    66  
    67 If you've setup web server to give out static resources directly (accessed using /chrome/ URL) then you need to refresh them using the same command: 
    68 {{{ 
    69 trac-admin /path/to/env deploy /deploy/path 
    70 }}} 
    71 this will extract static resources and CGI scripts (trac.wsgi, etc) from new Trac version and its plugins into `/deploy/path`. 
    72  
    73 Some web browsers cache the CSS and Javascript file in a strong way, so you'll perhaps need to refresh the cache of the browsers by a force reload (and tell your users to do so!). 
    74  
    75 === 6. Steps specific to a given Trac version  === 
    76 ==== Upgrading from Trac 0.11 to Trac 0.12 ==== 
    77 ===== Python 2.3 no longer supported ===== 
    78 The minimum supported version of python is now 2.4 
    79  
    80 ===== SQLite v3.x required ===== 
    81 SQLite v2.x is no longer supported, if you happen to still use a Trac database using this format, you'll need to convert it to SQLite v3.x first. See [trac:PySqlite#UpgradingSQLitefrom2.xto3.x] for details. 
    82  
    83 ===== Multiple Repository Support ===== 
    84 If you plan to add more repositories to your Trac instance, as this is now possible with the newly introduced multiple repository support, please refer to TracRepositoryAdmin#Migration. 
    85  
    86 This can be of interest even if you only have one repository, as there's now a way to avoid the potentially costly resync check at every request. 
    87  
    88112===== Improved repository synchronization ===== 
    89 In addition to supporting multiple repositories, a new more efficient method for synchronizing Trac and your repositories was implemented. 
     113In addition to supporting multiple repositories, there is now a more efficient method for synchronizing Trac and your repositories. 
    90114 
    91115While 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. 
    92116 
    93117Note 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, 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. 
     118 
     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). 
     121 
     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. 
    94124 
    95125==== Upgrading from Trac 0.10 to Trac 0.11 ==== 
     
    100130 
    101131===== Trac Macros, Plugins ===== 
    102 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 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. 
     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. 
    103133 
    104134===== For FCGI/WSGI/CGI users ===== 
     
    119149== Known Issues == 
    120150 
    121 === parent dir === 
    122 If you use a trac parent env configuration and one of the plugins in one child does not work, none of the children work. 
     151Things you should pay attention to, while upgrading. 
     152 
     153=== Customized Templates 
     154 
     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 ;-) 
     156 
     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. 
     158 
     159=== !ZipImportError === 
     160 
     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. 
    123163 
    124164=== Wiki Upgrade === 
    125165`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. 
    126166 
     167=== Trac database upgrade === 
    127168 
    128 == Changing Database Backend == 
    129 === SQLite to PostgreSQL === 
     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]. 
     170 
     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. 
     173 
     174== Related topics 
     175 
     176=== Upgrading Python === 
     177 
     178Upgrading Python to a newer version will require reinstallation of Python packages: Trac of course; also [http://pypi.python.org/pypi/setuptools easy_install], if you've been using that.  Assuming you're using Subversion, you'll also need to upgrade the Python bindings for svn. 
     179 
     180==== Windows and Python 2.6 ==== 
     181 
     182If 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 TracSubversion).  The good news is, that works with no tweaking. 
     183 
     184=== Changing Database Backend === 
     185==== SQLite to PostgreSQL ==== 
    130186 
    131187The [http://trac-hacks.org/wiki/SqliteToPgScript sqlite2pg] script on [http://trac-hacks.org trac-hacks.org] has been written to assist in migrating a SQLite database to a PostgreSQL database 
    132188 
    133 == Older Versions == 
     189=== Upgrading from older versions of Trac === #OlderVersions 
    134190 
    135191For upgrades from versions older than Trac 0.10, refer first to [trac:wiki:0.10/TracUpgrade#SpecificVersions].