Changes between Version 87 and Version 88 of TracUpgrade
- Timestamp:
- Feb 26, 2011, 12:21:26 PM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracUpgrade
v87 v88 3 3 [[TracGuideToc]] 4 4 [[TranslatedPages]] 5 [[PageOutline(2-3,,inline,unnumbered)]] 5 6 6 7 == Instructions == … … 8 9 Typically, there are seven steps involved in upgrading to a newer version of Trac: 9 10 10 === 1. Update the Trac Code === #UpdatetheTracCode 11 === 1. Bring your server off-line 12 13 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 internal errors. 14 15 === 2. Update the Trac Code === #UpdatetheTracCode 11 16 12 17 Get the new version as described in TracInstall, or your operating system specific procedure. … … 30 35 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. 31 36 32 === 2. Upgrade the Trac Environment === #UpgradetheTracEnvironment37 === 3. Upgrade the Trac Environment === #UpgradetheTracEnvironment 33 38 34 39 Environment upgrades are not necessary for minor version releases unless otherwise noted. … … 47 52 }}} 48 53 49 === 3. Update the Trac Documentation === #UpdatetheTracDocumentation54 === 4. Update the Trac Documentation === #UpdatetheTracDocumentation 50 55 51 56 Every [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: … … 57 62 58 63 59 === 4. Refresh static resources ===64 === 5. Refresh static resources === 60 65 61 66 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: … … 70 75 }}} 71 76 72 === 5. Steps specific to a given Trac version ===77 === 6. Steps specific to a given Trac version === 73 78 ==== Upgrading from Trac 0.11 to Trac 0.12 ==== 74 79 … … 87 92 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. 88 93 89 ===== Resynchronize the Trac Environment Against the Source Code Repository === 94 ===== Resynchronize the Trac Environment Against the Source Code Repository ===== 90 95 91 96 Each [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: … … 134 139 == Known Issues == 135 140 136 === parent dir === 137 If you use a trac parent env configuration and one of the plugins in one child does not work, none of the children work. 141 Things you should pay attention to, while upgrading. 142 143 === !ZipImportError === 144 145 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. 146 See [trac:#7014] for details. 138 147 139 148 === Wiki Upgrade === … … 144 153 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]. 145 154 146 == Upgrading Python == 155 === parent dir === 156 If you use a trac parent env configuration and one of the plugins in one child does not work, none of the children work. 157 158 == Related topics 159 160 === Upgrading Python === 147 161 148 162 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. 149 163 150 === Windows and Python 2.6===164 ==== Windows and Python 2.6 ==== 151 165 152 166 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. 153 167 154 == Changing Database Backend==155 === SQLite to PostgreSQL===168 === Changing Database Backend === 169 ==== SQLite to PostgreSQL ==== 156 170 157 171 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 158 172 159 == Older Versions ==173 === Upgrading from older versions of Trac === #OlderVersions 160 174 161 175 For upgrades from versions older than Trac 0.10, refer first to [trac:wiki:0.10/TracUpgrade#SpecificVersions].
