| 18 | | すでに存在する Trac のコードを削除するには、 Python の `lib/site-packages` ディレクトリから `trac` ディレクトリか、 Trac の .egg の古いバージョンを削除します。 |
| 19 | | site-packages ディレクトリの位置は OS のシステム、および Python のインストールパスにより異なりますが、一般的には以下の位置にあります: |
| 20 | | * Linux を使用している場合: /usr/lib/python2.X/site-packages |
| 21 | | * Windows を使用している場合: C:\Python2.X\lib\site-packages |
| 22 | | * MacOSX を使用している場合: /Library/Python2.X/site-packages |
| | 20 | 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. |
| | 21 | 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: |
| | 22 | * on Linux: `/usr/lib/python2.X/site-packages` |
| | 23 | * on Windows: `C:\Python2.X\lib\site-packages` |
| | 24 | * on MacOSX: `/Library/Python/2.X/site-packages` |
| 63 | | CGI で Trac を起動している場合、以下のコマンドを実行して trac.cgi ファイルを取得してください: |
| | 64 | === 5. Refresh static resources === |
| | 65 | |
| | 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: |
| | 67 | {{{ |
| | 68 | trac-admin /path/to/env deploy /deploy/path |
| | 69 | }}} |
| | 70 | this will extract static resources and CGI scripts (`trac.wsgi`, etc) from new Trac version and its plugins into `/deploy/path`. |
| | 71 | |
| | 72 | Some web browsers cache CSS and Javascript files persistently, so you may need to instruct your users to manually erase the contents of their browser's cache. |
| | 73 | |
| | 74 | === 6. Steps specific to a given Trac version === |
| | 75 | ==== Upgrading from Trac 0.11 to Trac 0.12 ==== |
| | 76 | ===== Python 2.3 no longer supported ===== |
| | 77 | The minimum supported version of python is now 2.4 |
| | 78 | |
| | 79 | ===== SQLite v3.x required ===== |
| | 80 | 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. |
| | 81 | |
| | 82 | ===== PySqlite 2 required ===== |
| | 83 | PySqlite 1.1.x is no longer supported. Please install 2.5.5 or later if possible (see [#Tracdatabaseupgrade Trac database upgrade] below). |
| | 84 | |
| | 85 | ===== Multiple Repository Support ===== |
| | 86 | The latest version includes support for multiple repositories. If you plan to add more repositories to your Trac instance, please refer to TracRepositoryAdmin#Migration. |
| | 87 | |
| | 88 | 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. |
| | 89 | |
| | 90 | ===== Improved repository synchronization ===== |
| | 91 | In addition to supporting multiple repositories, there is now a more efficient method for synchronizing Trac and your repositories. |
| | 92 | |
| | 93 | 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. |
| | 94 | |
| | 95 | 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. |
| | 96 | |
| | 97 | ===== Authz permission checking ===== |
| | 98 | 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). |
| | 99 | |
| | 100 | ===== Microsecond timestamps ===== |
| | 101 | 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. |
| | 102 | |
| | 103 | ==== Upgrading from Trac 0.10 to Trac 0.11 ==== |
| | 104 | ===== Site Templates and Styles ===== |
| | 105 | The templating engine has changed in 0.11 to Genshi, please look at TracInterfaceCustomization for more information. |
| | 106 | |
| | 107 | If you are using custom CSS styles 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. |
| | 108 | |
| | 109 | ===== Trac Macros, Plugins ===== |
| | 110 | 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. |
| | 111 | |
| | 112 | ===== For FCGI/WSGI/CGI users ===== |
| | 113 | For those who run Trac under the CGI environment, run this command in order to obtain the trac.*gi file: |
| 74 | | == 既知の問題 == #KnownIssues |
| 75 | | === 複数プロジェクトのホストに関して === #parentdir |
| 76 | | 複数のプロジェクトをホストした場合に、配下のプロジェクトのうち一つのプロジェクトで、プラグインの一つが動作していないとき、配下のすべてのプロジェクトではそのプラグインは動作していません。 |
| 77 | | === コアモジュールがロードされない === #somecoremoduleswontload |
| 78 | | Windows で Python 2.3 を使用している場合、最初にアンインストールを行わずにアップグレードすると時々発生します。 |
| 79 | | いくつかのモジュールは、以前はキャピタライズされていましたが、小文字のみに変更されました (例えば、 trac/About.py が trac/about.py に変更されるなど)。以下のようなメッセージが Trac のログに出てくる場合: |
| 80 | | {{{ |
| 81 | | ERROR: Skipping "trac.about = trac.about": (can't import "No module named about") |
| 82 | | }}} |
| 83 | | `Lib/site-packages/trac` ディレクトリを削除してから、再インストールしてください。 |
| 84 | | === Wiki Upgrade === WikiUpgrade |
| 85 | | `trac-admin` はページを削除しません。バージョン 0.10 では存在し、バージョン 0.11 では存在しないページはそのまま残ります。 (0.11 開発中に存在した !TracWikiMacros など) |
| | 125 | If you are not running [wiki:TracCgi CGI], reload the new Trac code by restarting your web server. |
| 96 | | Note: Trac 0.11 から Trac 0.10.4 や 0.10.5 にダウングレードするには、手作業が必要になります: |
| 97 | | {{{ |
| 98 | | $ sqlite3 db/trac.db "update system set value=20 where name='database_version'" |
| 99 | | }}} |
| 100 | | (あとで再度、正常にアップグレードすることができます) |
| | 137 | 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]. |
| | 138 | |
| | 139 | == Upgrading Python == |
| | 140 | |
| | 141 | 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. |
| | 142 | |
| | 143 | === Windows and Python 2.6 === |
| | 144 | |
| | 145 | If you've been using !CollabNet's Subversion package, you may need to uninstall that in favor of [http://alagazam.net/ Algazam], which has the Python bindings readily available (see TracSubversion). The good news is, that works with no tweaking. |
| | 146 | |
| | 147 | == Changing Database Backend == |
| | 148 | === SQLite to PostgreSQL === |
| | 149 | |
| | 150 | 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 |
| | 151 | |
| | 152 | == Older Versions == |
| | 153 | |
| | 154 | For upgrades from versions older than Trac 0.10, refer first to [trac:wiki:0.10/TracUpgrade#SpecificVersions]. |
