Bienvenue sur PostGIS.fr

Bienvenue sur PostGIS.fr , le site de la communauté des utilisateurs francophones de PostGIS.

PostGIS ajoute le support d'objets géographique à la base de données PostgreSQL. En effet, PostGIS "spatialise" le serverur PostgreSQL, ce qui permet de l'utiliser comme une base de données SIG.

Maintenu à jour, en fonction de nos disponibilités et des diverses sorties des outils que nous testons, nous vous proposons l'ensemble de nos travaux publiés en langue française.

Changes between Initial Version and Version 1 of TracUpgrade


Ignore:
Timestamp:
21/09/2011 00:47:47 (7 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracUpgrade

    v1 v1  
     1= Upgrade Instructions = 
     2[[TracGuideToc]] 
     3 
     4== Instructions == 
     5 
     6Typically, there are five steps involved in upgrading to a newer version of Trac: 
     7 
     8=== 1. Update the Trac Code === #UpdatetheTracCode 
     9 
     10Get the new version as described in TracInstall, or your operating system specific procedure. 
     11 
     12If you already have a 0.11 version of Trac installed via `easy_install`, it might be the easiest to use it also to upgrade you Trac installation. 
     13 
     14{{{ 
     15# easy_install --upgrade Trac=0.12beta1 
     16}}} 
     17(once beta1 is released, that is) 
     18 
     19If you do a manual (not operating system specific) upgrade, you should also stop any running Trac server before the installation. Doing "hot" upgrades is not advised, especially not on Windows ([trac:ticket:7625 #7265]). 
     20 
     21You 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 .eggs from former versions. 
     22The location of the site-packages directory depends on the operating system, and the location in which Python was installed. However, the following locations are common: 
     23 * on Linux: `/usr/lib/python2.X/site-packages` 
     24 * on Windows: `C:\Python2.X\lib\site-packages` 
     25 * on MacOSX: `/Library/Python/2.X/site-packages` 
     26 
     27You 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). 
     28 
     29This cleanup is not mandatory, but it 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. 
     30 
     31=== 2. Upgrade the Trac Environment === #UpgradetheTracEnvironment 
     32 
     33Environment upgrades are not necessary for minor version releases unless otherwise noted.  
     34 
     35After 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]: 
     36{{{ 
     37trac-admin /path/to/projenv upgrade 
     38}}} 
     39 
     40This command will do nothing if the environment is already up-to-date. 
     41 
     42Note that a backup of your database will be performed automatically prior to the upgrade.  
     43This feature is relatively new for the PostgreSQL or MySQL database backends, so if it fails, you will have to backup the database manually. Then, to perform the actual upgrade, run: 
     44{{{ 
     45trac-admin /path/to/projenv upgrade --no-backup 
     46}}} 
     47 
     48=== 3. Update the Trac Documentation === #UpdatetheTracDocumentation 
     49 
     50Every [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: 
     51{{{ 
     52trac-admin /path/to/projenv wiki upgrade 
     53}}} 
     54 
     55Note that this procedure will of course leave your `WikiStart` page intact. 
     56 
     57=== 4. Resynchronize the Trac Environment Against the Source Code Repository === 
     58 
     59Each [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: 
     60 
     61{{{ 
     62trac-admin /path/to/projenv resync 
     63}}} 
     64 
     65=== 5. Steps specific to a given Trac version  === 
     66==== Upgrading from Trac 0.11 to Trac 0.12 ==== 
     67===== Python 2.3 no longer supported ===== 
     68The minimum supported version of python is now 2.4 
     69 
     70===== SQLite v3.x required ===== 
     71SQLite v2.x is no longer supported, if you happen to still use a Trac database using this format, you'll need to convert it to SQLite v3.x first. See [trac:PySqlite#UpgradingSQLitefrom2.xto3.x] for details. 
     72 
     73===== Multiple Repository Support ===== 
     74If you plan to add more repositories to your Trac instance, as this is now possible with the newly introduced multiple repository support, please refer to TracRepositoryAdmin#Migration. 
     75 
     76This can be of interest even if you only have one repository, as there's now a way to avoid the potentially costly resync check at every request. 
     77 
     78===== Improved repository synchronization ===== 
     79In addition to supporting multiple repositories, a new more efficient method for synchronizing Trac and your repositories was implemented. 
     80 
     81While 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. 
     82 
     83Note 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. 
     84 
     85==== Upgrading from Trac 0.10 to Trac 0.11 ==== 
     86===== Site Templates and Styles ===== 
     87The templating engine has changed in 0.11 to Genshi, please look at TracInterfaceCustomization for more information. 
     88 
     89If 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. 
     90 
     91===== Trac Macros, Plugins ===== 
     92The Trac macros will need to be adapted, as the old-style wiki-macros are not supported anymore (due to the drop of [trac:ClearSilver 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. 
     93 
     94===== For FCGI/WSGI/CGI users ===== 
     95For those who run Trac under the CGI environment, run this command in order to obtain the trac.*gi file: 
     96{{{ 
     97trac-admin /path/to/env deploy /deploy/directory/path 
     98}}} 
     99 
     100This 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. 
     101 
     102===== Web Admin plugin integrated ===== 
     103If you had the webadmin plugin installed, you can uninstall it as it is part of the Trac code base since 0.11. 
     104 
     105=== 6. Restart the Web Server === #RestarttheWebServer 
     106 
     107If you are not running [wiki:TracCgi CGI], reload the new Trac code by restarting your web server. 
     108 
     109== Known Issues == 
     110 
     111=== parent dir === 
     112If you use a trac parent env configuration and one of the plugins in one child does not work, none of the children work. 
     113 
     114=== Wiki Upgrade === 
     115`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. 
     116 
     117 
     118== Changing Database Backend == 
     119=== SQLite to PostgreSQL === 
     120 
     121The [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 
     122 
     123== Older Versions == 
     124 
     125For upgrades from versions older than Trac 0.10, refer first to [trac:wiki:0.10/TracUpgrade#SpecificVersions]. 
     126 
     127----- 
     128See also: TracGuide, TracInstall