You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Mark Bohlman <mb...@tcicredit.com> on 2004/06/29 16:35:18 UTC

SVN command line and Cygwin problem (and resolution) on Windows - FYI

All,

    Recently I modified the my startup batch file for cygwin on WinXP 
including setting the CYGWIN environment variable to 'tty' as 
recommended for emacs usage.  This has an unpleasant side effect of 
hiding the password prompt for a new repository (or if you blow away the 
credential auth files under %APPDATA%/Subversion/auth).  Without the 
auth files from the command line you are prompted for the password (I'm 
using domain authentication with the sspi options in my httpd.conf file).

So a command line like:
    $ svn ls http://server/repos

results in output like:
    Authentication realm: <http://a_server:80>my text blurb here

Hitting return shows the password prompt one time along with an 
additional message and a username prompt as in:
    Password for 'fred':
    Authentication realm: <http://a_server:80>my text blurb here
    Username:


You can enter a new username, but nothing ever comes back.  Ctrl-C gets 
you out of this.  Drove me nuts for a bit (ok, so that's a short trip) 
until I remembered making that change to my Cygwin environment.

Reverting (yeah, Subversion) the startup batch file for Cygwin allowed 
me to be prompted properly again, and have my password accepted (and the 
auth file properly created).

This is an FYI for anyone else with a similar problem.  Now to get my 
emacs back :(

-- Mark


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: SVN command line and Cygwin problem (and resolution) on Windows - FYI

Posted by Mark Bohlman <mb...@tcicredit.com>.
Max Bowsher wrote:
> Mark Bohlman wrote:
> 
>>Max,
>>
>>    Looks like I was a bit premature in being happy about the cygwin
>>version.  Initial testing with the following file:/// access command did
>>not work.
>>
>>$ svn ls file:///ap
>>svn: Unable to open an ra_local session to URL
>>svn: Unable to open repository 'file:///ap'
>>
>>The native Windows build does work still:
>>$ ./svn ls file:///ap
>>t3/
>>test/
>>xml/
>>
>>Note that this was a repository that was built with the native Windows
>>version of code.
>>
>>Building a repository with the Cygwin version of svnadmin generates the
>>following error message when trying to access it with the native Windows
>>svn command:
>>$ svnadmin create /ap1
>>#import some files
>>
>>$ svn ls file:///ap1
>>t3/
>>test/
>>xml/
>>
>># in the Windows version (e.g. Program Files/Subversion/bin/)
>>$ ./svn ls file:///ap1
>>svn: Unable to open an ra_local session to URL
>>svn: Unable to open repository 'file:///ap1'
>>svn: Berkeley DB error while opening environment for filesystem /ap1/db:
>>Invalid argument
>>
>>So it looks like the modes of code being used cannot be mixed.
> 
> 
> Ah, yes. Cygwin and native Windows are effectively different OSes as far as BDB is concerned.
> Therefore, the format of shared region files (__db.00*) is not compatible between the two.
> 
> I do not run into this problem, because I'm so acclimated to a bash shell, I find the Windows cmd shell intolerable, and everything
> in subversion.
> 
> If you need to access a repository via both a native Windows and a Cygwin client, you must use svn:// or http:// access for the
> client which does not match the repository in terms of native/Cygwin. You may switch a repository from native to Cygwin and back
> again by *making sure it is not being accessed* and running "svnadmin recover" on it.
> 
> Max.

Thanks Max - now can you convince my co-workers to use bash as well?? 
;-)  I wish!

"That's the nice thing about standards - there are so many to choose from!"


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: SVN command line and Cygwin problem (and resolution) on Windows - FYI

Posted by Max Bowsher <ma...@ukf.net>.
Mark Bohlman wrote:
> Max,
>
>     Looks like I was a bit premature in being happy about the cygwin
> version.  Initial testing with the following file:/// access command did
> not work.
>
> $ svn ls file:///ap
> svn: Unable to open an ra_local session to URL
> svn: Unable to open repository 'file:///ap'
>
> The native Windows build does work still:
> $ ./svn ls file:///ap
> t3/
> test/
> xml/
>
> Note that this was a repository that was built with the native Windows
> version of code.
>
> Building a repository with the Cygwin version of svnadmin generates the
> following error message when trying to access it with the native Windows
> svn command:
> $ svnadmin create /ap1
> #import some files
>
> $ svn ls file:///ap1
> t3/
> test/
> xml/
>
> # in the Windows version (e.g. Program Files/Subversion/bin/)
> $ ./svn ls file:///ap1
> svn: Unable to open an ra_local session to URL
> svn: Unable to open repository 'file:///ap1'
> svn: Berkeley DB error while opening environment for filesystem /ap1/db:
> Invalid argument
>
> So it looks like the modes of code being used cannot be mixed.

Ah, yes. Cygwin and native Windows are effectively different OSes as far as BDB is concerned.
Therefore, the format of shared region files (__db.00*) is not compatible between the two.

I do not run into this problem, because I'm so acclimated to a bash shell, I find the Windows cmd shell intolerable, and everything
in subversion.

If you need to access a repository via both a native Windows and a Cygwin client, you must use svn:// or http:// access for the
client which does not match the repository in terms of native/Cygwin. You may switch a repository from native to Cygwin and back
again by *making sure it is not being accessed* and running "svnadmin recover" on it.

Max.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: SVN command line and Cygwin problem (and resolution) on Windows - FYI

Posted by Mark Bohlman <mb...@tcicredit.com>.
Mark Bohlman wrote:
> Max Bowsher wrote:
> 
>> Mark Bohlman wrote:
>>
>>> All,
>>>
>>>    Recently I modified the my startup batch file for cygwin on WinXP
>>> including setting the CYGWIN environment variable to 'tty' as
>>> recommended for emacs usage.  This has an unpleasant side effect of
>>> hiding the password prompt for a new repository (or if you blow away the
>>> credential auth files under %APPDATA%/Subversion/auth).  Without the
>>> auth files from the command line you are prompted for the password (I'm
>>> using domain authentication with the sspi options in my httpd.conf 
>>> file).
>>>
>>> So a command line like:
>>>    $ svn ls http://server/repos
>>>
>>> results in output like:
>>>    Authentication realm: <http://a_server:80>my text blurb here
>>>
>>> Hitting return shows the password prompt one time along with an
>>> additional message and a username prompt as in:
>>>    Password for 'fred':
>>>    Authentication realm: <http://a_server:80>my text blurb here
>>>    Username:
>>>
>>>
>>> You can enter a new username, but nothing ever comes back.  Ctrl-C gets
>>> you out of this.  Drove me nuts for a bit (ok, so that's a short trip)
>>> until I remembered making that change to my Cygwin environment.
>>
>>
>>
>> Yes, if you are using a *native Windows* subversion. If you use a 
>> *Cygwin* subversion, you won't have this problem (and, as an extra
>> bonus, a Cygwin subversion will understand Cygwin unix-style paths).
>>
>> Max.
> 
> 
> Thanks Max - this works like a charm!  Glad that Subversion is part of 
> the Cygwin installs.  I just hadn't gotten round to updating since the 
> announcement.
> 
> -- Mark

Max,

    Looks like I was a bit premature in being happy about the cygwin 
version.  Initial testing with the following file:/// access command did 
not work.

$ svn ls file:///ap
svn: Unable to open an ra_local session to URL
svn: Unable to open repository 'file:///ap'

The native Windows build does work still:
$ ./svn ls file:///ap
t3/
test/
xml/

Note that this was a repository that was built with the native Windows 
version of code.

Building a repository with the Cygwin version of svnadmin generates the 
following error message when trying to access it with the native Windows 
svn command:
$ svnadmin create /ap1
#import some files

$ svn ls file:///ap1
t3/
test/
xml/

# in the Windows version (e.g. Program Files/Subversion/bin/)
$ ./svn ls file:///ap1
svn: Unable to open an ra_local session to URL
svn: Unable to open repository 'file:///ap1'
svn: Berkeley DB error while opening environment for filesystem /ap1/db:
Invalid argument

So it looks like the modes of code being used cannot be mixed.  Have 
other errors accessing via http:// that I'm not able to chase further at 
the moment.

-- Mark


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: SVN command line and Cygwin problem (and resolution) on Windows - FYI

Posted by Mark Bohlman <mb...@tcicredit.com>.
Max Bowsher wrote:

> Mark Bohlman wrote:
> 
>>All,
>>
>>    Recently I modified the my startup batch file for cygwin on WinXP
>>including setting the CYGWIN environment variable to 'tty' as
>>recommended for emacs usage.  This has an unpleasant side effect of
>>hiding the password prompt for a new repository (or if you blow away the
>>credential auth files under %APPDATA%/Subversion/auth).  Without the
>>auth files from the command line you are prompted for the password (I'm
>>using domain authentication with the sspi options in my httpd.conf file).
>>
>>So a command line like:
>>    $ svn ls http://server/repos
>>
>>results in output like:
>>    Authentication realm: <http://a_server:80>my text blurb here
>>
>>Hitting return shows the password prompt one time along with an
>>additional message and a username prompt as in:
>>    Password for 'fred':
>>    Authentication realm: <http://a_server:80>my text blurb here
>>    Username:
>>
>>
>>You can enter a new username, but nothing ever comes back.  Ctrl-C gets
>>you out of this.  Drove me nuts for a bit (ok, so that's a short trip)
>>until I remembered making that change to my Cygwin environment.
> 
> 
> Yes, if you are using a *native Windows* subversion. If you use a *Cygwin* subversion, you won't have this problem (and, as an extra
> bonus, a Cygwin subversion will understand Cygwin unix-style paths).
> 
> Max.

Thanks Max - this works like a charm!  Glad that Subversion is part of 
the Cygwin installs.  I just hadn't gotten round to updating since the 
announcement.

-- Mark


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: SVN command line and Cygwin problem (and resolution) on Windows - FYI

Posted by Max Bowsher <ma...@ukf.net>.
Mark Bohlman wrote:
> All,
>
>     Recently I modified the my startup batch file for cygwin on WinXP
> including setting the CYGWIN environment variable to 'tty' as
> recommended for emacs usage.  This has an unpleasant side effect of
> hiding the password prompt for a new repository (or if you blow away the
> credential auth files under %APPDATA%/Subversion/auth).  Without the
> auth files from the command line you are prompted for the password (I'm
> using domain authentication with the sspi options in my httpd.conf file).
>
> So a command line like:
>     $ svn ls http://server/repos
>
> results in output like:
>     Authentication realm: <http://a_server:80>my text blurb here
>
> Hitting return shows the password prompt one time along with an
> additional message and a username prompt as in:
>     Password for 'fred':
>     Authentication realm: <http://a_server:80>my text blurb here
>     Username:
>
>
> You can enter a new username, but nothing ever comes back.  Ctrl-C gets
> you out of this.  Drove me nuts for a bit (ok, so that's a short trip)
> until I remembered making that change to my Cygwin environment.

Yes, if you are using a *native Windows* subversion. If you use a *Cygwin* subversion, you won't have this problem (and, as an extra
bonus, a Cygwin subversion will understand Cygwin unix-style paths).

Max.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org