Here's the latest...
- 1 new tickets were filed this week (1 of them are still open)
- No tickets were closed this week. Better get on that.
Some recent discussions you might care about...
Thanks! This will be part of 3.0.21 (fixed in
6d0c7ed62ee6023ee7e91bc6b68aae20bcd8273d
onrelease-3.0.x
).
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 ofbcrypt
and reviewboard did not work. I was only able to get it working by using a requirements file and limiting the version ofbcrypt
.
Thanks for the heads up! Can you verify whether you're using
easy_install
orpip
? It seems the capping is already happening naturally throughpip
packages, but probably noteasy_install
(which isn't as smart about this, and won't be supported much longer).
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?