Changes between Version 118 and Version 119 of TracUpgrade
- Timestamp:
- Jun 22, 2016, 11:31:14 AM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracUpgrade
v118 v119 43 43 }}} 44 44 45 This command will do nothingif the environment is already up-to-date.45 This command will not have any effect if the environment is already up-to-date. 46 46 47 47 Note that a backup of your database will be performed automatically prior to the upgrade. 48 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:48 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: 49 49 {{{#!sh 50 50 trac-admin /path/to/projenv upgrade --no-backup … … 66 66 trac-admin /path/to/env deploy /deploy/path 67 67 }}} 68 68 69 this will extract static resources and CGI scripts (`trac.wsgi`, etc) from new Trac version and its plugins into `/deploy/path`. 69 70 … … 78 79 79 80 ===== Python 2.4 no longer supported 81 80 82 Upgrade Python to at least 2.5, but not 3.0. 81 83 … … 107 109 108 110 ===== Python 2.3 no longer supported 111 109 112 The minimum supported version of Python is now 2.4. 110 113 111 114 ===== SQLite v3.x required 115 112 116 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. 113 117 114 118 ===== [trac:PySqlite] 2 required 119 115 120 [trac:PySqlite] 1.1.x is no longer supported. Please install 2.5.5 or later if possible, see [#Tracdatabaseupgrade Trac database upgrade] below. 116 121 … … 131 136 132 137 ===== Multiple Repository Support 138 133 139 The latest version includes support for multiple repositories. If you plan to add more repositories to your Trac instance, please refer to TracRepositoryAdmin#Migration. 134 140 … … 144 150 145 151 ===== Improved repository synchronization 152 146 153 In addition to supporting multiple repositories, there is now a more efficient method for synchronizing Trac and your repositories. 147 154 … … 151 158 152 159 ===== Authz permission checking 160 153 161 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. 154 162 155 163 ===== Microsecond timestamps 164 156 165 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. 157 166 158 167 ==== Upgrading from Trac 0.10 to Trac 0.11 168 159 169 ===== Site Templates and Styles 170 160 171 The templating engine has changed in 0.11 to Genshi, please look at TracInterfaceCustomization for more information. 161 172 … … 163 174 164 175 ===== Trac Macros, Plugins 176 165 177 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. 166 178 167 179 ===== For FCGI/WSGI/CGI users 180 168 181 For those who run Trac under the CGI environment, run this command in order to obtain the trac.*gi file: 169 182 {{{#!sh … … 178 191 ===== New Default Configurable Workflow 179 192 180 When you run `trac-admin <env> upgrade`, your `trac.ini` will be modified to include a `[ticket-workflow]` section. The workflow configured in this case is the original workflow, so that ticket actions will behave like they did in 0.10. 181 182 Graphically, that looks like this: 193 When you run `trac-admin <env> upgrade`, your `trac.ini` will be modified to include a `[ticket-workflow]` section. The workflow configured in this case is the original workflow, so that ticket actions will behave like they did in 0.10: 183 194 184 195 {{{#!Workflow width=500 height=240 … … 244 255 === Changing Database Backend 245 256 246 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.257 The [https://trac-hacks.org/wiki/TracMigratePlugin TracMigratePlugin] on [https://trac-hacks.org trac-hacks.org] has been written to assist in migrating between SQLite, MySQL and PostgreSQL databases. 247 258 248 259 === Upgrading from older versions of Trac #OlderVersions