Here's the latest...

Some recent discussions you might care about...

chipx86
#4 chipx86

Thanks! This will be part of 3.0.21 (fixed in 6d0c7ed62ee6023ee7e91bc6b68aae20bcd8273d on release-3.0.x).

#3 splatter2

I am using pip. I am running CentOS 7.9, pip version 8.1.2, python 2.7.5 (from yum).
I install with pip using the --upgrade option to upgrade all specified packages. It tried to install the wrong version of bcrypt and reviewboard did not work. I was only able to get it working by using a requirements file and limiting the version of bcrypt.

chipx86
#2 chipx86

Patch up at https://reviews.reviewboard.org/r/11471/

chipx86
#1 chipx86

Fix up for review at https://reviews.reviewboard.org/r/11470/

This will be part of RC 1 this week.

chipx86
#1 chipx86

Thanks for the heads up! Can you verify whether you're using easy_install or pip? It seems the capping is already happening naturally through pip packages, but probably not easy_install (which isn't as smart about this, and won't be supported much longer).

berquist
#4 berquist

I had this problem as well, with Ubuntu 18.04 and Review Board 3.0.20:

>>> Error data: {'stat': 'fail', 'err': {'msg': "Unable to connect to a repository at URL 'https://remote.com/svnroot/repo/branches/rdm2/include/qinks_main.h'\nServer SSL certificate verification failed: issuer is not trusted", 'code': 224}}

and the problem was that the remote's certificate had expired and been updated, so command-line Subversion usage worked, but Review Board didn't know about the updated certificate. I had to go to the Admin panel, click "Repositories", click on the offending repository, save, and accept the new certificate.

Is there a way to do that from the CLI, rather than the Admin panel?

david
#4 david

Fixed in release-4.0.x (6c28b14). Thanks!

Qianxi_Li
#3 Qianxi_Li

Changes published.

Qianxi_Li
#3 Qianxi_Li

Changes published.

Qianxi_Li
#3 Qianxi_Li

Changes published.