06/25/17 06:07:12 (5 years ago)

[titan] autoupdate wiki files

1 edited


  • wiki/pages/TracUpgrade

    r40226 r40551  
    1 = Upgrade Instructions
    2 [[TracGuideToc]]
    3 [[PageOutline(2-4,,inline,unnumbered)]]
    5 == Instructions
    7 Typically, there are seven steps involved in upgrading to a newer version of Trac:
    9 === 1. Bring your server off-line
    11 It 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].
    13 Although a database backup will be implicitly created by default when upgrading the environment, it is always a good idea to perform a full backup of the environment using the [TracBackup hotcopy] command before beginning.
    15 === 2. Update the Trac Code #UpdatetheTracCode
    17 Get the new version as described in TracInstall, or your operating system specific procedure.
    19 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:
    21 {{{#!sh
    22 easy_install --upgrade Trac==1.0
    23 }}}
    25 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]).
    27 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.
    28 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:
    29  * on Linux: `/usr/lib/python2.X/site-packages`
    30  * on Windows: `C:\Python2.X\lib\site-packages`
    31  * on MacOSX: `/Library/Python/2.X/site-packages`
    33 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. This cleanup is not mandatory, but makes it easier to troubleshoot issues later on, as your installation is uncluttered by code or templates from a previous release that is not used anymore. As usual, make a backup before actually removing things.
    35 === 3. Upgrade the Trac Environment #UpgradetheTracEnvironment
    37 Environment upgrades are not necessary for minor version releases unless otherwise noted.
    39 After 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]:
    40 {{{#!sh
    41 trac-admin /path/to/projenv upgrade
    42 }}}
    44 This command will do nothing if the environment is already up-to-date.
    46 Note that a backup of your database will be performed automatically prior to the upgrade.
    47 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 {{{#!sh
    49 trac-admin /path/to/projenv upgrade --no-backup
    50 }}}
    52 === 4. Update the Trac Documentation === #UpdatetheTracDocumentation
    54 By default, every [TracEnvironment Trac environment] includes a copy of the Trac documentation for the installed version. However, to keep the included documentation in sync with the installed version of Trac, use the following [TracAdmin trac-admin] command to upgrade the documentation:
    55 {{{#!sh
    56 trac-admin /path/to/projenv wiki upgrade
    57 }}}
    59 Note that this procedure will leave your `WikiStart` page intact.
    61 === 5. Refresh static resources
    63 If 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:
    64 {{{#!sh
    65 trac-admin /path/to/env deploy /deploy/path
    66 }}}
    67 this will extract static resources and CGI scripts (`trac.wsgi`, etc) from new Trac version and its plugins into `/deploy/path`.
    69 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.
    70 {{{#!comment
    71 Remove above note once #9936 is fixed.
    72 }}}
    74 === 6. Steps specific to a given Trac version
    76 ==== Upgrading from Trac 1.0 to 1.1.x #to1.1.x
    78 ===== Python 2.5 no longer supported
    79 Upgrade Python to at least 2.6, but not 3.0.
    81 ===== New workflow actions
    83 The ticket creation step is now controlled with a workflow action. The default workflow has `create` and `create_and_assign` actions. The `create` action will always be added when upgrading the database. The `create_and_assign` action will be added if the workflow has an //assigned// state. You may want to edit your workflow after upgrading the database to customize the actions available on the //New Ticket// page.
    85 ===== New permissions policy for read-only wiki pages
    86 Since 1.1.2 the read-only attribute of wiki pages is enabled and enforced only when `ReadonlyWikiPolicy` is in the list of active permission policies. If `[trac] permission_policy` has the default value `DefaultPermissionPolicy, LegacyAttachmentPolicy`, then `ReadonlyWikiPolicy` should be automatically appended to the list when upgrading the environment:
    87 {{{#!ini
    88 [trac]
    89 permission_policies = ReadonlyWikiPolicy,
    90  DefaultPermissionPolicy,
    91  LegacyAttachmentPolicy
    92 }}}
    93 If other permission policies are enabled, //trac.ini// will need to be edited to append `ReadonlyWikiPolicy` to the list of active `permission_policies`. See TracFineGrainedPermissions#ReadonlyWikiPolicy for additional details on the proper ordering.
    95 ==== Upgrading from Trac 0.12 to Trac 1.0 #to1.0
    97 ===== Python 2.4 no longer supported
    98 Upgrade Python to at least 2.5, but not 3.0.
    100 ===== Subversion components not enabled by default for new installations
    101 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:
    102 {{{#!ini
    103 [components]
    104 tracopt.versioncontrol.svn.* = enabled
    105 }}}
    106 The upgrade procedure should take care of this and change the TracIni appropriately, unless you already had the svn components explicitly disabled.
    108 ===== Attachments migrated to new location
    109 Another step in the automatic upgrade will change the way the attachments are stored. Create a backup of the `attachments` directory before upgrading. 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 to move them elsewhere and remove the `attachments` directory manually. The attachments themselves are now all located in your environment below the `files/attachments` directory.
    111 ===== Behavior of `[ticket] default_owner` changed
    112 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.
    114 ==== Upgrading from Trac 0.11 to Trac 0.12
    116 ===== Python 2.3 no longer supported
    117 The minimum supported version of Python is now 2.4.
    119 ===== SQLite v3.x required
    120 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.
    122 ===== [trac:PySqlite] 2 required
    123 [trac:PySqlite] 1.1.x is no longer supported. Please install 2.5.5 or later if possible, see [#Tracdatabaseupgrade Trac database upgrade] below.
    125 ===== Multiple Repository Support
    126 The latest version includes support for multiple repositories. If you plan to add more repositories to your Trac instance, please refer to TracRepositoryAdmin#Migration.
    128 This may be of interest to users with only one repository, since there is now a way to avoid the potentially costly resync check at every request.
    130 ===== Resynchronize the Trac Environment Against the Source Code Repository
    132 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:
    134 {{{#!sh
    135 trac-admin /path/to/projenv repository resync '*'
    136 }}}
    138 ===== Improved repository synchronization
    139 In addition to supporting multiple repositories, there is now a more efficient method for synchronizing Trac and your repositories.
    141 While 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.
    143 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.
    145 ===== Authz permission checking
    146 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.
    148 ===== Microsecond timestamps
    149 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.
    151 ==== Upgrading from Trac 0.10 to Trac 0.11
    152 ===== Site Templates and Styles
    153 The templating engine has changed in 0.11 to Genshi, please look at TracInterfaceCustomization for more information.
    155 If you are using custom CSS 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.
    157 ===== Trac Macros, Plugins
    158 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.
    160 ===== For FCGI/WSGI/CGI users
    161 For those who run Trac under the CGI environment, run this command in order to obtain the trac.*gi file:
    162 {{{#!sh
    163 trac-admin /path/to/env deploy /deploy/directory/path
    164 }}}
    166 This 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.
    168 ===== Web Admin plugin integrated
    169 If you had the [trac:WebAdmin] plugin installed, you can uninstall it as it is part of the Trac code base since 0.11.
    171 ===== New Default Configurable Workflow
    173 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.
    175 Graphically, that looks like this:
    177 {{{#!Workflow width=500 height=240
    178 leave = * -> *
    179 leave.operations = leave_status
    180 leave.default = 1
    181 accept = new -> assigned
    182 accept.permissions = TICKET_MODIFY
    183 accept.operations = set_owner_to_self
    184 resolve = new,assigned,reopened -> closed
    185 resolve.permissions = TICKET_MODIFY
    186 resolve.operations = set_resolution
    187 reassign = new,assigned,reopened -> new
    188 reassign.permissions = TICKET_MODIFY
    189 reassign.operations = set_owner
    190 reopen = closed -> reopened
    191 reopen.permissions = TICKET_CREATE
    192 reopen.operations = del_resolution
    193 }}}
    195 There are some significant caveats in this, such as accepting a ticket sets it to 'assigned' state, and assigning a ticket sets it to 'new' state. So you will probably want to migrate to "basic" workflow; [trac:source:trunk/contrib/workflow/migrate_original_to_basic.py contrib/workflow/migrate_original_to_basic.py] may be helpful. See TracWorkflow for a detailed description of the new basic workflow.
    197 === 7. Restart the Web Server #RestarttheWebServer
    199 If you are not running [wiki:TracCgi CGI], reload the new Trac code by restarting your web server.
    201 == Known Issues
    203 === Customized Templates
    205 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 aware 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.
    207 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 [trac:TracDev/ApiChanges] pages.
    209 === !ZipImportError
    211 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.
    212 See [trac:#7014] for details.
    214 === Wiki Upgrade
    215 `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.
    217 === Trac database upgrade
    219 A known issue in some versions of [trac: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].
    221 === Parent dir
    222 If you use a Trac parent env configuration and one of the plugins in one child does not work, none of the children will work.
    224 == Related topics
    226 === Upgrading Python
    228 Upgrading Python to a newer version will require reinstallation of Python packages: Trac itself of course, but also [http://pypi.python.org/pypi/setuptools easy_install], if you've been using that. If you are using Subversion, you'll also need to upgrade the Python bindings for svn.
    230 ==== Windows and Python 2.6
    232 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 [trac:TracSubversion]. That package works without tweaking.
    234 === Changing Database Backend
    236 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.
    238 === Upgrading from older versions of Trac #OlderVersions
    240 For upgrades from versions older than Trac 0.10, refer first to [trac:wiki:0.10/TracUpgrade#SpecificVersions].
    242 -----
    243 See also: TracGuide, TracInstall
Note: See TracChangeset for help on using the changeset viewer.