Edgewall Software

Changes between Version 118 and Version 119 of TracUpgrade


Ignore:
Timestamp:
Jun 22, 2016, 11:31:14 AM (5 years ago)
Author:
Jun Omae
Comment:

Must make consistent between TracUpgrade and 1.1/TracUpgrade (refs 1.1/TracUpgrade@22)

Legend:

Unmodified
Added
Removed
Modified
  • TracUpgrade

    v118 v119  
    4343}}}
    4444
    45 This command will do nothing if the environment is already up-to-date.
     45This command will not have any effect if the environment is already up-to-date.
    4646
    4747Note 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:
     48This 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:
    4949{{{#!sh
    5050trac-admin /path/to/projenv upgrade --no-backup
     
    6666trac-admin /path/to/env deploy /deploy/path
    6767}}}
     68
    6869this will extract static resources and CGI scripts (`trac.wsgi`, etc) from new Trac version and its plugins into `/deploy/path`.
    6970
     
    7879
    7980===== Python 2.4 no longer supported
     81
    8082Upgrade Python to at least 2.5, but not 3.0.
    8183
     
    107109
    108110===== Python 2.3 no longer supported
     111
    109112The minimum supported version of Python is now 2.4.
    110113
    111114===== SQLite v3.x required
     115
    112116SQLite 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.
    113117
    114118===== [trac:PySqlite] 2 required
     119
    115120[trac:PySqlite] 1.1.x is no longer supported. Please install 2.5.5 or later if possible, see [#Tracdatabaseupgrade Trac database upgrade] below.
    116121
     
    131136
    132137===== Multiple Repository Support
     138
    133139The latest version includes support for multiple repositories. If you plan to add more repositories to your Trac instance, please refer to TracRepositoryAdmin#Migration.
    134140
     
    144150
    145151===== Improved repository synchronization
     152
    146153In addition to supporting multiple repositories, there is now a more efficient method for synchronizing Trac and your repositories.
    147154
     
    151158
    152159===== Authz permission checking
     160
    153161The 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.
    154162
    155163===== Microsecond timestamps
     164
    156165All 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.
    157166
    158167==== Upgrading from Trac 0.10 to Trac 0.11
     168
    159169===== Site Templates and Styles
     170
    160171The templating engine has changed in 0.11 to Genshi, please look at TracInterfaceCustomization for more information.
    161172
     
    163174
    164175===== Trac Macros, Plugins
     176
    165177The 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.
    166178
    167179===== For FCGI/WSGI/CGI users
     180
    168181For those who run Trac under the CGI environment, run this command in order to obtain the trac.*gi file:
    169182{{{#!sh
     
    178191===== New Default Configurable Workflow
    179192
    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:
     193When 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:
    183194
    184195{{{#!Workflow width=500 height=240
     
    244255=== Changing Database Backend
    245256
    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.
     257The [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.
    247258
    248259=== Upgrading from older versions of Trac #OlderVersions