Re: Manual server updates required after months of running fine?

2011-06-17 Thread Bill Fenner
Hi Christian,

Thanks for the reply.  Obviously, you're right, I looked at the
database dump that I did before the rb-site upgrade and it did say
1.5.3, so I was not as careful as I thought I was when doing the
migration months ago.  Mea culpa.

I finally twigged on the wording of the yellow box: ...and then
restart your web server.  Whatever was happening seemed to be cached
state in certain httpd processes (thus the intermittent nature, it
depended on what process served what request).  I restarted Apache and
all was well.

Thanks for all your hard work on reviewboard.  I installed it on a
whim years ago and we have gradually built our whole workflow around
it.

  Bill

On Thu, Jun 16, 2011 at 2:22 PM, Christian Hammond chip...@chipx86.com wrote:
 Hi Bill,

 That message should never really be seen outside of developer installs, but
 it does happen on occasion if something got messed up.

 The first thing to check is actually your database. Make sure it didn't
 crash at some point and have locked tables that need to be cleaned up. You
 should otherwise never see this page about the database schema.

 Now, at some point, you did have an install of 1.5.3 at least attempted.
 That number came directly from the database, put there after an rb-site
 upgrade when using 1.5.3. It's probably not related, but just something to
 point out.

 But yeah, check the database. I suspect that's where the problem is.

 Christian

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


 On Thu, Jun 16, 2011 at 6:55 AM, Bill Fenner fen...@gmail.com wrote:

 Hi,

 We've got a reviewboard installation, which we upgraded to 1.5.5
 several months ago.  That went swimmingly, and it's been working for
 months.

 Nothing has changed on the server, but now it is intermittently
 reporting Manual server updates required -- The Review Board
 database schema has changed since your last upgrade.  Oddly, the
 Manual server updates required box suggests running ./manage.py
 syncdb, when I know that the upgrade command is actually rb-site
 upgrade.

 I ran rb-site upgrade, and got:


 Rebuilding directory structure
 Upgrading from version 1.5.3
 Updating database. This may take a while.
 Upgrading Review Board from 1.5.3 to 1.5.5
 No fixtures found.
 No evolution required.
 Upgrade complete.


 We never had 1.5.3 installed, we went from pre-1.0 svn snapshot
 straight to 1.5.5.

 After the rb-site upgrade, things went fine for a little while, and
 then I started getting the intermittent message.

 By intermittent, I mean that sometimes it appears as the only content
 on the page, and sometimes it appears between diff chunks, and
 sometimes it doesn't appear at all and reviewboard behaves as normal.

 I've looked in the Apache error_log, and all I see are the reviewboard
 debugging messages about diff generation.  The log directory in my
 rb-site root is empty.

 Anyone have an idea of what else to try?

 Thanks,
  Bill

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

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

-- 
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: post-reviews: The requested URL could not be retrieved

2011-06-17 Thread ptrchen
Hi Christian,

I think this page suggestions that should address my issues, correct?
http://groups.google.com/group/reviewboard/browse_thread/thread/69e334db357f183e/955e8ebd634d0a94?lnk=gstq=proxy+post-review#955e8ebd634d0a94



On Jun 10, 4:54 pm, ptrchen ptrc...@gmail.com wrote:
 Sorry Chrisitan, never mind, I misread your post. I'll do some more
 digging for overriding the proxy configuration

 On Jun 10, 4:51 pm,ptrchenptrc...@gmail.com wrote:

  Ah, so would setting the environment variable in the command prompt
  window do the trick?

  On Jun 10, 4:32 pm, Christian Hammond chip...@chipx86.com wrote:

   We've seen people run into this sort of error with proxy servers. 
   Regardless
   of your client-side proxy server configuration (say, in your Internet
   settings, on Windows), it may still use the proxy server on post-review.

   The error output looks very much like it came from a proxy server, meaning
   that the request is going out to the proxy, and the proxy can't find the
   domain. You'll need to blacklist it. I don't recall if it will at all
   respect this black list with Python running on Windows. If it's Linux, 
   then
   you want to be sure your http_proxy environment variable isn't set.

   This has come up a couple of times, and it's clear we need a setting in
   post-review itself to just override the proxy configuration.

   If you search on this mailing list, you'll probably find a couple other
   solutions.

   Christian

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

   On Fri, Jun 10, 2011 at 3:55 PM,ptrchenptrc...@gmail.com wrote:
Sorry for not listing all the output, but company policy prohibits me
from doing that.

Yes, the error lists the hostname and FQDN

Also, we do give it the FQDN following the --server option

On Jun 10, 2:56 pm, Tucker j...@gmail.com wrote:
 Does the error actually only list the hostname and not the fully
 qualified name?  If so, that may be part of your problem (throwing out
 guesses).  Have you tried using the fully qualified name?

 On Fri, Jun 10, 2011 at 11:22 AM,ptrchenptrc...@gmail.com wrote:
  Hi Tucker,

  Thanks for the reply.

  I ran nslookup server_name from both server_name (XP server) 
  and
  from a sparc-solaris2.10 machine.

  Both return

  Name:   server_name.domain
  Address: ip_address

  On Jun 10, 11:15 am, Tucker j...@gmail.com wrote:
  You appear to have a DNS problem:

  Unable to determine IP address from host name for server_name.

  What does nslookup server_name say?

  On Thu, Jun 9, 2011 at 7:12 PM,ptrchenptrc...@gmail.com wrote:
   Hi,

   We've been trying to run post-review but have been running into a
   requested URL could not be retrieved error

   We're running:

   ReviewBoard 1.5.5 on Windows XP
   Python 2.5.x
   Apache 2.2.x

   Subversion 1.6.16, running on a sparc-solaris2.10

   Here is the output after adding the --debug option:

--
   post-review --server=server_name/rb_site --username= --
   password= --revision-range=8325 --debug
   RBTools 0.3.2
   Home = C:\Documents and Settings\\Application Data
   svn info
   diff --version
   repository info: Path: svn-server/ParentPath/RepoName, 
   Base
pa
   th: /trunk, Supports changesets: False
   HTTP GETting api/
   Got HTTP error: 503: !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 
   4.01
Transition
   al//EN http://www.w3.org/TR/html4/loose.dtd;
   HTMLHEADMETA HTTP-EQUIV=Content-Type CONTENT=text/html;
   charset=iso-8859
   -1
   TITLEERROR: The requested URL could not be retrieved/TITLE
   STYLE type=text/css!--BODY{background-color:#ff;font-
   family:verdana,san
   s-serif}PRE{font-family:sans-serif}--/STYLE
   /HEADBODY
   H2The requested URL could not be retrieved/H2
   HR noshade size=1px
   P
   While trying to retrieve the URL:
   A
HREF=server_name/rb_site/api/server_name/rb_site/api//
   A
   P
   The following error was encountered:
   BLOCKQUOTE
   Unable to determine IP address from host name for
   Iserver_name/I
   /BLOCKQUOTE

   P
   The dnsserver returned:
   BLOCKQUOTE
   Name Error: The domain name does not exist.
   /BLOCKQUOTE

   P
   This means that:
   PRE
   The cache was not able to resolve the hostname presented in the 
   URL.
   Check if the address is correct.

--

   Thanks!

   --
   Want to help the Review Board project? Donate 

Re: post-reviews: The requested URL could not be retrieved

2011-06-17 Thread Christian Hammond
It should, yes.

I think after some restructuring work is finished in post-review, we'll go
about making this a bit easier to deal with.

Christian

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


On Fri, Jun 17, 2011 at 3:48 PM, ptrchen ptrc...@gmail.com wrote:

 Hi Christian,

 I think this page suggestions that should address my issues, correct?

 http://groups.google.com/group/reviewboard/browse_thread/thread/69e334db357f183e/955e8ebd634d0a94?lnk=gstq=proxy+post-review#955e8ebd634d0a94



 On Jun 10, 4:54 pm, ptrchen ptrc...@gmail.com wrote:
  Sorry Chrisitan, never mind, I misread your post. I'll do some more
  digging for overriding the proxy configuration
 
  On Jun 10, 4:51 pm,ptrchenptrc...@gmail.com wrote:
 
   Ah, so would setting the environment variable in the command prompt
   window do the trick?
 
   On Jun 10, 4:32 pm, Christian Hammond chip...@chipx86.com wrote:
 
We've seen people run into this sort of error with proxy servers.
 Regardless
of your client-side proxy server configuration (say, in your Internet
settings, on Windows), it may still use the proxy server on
 post-review.
 
The error output looks very much like it came from a proxy server,
 meaning
that the request is going out to the proxy, and the proxy can't find
 the
domain. You'll need to blacklist it. I don't recall if it will at all
respect this black list with Python running on Windows. If it's
 Linux, then
you want to be sure your http_proxy environment variable isn't set.
 
This has come up a couple of times, and it's clear we need a setting
 in
post-review itself to just override the proxy configuration.
 
If you search on this mailing list, you'll probably find a couple
 other
solutions.
 
Christian
 
--
Christian Hammond - chip...@chipx86.com
Review Board -http://www.reviewboard.org
VMware, Inc. -http://www.vmware.com
 
On Fri, Jun 10, 2011 at 3:55 PM,ptrchenptrc...@gmail.com wrote:
 Sorry for not listing all the output, but company policy prohibits
 me
 from doing that.
 
 Yes, the error lists the hostname and FQDN
 
 Also, we do give it the FQDN following the --server option
 
 On Jun 10, 2:56 pm, Tucker j...@gmail.com wrote:
  Does the error actually only list the hostname and not the fully
  qualified name?  If so, that may be part of your problem
 (throwing out
  guesses).  Have you tried using the fully qualified name?
 
  On Fri, Jun 10, 2011 at 11:22 AM,ptrchenptrc...@gmail.com
 wrote:
   Hi Tucker,
 
   Thanks for the reply.
 
   I ran nslookup server_name from both server_name (XP
 server) and
   from a sparc-solaris2.10 machine.
 
   Both return
 
   Name:   server_name.domain
   Address: ip_address
 
   On Jun 10, 11:15 am, Tucker j...@gmail.com wrote:
   You appear to have a DNS problem:
 
   Unable to determine IP address from host name for
 server_name.
 
   What does nslookup server_name say?
 
   On Thu, Jun 9, 2011 at 7:12 PM,ptrchenptrc...@gmail.com
 wrote:
Hi,
 
We've been trying to run post-review but have been running
 into a
requested URL could not be retrieved error
 
We're running:
 
ReviewBoard 1.5.5 on Windows XP
Python 2.5.x
Apache 2.2.x
 
Subversion 1.6.16, running on a sparc-solaris2.10
 
Here is the output after adding the --debug option:
 

 --
post-review --server=server_name/rb_site --username=
 --
password= --revision-range=8325 --debug
RBTools 0.3.2
Home = C:\Documents and Settings\\Application Data
svn info
diff --version
repository info: Path:
 svn-server/ParentPath/RepoName, Base
 pa
th: /trunk, Supports changesets: False
HTTP GETting api/
Got HTTP error: 503: !DOCTYPE HTML PUBLIC -//W3C//DTD
 HTML 4.01
 Transition
al//EN http://www.w3.org/TR/html4/loose.dtd;
HTMLHEADMETA HTTP-EQUIV=Content-Type
 CONTENT=text/html;
charset=iso-8859
-1
TITLEERROR: The requested URL could not be
 retrieved/TITLE
STYLE
 type=text/css!--BODY{background-color:#ff;font-
family:verdana,san
s-serif}PRE{font-family:sans-serif}--/STYLE
/HEADBODY
H2The requested URL could not be retrieved/H2
HR noshade size=1px
P
While trying to retrieve the URL:
A
 HREF=server_name/rb_site/api/server_name/rb_site/api//
A
P
The following error was encountered:
BLOCKQUOTE
Unable to determine IP address from host name for
Iserver_name/I
/BLOCKQUOTE
 
P
The dnsserver returned:
BLOCKQUOTE
  

Re: Issue 2113 in reviewboard: Installer contradicts itself and recommends an unsupported configuration

2011-06-17 Thread reviewboard

Updates:
Status: Fixed
Owner: chip...@gmail.com

Comment #2 on issue 2113 by chip...@gmail.com: Installer contradicts itself  
and recommends an unsupported configuration

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

Fixed on master (36ad689)

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



Re: Issue 1847 in reviewboard: The diff-comments resource is unaccessible in REST API 2.0

2011-06-17 Thread reviewboard

Updates:
Status: Fixed

Comment #2 on issue 1847 by chip...@gmail.com: The diff-comments resource  
is unaccessible in REST API 2.0

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

Not sure where the original bug is, but this has since been fixed.

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



Re: Issue 2005 in reviewboard: IE support broken in 1.6beta1

2011-06-17 Thread reviewboard

Updates:
Status: Fixed
Owner: chip...@gmail.com
Labels: -Priority-Medium Priority-Critical Milestone-Release1.6 Browser

Comment #8 on issue 2005 by chip...@gmail.com: IE support broken in 1.6beta1
http://code.google.com/p/reviewboard/issues/detail?id=2005

Fixed on master (35b3bf2). Thanks!

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



Re: Issue 1611 in reviewboard: Unable to log in after visit and save admin/db/siteconfig/siteconfiguration/*/

2011-06-17 Thread reviewboard

Updates:
Status: Fixed
Owner: chip...@gmail.com

Comment #2 on issue 1611 by chip...@gmail.com: Unable to log in after visit  
and save admin/db/siteconfig/siteconfiguration/*/

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

Assuming this has since been dealt with. In 1.6, you can't edit the text on  
this page.


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



Re: Issue 2135 in reviewboard: clearcase.py failing on CentOS 5 (Python 2.4)

2011-06-17 Thread reviewboard

Updates:
Status: Fixed
Owner: chip...@gmail.com
Labels: Component-SCMTools

Comment #1 on issue 2135 by chip...@gmail.com: clearcase.py failing on  
CentOS 5 (Python 2.4)

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

Fixed on master (r6eb15d0).

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



Re: Issue 2105 in reviewboard: Publishing comments ignores edits when unpublished edits exist

2011-06-17 Thread reviewboard

Updates:
Status: Confirmed
Labels: Milestone-Release1.6.x Component-Reviews

Comment #1 on issue 2105 by chip...@gmail.com: Publishing comments ignores  
edits when unpublished edits exist

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

(No comment was entered for this change.)

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



Re: Issue 2002 in reviewboard: linkified URL has succeeding parenthesis included in link's target URL

2011-06-17 Thread reviewboard

Updates:
Status: Confirmed
	Labels: -Priority-Medium Priority-Low Milestone-Release1.6  
Component-Reviews


Comment #2 on issue 2002 by chip...@gmail.com: linkified URL has succeeding  
parenthesis included in link's target URL

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

(No comment was entered for this change.)

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



Re: Issue 2002 in reviewboard: linkified URL has succeeding parenthesis included in link's target URL

2011-06-17 Thread reviewboard

Updates:
Labels: EasyFix

Comment #3 on issue 2002 by chip...@gmail.com: linkified URL has succeeding  
parenthesis included in link's target URL

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

(No comment was entered for this change.)

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



Issue 2140 in reviewboard: unable to install RBTools

2011-06-17 Thread reviewboard

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

New issue 2140 by tarun.te...@gmail.com: unable to install RBTools
http://code.google.com/p/reviewboard/issues/detail?id=2140

I extracted RBTools-0.3.2.tar.gz in C:\RBTools-0.3.2\ in Windows 7  
Enterprise edition PC with Python 3.2.


while running the command below:
python setup.py

I am getting the following error :

Traceback (most recent call last):
  File setup.py, line 22, in module
from ez_setup import use_setuptools
  File C:\RBTools-0.3.2\ez_setup.py, line 106
except pkg_resources.VersionConflict, e:
^
SyntaxError: invalid syntax

Please resolve the issue.

Regards,
Tarun
2.
3.

$ python setup.py

What is the expected output? What do you see instead?


What operating system are you using? What browser?


Please provide any additional information below.


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



Re: Issue 2001 in reviewboard: wrong method name displayed in condensed diff view

2011-06-17 Thread reviewboard

Updates:
Status: Confirmed
Labels: Component-DiffViewer Milestone-Release1.6.x

Comment #2 on issue 2001 by chip...@gmail.com: wrong method name displayed  
in condensed diff view

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

Strange. I can't figure out why it would have done that. Think we'd need a  
public repro case here.


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



Re: Issue 1637 in reviewboard: Review Board + perforce can not upload diff

2011-06-17 Thread reviewboard


Comment #10 on issue 1637 by vpeng...@gmail.com: Review Board + perforce  
can not upload diff

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

Comment 7 gives the right clue.

Suggest improving the error output messages.  Ask users to check the p4  
path for the Python scripts!



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



Re: Issue 2039 in reviewboard: My Dashboard datagrid table is not properly aligned in Chrome browser (dev channel)

2011-06-17 Thread reviewboard


Comment #2 on issue 2039 by chu.e...@gmail.com: My Dashboard datagrid  
table is not properly aligned in Chrome browser (dev channel)

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

When you say newer builds I'm not sure if you're referring to Chrome  
builds or RB builds.  The issue was reported against Chrome 11.0.696.14,  
and as of today (Chrome 14.0.794.0) it is still happening.



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



Issue 2141 in reviewboard: Cannot generate docs from tarball release

2011-06-17 Thread reviewboard

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

New issue 2141 by karrde...@gmail.com: Cannot generate docs from tarball  
release

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


What version are you running?
ReviewBoard 1.5.5 and 1.6beta2.1

What's the URL of the page containing the problem?
N/A

What steps will reproduce the problem?
1. tar zvfz ReviewBoard-1.5.5.tar.gz
2. cd ReviewBoard-1.5.5.tar.gz
3. make -C docs/manual SPHINXOPTS=-N

What is the expected output? What do you see instead?
I would expect that it would generate the HTML documentation. Instead, I  
get an error message (see attached log)


What operating system are you using? What browser?
Fedora Linux 15

Please provide any additional information below.
I am building this from source to include in the RPM in Fedora.

Attachments:
makedocs.log  10.9 KB

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



Re: Issue 2141 in reviewboard: Cannot generate docs from tarball release

2011-06-17 Thread reviewboard


Comment #1 on issue 2141 by karrde...@gmail.com: Cannot generate docs from  
tarball release

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

For the record, I can generate the docs from a git checkout, so I suspect  
the issue occurs during the release process.


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