My Workaround:
I have the same problem but found a workaround inspired by Alexis' debug
information:
Add the new repository with "Show this repository" option unchecked.
Afterwards got directly to the database and change the visible flag for the
repository in the table scmtools_repository to
Trying to get up to 2.x to work on the SSL certificate errors. Environment
is:
Centos 65 updated.
Python 2.6 (yum installed)
ReviewBoard 1.7.25 (yum installed)
Setuptools are installed, so easy_install is available.
Attempting to do ANY upgrade (easy_install -U reviewboard or
reviewboard=1.7.2
Hi Michael,
You'll likely run into problems attempting to mix yum-installed and
easy_installed packages for Review Board. You need to use one or the other,
but not both. This applies to ReviewBoard, Djblets, django-evolution,
django-pipeline, and more.
It sounds like the attempts to deal with Pyt
Hi,
What version of Review Board? Are you using PySVN or Subvertpy?
Christian
On Wednesday, July 30, 2014, Holger wrote:
> My Workaround:
>
> I have the same problem but found a workaround inspired by Alexis' debug
> information:
>
> Add the new repository with "Show this repository" option u
>
> OK so given the yum install is topped out at RB 1.7.25, Python at 2.6 and
> others accordingly, would the best way to be rpm -e on everything and
> reinstalling from scratch? Again, I have a snapshot of the running base
> system so reverting is not an issue when I get down a dead end..
>
O
It doesn’t sound like anything but the metadata for Review Board 2.0.x was ever
installed. No files were ever fetched.
Your mixing and matching of yum packages and easy_install packages is likely
causing your problems. You also tried to install Review Board 2.0.x previously
(given that it’s try
>
> Christian:
>
Again, just to be clear the machine is snapshot'd at the running
1.7.25 yum install, which is working. The steps above all related to
getting 1.7.25 upgraded to 1.7.27; the snapshot in question had never been
used to attempt a 2.0.x install.
I will revert, then uninsta
Hi Michael,
“Whoosh” is a new dependency only in Review Board 2.0.x. The fact that it was
trying to find Whoosh says that there’s some metadata specifying that Review
Board is depending on Whoosh. Is there any chance that your first upgrade
attempt resulted in an “easy_install -U ReviewBoard” t
Christian: Personally, I am running ReviewBoard 2.0.2 and I believe I am
using the default which is PySVN. I still think it's the wrapper tools
trying to access the repository without a username or password at first.
The setup is simple and easy to reproduce: VisualSVN server with no public
access
Hi Alexis,
>From the code I’m seeing, it does look like we’re passing in the credentials.
>I am, however, seeing that we don’t pass in credentials when confirming an
>HTTPS certificate. Is that the point where things go wrong, or is it on the
>initial save?
Christian
--
Christian Hammond - c
Hi Christian,
It is the original save: it fails even before asking to accept the SSL
certificate (as mine is not signed by an authority, I have to accept it).
Alexis
On Wed, Jul 30, 2014 at 4:42 PM, Christian Hammond wrote:
> Hi Alexis,
>
> From the code I'm seeing, it does look like we're pass
Hi Alexis,
So, Review Board 2.0.2 is busted with SVN. That’s the primary cause of your
problems. You need 2.0.3 or higher to have a working setup with a self-signed
cert. (You should install 2.0.5 though.)
When trying to verify the issue, though, I hit some other problems with
accepting a cert
Hi Christian,
It worked! No hitch. No need to install the patch.
Thanks,
Alexis
On Wed, Jul 30, 2014 at 6:09 PM, Christian Hammond wrote:
> Hi Alexis,
>
> So, Review Board 2.0.2 is busted with SVN. That's the primary cause of
> your problems. You need 2.0.3 or higher to have a working setup
13 matches
Mail list logo
