It looks like we have a bug in 'rbt patch'. It's only really been tested with git repositories, so I'm not too surprised. Would you mind filing this in our issue tracker?
-David On Wed, May 21, 2014 at 4:47 AM, shankar KC <[email protected]> wrote: > Hi I have review board setup against perforce repository. I can login to > use. Using rbt post i can upload the perforce changelist. If i have to > download my code changes to some other machine having rbt tools how can i > do it? > As per the docs > *rbt patch* will download the latest diff from the review request > matching review-request-id > > I see this in review board webUI:- > Review Request *#11* <http://10.138.168.44/r/11/> - Created May 7, 2014 > and updated 1 week ago > So i assumed that review-request-id = 11. Am i correct? How to get > review-request-id for a code request? > > *rbt patch -d 11* > >>> RBTools 0.6 > >>> Python 2.7.6 (default, Nov 10 2013, 19:24:18) [MSC v.1500 32 bit > (Intel)] > >>> Running on Windows-7-6.1.7601-SP1 > >>> Home = C:\Users\shankarkc\AppData\Roaming > >>> Current directory = d:\ariba\s2837\ariba > >>> Checking for a Subversion repository... > >>> Unable to execute "svn help": skipping SVN > >>> Checking for a Git repository... > >>> Unable to execute "git --help" or "git.cmd --help": skipping Git > >>> Checking for a Mercurial repository... > >>> Unable to execute "hg --help": skipping Mercurial > >>> Checking for a CVS repository... > >>> Unable to execute "cvs": skipping CVS > >>> Checking for a Perforce repository... > >>> Running: p4 info > >>> Running: diff --version > >>> repository info: Path: ['perforce3:1666', 'PERFORCE3:1666'], Base > path: None > , Supports changesets: True > >>> Making HTTP GET request to http://10.138.168.44/api/ > >>> Making HTTP GET request to > http://10.138.168.44/api/review-requests/11/diffs > /1/ > Patch is being applied from request 11 with diff revision 1. > Traceback (most recent call last): > File "C:\Python27\Scripts\rbt-script.py", line 9, in <module> > load_entry_point('RBTools==0.6.dev', 'console_scripts', 'rbt')() > File > "C:\Python27\lib\site-packages\rbtools-0.6.dev-py2.7.egg\rbtools\commands > \main.py", line 134, in main > command.run_from_argv([RB_MAIN, command_name] + args) > File > "C:\Python27\lib\site-packages\rbtools-0.6.dev-py2.7.egg\rbtools\commands > \__init__.py", line 422, in run_from_argv > exit_code = self.main(*args) or 0 > File > "C:\Python27\lib\site-packages\rbtools-0.6.dev-py2.7.egg\rbtools\commands > \patch.py", line 141, in main > tmp_patch_file, base_dir) > File > "C:\Python27\lib\site-packages\rbtools-0.6.dev-py2.7.egg\rbtools\commands > \patch.py", line 82, in apply_patch > base_dir, self.options.px) > File > "C:\Python27\lib\site-packages\rbtools-0.6.dev-py2.7.egg\rbtools\clients\ > __init__.py", line 163, in apply_patch > p_num = p or self._get_p_number(patch_file, base_path, base_dir) > File > "C:\Python27\lib\site-packages\rbtools-0.6.dev-py2.7.egg\rbtools\clients\ > __init__.py", line 136, in _get_p_number > if (base_dir.startswith(base_path)): > TypeError: startswith first arg must be str, unicode, or tuple, not > NoneType > > Really appriciate your help. > Thanks > Shankar KC > > > -- > Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ > --- > Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ > --- > Happy user? Let us know at http://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 [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://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 [email protected]. For more options, visit https://groups.google.com/d/optout.
