Re: Repository List Resource does not return restricted repositories

2014-10-04 Thread David Carson
Is there any way to determine if 'rbt setup-repo' is using the wrong 
username?  I've double-checked, and she is definitely in the SCM group, and 
the SCM group has access to the repository that the command cannot find.

Here is the info you requested:

   - ReviewBoard version: 2.0.8
   - RBTools version: 0.6.2

Here is the debug run of the command:

(0)[praj@cyprus cmtools] rbt setup-repo --debug
>>> RBTools 0.6.2
>>> Python 2.6.6 (r266:84292, Jan 22 2014, 09:42:36) 
[GCC 4.4.7 20120313 (Red Hat 4.4.7-4)]
>>> Running on Linux-2.6.32-431.29.2.el6.x86_64-x86_64-with-centos-6.5-Final
>>> Home = /home/praj
>>> Current directory = /home/praj/cmtools
Enter the Review Board server URL: http://reviewboard
>>> Checking for a Subversion repository...
>>> Running: svn info --non-interactive
>>> Running: diff --version
>>> *repository info*: Path: svn://*buildmaster*/cmtools, Base path: 
/trunk, Supports changesets: False
>>> Making HTTP GET request to http://reviewboard/api/
>>> Making HTTP GET request to http://reviewboard/api/repositories/
No Subversion repository found or selected for http://reviewboard. 
.reviewboardrc not created.

Note that the "repository info" line, which gives the URL as svn://
*buildmaster*/cmtools, is sort of incorrect.  In ReviewBoard itself, I have 
defined the 'cmtools' repository using its fully qualifed hostname, rather 
than the short hostname (buildmaster).  However, I checked out my own copy 
of 'cmtools' exactly the same way, using the short hostname, and I ran 'rbt 
setup-repo' without incident.

Thanks for looking into it.

David

On Saturday, October 4, 2014 9:26:37 PM UTC-4, chri...@beanbaginc.com wrote:
>
> Hey David, 
>
> rbt setup-repo should definitely return those repositories, provided that 
> they're actually accessible as that user (make sure it's the correct user!) 
> and they're marked as visible in the administration UI. 
>
> What version of Review Board and RBTools are you using? 
>
> Can you show me the setup-repo command with --debug? 
>
> Christian 
>
> --   
> Christian Hammond - chri...@beanbaginc.com
> Review Board - https://www.reviewboard.org   
> Beanbag, Inc. - https://www.beanbaginc.com 
>
> -Original Message- 
> From: David Carson > 
> Reply: revie...@googlegroups.com   >> 
> Date: October 3, 2014 at 8:33:48 PM 
> To: revie...@googlegroups.com   >> 
> Cc: dcca...@gmail.com  >>, 
> chri...@beanbaginc.com  >> 
>
> Subject:  Re: Repository List Resource does not return restricted 
> repositories 
>
> > Christian, 
> >   
> > Yeah, I thought that might be the case with the command line I was 
> using. 
> > I didn't know how to force a specific user. 
> >   
> > But my real question has to do with using "rbt setup-repo" -- which I 
> > assume somehow knows how to either use a proper username or prompt for 
> > one. I could not help my colleague to get this working, even though my 
> own 
> > attempt was successful. As far as we could tell, we were both doing the 
> > same thing. 
> >   
> > At any rate, we just went ahead and created a .reviewboardrc manually, 
> but 
> > since I'm administering this site, I'd like to be able to help someone 
> > else, should they come upon the same problem. 
> >   
> > On Friday, October 3, 2014 7:06:37 PM UTC-4, chri...@beanbaginc.com 
> wrote: 
> > > 
> > > Hey David, 
> > > 
> > > Is that the full command line? That's going to make the request as an 
> > > anonymous user, not as your user, since there aren't any auth 
> credentials 
> > > there. 
> > > 
> > > What version of Review Board are you using? 
> > > 
> > > Christian 
> > > 
> > > -- 
> > > Christian Hammond - chri...@beanbaginc.com   
> > > Review Board - https://www.reviewboard.org 
> > > Beanbag, Inc. - https://www.beanbaginc.com 
> > > 
> > > -Original Message- 
> > > From: David Carson > 
> > > Reply: revie...@googlegroups.com > > >> 
> > > Date: October 3, 2014 at 4:02:54 PM 
> > > To: revie...@googlegroups.com > > >> 
> > > Subject: Repository List Resource does not return restricted 
> repositories 
> > > 
> > > > Some of our repositories are wide open. But we also have a few which 
> are 
> > > > restricted for the SCM team's use only. 
> > > > 
> > > > If I do the following, I would expect to get all the repositories 
>

Re: Repository List Resource does not return restricted repositories

2014-10-04 Thread christ...@beanbaginc.com
Hey David,

rbt setup-repo should definitely return those repositories, provided that 
they're actually accessible as that user (make sure it's the correct user!) and 
they're marked as visible in the administration UI.

What version of Review Board and RBTools are you using?

Can you show me the setup-repo command with --debug?

Christian

--  
Christian Hammond - christ...@beanbaginc.com  
Review Board - https://www.reviewboard.org  
Beanbag, Inc. - https://www.beanbaginc.com

-Original Message-
From: David Carson 
Reply: reviewboard@googlegroups.com >
Date: October 3, 2014 at 8:33:48 PM
To: reviewboard@googlegroups.com >
Cc: dccar...@gmail.com >, christ...@beanbaginc.com 
>
Subject:  Re: Repository List Resource does not return restricted repositories

> Christian,
>  
> Yeah, I thought that might be the case with the command line I was using.
> I didn't know how to force a specific user.
>  
> But my real question has to do with using "rbt setup-repo" -- which I
> assume somehow knows how to either use a proper username or prompt for
> one. I could not help my colleague to get this working, even though my own
> attempt was successful. As far as we could tell, we were both doing the
> same thing.
>  
> At any rate, we just went ahead and created a .reviewboardrc manually, but
> since I'm administering this site, I'd like to be able to help someone
> else, should they come upon the same problem.
>  
> On Friday, October 3, 2014 7:06:37 PM UTC-4, chri...@beanbaginc.com wrote:
> >
> > Hey David,
> >
> > Is that the full command line? That's going to make the request as an
> > anonymous user, not as your user, since there aren't any auth credentials
> > there.
> >
> > What version of Review Board are you using?
> >
> > Christian
> >
> > --
> > Christian Hammond - chri...@beanbaginc.com  
> > Review Board - https://www.reviewboard.org
> > Beanbag, Inc. - https://www.beanbaginc.com
> >
> > -----Original Message-
> > From: David Carson >
> > Reply: revie...@googlegroups.com > > >>
> > Date: October 3, 2014 at 4:02:54 PM
> > To: revie...@googlegroups.com > > >>
> > Subject: Repository List Resource does not return restricted repositories
> >
> > > Some of our repositories are wide open. But we also have a few which are
> > > restricted for the SCM team's use only.
> > >
> > > If I do the following, I would expect to get all the repositories back,
> > > since I am in the SCM group which has been given access to the
> > restricted
> > > repos.
> > >
> > > curl http://reviewboard/api/repositories/ -A application/json
> > > {"*total_results"**: 2,* "stat": "ok", "repositories": [{"n
> > >
> > >
> > >
> > > I was not expecting two, I was expecting four, which includes the ones
> > only
> > > my team can access.
> > >
> > > On the admin page for repositories, in the *Access Control* section, I
> > have
> > > the following for one of the repos which was not returned:
> > >
> > > - Publicly Accessible is *not* checked
> > > - Users with Access is empty
> > > - Review Groups with Access contains the group called SCM, of which I am
> > > a member.
> > >
> > > Should I need to add users to the "Users with Access" box? I hope not,
> > > because that seems to defeat the purpose of having groups.
> > >
> > > The reason I hit this issue is because one of the other members of the
> > SCM
> > > team was trying to get rbt setup-repo working, and it kept complaining
> > > that it could not find the repository, no matter how she answered the
> > > prompts. I used the '--debug' option and discovered it was using the
> > API,
> > > so then I started playing with that.
> > >
> > > Even when I run the 'curl' command above myself, I only get two
> > > repositories, which does *not* include the one that I have successfully
> > set
> > > up using the "setup-repo" command. If I can use rbt setup-repo to set up
> > > my working copy, then why does curl not return all four of the
> > repositories
> > > to me?
> > >
> > > What gives?
> > >
> > > --
> > > Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
> > > ---
> > > Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
> > > ---

Re: Repository List Resource does not return restricted repositories

2014-10-03 Thread David Carson
Christian,

Yeah, I thought that might be the case with the command line I was using.  
I didn't know how to force a specific user.

But my real question has to do with using "rbt setup-repo" -- which I 
assume somehow knows how to either use a proper username or prompt for 
one.  I could not help my colleague to get this working, even though my own 
attempt was successful.  As far as we could tell, we were both doing the 
same thing.

At any rate, we just went ahead and created a .reviewboardrc manually, but 
since I'm administering this site, I'd like to be able to help someone 
else, should they come upon the same problem.

On Friday, October 3, 2014 7:06:37 PM UTC-4, chri...@beanbaginc.com wrote:
>
> Hey David, 
>
> Is that the full command line? That's going to make the request as an 
> anonymous user, not as your user, since there aren't any auth credentials 
> there. 
>
> What version of Review Board are you using? 
>
> Christian 
>
> --   
> Christian Hammond - chri...@beanbaginc.com
> Review Board - https://www.reviewboard.org   
> Beanbag, Inc. - https://www.beanbaginc.com 
>
> -Original Message- 
> From: David Carson > 
> Reply: revie...@googlegroups.com   >> 
> Date: October 3, 2014 at 4:02:54 PM 
> To: revie...@googlegroups.com   >> 
> Subject:  Repository List Resource does not return restricted repositories 
>
> > Some of our repositories are wide open. But we also have a few which are 
> > restricted for the SCM team's use only. 
> >   
> > If I do the following, I would expect to get all the repositories back, 
> > since I am in the SCM group which has been given access to the 
> restricted 
> > repos. 
> >   
> > curl http://reviewboard/api/repositories/ -A application/json 
> > {"*total_results"**: 2,* "stat": "ok", "repositories": [{"n 
> >   
> >   
> >   
> > I was not expecting two, I was expecting four, which includes the ones 
> only 
> > my team can access. 
> >   
> > On the admin page for repositories, in the *Access Control* section, I 
> have 
> > the following for one of the repos which was not returned: 
> >   
> > - Publicly Accessible is *not* checked 
> > - Users with Access is empty 
> > - Review Groups with Access contains the group called SCM, of which I am 
> > a member. 
> >   
> > Should I need to add users to the "Users with Access" box? I hope not, 
> > because that seems to defeat the purpose of having groups. 
> >   
> > The reason I hit this issue is because one of the other members of the 
> SCM 
> > team was trying to get rbt setup-repo working, and it kept complaining 
> > that it could not find the repository, no matter how she answered the 
> > prompts. I used the '--debug' option and discovered it was using the 
> API, 
> > so then I started playing with that. 
> >   
> > Even when I run the 'curl' command above myself, I only get two 
> > repositories, which does *not* include the one that I have successfully 
> set 
> > up using the "setup-repo" command. If I can use rbt setup-repo to set up 
> > my working copy, then why does curl not return all four of the 
> repositories 
> > to me? 
> >   
> > What gives? 
> >   
> > -- 
> > 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/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 reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Repository List Resource does not return restricted repositories

2014-10-03 Thread christ...@beanbaginc.com
Hey David,

Is that the full command line? That's going to make the request as an anonymous 
user, not as your user, since there aren't any auth credentials there.

What version of Review Board are you using?

Christian

--  
Christian Hammond - christ...@beanbaginc.com  
Review Board - https://www.reviewboard.org  
Beanbag, Inc. - https://www.beanbaginc.com

-Original Message-
From: David Carson 
Reply: reviewboard@googlegroups.com >
Date: October 3, 2014 at 4:02:54 PM
To: reviewboard@googlegroups.com >
Subject:  Repository List Resource does not return restricted repositories

> Some of our repositories are wide open. But we also have a few which are
> restricted for the SCM team's use only.
>  
> If I do the following, I would expect to get all the repositories back,
> since I am in the SCM group which has been given access to the restricted
> repos.
>  
> curl http://reviewboard/api/repositories/ -A application/json
> {"*total_results"**: 2,* "stat": "ok", "repositories": [{"n
>  
>  
>  
> I was not expecting two, I was expecting four, which includes the ones only
> my team can access.
>  
> On the admin page for repositories, in the *Access Control* section, I have
> the following for one of the repos which was not returned:
>  
> - Publicly Accessible is *not* checked
> - Users with Access is empty
> - Review Groups with Access contains the group called SCM, of which I am
> a member.
>  
> Should I need to add users to the "Users with Access" box? I hope not,
> because that seems to defeat the purpose of having groups.
>  
> The reason I hit this issue is because one of the other members of the SCM
> team was trying to get rbt setup-repo working, and it kept complaining
> that it could not find the repository, no matter how she answered the
> prompts. I used the '--debug' option and discovered it was using the API,
> so then I started playing with that.
>  
> Even when I run the 'curl' command above myself, I only get two
> repositories, which does *not* include the one that I have successfully set
> up using the "setup-repo" command. If I can use rbt setup-repo to set up
> my working copy, then why does curl not return all four of the repositories
> to me?
>  
> What gives?
>  
> --
> 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/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 reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Repository List Resource does not return restricted repositories

2014-10-03 Thread David Carson
Some of our repositories are wide open.  But we also have a few which are 
restricted for the SCM team's use only.

If I do the following, I would expect to get all the repositories back, 
since I am in the SCM group which has been given access to the restricted 
repos.

curl http://reviewboard/api/repositories/ -A application/json
{"*total_results"**: 2,* "stat": "ok", "repositories": [{"n



I was not expecting two, I was expecting four, which includes the ones only 
my team can access.

On the admin page for repositories, in the *Access Control* section, I have 
the following for one of the repos which was not returned:

   - Publicly Accessible is *not* checked
   - Users with Access is empty
   - Review Groups with Access contains the group called SCM, of which I am 
   a member.

Should I need to add users to the "Users with Access" box?  I hope not, 
because that seems to defeat the purpose of having groups.

The reason I hit this issue is because one of the other members of the SCM 
team was trying to get  rbt setup-repo  working, and it kept complaining 
that it could not find the repository, no matter how she answered the 
prompts.  I used the '--debug' option and discovered it was using the API, 
so then I started playing with that.

Even when I run the 'curl' command above myself, I only get two 
repositories, which does *not* include the one that I have successfully set 
up using the "setup-repo" command.  If I can use  rbt setup-repo  to set up 
my working copy, then why does curl not return all four of the repositories 
to me?

What gives?

-- 
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/d/optout.