Thanks Ryan. I appreciate the detailed information. It sounds like Mercurial
isn't seeing the proper directory when it invokes its own ssh functionality,
so we'll need to look further into it. It would help if someone
knowledgeable with Mercurial could do some digging to figure out why it's
not see
Actually, on reviewing the thread, I'm not sure #1 in my email was the
problem in John's original one. Checks #1 in #2 in my latest
response, however, were both problems for my install/setup until I
added "id_dsa" to the two (different) respective .ssh directory
locations.
And, as a nit, when I e
Hi Christian,
I run post-review from my laptop ("dev box") to submit review requests
to our remote RB server, which is running in a cloud VM.
For our RB server, we take a new VM with Ubuntu, install vanilla
apache, and issue an 'rb-site' command to install RB and host through
Apache. So, this is
Glad it works for you, though I want to understand this a bit more.
When you say you run post-review with a dev box, I assume you mean that it's
still Apache looking for the /var/www/.ssh/id_dsa, right? is that a
different install from the main install, or is it just that you're running
post-revie
I've been working with John on this, and we finally pounded out
something that works. We are running Review Board 1.5 RC1. Say we
have a code base repo with ssh string of:
ssh://some_u...@foo.codebasehq.com/path/to/repo.hg
. To generalize, it took us something like this to get hosted SSH from
Co
On Aug 13, 2010, at 3:20 AM, Christian Hammond wrote:
> Try renaming id_rsa_ipstreet to just id_rsa. This is what paramiko is
> expecting to find in that directory.
>
> Christian
>
Done. Same thing happens.
John
--
Want to help the Review Board project? Donate today at
http://www.reviewbo
Try renaming id_rsa_ipstreet to just id_rsa. This is what paramiko is
expecting to find in that directory.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Tue, Aug 10, 2010 at 10:45 AM, John DeRosa wrote:
Should I file a ticket on this exchange, so it's in the bug tracker?
On Aug 10, 2010, at 10:45 AM, John DeRosa wrote:
> On Aug 10, 2010, at 1:00 AM, Christian Hammond wrote:
>
>> It sounds like the publickey method didn't work correctly.
>>
>> Are the files in data/.ssh/ owned by the web server
On Aug 10, 2010, at 1:00 AM, Christian Hammond wrote:
> It sounds like the publickey method didn't work correctly.
>
> Are the files in data/.ssh/ owned by the web server's user, and contain the
> right permissions?
Yes:
r...@reviewboard:/var/www/reviewboard/data# ls -alrt
total 12
drwxr-xr-x
It sounds like the publickey method didn't work correctly.
Are the files in data/.ssh/ owned by the web server's user, and contain the
right permissions?
There was another issue we saw recently involving paramiko (the library we
use to handle SSH connections), so we're trying to collect all the d
On Aug 7, 2010, at 1:02 AM, Christian Hammond wrote:
> Hi John,
>
> I suspect the problem is due to the repository being SSH-based. Review Board
> 1.0.x doesn't in general support SSH-backed repositories, as it has no way to
> present host key confirmation or key checking/storage.
>
> We've be
On Aug 7, 2010, at 1:02 AM, Christian Hammond wrote:
> Hi John,
>
> I suspect the problem is due to the repository being SSH-based. Review Board
> 1.0.x doesn't in general support SSH-backed repositories, as it has no way to
> present host key confirmation or key checking/storage.
>
> We've be
Hi John,
I suspect the problem is due to the repository being SSH-based. Review Board
1.0.x doesn't in general support SSH-backed repositories, as it has no way
to present host key confirmation or key checking/storage.
We've been added this support to Review Board 1.5. I'd suggest installing
1.5
13 matches
Mail list logo
