Re: How to stop new reviews being created on 1.6.16 from RBTools?

2014-07-29 Thread Stephen
Hi David,

Thanks for replying. It was necessary for me to get confidence in the 
migration procedure and my earlier post was made when I have not really 
practised it. At the end of last week I was ready and I moved the 
rbsite/database (~140MB) over to the new server and switched the older 
server off as you suggested. The site/DB upgrade scripts worked with no 
issues, so thanks guys for supporting the upgrade path with quality scripts.

Regards,
Stephen.

-- 
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.


Cursor placement issues in 'View diff' comment dialogue RB 2.0.3

2014-07-29 Thread Stephen
Hi,

I've noticed an issue with the cursor placement in the comment dialogue 
used when adding comments to a line of code in a 'View diff' review mode. 
It seems the when do I wrap code used for painting the text to the 
writeable field is working differently to the wrap code used for cursor 
position. I see this quite often in the default sized dialogue the cursor 
ends up ahead of the actual insertion point due to the word wrap decision 
of the previous line(s). See attached.

It would be good to get this fixed soon as it occurs in almost every 
comment I add in a review. If there is a workaround then let me know, maybe 
it is my browser (Internet Explorer) or the default fonts I'm using.

Thanks,
Stephen.

-- 
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: Cursor placement issues in 'View diff' comment dialogue RB 2.0.3

2014-07-29 Thread Stephen

Seems to work without issues in Firefox 30.0 however.
I was using IE 11.0.10 where the problem occurs in Windows 7.



-- 
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: Formatting errors in description field

2014-07-29 Thread Philip Schiffer
Unfortunately that didn't help: using RBTools 0.6.2 it still is not 
correctly formatted

Am Montag, 28. Juli 2014 22:29:16 UTC+2 schrieb David Trowbridge:

 I believe that things should be fixed just by upgrading your version of 
 rbtools and swapping out 'post-review' for 'rbt post'.

 -David


 On Mon, Jul 28, 2014 at 1:22 PM, Philip Schiffer philip@sprylab.com 
 javascript: wrote:

 We are all creating our review with this git alias:

 prd = !sh -c 'git fetch origin  git push origin -u $(git name-rev 
 --name-only HEAD)  post-review -d --guess-summary --description=\$(git 
 log origin/develop...HEAD)\ --branch=$(git name-rev --name-only HEAD) 
 --tracking-branch=origin/develop --target-groups=$(git config 
 reviewboard.group) --repository-url=$(git config reviewboard.repository) 
 --server=$(git config reviewboard.url) --open'


 Am Montag, 28. Juli 2014 22:10:30 UTC+2 schrieb David Trowbridge:

 How are you putting the git log into the description? By hand? With the 
 JSON API? Using arguments to post-review?

 -David


 On Mon, Jul 28, 2014 at 1:54 AM, Philip Schiffer philip@sprylab.com
  wrote:

 Okay, can that be fixed? I don't want to change our templates. Or can 
 markdown be disabled?

 Am Freitag, 25. Juli 2014 23:51:20 UTC+2 schrieb David Trowbridge:

 OK, I believe that the problem is the indentation. Markdown treats 
 indented text as a code block, and won't handle any markdown syntax in it.

 -David
  

 On Thu, Jul 24, 2014 at 11:15 PM, Philip Schiffer 
 philip@sprylab.com wrote:

 Sorry for the late answer - I did not get any notification :/



 Am Donnerstag, 17. Juli 2014 22:30:38 UTC+2 schrieb David Trowbridge:

 Can you show what the source markdown looks like? (Click the pencil 
 and then copy/paste/redact)

 -David


 On Thu, Jul 17, 2014 at 2:34 AM, Philip Schiffer 
 philip@sprylab.com wrote:

 Hello everyone,
 I have upgraded our reviewboard installation from 1.7.x to 2.0.3. 
 Unfortunately we have some issues with the formatting of the 
 description 
 field. We are using the post-review tool in our scripts to post our 
 reviews. Inside the description field we put the git commit log 
 entries.
 As you can see in the attachment, there are problems displaying the 
 links.

 I've searched the bug tracker but unfortunately I'm getting http 
 500 errors from google code for this issue: 
 https://code.google.com/p/reviewboard/issues/detail?id=3377
  
 -- 
 Get the Review Board Power Pack at http://www.reviewboard.org/pow
 erpack/
 ---
 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/pow
 erpack/
 ---
 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...@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...@googlegroups.com javascript:.
 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: Formatting errors in description field

2014-07-29 Thread Christian Hammond
Hi Philip,

Unless you specifically post with a flag enabling Markdown, we convert the text 
to valid Markdown. I believe when we do this, we don’t escape sequences of 4 
spaces, which ends up triggering Markdown’s inline mode. So, this is a bug in 
Review Board. We would need to basically recognize 4+ leading spaces and insert 
some backslashes (which is ugly, but necessary for this).

Can you file a new bug for this?

(The HTTP 500 errors on the bug tracker are annoying… We’ve been unable to get 
Google to care about this problem.)

Christian

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

On July 29, 2014 at 3:14:57 AM, Philip Schiffer (philip.schif...@sprylab.com) 
wrote:

Unfortunately that didn't help: using RBTools 0.6.2 it still is not correctly 
formatted

Am Montag, 28. Juli 2014 22:29:16 UTC+2 schrieb David Trowbridge:
I believe that things should be fixed just by upgrading your version of rbtools 
and swapping out 'post-review' for 'rbt post'.

-David


On Mon, Jul 28, 2014 at 1:22 PM, Philip Schiffer philip@sprylab.com wrote:
We are all creating our review with this git alias:

    prd = !sh -c 'git fetch origin  git push origin -u $(git name-rev 
--name-only HEAD)  post-review -d --guess-summary --description=\$(git log 
origin/develop...HEAD)\ --branch=$(git name-rev --name-only HEAD) 
--tracking-branch=origin/develop --target-groups=$(git config 
reviewboard.group) --repository-url=$(git config reviewboard.repository) 
--server=$(git config reviewboard.url) --open'


Am Montag, 28. Juli 2014 22:10:30 UTC+2 schrieb David Trowbridge:
How are you putting the git log into the description? By hand? With the JSON 
API? Using arguments to post-review?

-David


On Mon, Jul 28, 2014 at 1:54 AM, Philip Schiffer philip@sprylab.com wrote:
Okay, can that be fixed? I don't want to change our templates. Or can markdown 
be disabled?

Am Freitag, 25. Juli 2014 23:51:20 UTC+2 schrieb David Trowbridge:
OK, I believe that the problem is the indentation. Markdown treats indented 
text as a code block, and won't handle any markdown syntax in it.

-David


On Thu, Jul 24, 2014 at 11:15 PM, Philip Schiffer philip@sprylab.com 
wrote:
Sorry for the late answer - I did not get any notification :/



Am Donnerstag, 17. Juli 2014 22:30:38 UTC+2 schrieb David Trowbridge:
Can you show what the source markdown looks like? (Click the pencil and then 
copy/paste/redact)

-David


On Thu, Jul 17, 2014 at 2:34 AM, Philip Schiffer philip@sprylab.com wrote:
Hello everyone,
I have upgraded our reviewboard installation from 1.7.x to 2.0.3. Unfortunately 
we have some issues with the formatting of the description field. We are using 
the post-review tool in our scripts to post our reviews. Inside the description 
field we put the git commit log entries.
As you can see in the attachment, there are problems displaying the links.

I've searched the bug tracker but unfortunately I'm getting http 500 errors 
from google code for this issue: 
https://code.google.com/p/reviewboard/issues/detail?id=3377
--
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...@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...@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 

Problem setting up Subversion repo

2014-07-29 Thread Roman Parkhunovsky
Hi, 
I have a problem with setting up SVN as a repository:
A repository was not found at the specified path.

And from httpd logs:
[Tue Jul 29 17:25:32 2014] [error] ERROR:root:SVN: Failed to get repository 
information for https://svn.mycompany.com/svn/project:
 (OPTIONS of 'https://svn.mycompany.com/svn/project': authorization 
failed (https://svn.mycompany.com), 170001)
[Tue Jul 29 18:04:39 2014] [error] ERROR:root:SVN: Failed to get repository 
information for https://svn.mycompany.com/svn: (OPTIONS of 'https://
svn.mycompany.com/svn': 200 OK (https://svn.mycompany.com), 175002)

Information for  project app trunk:
$svn info
Path: .
URL: https://svn.mycompany.com/svn/project/app/trunk
Repository Root: https://svn.mycompany.com/svn/project

I use definitely correct login/password that I put in on Repository 
configuration page. I tried a few ones in ReviewBoard and all of them 
produce the error above albeit using them for svn checkout succeeds. 
I also tried different svn roots like https://svn.mycompany.com, 
https://svn.mycompany.com/svn, https://svn.mycompany.com/svn/myproj/trunk 
but all of them were causing the same error.
Reviewboard 2.0.5, RBtools 0.6.2, subversion 1.6.15 (both client and repo), 
subvertpy-0.9.1-py2.6-linux-x86_64.egg, CentOS 5.10 x64.

Thanks.

-- 
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: Problem setting up Subversion repo

2014-07-29 Thread Christian Hammond
Hi Roman,

What type of authentication does the server expect? Simple username/password, 
or more?

Can you check the log files to see whether PySVN or Subvertpy is being used?

Also, any unusual characters (such as Unicode) in your password?

Christian

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

On July 29, 2014 at 12:10:06 PM, Roman Parkhunovsky (esqrot...@gmail.com) wrote:

Hi,
I have a problem with setting up SVN as a repository:
A repository was not found at the specified path.

And from httpd logs:
[Tue Jul 29 17:25:32 2014] [error] ERROR:root:SVN: Failed to get repository 
information for https://svn.mycompany.com/svn/project:
 (OPTIONS of 'https://svn.mycompany.com/svn/project': authorization
failed (https://svn.mycompany.com), 170001)
[Tue Jul 29 18:04:39 2014] [error] ERROR:root:SVN: Failed to get repository 
information for https://svn.mycompany.com/svn: (OPTIONS of 
'https://svn.mycompany.com/svn': 200 OK (https://svn.mycompany.com), 175002)

Information for  project app trunk:
$svn info
Path: .
URL: https://svn.mycompany.com/svn/project/app/trunk
Repository Root: https://svn.mycompany.com/svn/project

I use definitely correct login/password that I put in on Repository 
configuration page. I tried a few ones in ReviewBoard and all of them produce 
the error above albeit using them for svn checkout succeeds.
I also tried different svn roots like https://svn.mycompany.com, 
https://svn.mycompany.com/svn, https://svn.mycompany.com/svn/myproj/trunk but 
all of them were causing the same error.
Reviewboard 2.0.5, RBtools 0.6.2, subversion 1.6.15 (both client and repo), 
subvertpy-0.9.1-py2.6-linux-x86_64.egg, CentOS 5.10 x64.

Thanks.
--
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.


Re: Formatting errors in description field

2014-07-29 Thread Philip Schiffer
It's not that important. It can stay that way.

Am Dienstag, 29. Juli 2014 22:00:05 UTC+2 schrieb Christian Hammond:

 Hi Philip,

 We can’t, but we can delete the ticket.

 Christian

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

 On July 29, 2014 at 3:29:22 AM, Philip Schiffer (philip@sprylab.com 
 javascript:) wrote:

 I've created it: 
 https://code.google.com/p/reviewboard/issues/detail?id=3503 
 (Can you redact the url? I forgot to do this :/)

 Am Dienstag, 29. Juli 2014 12:21:35 UTC+2 schrieb Christian Hammond: 

  Hi Philip,
  
  Unless you specifically post with a flag enabling Markdown, we convert 
 the text to valid Markdown. I believe when we do this, we don’t escape 
 sequences of 4 spaces, which ends up triggering Markdown’s inline mode. So, 
 this is a bug in Review Board. We would need to basically recognize 4+ 
 leading spaces and insert some backslashes (which is ugly, but necessary 
 for this).
  
  Can you file a new bug for this?
  
  (The HTTP 500 errors on the bug tracker are annoying… We’ve been unable 
 to get Google to care about this problem.)
  
  Christian
  
   -- 
  Christian Hammond - chri...@beanbaginc.com
  Review Board - http://www.reviewboard.org 
 Beanbag, Inc. - http://www.beanbaginc.com
  
 On July 29, 2014 at 3:14:57 AM, Philip Schiffer (philip@sprylab.com) 
 wrote:

  Unfortunately that didn't help: using RBTools 0.6.2 it still is not 
 correctly formatted

 Am Montag, 28. Juli 2014 22:29:16 UTC+2 schrieb David Trowbridge: 

 I believe that things should be fixed just by upgrading your version of 
 rbtools and swapping out 'post-review' for 'rbt post'. 

 -David
  

 On Mon, Jul 28, 2014 at 1:22 PM, Philip Schiffer philip@sprylab.com
  wrote:

 We are all creating our review with this git alias: 

  prd = !sh -c 'git fetch origin  git push origin -u $(git 
 name-rev --name-only HEAD)  post-review -d --guess-summary 
 --description=\$(git log origin/develop...HEAD)\ --branch=$(git name-rev 
 --name-only HEAD) --tracking-branch=origin/develop --target-groups=$(git 
 config reviewboard.group) --repository-url=$(git config 
 reviewboard.repository) --server=$(git config reviewboard.url) --open'


 Am Montag, 28. Juli 2014 22:10:30 UTC+2 schrieb David Trowbridge: 

  How are you putting the git log into the description? By hand? With 
 the JSON API? Using arguments to post-review?

 -David


 On Mon, Jul 28, 2014 at 1:54 AM, Philip Schiffer 
 philip@sprylab.com wrote:

 Okay, can that be fixed? I don't want to change our templates. Or can 
 markdown be disabled?

 Am Freitag, 25. Juli 2014 23:51:20 UTC+2 schrieb David Trowbridge: 

  OK, I believe that the problem is the indentation. Markdown treats 
 indented text as a code block, and won't handle any markdown syntax in 
 it. 

 -David
   

 On Thu, Jul 24, 2014 at 11:15 PM, Philip Schiffer 
 philip@sprylab.com wrote:

 Sorry for the late answer - I did not get any notification :/ 



 Am Donnerstag, 17. Juli 2014 22:30:38 UTC+2 schrieb David 
 Trowbridge: 

  Can you show what the source markdown looks like? (Click the 
 pencil and then copy/paste/redact) 

 -David
  

  On Thu, Jul 17, 2014 at 2:34 AM, Philip Schiffer 
 philip@sprylab.com wrote:

  Hello everyone, 
 I have upgraded our reviewboard installation from 1.7.x to 2.0.3. 
 Unfortunately we have some issues with the formatting of the 
 description 
 field. We are using the post-review tool in our scripts to post our 
 reviews. Inside the description field we put the git commit log 
 entries.
 As you can see in the attachment, there are problems displaying 
 the links.

 I've searched the bug tracker but unfortunately I'm getting http 
 500 errors from google code for this issue: 
 https://code.google.com/p/reviewboard/issues/detail?id=3377
  --
 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...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.
  
  
--
 Get the Review Board Power Pack at 
 

Re: Problem setting up Subversion repo

2014-07-29 Thread Roman Parkhunovsky
Hi, Christian, thanks for a quick reply.
I'm using subvertpy-0.9.1-py2.6-linux-x86_64.egg installed by 
easy_install26 and python2.6.
SVN requires simple username/password, it consists of upper, lower symbols 
and numbers only.

Thanks.

Вівторок, 29 липня 2014 р. 14:42:19 UTC-5 користувач Christian Hammond 
написав:

 Hi Roman,

 What type of authentication does the server expect? Simple 
 username/password, or more?

 Can you check the log files to see whether PySVN or Subvertpy is being 
 used?

 Also, any unusual characters (such as Unicode) in your password?

 Christian

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

 On July 29, 2014 at 12:10:06 PM, Roman Parkhunovsky (esqr...@gmail.com 
 javascript:) wrote:

 Hi,
 I have a problem with setting up SVN as a repository:
  A repository was not found at the specified path.
  
 And from httpd logs:
  [Tue Jul 29 17:25:32 2014] [error] ERROR:root:SVN: Failed to get repository 
 information for https://svn.mycompany.com/svn/project:
  (OPTIONS of 'https://svn.mycompany.com/svn/project': authorization
 failed (https://svn.mycompany.com), 170001)
  [Tue Jul 29 18:04:39 2014] [error] ERROR:root:SVN: Failed to get repository 
 information for https://svn.mycompany.com/svn: (OPTIONS of 'https://
 svn.mycompany.com/svn': 200 OK (https://svn.mycompany.com), 175002)
  
 Information for  project app trunk:
  $svn info
 Path: .
 URL: https://svn.mycompany.com/svn/project/app/trunk
 Repository Root: https://svn.mycompany.com/svn/project
  
 I use definitely correct login/password that I put in on Repository 
 configuration page. I tried a few ones in ReviewBoard and all of them 
 produce the error above albeit using them for svn checkout succeeds.
 I also tried different svn roots like https://svn.mycompany.com, 
 https://svn.mycompany.com/svn, https://svn.mycompany.com/svn/myproj/trunk 
 but all of them were causing the same error.
 Reviewboard 2.0.5, RBtools 0.6.2, subversion 1.6.15 (both client and 
 repo), subvertpy-0.9.1-py2.6-linux-x86_64.egg, CentOS 5.10 x64.

 Thanks.
 --
 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 javascript:.
 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.


Power Pack 1.0.4 is released

2014-07-29 Thread Christian Hammond
Hey everyone,

We just put out a release of Power Pack 1.0.4. Power Pack is our premium add-on 
to Review Board that offers PDF document review, GitHub Enterprise, and more.

The new version of Power Pack makes it easier to install new trial licenses, 
and enhances our support for PDF rendering.

More details are up on the announcement at 
https://www.reviewboard.org/news/2014/07/29/power-pack-1-0-4-released/

For more information on Power Pack, see https://www.reviewboard.org/powerpack/

Christian

-- 
Christian Hammond - christ...@beanbaginc.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/d/optout.


Re: Problem setting up Subversion repo

2014-07-29 Thread Christian Hammond
Can you try uninstalling Subvertpy and installing PySVN? Subvertpy support is 
new, and I want to rule it out as a problem.

Christian

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

On July 29, 2014 at 6:07:57 PM, Roman Parkhunovsky (esqrot...@gmail.com) wrote:

Hi, Christian, thanks for a quick reply.
I'm using subvertpy-0.9.1-py2.6-linux-x86_64.egg installed by easy_install26 
and python2.6.
SVN requires simple username/password, it consists of upper, lower symbols and 
numbers only.

Thanks.

Вівторок, 29 липня 2014 р. 14:42:19 UTC-5 користувач Christian Hammond написав:
Hi Roman,

What type of authentication does the server expect? Simple username/password, 
or more?

Can you check the log files to see whether PySVN or Subvertpy is being used?

Also, any unusual characters (such as Unicode) in your password?

Christian

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

On July 29, 2014 at 12:10:06 PM, Roman Parkhunovsky (esqr...@gmail.com) wrote:

Hi,
I have a problem with setting up SVN as a repository:
A repository was not found at the specified path.

And from httpd logs:
[Tue Jul 29 17:25:32 2014] [error] ERROR:root:SVN: Failed to get repository 
information for https://svn.mycompany.com/svn/project:
 (OPTIONS of 'https://svn.mycompany.com/svn/project': authorization
failed (https://svn.mycompany.com), 170001)
[Tue Jul 29 18:04:39 2014] [error] ERROR:root:SVN: Failed to get repository 
information for https://svn.mycompany.com/svn: (OPTIONS of 
'https://svn.mycompany.com/svn': 200 OK (https://svn.mycompany.com), 175002)

Information for  project app trunk:
$svn info
Path: .
URL: https://svn.mycompany.com/svn/project/app/trunk
Repository Root: https://svn.mycompany.com/svn/project

I use definitely correct login/password that I put in on Repository 
configuration page. I tried a few ones in ReviewBoard and all of them produce 
the error above albeit using them for svn checkout succeeds.
I also tried different svn roots like https://svn.mycompany.com, 
https://svn.mycompany.com/svn, https://svn.mycompany.com/svn/myproj/trunk but 
all of them were causing the same error.
Reviewboard 2.0.5, RBtools 0.6.2, subversion 1.6.15 (both client and repo), 
subvertpy-0.9.1-py2.6-linux-x86_64.egg, CentOS 5.10 x64.

Thanks.
--
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: Problem setting up Subversion repo

2014-07-29 Thread Roman Parkhunovsky
I uninstalled Subvertpy but the package from centos repository was built 
for python2.4 so I had to compile pysvn-1.6.3 from source. (You need to 
install e2fsprogs-devel, neon-devel in case one needs to compile).
Now I can add repositories and I can see latest commits when creating a 
review.
If you need more information I'd be glad to provide it for figuring out 
subvertpy issue.

Thanks.

Вівторок, 29 липня 2014 р. 13:29:21 UTC-5 користувач Roman Parkhunovsky 
написав:

 Hi, 
 I have a problem with setting up SVN as a repository:
 A repository was not found at the specified path.

 And from httpd logs:
 [Tue Jul 29 17:25:32 2014] [error] ERROR:root:SVN: Failed to get 
 repository information for https://svn.mycompany.com/svn/project:
  (OPTIONS of 'https://svn.mycompany.com/svn/project': authorization 
 failed (https://svn.mycompany.com), 170001)
 [Tue Jul 29 18:04:39 2014] [error] ERROR:root:SVN: Failed to get 
 repository information for https://svn.mycompany.com/svn: (OPTIONS of 
 'https://svn.mycompany.com/svn': 200 OK (https://svn.mycompany.com), 
 175002)

 Information for  project app trunk:
 $svn info
 Path: .
 URL: https://svn.mycompany.com/svn/project/app/trunk
 Repository Root: https://svn.mycompany.com/svn/project

 I use definitely correct login/password that I put in on Repository 
 configuration page. I tried a few ones in ReviewBoard and all of them 
 produce the error above albeit using them for svn checkout succeeds. 
 I also tried different svn roots like https://svn.mycompany.com, 
 https://svn.mycompany.com/svn, https://svn.mycompany.com/svn/myproj/trunk 
 but all of them were causing the same error.
 Reviewboard 2.0.5, RBtools 0.6.2, subversion 1.6.15 (both client and 
 repo), subvertpy-0.9.1-py2.6-linux-x86_64.egg, CentOS 5.10 x64.

 Thanks.


-- 
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.


Issue 3503 in reviewboard: Formattings errors in description field

2014-07-29 Thread reviewboard

Status: New
Owner: 
Labels: Type-Defect Priority-Medium

New issue 3503 by philip.s...@sprylab.com: Formattings errors in  
description field

http://code.google.com/p/reviewboard/issues/detail?id=3503

What version are you running?
2.0.5

What's the URL of the page containing the problem?
https://reviews.sprylab.com/r/ID/

What steps will reproduce the problem?
1. create a commit
2. create a review with rbt post and the following command:
rbt post -d --guess-summary --description=\$(git log  
origin/develop...HEAD)\ --branch=$(git name-rev --name-only HEAD)  
--tracking-branch=origin/develop --target-groups=$(git config  
reviewboard.group) --repository-url=$(git config reviewboard.repository)  
--server=$(git config reviewboard.url) --open


What is the expected output? What do you see instead?
There are erros in the formatting of the description field.
This is described in  
https://groups.google.com/forum/#!topic/reviewboard/K0VTVC0mglQ


What operating system are you using? What browser?
Chrome stable / Windows 7, RbTool 0.6.2

Please provide any additional information below.
See thread https://groups.google.com/forum/#!topic/reviewboard/K0VTVC0mglQ

--
You received this message because this project is configured to send all  
issue notifications to this address.

You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups 
reviewboard-issues group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/d/optout.


Issue 3504 in reviewboard: Support mediawiki as a backend for reviewboard

2014-07-29 Thread reviewboard

Status: New
Owner: 
Labels: Type-Enhancement Priority-Medium

New issue 3504 by jmwal...@gmail.com: Support mediawiki as a backend for  
reviewboard

http://code.google.com/p/reviewboard/issues/detail?id=3504

What version are you running?
1.7.25

What's the URL of the page this enhancement relates to, if any?
-none-

Describe the enhancement and the motivation for it.

Our company avidly uses both mediawiki and reviewboard. I'm interested in  
soliciting feedback on some wiki text, and while I think I can rig up a  
hack for a new file, I'm realizing it'd be really nice to actually be  
able to review specific new versions of the file too. I could imagine an

  rbt post --source-url=wiki page url
[or perhaps it needs to be something other than post?] which puts up a  
reviewboard request with the text from that page, and the ability to [out  
of band of the wiki] start comment threads on all the individual lines.


What operating system are you using? What browser?
-various-

Please provide any additional information below.


--
You received this message because this project is configured to send all  
issue notifications to this address.

You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups 
reviewboard-issues group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/d/optout.


Issue 3505 in reviewboard: Empty drafts can be submitted

2014-07-29 Thread reviewboard

Status: New
Owner: 
Labels: Type-Defect Priority-Medium

New issue 3505 by anhi...@cisco.com: Empty drafts can be submitted
http://code.google.com/p/reviewboard/issues/detail?id=3505

*** READ THIS BEFORE POSTING!
***
*** You must complete this form in its entirety, or your bug report will be
*** rejected.
***
*** If you have a security issue to report, please send it confidentially
to
*** secur...@reviewboard.org. Posting security-related issues to this bug
*** tracker causes us to have to do an emergency release.
***
*** For customer support, please post to reviewbo...@googlegroups.com
***
*** If you have a patch, please submit it to
http://reviews.reviewboard.org/
***
*** This bug tracker is public. Please check that any logs or other
information
*** that you include has been stripped of confidential information.


What version are you running?
e625b89

What's the URL of the page containing the problem?
/r/N/ for any review request N with an unpublished draft

What steps will reproduce the problem?
1. Create a new review request and don't fill out any fields
2. Choose Close-Submitted from the menu on the top right

What is the expected output? What do you see instead?
When attempting to publish a draft with missing fields, error dialogs  
prevent it. However, this can be circumvented by submitting the review  
request (and reopening it, if desired).


What operating system are you using? What browser?
N/A

Please provide any additional information below.
I came across this while trying to figure out how to validate extra fields  
for an extension, but I can't see how any fields are validated aside from a  
few JavaScript barriers.


--
You received this message because this project is configured to send all  
issue notifications to this address.

You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups 
reviewboard-issues group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/d/optout.


Issue 3506 in reviewboard: Extension review request fields

2014-07-29 Thread reviewboard

Status: New
Owner: 
Labels: Type-Defect Priority-Medium

New issue 3506 by anhi...@cisco.com: Extension review request fields
http://code.google.com/p/reviewboard/issues/detail?id=3506

*** READ THIS BEFORE POSTING!
***
*** You must complete this form in its entirety, or your bug report will be
*** rejected.
***
*** If you have a security issue to report, please send it confidentially
to
*** secur...@reviewboard.org. Posting security-related issues to this bug
*** tracker causes us to have to do an emergency release.
***
*** For customer support, please post to reviewbo...@googlegroups.com
***
*** If you have a patch, please submit it to
http://reviews.reviewboard.org/
***
*** This bug tracker is public. Please check that any logs or other
information
*** that you include has been stripped of confidential information.


What version are you running?
e625b89

What's the URL of the page containing the problem?
/r/N/ for any review request N

What steps will reproduce the problem?
1. Create and enable an extension with extra fields extending  
BaseEditableField and/or BaseTextAreaField with is_required = True
2. Create a new review request and observe the fields displayed correctly  
(with a * indicating that the field is required)
3. Publish the draft with empty required fields, and submit the review  
request with fields still empty


What is the expected output? What do you see instead?
Something somewhere should prevent either draft publication or review  
request submission when required fields are empty. However, currently the  
draft publication and review request submission complete successfully with  
empty required fields.


What operating system are you using? What browser?
N/A

Please provide any additional information below.
Since the ReviewRequestApprovalHook only applies to API checks, and doesn't  
give any means to prevent submission on missing fields, some sort of  
validation process should be baked into the custom fields.


--
You received this message because this project is configured to send all  
issue notifications to this address.

You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups 
reviewboard-issues group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/d/optout.


Re: Issue 3506 in reviewboard: Extension review request fields

2014-07-29 Thread reviewboard


Comment #1 on issue 3506 by anhi...@cisco.com: Extension review request  
fields

http://code.google.com/p/reviewboard/issues/detail?id=3506

Sorry, the title is not descriptive because I forgot to finish typing it.  
It should read, Extension review request fields are never validated.


--
You received this message because this project is configured to send all  
issue notifications to this address.

You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups 
reviewboard-issues group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/d/optout.


Re: Issue 3505 in reviewboard: Empty drafts can be submitted

2014-07-29 Thread reviewboard

Updates:
Status: Confirmed
Labels: -Priority-Medium Priority-Low Component-Reviews

Comment #1 on issue 3505 by chip...@gmail.com: Empty drafts can be submitted
http://code.google.com/p/reviewboard/issues/detail?id=3505

This happens because the submitted state is just a flag, and doesn't deal  
with drafts (and therefore field validation). We don't require anything for  
a submitted review request.


That doesn't mean it's ideal, but fortunately, it's not a regression, from  
what I can tell.


--
You received this message because this project is configured to send all  
issue notifications to this address.

You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups 
reviewboard-issues group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/d/optout.


Re: Issue 3504 in reviewboard: Support mediawiki as a backend for reviewboard

2014-07-29 Thread reviewboard

Updates:
Status: Confirmed

Comment #1 on issue 3504 by chip...@gmail.com: Support mediawiki as  
a backend for reviewboard

http://code.google.com/p/reviewboard/issues/detail?id=3504

We were considering this functionality for Power Pack. It would require  
some design changes for both RBTools and Review Board that would have to go  
into a future release.


--
You received this message because this project is configured to send all  
issue notifications to this address.

You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups 
reviewboard-issues group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/d/optout.