SVN version authentication fails when starting with emacs

I use native emacs 24.2 windows on my desktop configured to use cygwin bash .

When I run SVN from cygwin bash, everything works fine. It remembers my authorization credentials and connects to the repository. But when I try to run any version control command from emacs, I always get the following message:

svn: E170001: cannot connect to the repository at the URL ' https: //address.to.repo ' svn: E170001: OPTIONS ' https: //address.to.repo ': authorization failed: server authentication failed: rejected task

I also tried connecting to the PSVN interface, which also ends with the same error message. It is somehow strange that this does not work the same as with cygwin terminal and emacs. Any help on this would be appreciated.

+4
source share
2 answers

Solved now. The problem was that integration with Emacs NT cygwin still used the Windows HOME path instead of using the Cygwinized HOME directory.

0
source

I think the complete answer should be something like this:

  • SVN depends on the HOME path to find it on user preferences (like most Unix programs).
  • In cygwin, that varible has something like "/ home / pablo".
  • "/ home / pablo" really translated "drive: \ cygwin_dir \ home \ pablo"
  • Emacs-nt grabs its HOUSE from a Windows environment, so this is a different HOUSE than cygwin <
  • emac vc-svn is using the wrong path to find its settings.

So there are two solutions (maybe more):

  • Use emacs-nt to use cygwin HOME (so that means cygwinization means !!: O), for this you need setup-cygwin, but specifically you need one script, it depends on cygwin-mount. In this way, emacs-nt can understand the "style" of the Qigvin way.
  • (Not recommended). Another way I did is to force cygwin to use the HOME window through the cygwin soft link. ln -s /cygdrive/c/Users/pablo/Roaming/ /home/pablo
  • Make a soft link so that the Cygwin subversion dir points to windows one ln -s /cygdrive/c/users/pablo/AppData/Roaming/.subversion /home/pablo/.subversion

The second solution will cause cygwin ".bashrc" to fail. Therefore, environment variables and aliases defined there will not be defined. I still think this can be done, but I do not have the proper cygwin knowledge needed to configure this solution. So now I'm using solution number 3.

0
source

All Articles