Re: rbt diff object of type 'NoneType' has no len(). RBTools 0.7.2 with svn

2015-04-09 Thread Richard Parks
Hi Griffin, Yes that got around it for me, particularly the "not generically point to the root of the repo." thank you very much for your help. In between there was another issue where it explicitly failed on a single file which it again complained about, but this was an empty file (i.e. size

Reviewboard 1.6.13 could not change password / debugging help

2015-04-09 Thread Mark Niemann
Hi there, we are using reviewboard 1.6.13 for a couple of years (to stupid to update :) ). Since a few days we could not add a new user and change the password. In the Web-Gui the password change is successfully confirmed, but the user could not log in. As I know there were no changes in the

Re: Will changing the name of our perforce server cause us to lose access to old review diffs?

2015-04-09 Thread David Trowbridge
Instead of registering the new name as a new repository, just update the existing repository inside the Review Board admin to point to the new hostname. After that, everything should work fine. -David On Thu, Apr 9, 2015 at 2:04 PM Steve wrote: > Our company has decided to clean up our perforce

Re: Will changing the name of our perforce server cause us to lose access to old review diffs?

2015-04-09 Thread Steve
So simple I'm embarrassed I didn't think to try it. I take it the repo is identified internally by a DB key and as long as that is left in place, the name and host information can change. However it's done, it works as advertised! Thanks --Steve On Thursday, April 9, 2015 at 2:09:32 PM UTC-

Will changing the name of our perforce server cause us to lose access to old review diffs?

2015-04-09 Thread Steve
Our company has decided to clean up our perforce host name conventions a bit and the short version is the server will have a new name. I've noticed that the reviews display the repo name in the review data like this: Repository: old_hostname:1666 If I rename old_hostname to new_hostname and re

Re: CRITICAL: not well-formed (invalid token): line 3, column 28

2015-04-09 Thread Richard Parks
Hi Griffin, Thanks for your help on this as well, here's the svn log: svn log -r 12192 -l 1 --xml Authentication realm: Subversion repositories (mydepartment) Password for 'myusername': myusername 2015-04-02T13:17:52.412260Z My description of what I'm working on h