'ascii' codec can't decode byte 0xc3 in position 7622: ordinal not in range(128)

2024-04-23 Thread Paulius
Hello! I recently installed(5.0.5) and upgraded(6.0.2) Review Board. I am testing out email service but getting error once review is updated. Error below. - Test email from settings was successfully sent. - I still receive error emails about this but not review emails Any idea what has

Older reviews has patch issue after upgraded from Reviewboard version 2.0.18 to 6.0.2

2024-04-23 Thread Andy Fong
Hi, After we migrated our reviewboard instance to a new server and upgraded from version 2.0.18 to 6.0.2, some older reviews has issue with patch with message like the following: == patching file CM.groovy-new (read from CM.groovy) Hunk #3 FAILED at 295. 1 out of 3 hunks

Re: Problem upgrading from 2.5.16

2024-04-23 Thread G Law
Great thank you. I found that adding an upgraded python while doing the ugprade confuses the upgrade and python 3 scripts were failing running referencing python2.7/site-packages. Also upgrading to python3 breaks 2.5.16. So, upgrade python3 and reviewboard will pull 2.5.16 into a working

Re: Problem upgrading from 2.5.16

2024-04-23 Thread David Trowbridge
You definitely need to make sure that everything is using the same Python version. In particular, if you're using something like Apache, you need to make sure that your mod_wsgi is built with the same Python version as everything that is installed. Moving to Python 3 is definitely annoying, but

Re: Problem upgrading from 2.5.16

2024-04-23 Thread David Trowbridge
Since you have to upgrade the world, you may find it easiest to set up a completely new system with a brand new install of Review Board. Once you've verified that everything is set up correctly, you can replace the database and site directory with the ones from your old server, and run rb-site

Re: Problem upgrading from 2.5.16

2024-04-23 Thread G Law
Thanks for the suggestion. I'll look at logs. I was trying to go to 4, but when seeing issues, tried something more conservative. Bumping 2.5.16 to 6 means I'd have to switch to python 3. When I tried upgrading to 4 I found an issue where it was conflicting between using 2 and 3.

Re: Problem upgrading from 2.5.16

2024-04-23 Thread G Law
Ah nice, I'll try that thanks! I tried copying same version to same version on new server, which didn't go well. On Tuesday, April 23, 2024 at 2:51:30 PM UTC-4 David Trowbridge wrote: > Since you have to upgrade the world, you may find it easiest to set up a > completely new system with a