Re: Error on SCM repo migration from RB 5.0.5 to 6.0.2

2024-03-01 Thread David Trowbridge
Florian, If you're seeing "missing support" in the list, it's because pysvn isn't loaded correctly. You'll still be able to create/edit repositories but they won't actually work until that's fixed. Recreating the repository configurations won't change that, and deleting a repository entry will

Re: Error on SCM repo migration from RB 5.0.5 to 6.0.2

2024-03-01 Thread Florian Miedniak
Hi David, I'm using the docker images, both for 5.0.5 and 6.0.2. For the 6.0.2 rb container I installed pysvn via Pip. Since adding a new subversion repo worked just fine, I doubt it's a general problem of pysvn, right? Any further ideas? Anything I can do to further track it down? Btw, it would

Re: Error on SCM repo migration from RB 5.0.5 to 6.0.2

2024-03-01 Thread David Trowbridge
Florian, You probably had subvertpy installed previously. Review Board 6 has removed the subvertpy backend because it caused significant problems. You'll need to install PySVN. We have a guide for doing that at

Re: The eviewboard api does not change users emails

2024-03-01 Thread David Trowbridge
Parameters to PUT and POST operations in the API need to be specified as form-data, not query parameters or JSON. This can be done with the -F parameter to curl: curl -H "Authorization: ..." -H "Accept: ..." -X PUT-F "email=" https:///api/users// David On Fri, Mar 1, 2024 at 10:45 AM Lyova

The eviewboard api does not change users emails

2024-03-01 Thread Lyova Pogosyan
Hi, I am using RB 6.0.2 and I want to change multiply users emails, so I need to use the api. I tried many options, but I could not update any user's email. My query is: curl -H "Authorization: token " -H "Accept: application/json" -X PUT "https:///api/users//?email=" The response is as

Error on SCM repo migration from RB 5.0.5 to 6.0.2

2024-03-01 Thread Florian Miedniak
Hi, I'm just trying to upgrade from RB 5.0.5 to 6.0.2, which went quite well so far. Though, having a look at the upgraded installation, I discovered a problem with SCM repository settings: Repos that had been are properly configured for Subversion in RB 5.0.5, are missing the repo-specific