bzr-svn new behaviour regarding authentication

[Jelmer Vernooij]

  On 08/28/2010 11:35 AM, Russel Winder wrote:
> Jelmer,
>
> On Thu, 2010-08-26 at 09:47 +0100, Russel Winder wrote:
>> Jelmer,
>>
>> Since one of the bzr-svn updates a few days ago, some Subversion sites
>> are now asking authentication questions that they never used to.  So for
>> example:
>>
>>          Using saved parent location: http://clam-project.org/clam/trunk/CLAM/scons/sconstools
>>          HTTP clam-project.org, Realm: 'clam' username:
>>          HTTP @clam-project.org, Realm: 'clam' password:
>>          No revisions to pull.
>>
>> I don't ever recollect having accounts on the affected repositories so
>> perhaps this is an anonymous access issue?  I don't get authentication
>> challenges for GoogleCode and Tigiris where I do have accounts, the
>> Subversion authentication data seems to be used.
>>
>> The irritation is that all my update scripts now block awaiting input
>> for these questions when previously they sailed right through.
>>
>> Thanks.
> As well as this behaviour, I am finding that svn-import no longer
> imports Subversion repositories :-((((
>
>          |>  bzr info
>          Shared repository (format: 2a)
>          Location:
>            shared repository: .
>          |>  bzr info trunk
>          Repository branch (format: 2a)
>          Location:
>            shared repository: .
>            repository branch: trunk
>
>          Related branches:
>            parent branch: http://projects.cs.kent.ac.uk/projects/kroc/svn/kroc/trunk
>          |>  bzr svn-import http://projects.cs.kent.ac.uk/projects/kroc/svn/kroc .
>          bzr: ERROR: Not a branch: "http://projects.cs.kent.ac.uk/projects/kroc/svn/kroc/".
>          |>  svn ls http://projects.cs.kent.ac.uk/projects/kroc/svn/kroc
>          branches/
>          tags/
>          trunk/
>          |>
>
> Basically bzr-svn isn't what it used to be :-(
I did some refactoring in bzr recently to make it easier to register 
custom control directories and to allow probing for foreign formats to 
be more flexible and efficient. Unfortunately this broke one of the 
hacks in bzr-svn (check for svn repositories before probing for other 
formats) to work around some broken http servers.

I'm now working on adding the right infrastructure in bzr to handle this 
in a saner manner; until then, I would suggest using svn+http:// or a 
released version of bzr-svn.

Cheers,

Jelmer