32 replies to this topic

[kai]

Mountain/\Ash, I had the same problem you had with svnx. It's been a while since you posted, but no one has replied yet and just in case you still need it (and for future reference)... You have to use "SSH with Keys" in order to log on properly, since svnx (and presumably many other svn programs) cannot authenticate using SSH.
So I Generated an public and private keypair for SSH, using this guide and uploaded the key to ~/.ssh/authorizedkeys, as per the directions in the guide. (I only made the SSH v2 key)

Then I downloaded SSHKeychain and added my private key. I used a private key with a passphrase, so I saved the passphrase using SSHKeychain. With SSHKeychain open, I open svnx and do put the whole "svn+ssh://..." in the path and everything works fine.

And this also solves your password issue, since I don't have to type in my password for SSH nor SVNX while I have SSHKeychain open. Of course, be careful with your private key, since that's all a h4x0r would need (and passphrase if you made one) to get into your account.

Kai

Thanks for the instuctions. Sure makes the setup easy.

I have no problems using this from the command line ("Terminal"), but when I try to commit/checkout/update through (SCPlugin v243 or svnX v0.9.6.4) I get the following error constantly:

CODE

Permission denied, please try again.
Permission denied, please try again.
Permission denied (publickey,password,keyboard-interactive).
svn: Commit failed (details follow):
svn: Connection closed unexpectedly

Process finished with exit status 1.

Also does anyone know how to save the password at the command prompt so that if I am stuck using it I don't need to re-type the [aso] password each time?

[b]

[floyd]

Does anyone know whether it's possible to set up a respository with http access on a shared account, or does that require VPS/dedicated?

[alfonx]

I just found a solution for this kind of problem:

CODE

Unable to write to standard output (stderr)

I had the same error. I logged into the server with ssh and there was actually an error reported after pwd. This error was some stupid typo in the .bashrc, and itself has nothing todo with the problem. But because there was any error-text while stating the shell, the shell wanted to write it to the stderr. So, to get rid of that problem:

check with ssh-login (e.g. putty for the pu**ys) that there are no error-messages after the login. If there are error-messages, check files like .bashrc /etc/profile ... for the reason.

good luck, alfonx

this should be: solved

Edited by alfonx, 14 July 2006 - 12:20 PM.

[digifer]

Been having some difficulties as well. This thread has been very helpful  

svnserve seems to be accessible from plink, so this no longer seems to be the problem.

what alfonx says is correct. I found out by using TortoisePlink from the command line and redirecting stderr to stdout and dumping to a file, that the shell was returning:

stdin not a tty

Or something like that.

After googling I found out that this is most likely because of

mesg y

in the bash profile.

So a workaround I did was to copy /etc/bashrc to ~/etc/bashrc and replace

mesg y

with

tty -s
if [ $? -eq 0 ]; then
    mesg y
fi

and finally point .bashrc to ~/etc/bashrc.

This is maybe not so good if Tim updates /etc/bashrc.. then ~/etc/bashrc  will not be updated.
Better workarounds welcomed.

With this workaround I seem to be able to use my normal shell password for TortoisePlink, and I can also create .ssh and use this way with a public and private key

Edited by digifer, 20 July 2006 - 05:39 PM.

[digifer]

BTW: I used this HOWTO to use ssh keys with TortoiseSVN.

If you don't feel like using passphrases, just don't use any.. it's unsafe though.

[mmonter]

I'm having the same issues with "Unable to write to standard output (stderr)".

What is the syntax to execute TortoisePlink via command line so that I can see what is exactly causing this error?  Basically how do I do what is mentioned in digifer's post?

Thanks in advance for the help.

what alfonx says is correct. I found out by using TortoisePlink from the command line and redirecting stderr to stdout and dumping to a file, that the shell was returning:

[mook]

What is the syntax to execute TortoisePlink via command line so that I can see what is exactly causing this error?  Basically how do I do what is mentioned in digifer's post?

Basically mmonter, I did this to make it work after all the 'Unable to write to standard output (stderr)' annoyances.

Backed up ~/.bashrc
Copied /etc/bashrc to ~/.bashrc
Pico'd ~/.bashrc to remove the line mesg y and replaced it with:

CODE

tty -s
if [ $? -eq 0 ]; then
mesg y
fi

Saved, and voila! Worked a treat

[mmonter]

What is the syntax to execute TortoisePlink via command line so that I can see what is exactly causing this error?  Basically how do I do what is mentioned in digifer's post?

Basically mmonter, I did this to make it work after all the 'Unable to write to standard output (stderr)' annoyances.

Backed up ~/.bashrc
Copied /etc/bashrc to ~/.bashrc
Pico'd ~/.bashrc to remove the line mesg y and replaced it with:

CODE

tty -s
if [ $? -eq 0 ]; then
mesg y
fi

Saved, and voila! Worked a treat

Thanks mook!  I believe I've got it working now.

[Mountain/\Ash]

Also if you want to checkout your files on to the same server that the repos is stored (ie. your ASO host), you can just do

CODE

svn checkout file:///home/ASO-USERNAME/svn/REPOS/

This seems much quicker that doing a SSH connection back to the same host.

[kabari]

I haven't had luck with any of this. Even after doing all the changes I still get the "cannot write to standard output" error. Also, even when I try a normal commit without using Tortoise it tells me the directory doesn't exist.

I don't think that it is letting me connect through svn+ssh. Any thoughts as to why this might be happening?

[DanSheldon]

I went ahead and added the op to the wiki: http://wiki.asmallorange.com/Subversion

[sagelt]

So this may be a stupid question, but is it possible to host a repository on ASO in such a way that it can be publicly available? The method posted here requires my username and password everytime, not a great option if I want a small repository to share with a couple of other people. Is hosting via the http or svn methods supported?