Re: "Login to the SCM server failed." when using "rbt post -d". Also, /api/repositories is empty.

[Zachary Gallagher]

Oh my goodness. It worked.

On Wednesday, January 15, 2014 4:36:12 PM UTC-5, Christian Hammond wrote:
>
> Run 'svn info' in your local checkout and see what Repository Root is. If 
> it's https://SvnServer/SvnDirectory/, then there should be only one 
> repository entry for that. All the others are just there to cause problems. 
> That would be why your rbt post is broken.
>
> I suspect that that's the case.
>
> If that is the case, what you want to do is set up the SvnDirectory one 
> and mark all the other ones as invisible so they won't be used anymore. 
> They won't break existing review requests, since they'll still be in the 
> database, but RBTools won't look at them anymore.
>
> Christian
>
> -- 
> Christian Hammond - chi...@chipx86.com 
> Review Board - http://www.reviewboard.org
> Beanbag, Inc. - http://www.beanbaginc.com
>
>
> On Wed, Jan 15, 2014 at 1:23 PM, Zachary Gallagher 
> 
> > wrote:
>
>> The reason there is a *SvnDirectory* at all is because there are 
>> multiple 'repositories' under it, all with their own branches and trunks. I 
>> put repositories in air quotes because I'm not sure if those 
>> branches/trunks parent directories are themselves the repositories, or if 
>> "repository" exclusively refers to the entire package.
>>
>>
>> On Wednesday, January 15, 2014 4:21:11 PM UTC-5, Zachary Gallagher wrote:
>>>
>>> So this very last issue... (An optimistic claim)
>>>
>>> DEBUG:root:Got API Error 207 (HTTP code 400): The file was not found in 
 the repository
 DEBUG:root:Error data: {u'stat': u'fail', u'file': u'/*RepositoryName*
 /branches/20131209-repo-P14/dev/src/modelLibraries/VTRPEAdapter/Makefile', 
 u'err': {u'msg': u'The file was not found in the repository', u'code': 
 207}, u'revision': u'15168'}
 Traceback (most recent call last):
   File "/usr/bin/rbt", line 9, in 
 load_entry_point('RBTools==0.5.5', 'console_scripts', 'rbt')()
   File 
 "/usr/lib/python2.6/site-packages/RBTools-0.5.5-py2.6.egg/rbtools/commands/main.py",
  
 line 127, in main
 command.run_from_argv([RB_MAIN] + args)
   File "/usr/lib/python2.6/site-packages/RBTools-0.5.5-py2.6.
 egg/rbtools/commands/__init__.py", line 158, in run_from_argv
 exit_code = self.main(*args) or 0
   File 
 "/usr/lib/python2.6/site-packages/RBTools-0.5.5-py2.6.egg/rbtools/commands/post.py",
  
 line 659, in main
 submit_as=self.options.submit_as)
   File 
 "/usr/lib/python2.6/site-packages/RBTools-0.5.5-py2.6.egg/rbtools/commands/post.py",
  
 line 534, in post_request
 raise CommandError('\n'.join(error_msg))
 rbtools.commands.CommandError: Error uploading diff

 The file was not found in the repository (HTTP 400, API Error 207)
 Your review request still exists, but the diff is not attached.
>>>
>>>
>>>
>>> The file *is* there on the machine. The absolute path is
>>>
>>> /dfs/*User*/*RepositoryName*_nrl_p14/dev/src/modelLibraries/
>>> VTRPEAdapter/Makefile
>>>
>>> And the path in svn is
>>>
>>> https://*SvnServer*/*SvnDirectory*/*RepositoryName*/branches/
>>> 20131209-repo-P14/dev/src/modelLibraries/VTRPEAdapter/Makefile
>>>
>>>
>>>
>>> Any idea what's going on? I'm running "rbt post" from 
>>>
>>> /dfs/*User*/*RepositoryName*_nrl_p14/
>>>
>>> and "Repository" in .reviewboardrc is set to the single word 
>>> *"RepositoryName."*
>>>
>>>
>>> The slight confusion is that (and I didn't do this, so I'm not sure if 
>>> it was right or not at the time)
>>>
>>> as noted above, these are the repositories in ReviewBoard
>>>
>>>
>>>
>>>  Repository
>>> Path 
>>> Hosting
>>> Show this repository 
>>>  SvnDirectoryhttps://*SvnServer*/*SvnDirectory*/  [image: True] 
>>> RepositoryName_20131209-repo-P14https://*SvnServer*/*SvnDirectory*/
>>> *RepositoryName*/branches/20131209-repo-P14  [image: True]  
>>> RepositoryName-Trunkhttps://*SvnServer*/*SvnDirectory*/*RepositoryName*
>>> /trunk  [image: True] Results Viewerhttps://*SvnServer*/*SvnDirectory*
>>> /results_viewer/trunk/  [image: False]  RepositoryName
>>> https://*SvnServer*/*SvnDirectory*/*RepositoryName*/  [image: False] 
>>>
>>> 5 Repositories
>>>
>>>
>>> So I don't even know which one "rbt post" is trying to attach this to. 
>>> The second? Or fifth? Maybe the first?
>>>
>>>
>>>
>>>
>>> On Wednesday, January 15, 2014 4:11:03 PM UTC-5, Christian Hammond wrote:

 No worries. We used to redirect calls like /api/repositories to 
 /api/repositories/, but got rid of it.

 The base path is everything between the root of the repository and 
 where the diff was taken.

 So basically, if you are in /trunk/myproject, and you run 'svn diff' 
 (or 'rbt post', which runs it for you), the base path is /trunk/myproject.

 This requires that the repository entry is set up properly on Review 
 Board. It must always po

Re: "Login to the SCM server failed." when using "rbt post -d". Also, /api/repositories is empty.

[Christian Hammond]

Run 'svn info' in your local checkout and see what Repository Root is. If
it's https://SvnServer/SvnDirectory/, then there should be only one
repository entry for that. All the others are just there to cause problems.
That would be why your rbt post is broken.

I suspect that that's the case.

If that is the case, what you want to do is set up the SvnDirectory one and
mark all the other ones as invisible so they won't be used anymore. They
won't break existing review requests, since they'll still be in the
database, but RBTools won't look at them anymore.

Christian

-- 
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com


On Wed, Jan 15, 2014 at 1:23 PM, Zachary Gallagher <
zachary.gallag...@remcom.com> wrote:

> The reason there is a *SvnDirectory* at all is because there are multiple
> 'repositories' under it, all with their own branches and trunks. I put
> repositories in air quotes because I'm not sure if those branches/trunks
> parent directories are themselves the repositories, or if "repository"
> exclusively refers to the entire package.
>
>
> On Wednesday, January 15, 2014 4:21:11 PM UTC-5, Zachary Gallagher wrote:
>>
>> So this very last issue... (An optimistic claim)
>>
>> DEBUG:root:Got API Error 207 (HTTP code 400): The file was not found in
>>> the repository
>>> DEBUG:root:Error data: {u'stat': u'fail', u'file': u'/*RepositoryName*
>>> /branches/20131209-repo-P14/dev/src/modelLibraries/VTRPEAdapter/Makefile',
>>> u'err': {u'msg': u'The file was not found in the repository', u'code':
>>> 207}, u'revision': u'15168'}
>>> Traceback (most recent call last):
>>>   File "/usr/bin/rbt", line 9, in 
>>> load_entry_point('RBTools==0.5.5', 'console_scripts', 'rbt')()
>>>   File 
>>> "/usr/lib/python2.6/site-packages/RBTools-0.5.5-py2.6.egg/rbtools/commands/main.py",
>>> line 127, in main
>>> command.run_from_argv([RB_MAIN] + args)
>>>   File "/usr/lib/python2.6/site-packages/RBTools-0.5.5-py2.6.
>>> egg/rbtools/commands/__init__.py", line 158, in run_from_argv
>>> exit_code = self.main(*args) or 0
>>>   File 
>>> "/usr/lib/python2.6/site-packages/RBTools-0.5.5-py2.6.egg/rbtools/commands/post.py",
>>> line 659, in main
>>> submit_as=self.options.submit_as)
>>>   File 
>>> "/usr/lib/python2.6/site-packages/RBTools-0.5.5-py2.6.egg/rbtools/commands/post.py",
>>> line 534, in post_request
>>> raise CommandError('\n'.join(error_msg))
>>> rbtools.commands.CommandError: Error uploading diff
>>>
>>> The file was not found in the repository (HTTP 400, API Error 207)
>>> Your review request still exists, but the diff is not attached.
>>
>>
>>
>> The file *is* there on the machine. The absolute path is
>>
>> /dfs/*User*/*RepositoryName*_nrl_p14/dev/src/modelLibraries/
>> VTRPEAdapter/Makefile
>>
>> And the path in svn is
>>
>> https://*SvnServer*/*SvnDirectory*/*RepositoryName*/branches/
>> 20131209-repo-P14/dev/src/modelLibraries/VTRPEAdapter/Makefile
>>
>>
>>
>> Any idea what's going on? I'm running "rbt post" from
>>
>> /dfs/*User*/*RepositoryName*_nrl_p14/
>>
>> and "Repository" in .reviewboardrc is set to the single word
>> *"RepositoryName."*
>>
>>
>> The slight confusion is that (and I didn't do this, so I'm not sure if it
>> was right or not at the time)
>>
>> as noted above, these are the repositories in ReviewBoard
>>
>>
>>
>>  Repository
>> Path 
>> Hosting
>> Show this repository 
>>  SvnDirectoryhttps://*SvnServer*/*SvnDirectory*/  [image: True]
>> RepositoryName_20131209-repo-P14https://*SvnServer*/*SvnDirectory*/
>> *RepositoryName*/branches/20131209-repo-P14  [image: True]
>> RepositoryName-Trunkhttps://*SvnServer*/*SvnDirectory*/*RepositoryName*
>> /trunk  [image: True] Results Viewerhttps://*SvnServer*/*SvnDirectory*
>> /results_viewer/trunk/  [image: False]  RepositoryName
>> https://*SvnServer*/*SvnDirectory*/*RepositoryName*/  [image: False]
>>
>> 5 Repositories
>>
>>
>> So I don't even know which one "rbt post" is trying to attach this to.
>> The second? Or fifth? Maybe the first?
>>
>>
>>
>>
>> On Wednesday, January 15, 2014 4:11:03 PM UTC-5, Christian Hammond wrote:
>>>
>>> No worries. We used to redirect calls like /api/repositories to
>>> /api/repositories/, but got rid of it.
>>>
>>> The base path is everything between the root of the repository and where
>>> the diff was taken.
>>>
>>> So basically, if you are in /trunk/myproject, and you run 'svn diff' (or
>>> 'rbt post', which runs it for you), the base path is /trunk/myproject.
>>>
>>> This requires that the repository entry is set up properly on Review
>>> Board. It must always point to the very root of a Subversion repository,
>>> and not a directory inside it.
>>>
>>> Christian
>>>
>>> --
>>> Christian Hammond - chi...@chipx86.com
>>> Review Board - http://www.reviewboard.org
>>> Beanbag, Inc. - http://www.beanbaginc.com
>>>
>>>
>>> On Wed

Re: "Login to the SCM server failed." when using "rbt post -d". Also, /api/repositories is empty.

[Zachary Gallagher]

And the confusion in the first place exists because I haven't been the 
sysadmin for a software company for long, the programmers use the term for 
both, and when I once asked which it was I was met with a shrug and "iunno."

-- 
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 reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: "Login to the SCM server failed." when using "rbt post -d". Also, /api/repositories is empty.

[Zachary Gallagher]

And there is confusion at all because I haven't been the sysadmin for a 
software company for long, the programmers use the term for both, and when 
I once asked which was which I was met with a shrug and "iunno".

On Wednesday, January 15, 2014 4:23:30 PM UTC-5, Zachary Gallagher wrote:
>
> The reason there is a *SvnDirectory* at all is because there are multiple 
> 'repositories' under it, all with their own branches and trunks. I put 
> repositories in air quotes because I'm not sure if those branches/trunks 
> parent directories are themselves the repositories, or if "repository" 
> exclusively refers to the entire package.
>
> On Wednesday, January 15, 2014 4:21:11 PM UTC-5, Zachary Gallagher wrote:
>>
>> So this very last issue... (An optimistic claim)
>>
>> DEBUG:root:Got API Error 207 (HTTP code 400): The file was not found in 
>>> the repository
>>> DEBUG:root:Error data: {u'stat': u'fail', u'file': 
>>> u'/*RepositoryName*/branches/20131209-repo-P14/dev/src/modelLibraries/VTRPEAdapter/Makefile',
>>>  
>>> u'err': {u'msg': u'The file was not found in the repository', u'code': 
>>> 207}, u'revision': u'15168'}
>>> Traceback (most recent call last):
>>>   File "/usr/bin/rbt", line 9, in 
>>> load_entry_point('RBTools==0.5.5', 'console_scripts', 'rbt')()
>>>   File 
>>> "/usr/lib/python2.6/site-packages/RBTools-0.5.5-py2.6.egg/rbtools/commands/main.py",
>>>  
>>> line 127, in main
>>> command.run_from_argv([RB_MAIN] + args)
>>>   File 
>>> "/usr/lib/python2.6/site-packages/RBTools-0.5.5-py2.6.egg/rbtools/commands/__init__.py",
>>>  
>>> line 158, in run_from_argv
>>> exit_code = self.main(*args) or 0
>>>   File 
>>> "/usr/lib/python2.6/site-packages/RBTools-0.5.5-py2.6.egg/rbtools/commands/post.py",
>>>  
>>> line 659, in main
>>> submit_as=self.options.submit_as)
>>>   File 
>>> "/usr/lib/python2.6/site-packages/RBTools-0.5.5-py2.6.egg/rbtools/commands/post.py",
>>>  
>>> line 534, in post_request
>>> raise CommandError('\n'.join(error_msg))
>>> rbtools.commands.CommandError: Error uploading diff
>>>
>>> The file was not found in the repository (HTTP 400, API Error 207)
>>> Your review request still exists, but the diff is not attached.
>>
>>
>>
>> The file *is* there on the machine. The absolute path is
>>
>> /dfs/*User*/*RepositoryName*
>> _nrl_p14/dev/src/modelLibraries/VTRPEAdapter/Makefile
>>
>> And the path in svn is
>>
>> https://*SvnServer*/*SvnDirectory*/*RepositoryName*
>> /branches/20131209-repo-P14/dev/src/modelLibraries/VTRPEAdapter/Makefile
>>
>>
>>
>> Any idea what's going on? I'm running "rbt post" from 
>>
>> /dfs/*User*/*RepositoryName*_nrl_p14/
>>
>> and "Repository" in .reviewboardrc is set to the single word 
>> *"RepositoryName."*
>>
>>
>> The slight confusion is that (and I didn't do this, so I'm not sure if it 
>> was right or not at the time)
>>
>> as noted above, these are the repositories in ReviewBoard
>>
>>
>>
>> Repository
>> Path 
>> Hosting
>> Show this repository 
>> SvnDirectoryhttps://*SvnServer*/*SvnDirectory*/ [image: True]
>> RepositoryName_20131209-repo-P14https://*SvnServer*/*SvnDirectory*/
>> *RepositoryName*/branches/20131209-repo-P14 [image: True]RepositoryName
>> -Trunkhttps://*SvnServer*/*SvnDirectory*/*RepositoryName*/trunk [image: 
>> True]Results Viewerhttps://*SvnServer*/*SvnDirectory*
>> /results_viewer/trunk/ [image: False]RepositoryName
>> https://*SvnServer*/*SvnDirectory*/*RepositoryName*/ [image: False]
>>
>> 5 Repositories
>>
>>
>> So I don't even know which one "rbt post" is trying to attach this to. 
>> The second? Or fifth? Maybe the first?
>>
>>
>>
>>
>> On Wednesday, January 15, 2014 4:11:03 PM UTC-5, Christian Hammond wrote:
>>>
>>> No worries. We used to redirect calls like /api/repositories to 
>>> /api/repositories/, but got rid of it.
>>>
>>> The base path is everything between the root of the repository and where 
>>> the diff was taken.
>>>
>>> So basically, if you are in /trunk/myproject, and you run 'svn diff' (or 
>>> 'rbt post', which runs it for you), the base path is /trunk/myproject.
>>>
>>> This requires that the repository entry is set up properly on Review 
>>> Board. It must always point to the very root of a Subversion repository, 
>>> and not a directory inside it.
>>>
>>> Christian
>>>
>>> -- 
>>> Christian Hammond - chi...@chipx86.com
>>> Review Board - http://www.reviewboard.org
>>> Beanbag, Inc. - http://www.beanbaginc.com
>>>
>>>
>>> On Wed, Jan 15, 2014 at 1:08 PM, Zachary Gallagher <
>>> zachary@remcom.com> wrote:
>>>
 Oh.

 Ok, well, that's embarrassing. 

 But now I have a new error. And it's part of what my issue was before. 
 When Subversion speaks of "base path." Does that refer to the parent 
 directory of branches/, trunk/, etc. Or the parent directory of *that* 
 directory. 
 It's something that's apparently so basic that I can't even find 
 in

Re: "Login to the SCM server failed." when using "rbt post -d". Also, /api/repositories is empty.

[Zachary Gallagher]

The reason there is a *SvnDirectory* at all is because there are multiple 
'repositories' under it, all with their own branches and trunks. I put 
repositories in air quotes because I'm not sure if those branches/trunks 
parent directories are themselves the repositories, or if "repository" 
exclusively refers to the entire package.

On Wednesday, January 15, 2014 4:21:11 PM UTC-5, Zachary Gallagher wrote:
>
> So this very last issue... (An optimistic claim)
>
> DEBUG:root:Got API Error 207 (HTTP code 400): The file was not found in 
>> the repository
>> DEBUG:root:Error data: {u'stat': u'fail', u'file': 
>> u'/*RepositoryName*/branches/20131209-repo-P14/dev/src/modelLibraries/VTRPEAdapter/Makefile',
>>  
>> u'err': {u'msg': u'The file was not found in the repository', u'code': 
>> 207}, u'revision': u'15168'}
>> Traceback (most recent call last):
>>   File "/usr/bin/rbt", line 9, in 
>> load_entry_point('RBTools==0.5.5', 'console_scripts', 'rbt')()
>>   File 
>> "/usr/lib/python2.6/site-packages/RBTools-0.5.5-py2.6.egg/rbtools/commands/main.py",
>>  
>> line 127, in main
>> command.run_from_argv([RB_MAIN] + args)
>>   File 
>> "/usr/lib/python2.6/site-packages/RBTools-0.5.5-py2.6.egg/rbtools/commands/__init__.py",
>>  
>> line 158, in run_from_argv
>> exit_code = self.main(*args) or 0
>>   File 
>> "/usr/lib/python2.6/site-packages/RBTools-0.5.5-py2.6.egg/rbtools/commands/post.py",
>>  
>> line 659, in main
>> submit_as=self.options.submit_as)
>>   File 
>> "/usr/lib/python2.6/site-packages/RBTools-0.5.5-py2.6.egg/rbtools/commands/post.py",
>>  
>> line 534, in post_request
>> raise CommandError('\n'.join(error_msg))
>> rbtools.commands.CommandError: Error uploading diff
>>
>> The file was not found in the repository (HTTP 400, API Error 207)
>> Your review request still exists, but the diff is not attached.
>
>
>
> The file *is* there on the machine. The absolute path is
>
> /dfs/*User*/*RepositoryName*
> _nrl_p14/dev/src/modelLibraries/VTRPEAdapter/Makefile
>
> And the path in svn is
>
> https://*SvnServer*/*SvnDirectory*/*RepositoryName*
> /branches/20131209-repo-P14/dev/src/modelLibraries/VTRPEAdapter/Makefile
>
>
>
> Any idea what's going on? I'm running "rbt post" from 
>
> /dfs/*User*/*RepositoryName*_nrl_p14/
>
> and "Repository" in .reviewboardrc is set to the single word 
> *"RepositoryName."*
>
>
> The slight confusion is that (and I didn't do this, so I'm not sure if it 
> was right or not at the time)
>
> as noted above, these are the repositories in ReviewBoard
>
>
>
> Repository
> Path 
> Hosting
> Show this repository 
> SvnDirectoryhttps://*SvnServer*/*SvnDirectory*/ [image: True]
> RepositoryName_20131209-repo-P14https://*SvnServer*/*SvnDirectory*/
> *RepositoryName*/branches/20131209-repo-P14 [image: True]RepositoryName
> -Trunkhttps://*SvnServer*/*SvnDirectory*/*RepositoryName*/trunk [image: 
> True]Results Viewerhttps://*SvnServer*/*SvnDirectory*
> /results_viewer/trunk/ [image: False]RepositoryName
> https://*SvnServer*/*SvnDirectory*/*RepositoryName*/ [image: False]
>
> 5 Repositories
>
>
> So I don't even know which one "rbt post" is trying to attach this to. The 
> second? Or fifth? Maybe the first?
>
>
>
>
> On Wednesday, January 15, 2014 4:11:03 PM UTC-5, Christian Hammond wrote:
>>
>> No worries. We used to redirect calls like /api/repositories to 
>> /api/repositories/, but got rid of it.
>>
>> The base path is everything between the root of the repository and where 
>> the diff was taken.
>>
>> So basically, if you are in /trunk/myproject, and you run 'svn diff' (or 
>> 'rbt post', which runs it for you), the base path is /trunk/myproject.
>>
>> This requires that the repository entry is set up properly on Review 
>> Board. It must always point to the very root of a Subversion repository, 
>> and not a directory inside it.
>>
>> Christian
>>
>> -- 
>> Christian Hammond - chi...@chipx86.com
>> Review Board - http://www.reviewboard.org
>> Beanbag, Inc. - http://www.beanbaginc.com
>>
>>
>> On Wed, Jan 15, 2014 at 1:08 PM, Zachary Gallagher <
>> zachary@remcom.com> wrote:
>>
>>> Oh.
>>>
>>> Ok, well, that's embarrassing. 
>>>
>>> But now I have a new error. And it's part of what my issue was before. 
>>> When Subversion speaks of "base path." Does that refer to the parent 
>>> directory of branches/, trunk/, etc. Or the parent directory of *that* 
>>> directory. 
>>> It's something that's apparently so basic that I can't even find 
>>> information on it. I was told that the repositories had to be "base paths".
>>>
>>> The error I'm getting now is
>>>
>>>
>>> DEBUG:root:Error data: {u'stat': u'fail', u'file': 
>>> u'/*RepositoryName*/branches/20131209-repo-P14/dev/src/modelLibraries/Adapter/Makefile',
>>>  
>>> u'err': {u'msg': u'The file was not found in the repository', u'code': 
>>> 207}, u'revision': u'15168'}
>>>
>>> I think it's because the checkout is 

Re: "Login to the SCM server failed." when using "rbt post -d". Also, /api/repositories is empty.

[Zachary Gallagher]

So this very last issue... (An optimistic claim)

DEBUG:root:Got API Error 207 (HTTP code 400): The file was not found in the 
> repository
> DEBUG:root:Error data: {u'stat': u'fail', u'file': 
> u'/*RepositoryName*/branches/20131209-repo-P14/dev/src/modelLibraries/VTRPEAdapter/Makefile',
>  
> u'err': {u'msg': u'The file was not found in the repository', u'code': 
> 207}, u'revision': u'15168'}
> Traceback (most recent call last):
>   File "/usr/bin/rbt", line 9, in 
> load_entry_point('RBTools==0.5.5', 'console_scripts', 'rbt')()
>   File 
> "/usr/lib/python2.6/site-packages/RBTools-0.5.5-py2.6.egg/rbtools/commands/main.py",
>  
> line 127, in main
> command.run_from_argv([RB_MAIN] + args)
>   File 
> "/usr/lib/python2.6/site-packages/RBTools-0.5.5-py2.6.egg/rbtools/commands/__init__.py",
>  
> line 158, in run_from_argv
> exit_code = self.main(*args) or 0
>   File 
> "/usr/lib/python2.6/site-packages/RBTools-0.5.5-py2.6.egg/rbtools/commands/post.py",
>  
> line 659, in main
> submit_as=self.options.submit_as)
>   File 
> "/usr/lib/python2.6/site-packages/RBTools-0.5.5-py2.6.egg/rbtools/commands/post.py",
>  
> line 534, in post_request
> raise CommandError('\n'.join(error_msg))
> rbtools.commands.CommandError: Error uploading diff
>
> The file was not found in the repository (HTTP 400, API Error 207)
> Your review request still exists, but the diff is not attached.



The file *is* there on the machine. The absolute path is

/dfs/*User*/*RepositoryName*
_nrl_p14/dev/src/modelLibraries/VTRPEAdapter/Makefile

And the path in svn is

https://*SvnServer*/*SvnDirectory*/*RepositoryName*
/branches/20131209-repo-P14/dev/src/modelLibraries/VTRPEAdapter/Makefile



Any idea what's going on? I'm running "rbt post" from 

/dfs/*User*/*RepositoryName*_nrl_p14/

and "Repository" in .reviewboardrc is set to the single word 
*"RepositoryName."*


The slight confusion is that (and I didn't do this, so I'm not sure if it 
was right or not at the time)

as noted above, these are the repositories in ReviewBoard



Repository
Path 
Hosting
Show this repository 
SvnDirectoryhttps://*SvnServer*/*SvnDirectory*/ [image: True]
RepositoryName_20131209-repo-P14https://*SvnServer*/*SvnDirectory*/
*RepositoryName*/branches/20131209-repo-P14 [image: True]RepositoryName
-Trunkhttps://*SvnServer*/*SvnDirectory*/*RepositoryName*/trunk [image: 
True]Results Viewerhttps://*SvnServer*/*SvnDirectory*/results_viewer/trunk/ 
[image: 
False]RepositoryName
https://*SvnServer*/*SvnDirectory*/*RepositoryName*/ [image: False]

5 Repositories


So I don't even know which one "rbt post" is trying to attach this to. The 
second? Or fifth? Maybe the first?




On Wednesday, January 15, 2014 4:11:03 PM UTC-5, Christian Hammond wrote:
>
> No worries. We used to redirect calls like /api/repositories to 
> /api/repositories/, but got rid of it.
>
> The base path is everything between the root of the repository and where 
> the diff was taken.
>
> So basically, if you are in /trunk/myproject, and you run 'svn diff' (or 
> 'rbt post', which runs it for you), the base path is /trunk/myproject.
>
> This requires that the repository entry is set up properly on Review 
> Board. It must always point to the very root of a Subversion repository, 
> and not a directory inside it.
>
> Christian
>
> -- 
> Christian Hammond - chi...@chipx86.com 
> Review Board - http://www.reviewboard.org
> Beanbag, Inc. - http://www.beanbaginc.com
>
>
> On Wed, Jan 15, 2014 at 1:08 PM, Zachary Gallagher 
> 
> > wrote:
>
>> Oh.
>>
>> Ok, well, that's embarrassing. 
>>
>> But now I have a new error. And it's part of what my issue was before. 
>> When Subversion speaks of "base path." Does that refer to the parent 
>> directory of branches/, trunk/, etc. Or the parent directory of *that* 
>> directory. 
>> It's something that's apparently so basic that I can't even find 
>> information on it. I was told that the repositories had to be "base paths".
>>
>> The error I'm getting now is
>>
>>
>> DEBUG:root:Error data: {u'stat': u'fail', u'file': 
>> u'/*RepositoryName*/branches/20131209-repo-P14/dev/src/modelLibraries/Adapter/Makefile',
>>  
>> u'err': {u'msg': u'The file was not found in the repository', u'code': 
>> 207}, u'revision': u'15168'}
>>
>> I think it's because the checkout is actually a directory of branches. 
>> But it's somehow trying to act like this is the base path.
>>
>>
>>
>>
>> On Wednesday, January 15, 2014 3:55:20 PM UTC-5, David Trowbridge wrote:
>>
>>> I mean in the repository configuration in the reviewboard admin.
>>>
>>> -David
>>>
>>> On Jan 15, 2014, at 12:49 PM, Zachary Gallagher  
>>> wrote:
>>>
>>> I can log in with
>>>
>>> gallagher
>>>
>>> password
>>>
>>>
>>> But I can't run *rbt post* with it.
>>>  
>>> -- 
>>> Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
>>> ---
>>> Sign up for Review Board hosting at RBCom

Re: "Login to the SCM server failed." when using "rbt post -d". Also, /api/repositories is empty.

[Christian Hammond]

No worries. We used to redirect calls like /api/repositories to
/api/repositories/, but got rid of it.

The base path is everything between the root of the repository and where
the diff was taken.

So basically, if you are in /trunk/myproject, and you run 'svn diff' (or
'rbt post', which runs it for you), the base path is /trunk/myproject.

This requires that the repository entry is set up properly on Review Board.
It must always point to the very root of a Subversion repository, and not a
directory inside it.

Christian

-- 
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com


On Wed, Jan 15, 2014 at 1:08 PM, Zachary Gallagher <
zachary.gallag...@remcom.com> wrote:

> Oh.
>
> Ok, well, that's embarrassing.
>
> But now I have a new error. And it's part of what my issue was before.
> When Subversion speaks of "base path." Does that refer to the parent
> directory of branches/, trunk/, etc. Or the parent directory of *that* 
> directory.
> It's something that's apparently so basic that I can't even find
> information on it. I was told that the repositories had to be "base paths".
>
> The error I'm getting now is
>
>
> DEBUG:root:Error data: {u'stat': u'fail', u'file': 
> u'/*RepositoryName*/branches/20131209-repo-P14/dev/src/modelLibraries/Adapter/Makefile',
> u'err': {u'msg': u'The file was not found in the repository', u'code':
> 207}, u'revision': u'15168'}
>
> I think it's because the checkout is actually a directory of branches. But
> it's somehow trying to act like this is the base path.
>
>
>
>
> On Wednesday, January 15, 2014 3:55:20 PM UTC-5, David Trowbridge wrote:
>
>> I mean in the repository configuration in the reviewboard admin.
>>
>> -David
>>
>> On Jan 15, 2014, at 12:49 PM, Zachary Gallagher 
>> wrote:
>>
>> I can log in with
>>
>> gallagher
>>
>> password
>>
>>
>> But I can't run *rbt post* with it.
>>
>> --
>> 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 reviewboard...@googlegroups.com.
>>
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>  --
> 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 reviewboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
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 reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: "Login to the SCM server failed." when using "rbt post -d". Also, /api/repositories is empty.

[Zachary Gallagher]

-.-


On Wednesday, January 15, 2014 3:57:25 PM UTC-5, Christian Hammond wrote:
>
> On Wed, Jan 15, 2014 at 12:02 PM, Zachary Gallagher <
> zachary@remcom.com > wrote:
>
>> Also, if I navigate to http://*ReviewBoardServer*/api/repositories, I 
>> get this. Yet there are 5 repositories listed in the admin dashboard.
>>
>> Not sure if that is expected or not. Not entirely up to snuff on http and 
>> the web api.
>>
>> 
>>> 
>>>  fail
>>>  
>>>   Object does not exist
>>>   100
>>>  
>>> 
>>
>>
>
> You're missing a trailing slash. It must be 
> http://ReviewBoardServer/api/repositories/
>
> Christian
>
> -- 
> Christian Hammond - chi...@chipx86.com 
> Review Board - http://www.reviewboard.org
> Beanbag, Inc. - http://www.beanbaginc.com
>
>
>  
>
>

-- 
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 reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: "Login to the SCM server failed." when using "rbt post -d". Also, /api/repositories is empty.

[Zachary Gallagher]

Oh.

Ok, well, that's embarrassing. 

But now I have a new error. And it's part of what my issue was before. When 
Subversion speaks of "base path." Does that refer to the parent directory 
of branches/, trunk/, etc. Or the parent directory of *that* directory. 
It's something that's apparently so basic that I can't even find 
information on it. I was told that the repositories had to be "base paths".

The error I'm getting now is


DEBUG:root:Error data: {u'stat': u'fail', u'file': 
u'/*RepositoryName*/branches/20131209-repo-P14/dev/src/modelLibraries/Adapter/Makefile',
 
u'err': {u'msg': u'The file was not found in the repository', u'code': 
207}, u'revision': u'15168'}

I think it's because the checkout is actually a directory of branches. But 
it's somehow trying to act like this is the base path.




On Wednesday, January 15, 2014 3:55:20 PM UTC-5, David Trowbridge wrote:
>
> I mean in the repository configuration in the reviewboard admin.
>
> -David
>
> On Jan 15, 2014, at 12:49 PM, Zachary Gallagher 
> > 
> wrote:
>
> I can log in with
>
> gallagher
>
> password
>
>
> But I can't run *rbt post* with it.
>
> -- 
> 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 reviewboard...@googlegroups.com .
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

-- 
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 reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: "Login to the SCM server failed." when using "rbt post -d". Also, /api/repositories is empty.

[Christian Hammond]

On Wed, Jan 15, 2014 at 12:02 PM, Zachary Gallagher <
zachary.gallag...@remcom.com> wrote:

> Also, if I navigate to http://*ReviewBoardServer*/api/repositories, I get
> this. Yet there are 5 repositories listed in the admin dashboard.
>
> Not sure if that is expected or not. Not entirely up to snuff on http and
> the web api.
>
> 
>> 
>>  fail
>>  
>>   Object does not exist
>>   100
>>  
>> 
>
>

You're missing a trailing slash. It must be
http://ReviewBoardServer/api/repositories/

Christian

-- 
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com

-- 
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 reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: "Login to the SCM server failed." when using "rbt post -d". Also, /api/repositories is empty.

[David Trowbridge]

I mean in the repository configuration in the reviewboard admin.

-David

> On Jan 15, 2014, at 12:49 PM, Zachary Gallagher 
>  wrote:
> 
> I can log in with
> 
> gallagher
> 
> password
> 
> 
> But I can't run rbt post with it.
> -- 
> 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 reviewboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.

-- 
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 reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: "Login to the SCM server failed." when using "rbt post -d". Also, /api/repositories is empty.

[Zachary Gallagher]

I can log in with

gallagher

password


But I can't run *rbt post* with it.

-- 
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 reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: "Login to the SCM server failed." when using "rbt post -d". Also, /api/repositories is empty.

[Zachary Gallagher]

I changed the password for my username to *password*. The actual, all 
lowercase word. Then I ran

rbt post -d --username=gallagher --password=password --submit-as=gallagher

And got the same error.

On Wednesday, January 15, 2014 3:41:49 PM UTC-5, David Trowbridge wrote:
>
> This error is typically a problem with the credentials on the reviewboard 
> side, not rbtools. Can you check that those are correct, and if they are, 
> check the reviewboard log file for any more interesting errors?
>
> -David
>
> On Jan 15, 2014, at 12:35 PM, Zachary Gallagher 
> > 
> wrote:
>
> I suppose it should also be said that, as far as the *actual* problem at 
> hand. I'm sure that all the credentials I've entered were correct. I can 
> connect to svn and ReviewBoard with them. I just don't know if there's some 
> setting I'm missing, or I put the right ones in the wrong places.
>
> I just don't know how to see what it's trying to do before it gets the 
> Login error. I ran a strace, but I didn't glean anything useful from it.
>
> -- 
> 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 reviewboard...@googlegroups.com .
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

-- 
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 reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: "Login to the SCM server failed." when using "rbt post -d". Also, /api/repositories is empty.

[David Trowbridge]

This error is typically a problem with the credentials on the reviewboard side, 
not rbtools. Can you check that those are correct, and if they are, check the 
reviewboard log file for any more interesting errors?

-David

> On Jan 15, 2014, at 12:35 PM, Zachary Gallagher 
>  wrote:
> 
> I suppose it should also be said that, as far as the actual problem at hand. 
> I'm sure that all the credentials I've entered were correct. I can connect to 
> svn and ReviewBoard with them. I just don't know if there's some setting I'm 
> missing, or I put the right ones in the wrong places.
> 
> I just don't know how to see what it's trying to do before it gets the Login 
> error. I ran a strace, but I didn't glean anything useful from it.
> -- 
> 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 reviewboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.

-- 
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 reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: "Login to the SCM server failed." when using "rbt post -d". Also, /api/repositories is empty.

[Zachary Gallagher]

I suppose it should also be said that, as far as the *actual* problem at 
hand. I'm sure that all the credentials I've entered were correct. I can 
connect to svn and ReviewBoard with them. I just don't know if there's some 
setting I'm missing, or I put the right ones in the wrong places.

I just don't know how to see what it's trying to do before it gets the 
Login error. I ran a strace, but I didn't glean anything useful from it.

-- 
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 reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: "Login to the SCM server failed." when using "rbt post -d". Also, /api/repositories is empty.

[Zachary Gallagher]

Ok, really, last post. I made a mistake in one post.

The actual directory on the svn server that contains

conf  dav  db  format  hooks  locks  README.txt

is 

export/svn/code/

The "*SvnDirectory*" name itself is actually svncode. Somehow I thought 
keeping everything unnamed would help people reading this later to be able 
to apply it to their case. Not sure if that just made it more complicated.

-- 
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 reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: "Login to the SCM server failed." when using "rbt post -d". Also, /api/repositories is empty.

[Zachary Gallagher]

I suppose a brief summary, because it seems confusing reading it.


The directory on the svn machine goes

*SvnServer/*export/svn/*SvnDirectory/RepositoryName*
/branches/20131209_repo_p14

Likewise, to access this all, it's 

https://*SvnServer/SvnDirectory*/*RepositoryName*/branches/20131209_repo_p14



The user's machine one which RBTools is installed has a directory of 

/dfs/*User*/*RepositoryName_*repo_p14. Which I presume is a checkout of the 
directory under branches/. When I run "svn info" in that directory I get 
the result in the post above.


The .reviewboardrc file lists the primary repository name. And despite 
presumably working in a checkout of a directory under branches, the "rbt 
post" command seems to me to be configured (through .reviewboardrc) to want 
to post to the top level of the repository itself. Not sure how Subversion 
handles/cares for that.



The five directories in ReviewBoard are


Repository
Path 
Hosting
Show this repository 
SvnDirectoryhttps://*SvnServer*/*SvnDirectory*/ [image: True]
RepositoryName_20131209-repo-P14https://*SvnServer*/*SvnDirectory*/
*RepositoryName*/branches/20131209-repo-P14 [image: True]RepositoryName
-Trunkhttps://*SvnServer*/*SvnDirectory*/*RepositoryName*/trunk [image: 
True]Results Viewerhttps://*SvnServer*/*SvnDirectory*/results_viewer/trunk/ 
[image: 
False]RepositoryName
https://*SvnServer*/*SvnDirectory*/*RepositoryName*/ [image: False]

5 Repositories

-- 
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 reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: "Login to the SCM server failed." when using "rbt post -d". Also, /api/repositories is empty.

[Zachary Gallagher]

This looks like a mess, and sort of an overload. I'm only going on my own 
philosophy of preferring more information to less.

Also, anyone willing to take the time to go over this in the first place, I 
want to express sincere gratitude. Free software, free support. I really, 
really appreciate what that means.

-- 
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 reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: "Login to the SCM server failed." when using "rbt post -d". Also, /api/repositories is empty.

[Zachary Gallagher]

There is obviously some sort of credential mismatch. But there is no 
indication as to what credentials it's using on what. I don't know what is 
being mismatched. And I don't know how to find out.

-- 
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 reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

"Login to the SCM server failed." when using "rbt post -d". Also, /api/repositories is empty.

[Zachary Gallagher]

I've made it farther now than I have ever before. But I'm still running 
into one last issue. (Maybe two.)


First, background information. Hopefully this makes more sense. I'm 
learning Subversion as I do all this. C'est la vie.


The .reviewboardrc file reads as

REVIEWBOARD_URL = "http://*ReviewBoardServer*";
>
> REPOSITORY = "*RepositoryName*" (Not the name as it appears in the admin 
>> dashboard, but it is the parent directory to branches/, trunk/, tags/. It 
>> goes https://*ServerName/SvnDirectory/RepositoryName. *The checkout 
>> directory is a checkout of a repository under 
>
> *RepositoryName/*branches/. The *is* a repository named *RepositoryName *in 
> the admin dashboard, that refers to the parent directory of branches/, 
> trunk/, tags/. But there have been no noted conflicts. Not sure if the 
> repository names in ReviewBoard matter.)



*SvnDirectory* is the actual directory under /svn/ on the machine itself. 
I'm providing this information because I'm still learning Subversion, and 
don't know exactly/technically what Subversion defines as "repository" and 
"working copy." I understand the concepts, but I'm still learning their 
literal/technical/practical application.

Ok, so... 

I'm in the checkout directory. The checkout directory is a checkout of 
*RepositoryName/*branches/20131209-repo-P14.   The exact directory on the 
user's machine is /dfs/*User/RepositoryName*_repo_P14.

If I run just "svn info" I get

-bash-4.1$ svn info
> Path: .
> Working Copy Root Path: /dfs/*User*/*RepositoryName*_nrl_p14

URL: https://*ServerName*/*SvnDirectory*/*RepositoryName*
> /branches/20131209-repo-P14
> Repository Root: https://*ServerName*/*SvnDirectory*
> Repository UUID: (buncha letters & numbers)
> Revision: 15168
> Node Kind: directory
> Schedule: normal
> Depth: files
> Last Changed Author: *User*
> Last Changed Rev: 15168
> Last Changed Date: 2014-01-11 13:19:21 -0500 (Sat, 11 Jan 2014)

   


I use "rbt post -d".


It runs a bunch of "svn info" commands on the dev/ directory. Then gets to 
this.


DEBUG:root:Making HTTP GET request to http://*ReviewBoardServer*
>> /api/review-requests/
>
> DEBUG:root:Making HTTP POST request to http://*ReviewBoardServer*
>> /api/review-requests/
>
> DEBUG:root:Making HTTP GET request to http://*ReviewBoardServer*
>> /api/review-requests/45/diffs/
>
> DEBUG:root:Making HTTP POST request to http://*ReviewBoardServer*
>> /api/review-requests/45/diffs/
>
> DEBUG:root:Got API Error 105 (HTTP code 400): One or more fields had errors
>
> DEBUG:root:Error data: {u'fields': {u'path': [u'Login to the SCM server 
>> failed.']}, u'stat': u'fail', u'err': {u'msg': u'One or more fields had 
>> errors', u'code': 105}}
>
> Traceback (most recent call last):
>
>   File "/usr/bin/rbt", line 9, in 
>
> load_entry_point('RBTools==0.5.5', 'console_scripts', 'rbt')()
>
>   File 
>> "/usr/lib/python2.6/site-packages/RBTools-0.5.5-py2.6.egg/rbtools/commands/main.py",
>>  
>> line 127, in main
>
> command.run_from_argv([RB_MAIN] + args)
>
>   File 
>> "/usr/lib/python2.6/site-packages/RBTools-0.5.5-py2.6.egg/rbtools/commands/__init__.py",
>>  
>> line 158, in run_from_argv
>
> exit_code = self.main(*args) or 0
>
>   File 
>> "/usr/lib/python2.6/site-packages/RBTools-0.5.5-py2.6.egg/rbtools/commands/post.py",
>>  
>> line 659, in main
>
> submit_as=self.options.submit_as)
>
>   File 
>> "/usr/lib/python2.6/site-packages/RBTools-0.5.5-py2.6.egg/rbtools/commands/post.py",
>>  
>> line 534, in post_request
>
> raise CommandError('\n'.join(error_msg)) 
>
> rbtools.commands.CommandError: Error uploading diff   
>
>  
>
>  
>
>  
>
> One or more fields had errors (HTTP 400, API Error 105 
>
>  
>
>   path: Login to the SCM server failed 
>
>  
>
> Your review request still exists, but the diff is not attached.
>
>
>>
>







Also, if I navigate to http://*ReviewBoardServer*/api/repositories, I get 
this. Yet there are 5 repositories listed in the admin dashboard.

Not sure if that is expected or not. Not entirely up to snuff on http and 
the web api.


> 
>  fail
>  
>   Object does not exist
>   100
>  
> 

















-- 
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 reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Create new review request failed with error - 'Login to the SCM server failed.' Can anybody help ?

[Shridhar Vishwakarma]

Hi,

I setup ReviewBoard yesterday. My repository is over VPN which is of
the type -svn. Now if try to create new review request I am getting
error -

'Login to the SCM server failed.'

# Authentication : SVN authentication is provided in Repository
details,
# Repository path: svn:///  ('Repository Root' which i get
with 'svn info' command in the checked out directory)
# Repository Type : Subversion

Can anybody help me to resolve this problem.. ? How to debug the
error ? I didn't get any error log in the Apache log

Thanks,
Shridhar

-- 
Want to help the Review Board project? Donate today at 
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en

Re: Login to the SCM server failed

[Christian Hammond]

What type of repository is it?

It sounds like it's expecting credentials in the repository entry in the
admin UI, and doesn't have valid ones.

Christian

-- 
Christian Hammond - chip...@chipx86.com
Review Board - http://www.review-board.org
VMware, Inc. - http://www.vmware.com


On Sat, Jul 11, 2009 at 1:12 PM, henriquecoelho wrote:

>
> Hello,
>
> I'm getting the following message when i try to create a new review
> entry : "Login to the SCM server failed" What could be?
>
> Running review board on:
> Windows 2008 server
> Apache 2.2
> >
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To post to this group, send email to reviewboard@googlegroups.com
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en
-~--~~~~--~~--~--~---

Login to the SCM server failed

[henriquecoelho]

Hello,

I'm getting the following message when i try to create a new review
entry : "Login to the SCM server failed" What could be?

Running review board on:
Windows 2008 server
Apache 2.2
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To post to this group, send email to reviewboard@googlegroups.com
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en
-~--~~~~--~~--~--~---