2.00 => 2.1.0 introduces error on deploy:update_code

[scott.a...@gmail.com]

Hi everyone,

I just upgraded from 2.0.0 to 2.1.0, and I'm getting this error. I
spent some time sifting through the code and trying to figure out what
had changed, with no luck, so I thought I'd ask the experts. Here's
what I see

With Capistrano 2.1.0:

~/rails/grapher/trunk $>cap deploy:update_code
* executing `deploy:update_code'
* executing "svn checkout -q -r907 svn+ssh://
user...@svn.somehost.com/path/to/right/place/in/repository /mnt/app/
grapher/releases/20071016211140 && (echo 907 > /mnt/app/grapher/
releases/20071016211140/REVISION)"
servers: ["somehost.com"]
[somehost.com] executing command
** [err] Permission denied, please try again.
** [err] Permission denied, please try again.
** [err] Permission denied (publickey,gssapi-with-mic,password).
** [err] svn: Connection closed unexpectedly
command finished
command "svn checkout -q -r907 svn+ssh://user...@svn.somehost.com/
path/to/right/place/in/repository /mnt/app/grapher/releases/
20071016211140 && (echo 907 > /mnt/app/grapher/releases/20071016211140/
REVISION)" failed on plotomatic.com

with Capistrano 2.0.0:

~/rails/grapher/trunk $>cap _2.0.0_ deploy:update_code
* executing `deploy:update_code'
* executing "svn checkout -q -r908 svn+ssh://
user...@svn.somehost.com/path/to/right/place/in/repository /mnt/app/
grapher/releases/20071016211231 && (echo 908 > /mnt/app/grapher/
releases/20071016211231/REVISION)"
servers: ["somehost.com"]
[somehost.com] executing command
** [out] user...@svn.somehost.com's password:
Password:
** [out]
** [out] user...@svn.somehost.com's password:
** [out]

As far as I can see, the difference is that it asks for my password in
2.0.0. I tried fooling around with setting :scm_username
and :scm_password, and setting :scm_prefer_prompt to true, but that
didn't help.

Hopefully that's enough information to make things clear, but let me
know if anything else would help.

Thanks in advance,

Scott Patten

[Jamis Buck]

Please try adding the following:

default_run_options[:pty] = true

And see if that makes any difference.

- Jamis

> --~--~---------~--~----~------------~-------~--~----~
> To unsubscribe from this group, send email to capistrano-
> unsub...@googlegroups.com
> For more options, visit this group at http://groups.google.com/
> group/capistrano
> -~----------~----~----~----~------~----~------~--~---
>

[scott.a...@gmail.com]

Oops, I don't think the previous thread was posted when I started
writing this one. That does the trick!

Thanks so much, Jamis.

Scott Patten

On Oct 16, 2:43 pm, Jamis Buck <ja...@37signals.com> wrote:
> Please try adding the following:
>
> default_run_options[:pty] = true
>
> And see if that makes any difference.
>
> - Jamis
>

> On Oct 16, 2007, at 3:39 PM, scott.a.pat...@gmail.com wrote:
>
>
>
> > Hi everyone,
>
> > I just upgraded from 2.0.0 to 2.1.0, and I'm getting this error. I
> > spent some time sifting through the code and trying to figure out what
> > had changed, with no luck, so I thought I'd ask the experts. Here's
> > what I see
>
> > With Capistrano 2.1.0:
>
> > ~/rails/grapher/trunk $>cap deploy:update_code
> > * executing `deploy:update_code'
> > * executing "svn checkout -q -r907 svn+ssh://

> > usern...@svn.somehost.com/path/to/right/place/in/repository /mnt/app/

> > grapher/releases/20071016211140 && (echo 907 > /mnt/app/grapher/
> > releases/20071016211140/REVISION)"
> > servers: ["somehost.com"]
> > [somehost.com] executing command
> > ** [err] Permission denied, please try again.
> > ** [err] Permission denied, please try again.
> > ** [err] Permission denied (publickey,gssapi-with-mic,password).
> > ** [err] svn: Connection closed unexpectedly
> > command finished

> > command "svn checkout -q -r907 svn+ssh://usern...@svn.somehost.com/

> > path/to/right/place/in/repository /mnt/app/grapher/releases/
> > 20071016211140 && (echo 907 > /mnt/app/grapher/releases/
> > 20071016211140/
> > REVISION)" failed on plotomatic.com
>
> > with Capistrano 2.0.0:
>
> > ~/rails/grapher/trunk $>cap _2.0.0_ deploy:update_code
> > * executing `deploy:update_code'
> > * executing "svn checkout -q -r908 svn+ssh://

> > usern...@svn.somehost.com/path/to/right/place/in/repository /mnt/app/

> > grapher/releases/20071016211231 && (echo 908 > /mnt/app/grapher/
> > releases/20071016211231/REVISION)"
> > servers: ["somehost.com"]
> > [somehost.com] executing command

> > ** [out] usern...@svn.somehost.com's password:
> > Password:
> > ** [out]
> > ** [out] usern...@svn.somehost.com's password:

> > ** [out]
>
> > As far as I can see, the difference is that it asks for my password in
> > 2.0.0. I tried fooling around with setting :scm_username
> > and :scm_password, and setting :scm_prefer_prompt to true, but that
> > didn't help.
>
> > Hopefully that's enough information to make things clear, but let me
> > know if anything else would help.
>
> > Thanks in advance,
>
> > Scott Patten
>
> > >
>
>

> smime.p7s
> 3KDownload

[Jamis Buck]

Scott, out of curiosity, what operating system are you deploying to?
Some people have reported that when subversion is run without a pty,
it won't prompt, but I've not been able to duplicate that. I'd like
to have some idea of what to recommend when people report this issue.

Thanks,

Jamis

[scott.a...@gmail.com]

I'm deploying to Ubuntu 7.0.4 (Feisty) running on an EC2 instance.

I don't know if it matters, but:
I'm deploying from Mac OS X 10.4
The svn server is Fedora Core release 5 (Bordeaux)

I just did some more poking around, and found the following:

I ran in to the same problem deploying to a box running the same
Fedora release as my svn server (this one isn't on EC2). Adding
"default_run_options[:pty] = true" fixed it.

If I ssh in to my ec2 instance, I can run a svn checkout no problem:

EC2 prompt> svn checkout svn+ssh://us...@svn.somehost.com/path/to/right/
place/in/svn/repository /place/to/checkout/to <==== this works

but if I try to run the command directly from a ssh command like this:
Mac Prompt> ssh user...@somehost.com svn checkout svn+ssh://
us...@svn.somehost.com/path/to/right/place/in/svn/repository /place/to/
checkout/to
then it fails with the same error message:

Permission denied, please try again.
Permission denied, please try again.

Permission denied (publickey,gssapi-with-mic,password).
svn: Connection closed unexpectedly

Let me know if I can do anything else to help.

Scott

On Oct 16, 3:14 pm, Jamis Buck <ja...@37signals.com> wrote:
> Scott, out of curiosity, what operating system are you deploying to?
> Some people have reported that when subversion is run without a pty,
> it won't prompt, but I've not been able to duplicate that. I'd like
> to have some idea of what to recommend when people report this issue.
>
> Thanks,
>
> Jamis
>

> smime.p7s
> 3KDownload

[Paul Dowman]

I don't have this problem. I'm deploying to 7.04 on EC2 also (EC2 on Rails, http://ec2onrails.rubyforge.org/) and I can't reproduce this. I normally use:
set :deploy_via, :copy
set :copy_strategy, :export

but to test this I removed those lines so it would do an svn checkout and it didn't have a problem.

One difference between mine and Scott's setup is that I'm using http and he's using svn+ssh. I don't have an svn repo accessible by ssh so I can't test that right now.

The svn version on the server is 1.4.3.

Paul

--
http://pauldowman.com

[Jonathan del Strother]

On Oct 16, 11:14 pm, Jamis Buck <ja...@37signals.com> wrote:
> Scott, out of curiosity, what operating system are you deploying to?
> Some people have reported that when subversion is run without a pty,
> it won't prompt, but I've not been able to duplicate that. I'd like
> to have some idea of what to recommend when people report this issue.

FWIW, I'm getting this problem when deploying to EngineYard (gentoo),
accessing our git repository over ssh. default_run_options[:pty] =
true has fixed it for now.

[gregoryofmanhattan]

FYI same behavior from OS X tiger to rhel 3
2.10 reported permission problems on svn+ssh export until i added
default_run_options[:pty] = true

On Oct 16, 5:14 pm, Jamis Buck <ja...@37signals.com> wrote:
> Scott, out of curiosity, what operating system are you deploying to?
> Some people have reported that when subversion is run without a pty,
> it won't prompt, but I've not been able to duplicate that. I'd like
> to have some idea of what to recommend when people report this issue.
>
> Thanks,
>
> Jamis
>

> smime.p7s
> 3KDownload