Changes between Version 86 and Version 87 of TracUpgrade

Timestamp:

Feb 26, 2011, 12:00:35 PM (13 years ago)

Author:

Christian Boos

Comment:

resync repositories is actually a 0.11 → 0.12 specific step, it's not needed within 0.12.x → 0.12.y upgrades and probably won't be from 0.12.x to 0.13

TracUpgrade

@@ -56 +56 @@
 Note that this procedure will leave your `WikiStart` page intact.
 
-=== 4. Resynchronize the Trac Environment Against the Source Code Repository ===
 
-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:
-
-{{{
-trac-admin /path/to/projenv repository resync '*'
-}}}
-
-=== 5. Refresh static resources ===
+=== 4. Refresh static resources ===
 
 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:
@@ -77 +70 @@
 }}}
 
-=== 6. Steps specific to a given Trac version  ===
+=== 5. Steps specific to a given Trac version  ===
 ==== Upgrading from Trac 0.11 to Trac 0.12 ====
+
 ===== Python 2.3 no longer supported =====
 The minimum supported version of python is now 2.4
@@ -92 +86 @@
 
 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.
+
+===== Resynchronize the Trac Environment Against the Source Code Repository ===
+
+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:
+
+{{{
+trac-admin /path/to/projenv repository resync '*'
+}}}
 
 ===== Improved repository synchronization =====