Thanks so much for the hint! Yes I never realized that it's the rbssh path.
For some reason it's in /usr/local/bin but not in /usr/bin. sudo ln -s
/usr/local/bin/rbssh /usr/bin/rbssh did the trick. Thank you again!
On Mon, Jul 29, 2013 at 12:35 AM, Christian Hammond chip...@chipx86.comwrote:
Hello, did you eventually figure out this problem? I also have exactly the
same error log messages. Thanks!
Dai Wei
On Friday, May 4, 2012 7:29:13 AM UTC-4, Can Özmen wrote:
I first tried adding the SSH key to my GitHub account and then as a deploy
key to the private repo's account.
Both
How did you install Review Board exactly?
What OS/distro?
Any special web server or virtualenv setup?
If it's exactly the same error (please paste yours) then the PATH isn't set
up to find the rbssh that was installed when installing Review Board.
Christian
--
Christian Hammond -
On Wednesday, May 2, 2012 10:03:04 AM UTC-7, Can Özmen wrote:
Hi Christian Dan,
I'm on 1.6.6 and trying to set up a Private Org. Repo on Github.
I've got an API token via the web interface. I've generated a key pair and
uploaded the public part as a deploy key to the repo I want to
But in the case of a private org that would make 'foo' the owner, which is the
name of the organization.
Then the 'Get your API Token' part asks for foo's password, which doesn't make
sense since 'foo' is not an account that I can log-in with.
--
Can Özmen
On Wednesday, May 2, 2012 at
Do you have an SSH key configured and linked on that account? That could do
it.
If you check the Review Board log file, there may be more information.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Fri,
I first tried adding the SSH key to my GitHub account and then as a deploy key
to the private repo's account.
Both fail with the same message:
2012-05-04 14:24:39,977 - DEBUG - Switch to new keys ...
2012-05-04 14:24:39,983 - DEBUG - Trying SSH key
3e2bacb616553a8258f03dc1b70f3a9c
2012-05-04
How did you install Review Board? Looks like either a broken install or maybe
some tightened security disallowing it from running executables?
Christian
On May 4, 2012, at 4:29, Can Özmen canoz...@gmail.com wrote:
I first tried adding the SSH key to my GitHub account and then as a deploy
I'm on an EC2 instance that I got up through Bitnami. I then upgraded to 1.6.6
((was on 1.6.5 originally)) with help from victoria.
For example the default site's log folder wasn't writeable after the upgrade so
maybe some permissions are not set correctly.
Is there any way to check that?
Hi Christian Dan,
I'm on 1.6.6 and trying to set up a Private Org. Repo on Github.
I've got an API token via the web interface. I've generated a key pair and
uploaded the public part as a deploy key to the repo I want to connect to
((RB asked me to confirm the host afterwards)).
But I'm
The Project Name is the foo in foo.git. The owner field would be the
account owning the repo. So, github.com/foo/bar.git would use foo as the
owner and bar as the project.
Christian
On May 2, 2012, at 10:03, Can Özmen canoz...@gmail.com wrote:
Hi Christian Dan,
I'm on 1.6.6 and trying
I finally got a response from GitHub. Here is it:
The API Token has been removed. We encourage all third party applications
to migrate to API v3. Please check our latest blog post for more details:
https://github.com/blog/1090-github-api-moving-on;
Pretty much, they've said, We're shutting
They've been nice enough to give Review Board an extension on the one API call
we use, and are working on making the API token accessible somewhere until
then. Said it may be a couple days.
In the meantime, I'm making progress on v3 support, which will also come with a
much easier repository
Okay, so here's the situation.
I talked to GitHub and they're indeed switching to the new API, which we
are not yet using. My plan was to move to this in a 1.7.x release, but
that's too far off. Fortunately, I had some detailed plans worked out, so
I'll be spending some time on putting this into
14 matches
Mail list logo
