Changes between Version 74 and Version 75 of TracSubversion

Timestamp:

May 10, 2010, 11:03:04 AM (14 years ago)

Author:

Christian Boos

Comment:

s/tigris/apache/

TracSubversion

@@ -3 +3 @@
 = Trac and Subversion =
 
-Trac has supported the [http://subversion.tigris.org Subversion] VersioningSystemBackend since day one. Actually, Trac was even named `svntrac` back then!
+Trac has supported the [http://subversion.apache.org Subversion] VersioningSystemBackend since day one. Actually, Trac was even named `svntrac` back then!
 
 This page is intended to collect all the specific tips and tricks
@@ -13 +13 @@
 == Getting Subversion == 
 
-From subversion.tigris.org, in the [http://subversion.tigris.org/servlets/ProjectDocumentList download] area:
- - [http://subversion.tigris.org/servlets/ProjectDocumentList?folderID=260&expandFolder=260&folderID=91 Source] archives.
- - Pre-built binaries for [http://subversion.tigris.org/servlets/ProjectDocumentList?folderID=91&expandFolder=91&folderID=74 Windows].
-   With Subversion 1.4.6, there are pre-built installers for Python 2.3, 2.4, and 2.5.
+From subversion.apache.org:
+ - [http://subversion.apache.org/source-code.html Source Code]
+ - Pre-built binaries for [http://subversion.apache.org/packages.html Subversion Binary Packages].
  - On the various BSDs use ports or pkgsrc to install Subversion complete with Python bindings. For FreeBSD see use `/usr/ports/devel/py-subversion`. For pkgsrc use the `devel/py*-subversion` package for getting the bindings.
 
@@ -217 +216 @@
  If this succeeds, that's a good start.
 
- If it doesn't,  it usually means that your bindings are located in a place they can't be loaded from. So either move the `svn` and `libsvn` found in the /opt/subversion-xxx/lib/svn-python folder into your site-packages folder, or add the above folder to your PYTHONPATH, or create a [http://docs.python.org/lib/module-site.html svn.pth] file in your Python site-packages folder with the above folder path as its single line content (an example on a FreeBSD installation, again: /usr/local/lib/pythonN.N/site-packages/). One simple solution for rpm-based operating systems, is to install the subversion-python bindings rpm. The [http://subversion.tigris.org/project_packages.html official subversion site] points [http://summersoft.fay.ar.us/pub/subversion/latest/ here] to download those packages.
+ If it doesn't,  it usually means that your bindings are located in a place they can't be loaded from. So either move the `svn` and `libsvn` found in the /opt/subversion-xxx/lib/svn-python folder into your site-packages folder, or add the above folder to your PYTHONPATH, or create a [http://docs.python.org/lib/module-site.html svn.pth] file in your Python site-packages folder with the above folder path as its single line content (an example on a FreeBSD installation, again: /usr/local/lib/pythonN.N/site-packages/). One simple solution for rpm-based operating systems, is to install the subversion-python bindings rpm. The [http://subversion.apache.org/packages.html#redhat official subversion site] points [http://summersoft.fay.ar.us/pub/subversion/latest/ here] to download those packages.
 
  If you get the message {{{ImportError: libsvn_swig_py-1.so.0: cannot open shared object file: No such file or directory}}} even though you can see the .so file in the correct place, then try {{{ldconfig -v}}} as root.
@@ -293 +292 @@
 
  * !ReadTheFineBook: http://svnbook.red-bean.com and/or the   
-   [http://subversion.tigris.org/faq.html FAQ]
+   [http://subversion.apache.org/faq.html FAQ]
  * There's also a `#svn` channel on the `freenode` IRC network
  * If you think you've found a bug in Subversion, read these 
-   [http://subversion.tigris.org/project_issues.html instructions]
-
+   [http://subversion.apache.org/issue-tracker.html instructions]
+