| 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. |
| 13 | | |
| 14 | | {{{ |
| 15 | | # easy_install --upgrade Trac==0.12b1 |
| 16 | | }}} |
| 17 | | (once beta1 is released, that is) |
| 18 | | |
| 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]). |
| 20 | | |
| 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: |
| | 17 | 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: |
| | 18 | |
| | 19 | {{{ |
| | 20 | # easy_install --upgrade Trac==1.0 |
| | 21 | }}} |
| | 22 | |
| | 23 | If 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]). |
| | 24 | |
| | 25 | 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 `.egg` files from former versions. |
| | 26 | 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 typical: |
| 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). |
| 28 | | |
| 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. |
| 30 | | |
| 31 | | === 2. Upgrade the Trac Environment === #UpgradetheTracEnvironment |
| | 31 | 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.) |
| | 32 | |
| | 33 | This 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. |
| | 34 | |
| | 35 | === 3. Upgrade the Trac Environment === #UpgradetheTracEnvironment |
| 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!). |
| | 68 | this will extract static resources and CGI scripts (`trac.wsgi`, etc) from new Trac version and its plugins into `/deploy/path`. |
| | 69 | |
| | 70 | Some 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 |
| | 72 | Remove above note once #9936 is fixed. |
| | 73 | }}} |
| | 76 | |
| | 77 | ==== Upgrading from Trac 0.12 to Trac 1.0 ==== #to1.0 |
| | 78 | |
| | 79 | ===== Python 2.4 no longer supported ===== |
| | 80 | The minimum supported version of python is now 2.5 |
| | 81 | |
| | 82 | ===== Subversion components not enabled by default for new installations |
| | 83 | 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: |
| | 84 | {{{ |
| | 85 | [components] |
| | 86 | tracopt.versioncontrol.svn.* = enabled |
| | 87 | }}} |
| | 88 | The upgrade procedure should take care of this and change the TracIni appropriately, unless you already had the svn components explicitly disabled. |
| | 89 | |
| | 90 | |
| | 91 | ===== Attachments migrated to new location |
| | 92 | Another 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. |
| | 93 | |
| | 94 | ===== Behavior of `[ticket] default_owner` changed |
| | 95 | 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. |
| | 96 | |
| | 97 | |
| 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. |
| | 110 | The latest version includes support for multiple repositories. If you plan to add more repositories to your Trac instance, please refer to TracRepositoryAdmin#Migration. |
| | 111 | |
| | 112 | This 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. |
| | 113 | |
| | 114 | ===== Resynchronize the Trac Environment Against the Source Code Repository ===== |
| | 115 | |
| | 116 | 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: |
| | 117 | |
| | 118 | {{{ |
| | 119 | trac-admin /path/to/projenv repository resync '*' |
| | 120 | }}} |
| 93 | | 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, 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. |
| | 127 | 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. |
| | 128 | |
| | 129 | ===== Authz permission checking ===== |
| | 130 | 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). |
| | 131 | |
| | 132 | ===== Microsecond timestamps ===== |
| | 133 | 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. |
| | 161 | Things you should pay attention to, while upgrading. |
| | 162 | |
| | 163 | === Customized Templates |
| | 164 | |
| | 165 | Trac 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 ;-) |
| | 166 | |
| | 167 | 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 TracDev/ApiChanges pages. |
| | 168 | |
| | 169 | === !ZipImportError === |
| | 170 | |
| | 171 | 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. |
| | 172 | See [trac:#7014] for details. |
| | 173 | |
| | 174 | === Wiki Upgrade === |
| | 175 | `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. |
| | 176 | |
| | 177 | === Trac database upgrade === |
| | 178 | |
| | 179 | A 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]. |
| | 180 | |
| 124 | | === Wiki Upgrade === |
| 125 | | `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. |
| 126 | | |
| 127 | | |
| 128 | | == Changing Database Backend == |
| 129 | | === SQLite to PostgreSQL === |
| 130 | | |
| 131 | | The [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 |
| 132 | | |
| 133 | | == Older Versions == |
| | 184 | == Related topics |
| | 185 | |
| | 186 | === Upgrading Python === |
| | 187 | |
| | 188 | Upgrading 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. |
| | 189 | |
| | 190 | ==== Windows and Python 2.6 ==== |
| | 191 | |
| | 192 | 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 TracSubversion). The good news is, that works with no tweaking. |
| | 193 | |
| | 194 | === Changing Database Backend === |
| | 195 | |
| | 196 | 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. |
| | 197 | |
| | 198 | === Upgrading from older versions of Trac === #OlderVersions |
