Could it be some settings issue on hg server side?
--
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://www.reviewboard.org/users/
---
You received this message
Hi, I just updated review board to 1.7.21 and I'm trying to add a new repo
from gitlab with the new gitlab support, as I have no gitlab account
configured I'm leaving and filling user and
pass, I'm also adding redmine.
When I click on save I get *Unknown error when linking the account: PID
che
Hi Juia,
This is likely a PyCrypto-related issue. It's fortunately not
GitLab-specific, and can likely be fixed with a dependency upgrade.
Can you tell me which OS/Linux distro you installed this on?
Also, can you run:
$ python
>>> import Crypto
>>> Crypto.__file__
This should give
On 01/14/2014 09:01 PM, Christian Hammond wrote:
> Hey everyone,
>
> One release for the day just isn't enough. We just released Review Board
> 1.7.21. It adds support for GitLab and Unfuddle, fixes a number of bugs,
> adds some API improvements, and introduces a large optimization for
> large dif
On 01/14/2014 09:36 PM, Christian Hammond wrote:
> I just put out a 0.5.5 release that adds a missing commit for the
> repository matching fixes for Subversion, and introduces
> --svn-show-copies-as-adds to post-review.
>
> Give it a try!
RBTools 0.5.5 packages have been built for Fedora and EPEL
I've made it farther now than I have ever before. But I'm still running
into one last issue. (Maybe two.)
First, background information. Hopefully this makes more sense. I'm
learning Subversion as I do all this. C'est la vie.
The .reviewboardrc file reads as
REVIEWBOARD_URL = "http://*Review
There is obviously some sort of credential mismatch. But there is no
indication as to what credentials it's using on what. I don't know what is
being mismatched. And I don't know how to find out.
--
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review
This looks like a mess, and sort of an overload. I'm only going on my own
philosophy of preferring more information to less.
Also, anyone willing to take the time to go over this in the first place, I
want to express sincere gratitude. Free software, free support. I really,
really appreciate wh
I suppose a brief summary, because it seems confusing reading it.
The directory on the svn machine goes
*SvnServer/*export/svn/*SvnDirectory/RepositoryName*
/branches/20131209_repo_p14
Likewise, to access this all, it's
https://*SvnServer/SvnDirectory*/*RepositoryName*/branches/20131209_repo_
I'm behind a proxy, and setting http_proxy would not work for me with
easy_install, so I downloaded the required packages and installed
ReviewBoard 1.7.21 for Python 2.6 on Ubuntu 10. When I try to create a
site I get Error: Unknown command: 'registerscmtools'. I've tried
removing, re-install
Ok, really, last post. I made a mistake in one post.
The actual directory on the svn server that contains
conf dav db format hooks locks README.txt
is
export/svn/code/
The "*SvnDirectory*" name itself is actually svncode. Somehow I thought
keeping everything unnamed would help people r
I suppose it should also be said that, as far as the *actual* problem at
hand. I'm sure that all the credentials I've entered were correct. I can
connect to svn and ReviewBoard with them. I just don't know if there's some
setting I'm missing, or I put the right ones in the wrong places.
I just
This error is typically a problem with the credentials on the reviewboard side,
not rbtools. Can you check that those are correct, and if they are, check the
reviewboard log file for any more interesting errors?
-David
> On Jan 15, 2014, at 12:35 PM, Zachary Gallagher
> wrote:
>
> I suppose
I changed the password for my username to *password*. The actual, all
lowercase word. Then I ran
rbt post -d --username=gallagher --password=password --submit-as=gallagher
And got the same error.
On Wednesday, January 15, 2014 3:41:49 PM UTC-5, David Trowbridge wrote:
>
> This error is typicall
I can log in with
gallagher
password
But I can't run *rbt post* with it.
--
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://www.reviewboard.org/users/
---
How did you install the packages?
You're really going to need to get easy_install working. Did you also set
https_proxy?
Something like this will work best:
$ sudo -s
$ http_proxy= https_proxy= easy_install -U ReviewBoard
Christian
--
Christian Hammond - chip...@chipx86.com
Review Boa
I mean in the repository configuration in the reviewboard admin.
-David
> On Jan 15, 2014, at 12:49 PM, Zachary Gallagher
> wrote:
>
> I can log in with
>
> gallagher
>
> password
>
>
> But I can't run rbt post with it.
> --
> Get the Review Board Power Pack at http://www.reviewboard.org/
On Wed, Jan 15, 2014 at 12:02 PM, Zachary Gallagher <
zachary.gallag...@remcom.com> wrote:
> Also, if I navigate to http://*ReviewBoardServer*/api/repositories, I get
> this. Yet there are 5 repositories listed in the admin dashboard.
>
> Not sure if that is expected or not. Not entirely up to snu
Oh.
Ok, well, that's embarrassing.
But now I have a new error. And it's part of what my issue was before. When
Subversion speaks of "base path." Does that refer to the parent directory
of branches/, trunk/, etc. Or the parent directory of *that* directory.
It's something that's apparently so
-.-
On Wednesday, January 15, 2014 3:57:25 PM UTC-5, Christian Hammond wrote:
>
> On Wed, Jan 15, 2014 at 12:02 PM, Zachary Gallagher <
> zachary@remcom.com > wrote:
>
>> Also, if I navigate to http://*ReviewBoardServer*/api/repositories, I
>> get this. Yet there are 5 repositories listed in
No worries. We used to redirect calls like /api/repositories to
/api/repositories/, but got rid of it.
The base path is everything between the root of the repository and where
the diff was taken.
So basically, if you are in /trunk/myproject, and you run 'svn diff' (or
'rbt post', which runs it fo
http_proxy and https_proxy are both set:
sudo -E easy_install -U ReviewBoard
Searching for ReviewBoard
Reading http://pypi.python.org/simple/ReviewBoard/
Download error: [Errno 111] Connection refused -- Some packages may not be
found!
Reading http://pypi.python.org/simple/ReviewBoard/
Download e
So this very last issue... (An optimistic claim)
DEBUG:root:Got API Error 207 (HTTP code 400): The file was not found in the
> repository
> DEBUG:root:Error data: {u'stat': u'fail', u'file':
> u'/*RepositoryName*/branches/20131209-repo-P14/dev/src/modelLibraries/VTRPEAdapter/Makefile',
>
> u'e
The reason there is a *SvnDirectory* at all is because there are multiple
'repositories' under it, all with their own branches and trunks. I put
repositories in air quotes because I'm not sure if those branches/trunks
parent directories are themselves the repositories, or if "repository"
exclus
And there is confusion at all because I haven't been the sysadmin for a
software company for long, the programmers use the term for both, and when
I once asked which was which I was met with a shrug and "iunno".
On Wednesday, January 15, 2014 4:23:30 PM UTC-5, Zachary Gallagher wrote:
>
> The re
And the confusion in the first place exists because I haven't been the
sysadmin for a software company for long, the programmers use the term for
both, and when I once asked which it was I was met with a shrug and "iunno."
--
Get the Review Board Power Pack at http://www.reviewboard.org/powerpa
It certainly doesn't look like the environment variables are being used.
Can you run 'sudo -E -s' and echo both variables so I can see them? (You
can blank out the domain, but I want to see the format and that they're
both set.)
We've seen this come up from time to time, and it's always been due
Run 'svn info' in your local checkout and see what Repository Root is. If
it's https://SvnServer/SvnDirectory/, then there should be only one
repository entry for that. All the others are just there to cause problems.
That would be why your rbt post is broken.
I suspect that that's the case.
If t
Oh my goodness. It worked.
On Wednesday, January 15, 2014 4:36:12 PM UTC-5, Christian Hammond wrote:
>
> Run 'svn info' in your local checkout and see what Repository Root is. If
> it's https://SvnServer/SvnDirectory/, then there should be only one
> repository entry for that. All the others are
$ sudo -E -s
# env|grep proxy
http_proxy=http://..com:80
https_proxy=https://..com:81
On Wednesday, January 15, 2014 3:32:28 PM UTC-6, Christian Hammond wrote:
>
> It certainly doesn't look like the environment variables are being used.
>
> Can you run 'sudo -E -s' and echo both v
I was able to use easy_install with .egg file which I downloaded. I just
haven't been able to get it to connect to pyp.python.org for some reason.
On Wednesday, January 15, 2014 3:51:26 PM UTC-6, TIDave wrote:
>
> $ sudo -E -s
> # env|grep proxy
> http_proxy=http://..com:80
> https_proxy
try this:
export https_proxy="http://yourid:yourpassword@yourproxy:8081";
export http_proxy="http://yourid:yourpassword@yourproxy:8081";
On Thursday, January 16, 2014 9:04:31 AM UTC+11, TIDave wrote:
>
> I was able to use easy_install with .egg file which I downloaded. I just
> haven't been able
is it possible to allow each user to add its own avatar? if yes how?
--
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://www.reviewboard.org/users/
---
You rec
The proxy does not require authentication.
On Wed, Jan 15, 2014 at 4:33 PM, MoonWalker wrote:
> try this:
> export https_proxy="http://yourid:yourpassword@yourproxy:8081";
> export http_proxy="http://yourid:yourpassword@yourproxy:8081";
>
>
> On Thursday, January 16, 2014 9:04:31 AM UTC+11, TIDa
If you use easy_install on the eggs, it *should* work, but there's going to
be a lot of eggs needed, and these will increase with 2.0.
I'm surprised this isn't working. Can you show me what easy_install
--version says? I'm seeing some docs saying that some versions use
HTTP_PROXY and HTTPS_PROXY i
I had several issues with the ubuntu easy_install (13.10) and firewall, so
what I did first is to install the newone following the next steps:
1) Firewall access
$ export http_proxy="http://yourid:yourpassword@yourproxy:8081";
$ export https_proxy="http://yourid:yourpassword@yourproxy:8081";
2)
36 matches
Mail list logo
