Re: rbt post doesn't work if repository url configured in review board is not the root repostitory

[Heng Zhang]

Hi Christian:

*  my company's SVN configuration is specieal, no one has root repository 
permission, each one department's code corresponding to one SVN 
subdirectory, like this:*
Repository Root: svn://10.16.28.38/test 

department one's repository: svn://10.16.28.38/test 

/dep1
department two's repository: svn://10.16.28.38/test 

/dep2
department three's repository: svn://10.16.28.38/test 

/dep3

so I just can configure 3 repositories for Reveiw Board.

and I fix this issue by modifing your rbt code, and look like it work well 
in my environment:

I commented out 1 line in rbtools/clients/svn.py:
#diff = self.convert_to_absolute_paths(diff, repository_info)



在 2017年9月1日星期五 UTC+8上午10:37:52，Heng Zhang写道：
>
> Hi Christian:
>
> *   many thanks for your reponse so quickly.*
>
>
> 在 2017年8月31日星期四 UTC+8上午5:58:15，Christian Hammond写道：
>>
>> Hi,
>>
>> This is correct. Review Board must point to the repository, and not a 
>> subdirectory within the repository, or it won't be able to correctly 
>> compute paths relative to the root. Is there a reason that pointing to the 
>> root doesn't work in your case?
>>
>> Christian
>>
>> On Wed, Aug 30, 2017 at 4:05 AM, Heng Zhang  wrote:
>>
>>> my svn repository root url: svn://10.16.28.38/test
>>> repository url configured in RB: svn://10.16.28.38/test/Python2.7.13
>>> my checkout url: svn://10.16.28.38/test/Python-2.7.13/Python
>>>
>>> I create review request from RB web page is OK, but it is faild when I 
>>> tried to use rbt post command to create new review quest,
>>> I think rbt post has bug which need to fix.
>>> detailed infomation as shown below:
>>>
>>> (virtural_python2.7.13) [zhangheng-pd@dev33 Python]$ rbt --version
>>> RBTools 0.7.10
>>>
>>> (virtural_python2.7.13) [zhangheng-pd@dev33 Python]$ svn info
>>> Path: .
>>> Working Copy Root Path: /home/zhangheng-pd/28.38.svnserver/Python
>>> URL: svn://10.16.28.38/test/Python-2.7.13/Python
>>> Relative URL: ^/Python-2.7.13/Python
>>> Repository Root: svn://10.16.28.38/test
>>> Repository UUID: 0cfbf187-43c6-4c1e-980d-627b8a51bf26
>>> Revision: 77
>>> Node Kind: directory
>>> Schedule: normal
>>> Last Changed Author: zhangheng-pd
>>> Last Changed Rev: 77
>>> Last Changed Date: 2017-08-16 16:20:38 +0800 (三, 16 8月 2017)
>>>
>>> (virtural_python2.7.13) [zhangheng-pd@dev33 Python]$ rbt post -d
>>> >>> RBTools 0.7.10
>>> >>> Python 2.7.13 (default, Jun 13 2017, 18:49:24) 
>>> [GCC 4.4.6 20110731 (Red Hat 4.4.6-3)]
>>> >>> Running on Linux-2.6.32-2.0.0.8-6-x86_64-with-centos-6.8-Final
>>> >>> Home = /home/zhangheng-pd
>>> >>> Current directory = /home/zhangheng-pd/28.38.svnserver/Python
>>> >>> Command line: rbt post -d
>>> >>> Running: tf vc help
>>> >>> Checking for a Subversion repository...
>>> >>> Running: svn --non-interactive info
>>> >>> Running: diff --version
>>> >>> Running: svn --non-interactive --version -q
>>> >>> repository info: Path: svn://10.16.28.38/test, Base path: 
>>> /Python-2.7.13/Python, Supports changesets: False
>>> >>> Making HTTP GET request to http://10.16.28.33/reviews/api/
>>> >>> Making HTTP GET request to 
>>> http://10.16.28.33/reviews/api/repositories/?tool=Subversion
>>> >>> Cached response for HTTP GET 
>>> http://10.16.28.33/reviews/api/repositories/?tool=Subversion expired 
>>> and was modified
>>> >>> Making HTTP GET request to 
>>> http://10.16.28.33/reviews/api/repositories/2/info/
>>> >>> Cached response for HTTP GET 
>>> http://10.16.28.33/reviews/api/repositories/2/info/ expired and was 
>>> modified
>>> >>> Making HTTP GET request to 
>>> http://10.16.28.33/reviews/api/repositories/3/info/
>>> >>> Cached response for HTTP GET 
>>> http://10.16.28.33/reviews/api/repositories/3/info/ expired and was 
>>> modified
>>> >>> Making HTTP GET request to 
>>> http://10.16.28.33/reviews/api/repositories/4/info/
>>> >>> Cached response for HTTP GET 
>>> http://10.16.28.33/reviews/api/repositories/4/info/ expired and was 
>>> modified
>>> >>> Making HTTP GET request to 
>>> http://10.16.28.33/reviews/api/repositories/5/info/
>>> >>> Cached response for HTTP GET 
>>> http://10.16.28.33/reviews/api/repositories/5/info/ expired and was 
>>> modified
>>> >>> Making HTTP GET request to 
>>> http://10.16.28.33/reviews/api/repositories/6/info/
>>> >>> Cached response for HTTP GET 
>>> http://10.16.28.33/reviews/api/repositories/6/info/ expired and was 
>>> modified
>>> >>> Making HTTP GET request to 
>>> http://10.16.28.33/reviews/api/repositories/7/info/
>>> >>> Got API Error 210 (HTTP code 500): There was an error fetching 
>>> extended information for this repository.
>>> 

Re: rbt post doesn't work if repository url configured in review board is not the root repostitory

[Heng Zhang]

Hi Christian:

*   many thanks for your reponse so quickly.*


在 2017年8月31日星期四 UTC+8上午5:58:15，Christian Hammond写道：
>
> Hi,
>
> This is correct. Review Board must point to the repository, and not a 
> subdirectory within the repository, or it won't be able to correctly 
> compute paths relative to the root. Is there a reason that pointing to the 
> root doesn't work in your case?
>
> Christian
>
> On Wed, Aug 30, 2017 at 4:05 AM, Heng Zhang  > wrote:
>
>> my svn repository root url: svn://10.16.28.38/test
>> repository url configured in RB: svn://10.16.28.38/test/Python2.7.13
>> my checkout url: svn://10.16.28.38/test/Python-2.7.13/Python
>>
>> I create review request from RB web page is OK, but it is faild when I 
>> tried to use rbt post command to create new review quest,
>> I think rbt post has bug which need to fix.
>> detailed infomation as shown below:
>>
>> (virtural_python2.7.13) [zhangheng-pd@dev33 Python]$ rbt --version
>> RBTools 0.7.10
>>
>> (virtural_python2.7.13) [zhangheng-pd@dev33 Python]$ svn info
>> Path: .
>> Working Copy Root Path: /home/zhangheng-pd/28.38.svnserver/Python
>> URL: svn://10.16.28.38/test/Python-2.7.13/Python
>> Relative URL: ^/Python-2.7.13/Python
>> Repository Root: svn://10.16.28.38/test
>> Repository UUID: 0cfbf187-43c6-4c1e-980d-627b8a51bf26
>> Revision: 77
>> Node Kind: directory
>> Schedule: normal
>> Last Changed Author: zhangheng-pd
>> Last Changed Rev: 77
>> Last Changed Date: 2017-08-16 16:20:38 +0800 (三, 16 8月 2017)
>>
>> (virtural_python2.7.13) [zhangheng-pd@dev33 Python]$ rbt post -d
>> >>> RBTools 0.7.10
>> >>> Python 2.7.13 (default, Jun 13 2017, 18:49:24) 
>> [GCC 4.4.6 20110731 (Red Hat 4.4.6-3)]
>> >>> Running on Linux-2.6.32-2.0.0.8-6-x86_64-with-centos-6.8-Final
>> >>> Home = /home/zhangheng-pd
>> >>> Current directory = /home/zhangheng-pd/28.38.svnserver/Python
>> >>> Command line: rbt post -d
>> >>> Running: tf vc help
>> >>> Checking for a Subversion repository...
>> >>> Running: svn --non-interactive info
>> >>> Running: diff --version
>> >>> Running: svn --non-interactive --version -q
>> >>> repository info: Path: svn://10.16.28.38/test, Base path: 
>> /Python-2.7.13/Python, Supports changesets: False
>> >>> Making HTTP GET request to http://10.16.28.33/reviews/api/
>> >>> Making HTTP GET request to 
>> http://10.16.28.33/reviews/api/repositories/?tool=Subversion
>> >>> Cached response for HTTP GET 
>> http://10.16.28.33/reviews/api/repositories/?tool=Subversion expired and 
>> was modified
>> >>> Making HTTP GET request to 
>> http://10.16.28.33/reviews/api/repositories/2/info/
>> >>> Cached response for HTTP GET 
>> http://10.16.28.33/reviews/api/repositories/2/info/ expired and was 
>> modified
>> >>> Making HTTP GET request to 
>> http://10.16.28.33/reviews/api/repositories/3/info/
>> >>> Cached response for HTTP GET 
>> http://10.16.28.33/reviews/api/repositories/3/info/ expired and was 
>> modified
>> >>> Making HTTP GET request to 
>> http://10.16.28.33/reviews/api/repositories/4/info/
>> >>> Cached response for HTTP GET 
>> http://10.16.28.33/reviews/api/repositories/4/info/ expired and was 
>> modified
>> >>> Making HTTP GET request to 
>> http://10.16.28.33/reviews/api/repositories/5/info/
>> >>> Cached response for HTTP GET 
>> http://10.16.28.33/reviews/api/repositories/5/info/ expired and was 
>> modified
>> >>> Making HTTP GET request to 
>> http://10.16.28.33/reviews/api/repositories/6/info/
>> >>> Cached response for HTTP GET 
>> http://10.16.28.33/reviews/api/repositories/6/info/ expired and was 
>> modified
>> >>> Making HTTP GET request to 
>> http://10.16.28.33/reviews/api/repositories/7/info/
>> >>> Got API Error 210 (HTTP code 500): There was an error fetching 
>> extended information for this repository.
>> >>> Error data: {u'stat': u'fail', u'err': {u'msg': u'There was an error 
>> fetching extended information for this repository.', u'code': 210}}
>> >>> Making HTTP GET request to 
>> http://10.16.28.33/reviews/api/repositories/9/info/
>> >>> Cached response for HTTP GET 
>> http://10.16.28.33/reviews/api/repositories/9/info/ expired and was 
>> modified
>> >>> Making HTTP GET request to 
>> http://10.16.28.33/reviews/api/repositories/12/info/
>> >>> Cached response for HTTP GET 
>> http://10.16.28.33/reviews/api/repositories/12/info/ expired and was 
>> modified
>> >>> repository info: Path: svn://10.16.28.38/test/Python-2.7.13, Base 
>> path: /Python, Supports changesets: False
>> >>> Running: svn --non-interactive info
>> >>> Running: diff --version
>> >>> Running: svn --non-interactive --version -q
>> >>> repository info: Path: svn://10.16.28.38/test, Base path: 
>> /Python-2.7.13/Python, Supports changesets: False
>> >>> Running: svn --non-interactive status -q --ignore-externals
>> >>> Running: svn --non-interactive diff --diff-cmd=diff --notice-ancestry 
>> -r BASE
>> >>> Running: svn --non-interactive info README
>> >>> Running: svn --non-interactive diff --diff-cmd=diff --notice-ancestry 

Re: Archive ClearCase review board

[Ben]

Thank you Christian.
I want to port the ReviewBoard DB to a different site.

This may be an arcane follow-up question;
Would we need to ensure the ClearCase branches from posted reviews are 
mastered at the new site (writable).
Or is read only access at a different site sufficient for the closed 
reviews?
Thanks
Ben


On Wednesday, August 30, 2017 at 5:55:21 PM UTC-4, Christian Hammond wrote:
>
> Hi Ben,
>
> At the moment, you'll need to keep a working, accessible server around 
> with the same set of branches/commits, so that Review Board can access it. 
> Down the road, I expect we're going to provide proper archival 
> functionality of some sort (this might be a Power Pack feature) so you can 
> take the server offline. It'll be a post-3.0 project.
>
> Christian
>
> On Wed, Aug 30, 2017 at 11:03 AM, Ben  
> wrote:
>
>> Hi,
>> I would like to migrate a reviewboard database configured with Clearcase 
>> and archive it in read only mode.
>>
>> Any one know what live connection it needs with a clearcase replica (if 
>> any) for users to browse old reviews and diffs?
>>
>> Is connection to live clearcase required?
>> if so
>> do branches uses to post reviews need to be mastered in the replica?
>> Thanks
>> Ben
>>
>> -- 
>> Supercharge your Review Board with Power Pack: 
>> https://www.reviewboard.org/powerpack/
>> Want us to host Review Board for you? Check out RBCommons: 
>> https://rbcommons.com/
>> Happy user? Let us know! https://www.reviewboard.org/users/
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "reviewboard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to reviewboard...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Christian Hammond
> President/CEO of Beanbag 
> Makers of Review Board 
>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.