| 23 | | どのような場合でも、メジャーバージョンをアップグレードする場合 (0.8 から 0.9 にアップグレードするなど) 最初に今現在、存在している Trac のコードを削除することを''特に'' お勧めします。削除するには、 `trac` のディレクトリを Python の `lib/site-packages` ディレクトリから削除します。もし Trac `cgi-bin`, `htdocs`, `templates` ディレクトリも削除したいならば、それらは `share/trac` というディレクトリの中で見つかるでしょう。(正確なロケーションはプラットフォームに依存します) |
| | 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` |
| 50 | | 新しい Trac コードをリロードするために、 Web サーバを再起動する必要があります。 (古い [wiki:TracCgi CGI] プログラムを使用しているときは必要ありません。) |
| 51 | | |
| 52 | | == 特定のバージョン間のアップグレードについての付記 == |
| 53 | | |
| 54 | | 以下のセクションでは Trac の特定のバージョンにアップグレードするときにやらなければならないことについて記述します。 |
| 55 | | |
| 56 | | == 0.9-beta から 0.9 へのアップグレード == |
| 57 | | |
| 58 | | 静的リソース (CSS, javascript, 画像ファイル) のインクルードは機能しません。 trac.ini の `htdocs_location` を確認してください。 [wiki:TracModPython mod_python], [wiki:TracStandalone Tracd], [wiki:TracFastCgi FastCGI] を使用している場合、単にオプションを削除してください。 [wiki:TracCgi CGI] を使用している場合、Trac の `htdocs` ディレクトリへの URL マップを修正しなければいけません (以前の記述を削除し、 [wiki:TracCgi#静的なリソースをマッピングする 静的なリソースをマッピングする])。オプションを削除した後でも問題が残っている場合、ファイル `trac/siteconfig.py` のパスを確認し、誤っていれば修正してください。 |
| 59 | | |
| 60 | | Trac 0.9 のベータリリースでプラグインを使用しているか、組み込みコンポーネントの無効化を行っていたら、 [wiki:TracIni trac.ini] でコンポーネントの無効化 / 有効化のルールを更新しなければならないかもしれません。特にグローバルにインストールされたプラグインは、現在では明示的に有効化する必要があります。詳しくは TracPlugins と TracIni を参照して下さい。 |
| 61 | | |
| 62 | | タイムラインでチケットの全ての更新を表示させたい ("チケットの詳細" オプション) 場合も、 [wiki:TracIni trac.ini] での明示的な有効化が必要です: |
| | 58 | 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: |
| 73 | | from: PythonHandler trac.ModPythonHandler |
| 74 | | to: PythonHandler trac.web.modpython_frontend |
| | 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 | ==== Upgrading from Trac 0.10 to Trac 0.11 ==== |
| | 101 | ===== Site Templates and Styles ===== |
| | 102 | The templating engine has changed in 0.11 to Genshi, please look at TracInterfaceCustomization for more information. |
| | 103 | |
| | 104 | 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. |
| | 105 | |
| | 106 | ===== Trac Macros, Plugins ===== |
| | 107 | 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. |
| | 108 | |
| | 109 | ===== For FCGI/WSGI/CGI users ===== |
| | 110 | For those who run Trac under the CGI environment, run this command in order to obtain the trac.*gi file: |
| | 111 | {{{ |
| | 112 | trac-admin /path/to/env deploy /deploy/directory/path |
| 89 | | 0.8では追加のパーミッションを必要とする新しい機能が加わりました。 |
| 90 | | 新規にインストールを行なった場合は、 anonymous に ROADMAP_VIEW と MAILSTONE_VIEW パーミッションがデフォルトで与えられますが、 |
| 91 | | 既存のtrac をアップグレードしたときは、 |
| 92 | | これらのパーミッションを手動で与えなければなりません。: |
| 93 | | {{{ |
| 94 | | $ trac-admin /path/to/projectenv permission add anonymous MILESTONE_VIEW |
| 95 | | $ trac-admin /path/to/projectenv permission add anonymous ROADMAP_VIEW |
| 96 | | }}} |
| | 124 | == Known Issues == |
| | 125 | |
| | 126 | === parent dir === |
| | 127 | If you use a trac parent env configuration and one of the plugins in one child does not work, none of the children work. |
| | 128 | |
| | 129 | === Wiki Upgrade === |
| | 130 | `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. |
| | 131 | |
| | 132 | === Trac database upgrade === |
| | 133 | |
| | 134 | 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]. |
| | 135 | |
| | 136 | == Upgrading Python == |
| | 137 | |
| | 138 | 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. |
| | 139 | |
| | 140 | === Windows and Python 2.6 === |
| | 141 | |
| | 142 | 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. |
| | 143 | |
| | 144 | == Changing Database Backend == |
| | 145 | === SQLite to PostgreSQL === |
| | 146 | |
| | 147 | 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 |
| | 148 | |
| | 149 | == Older Versions == |
| | 150 | |
| | 151 | For upgrades from versions older than Trac 0.10, refer first to [trac:wiki:0.10/TracUpgrade#SpecificVersions]. |
