Hi Christian,
Could it be implemented as extension or not?
Thank you,
Michael Zhilin
On Dec 26, 2012, at 23:57, Christian Hammond chip...@chipx86.com wrote:
Hi Peer,
We don't e-mail when closing review requests. We only e-mail for new updates
and reviews/replies.
I'd be happy to take
Hi,
I'm trying to upgrade RB to the last version:
rd1:~/ReviewBoard-1.7.1# rb-site upgrade /srv/reviewboard
Rebuilding directory structure
Updating database. This may take a while.
The log output below, including warnings and errors,
can be ignored unless upgrade fails.
-- begin
All,
I have attempted an upgrade to 1.7.1, however the site-install is failing
due to unapplied evolutions:
Looking through the other threads I was unable to find a solution for my
issue. Right now I am not able to get access to the UI to try the proposed
workaround mentioned in
Hi Sebastien,
Was there ever a previous upgrade attempt to any other version, followed by
reverting back? Or any custom database modifications? We tend to find this type
of problem with one of the above.
Can you provide an SQL dump of the django_evolution and django_project_version
tables?
Sounds like a similar problem to what Sebastien had, which may be caused.
Reading through that thread reminded me of what we found to be a root
cause, which should be fixed in newer versions of Django Evolution, but you
wouldn't have that with an older version of Review Board.
Can you provide an
In theory, it could, but it would probably need a little bit of new code to
provide a signal we can emit on close/reopen.
I wouldn't be opposed to having this feature as part of Review Board, so
long as it's optional. It's pretty minimal.
Christian
--
Christian Hammond - chip...@chipx86.com
I can't really give you advice here, because any customizations you make
today are going to make it harder to debug problems you'll inevitably hit
with the database schema down the road.
I'll make it a priority to get proper extension support for customizable
fields in for 1.7.2 (or whatever the
Thanks.
Can you also try to reach your admin page - database - Django_Evolution
- Versions, and see if anything says Hinted Version? If so, screenshot
the page?
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
It looks like due to the failed upgrade I am unable to access any pages
outside the login page
2012-12-27 13:48:48,658 - ERROR - Internal Server Error: /dashboard/
Traceback (most recent call last):
File
The dashboard is inaccessible, but I'd expect you could reach /admin/ directly.
Christian
On Dec 27, 2012, at 13:59, jacob.j.rosales jacob.j.rosa...@gmail.com wrote:
It looks like due to the failed upgrade I am unable to access any pages
outside the login page
2012-12-27 13:48:48,658 -
Same issue when accessing url/admin/
2012-12-27 14:18:54,190 - ERROR - Internal Server Error: /admin/
Traceback (most recent call last):
File
/usr/local/lib/python2.7/dist-packages/Django-1.4.3-py2.7.egg/django/core/handlers/base.py,
line 89, in get_response
response =
Did you ever attempt an upgrade before and then downgrade?
I'm noticing two things in your dump:
1) Some of these things it's complaining about are already applied
evolutions, so you shouldn't see it again.
2) Some of them are things that existed in 1.6.13 (the repository fields in
particular
Can you also let me know if you've upgraded Python on this machine for 1.7,
or if you're still using the same version you were using with Review Board
1.6.13.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On
On Thu, Dec 27, 2012 at 10:08 PM, Christian Hammond chip...@gmail.com wrote:
Hi Sebastien,
Hi Christian
Was there ever a previous upgrade attempt to any other version, followed by
reverting back?
I don't think so. No upgrade since a long long time.
Or any custom database modifications?
If you have both before and after, that would certainly help a lot :)
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Thu, Dec 27, 2012 at 5:25 PM, Sebastien Douche sdou...@gmail.com wrote:
On Thu, Dec
hello Christian, thank you for your support, we have resolved the issue
with compilation(easy_install.txt) with upgrading from ubuntu 10.10 to
11.04. However now i see the same issue 'extra_data' problem that sebastian
saw(rb-site.txt). i have included the django tables that you requested in
--
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
--
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
Hello Christian, in order to get rid of error, i deleted the mysql database
and created another one with the same name. After that i saw rb-site
upgrade var/www/reviewboard was successful. I restarted the apache, and
memcahed however i still see reviewboard is taking a nap. I turned the
debug
Hi,
Thanks, these are all good data points.
I just want to make sure I'm understanding one part thoroughly. When you were
upgrading to 1.7.1, you were upgrading from a database and site using 1.5.1,
not 1.6.4? I believe this is the case, but just want confirmation.
I'm certainly not aware of
Hi,
The error log doesn't show it, but this is 1.7.1?
We need to trace the source of the import. Can you run:
$ rb-site manage /path/to/site shell
import reviewboard.admin.middleware
Hopefully that will show the same error, but with more information you can
paste.
Also, can you make sure
Would you mind also providing a full schema (not data) dump?
Christian
On Dec 27, 2012, at 22:58, Christian Hammond chip...@gmail.com wrote:
Hi,
The error log doesn't show it, but this is 1.7.1?
We need to trace the source of the import. Can you run:
$ rb-site manage /path/to/site
Comment #22 on issue 2445 by rapid7...@gmail.com: Unable to 'View Diff'
when using with RhodeCode for mercurial repositories
http://code.google.com/p/reviewboard/issues/detail?id=2445
Not sure if it's in rhodecode upstream, but a good point. I'll check,
though Marcin Kuzminski may have
23 matches
Mail list logo