Rev 1261: Update docs about new build instructions. in

Jelmer Vernooij jelmer at
Sun Jun 22 09:09:12 BST 2008


revno: 1261
revision-id: jelmer at
parent: jelmer at
committer: Jelmer Vernooij <jelmer at>
branch nick: 0.4
timestamp: Sun 2008-06-22 10:09:10 +0200
  Update docs about new build instructions.
  FAQ                            faq-20070910195147-p9u38s9wplds2d4o-1
  NEWS                           news-20061231030336-h9fhq245ie0de8bs-1
  README                         README-20051120210643-bd274a2fef9aed6a
=== modified file 'FAQ'
--- a/FAQ	2008-06-16 16:59:02 +0000
+++ b/FAQ	2008-06-22 08:09:10 +0000
@@ -13,23 +13,8 @@
 One way to work around this problem is to Ctrl+C the branch operation 
 and restart it.
-I am unable to access a repository that requires user/password authentication or uses self-signed SSL certificates
-The Python bindings required for password prompting are only present in 
-version 1.5 of Subversion so password prompting is only possible if 
-you have that version installed.
-If you have an older version of Subversion installed, bzr-svn can 
-use passwords cached by Subversion or credentials specified in the URL. 
-Subversion can be forced to cache the password by accessing the repository 
-using the Subversion command-line client. 
-For example, try running 'svn info <url>'. 
-You can specify the username and password in the URL in the standard way, e.g.::
-  $ bzr co svn+
+I am unable to access a repository that uses self-signed SSL certificates
 If you are using a Subversion repository over http or https it may be 
 necessary to prefix the repository URL with "svn+", e.g. 

=== modified file 'NEWS'
--- a/NEWS	2008-06-08 23:30:15 +0000
+++ b/NEWS	2008-06-22 08:09:10 +0000
@@ -1,7 +1,15 @@
-bzr-svn 0.4.11	UNRELEASED
+bzr-svn 0.4.11    UNRELEASED
+   * bzr-svn now comes with its own Python bindings for the Subversion 
+     libraries, removing the need for a unreleased version of Subversion and 
+     improving performance.
+     It does however mean the extensions have to be built. This requires 
+     the Subversion development libraries and should be possible by 
+     simply running ``make`` from the plugin directory.
    * Now uses absolute imports and no longer adds plugin directory to the system path.
@@ -114,6 +122,12 @@
 bzr-svn 0.4.9    2008-03-23
+   * The Python-Subversion bindings are no longer necessary. Instead, 
+     bzr-svn now comes with its own Python bindings for the Subversion 
+     libraries.
    * Set revision properties when possible.
@@ -137,6 +151,8 @@
    * Be a bit quieter with messages about experimental mappings. (#162496)
+   * Properly warn when trying to open a working copy with a newer version.
    * More correct implementation of Repository.get_ancestry(). 
    * Properly use current branching scheme when following branches. (#183361)

=== modified file 'README'
--- a/README	2008-05-18 12:31:57 +0000
+++ b/README	2008-06-22 08:09:10 +0000
@@ -165,17 +165,13 @@
 If you are using Python 2.4, you will need to have the pysqlite module installed. Python 2.5 and higher have sqlite support built in. 
-Python-Subversion >= 1.5
+Subversion development files
+You need the Subversion libraries, including the development files. This should
+be readily packaged for most platforms. The package name for Debian 
+and Debian-based distributions is ``libsvn-dev``.
-You also need a fairly recent version of the official Python bindings to the 
-Subversion libraries. At the moment, the svn plugin only works with 
-Subversion 1.5. The python-subversion (not python-svn!) package 
-in Ubuntu since Feisty and Debian since Etch also contain the 
-required changes. 
-The plugin requires a couple of fixes to the Python bindings for Subversion that are only available in Subversion 1.5 and higher. Subversion 1.5 has not been released yet, but packages with the appropriate patches applied to older versions are available for some platforms.
@@ -198,7 +194,7 @@
 Simply place this directory in ~/.bazaar/plugins and you should be able 
 to check out branches from Subversion using bzr. Make sure the directory 
-name is 'svn'.
+name is 'svn'. The plugin has to be built as well by running ``make``.

More information about the bazaar-commits mailing list