Re: There are only two Authentication method available.
Awesome, that was a huge help!
So the first time I ran the snippit below it gave me this:
import pkg_resources
list(pkg_resources.iter_entry_points('reviewboard.auth_backends'))
[]
To cut a long story short, we custom build packages for a lot of things and
unpack them to /path/to/packages/package_name/, then symlink to a common
location which makes dealing with PATH's very easy. So for example
/path/to/packages/reviewboard/site-packages/reviewboard-1.6.15.egg-info/
links to /path/to/common/site-packages/reviewboard-1.6.15.egg-info.
When we upgraded from 1.6.5 to 1.6.15 the process should have tidied up the
old version from /path/to/common/site-packages, but didn't do its job
properly. It cleared the contents of the old directory, but left the
directory itself behind. I straced the Python shell which showed me it was
looking for entry_points.txt under /path/to/common/site-packages, fine. It
then came across the old (empty) directory for reviewboard-1.6.5.egg-info,
saw it was empty and moved on, it didn't bother to check the new
reviewboard-1.6.15.egg-info directory that had a valid entry_points.txt
file inside. So I just removed all the old egg-info directories,
re-imported the database, ran rb-site upgrade and boom the drop-down
miraculously appeared.
I really appreciate you taking the time to help me, I've learned a bit more
about Python and can happily crack on with my testing now.
Cheers Christian!
On 16 January 2013 16:30, Christian Hammond chip...@chipx86.com wrote:
Hi Gavin,
Thanks for the detailed info.
The fact that the LDAP setup isn't working shouldn't prevent Review Board
from showing you the option in the list, so that's unlikely to be it.
Try this on the server and see what happens:
$ python
import pkg_resources
list(pkg_resources.iter_entry_points('reviewboard.auth_backends'))
If that shows an empty list, then the installed packages are failing to
bundle the provided entry points correctly, which is how we scan for known
auth backends. (You can see the file in the
ReviewBoard-*/EGG-INFO/entrypoints.txt file). I don't know off-hand what
the problem would be, but hopefully that'll give you a start in diagnosing
it.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Jan 15, 2013, at 11:53 PM, Gav Main gavm...@gmail.com wrote:
Hi Christian,
I appreciate you replying so quickly. We have the RH supplied version
installed (python-ldap-2.3.10-1.el6.x86_64).
To give you a bit more information. We are looking to move from
ReviewBoard 1.6.5 - 1.6.15. I have setup a lab instance of ReviewBoard
1.6.5 running on RHEL 6.3, which points to a clone of the production MySQL
database, which I created with mysqldump . I am deploying all ReviewBoard
dependencies as custom built RPM's via Puppet. 'rb-site upgrade' complained
that some of the dependencies were out of date, so I've repackaged those
(they are starred).
python-dateutil-1.5
python-django-1.3.4*
python-django-evolution-0.6.7
python-djblets-0.6.27*
python-flup-1.0.3.dev-20110405
python-feedparser-5.1.2*
python-memcached-1.48
python-paramiko-1.7.7.1
python-pil-1.1.7
python-pycrypto-2.5
python-pygments-1.5
python-pysvn-1.7.6
python-pytz-2012c
python-recaptcha-client-1.0.6
python-reviewboard-1.6.15*
python-setuptools-0.6c11
I've typically been building the RPMS with:
%build
CFLAGS=$RPM_OPT_FLAGS %{__python} -c 'import setuptools;
execfile(setup.py)' build
...
%{__python} -c 'import setuptools; execfile(setup.py)' install
--skip-build --root $RPM_BUILD_ROOT --install-lib
%{_basedir}/%{sw_name}-%{sw_version}/site-packages --install-data
%{_basedir}/%{sw_name}-%{sw_version}/site-packages
When I run rb-site upgrade I get this:
# rb-site -d upgrade /local/apache
Rebuilding directory structure
Updating database. This may take a while.
/opt/local/site-packages/djblets/gravatars/__init__.py:26:
DeprecationWarning: the md5 module is deprecated; use hashlib instead
from md5 import md5
Creating tables ...
Creating table hostingsvcs_hostingserviceaccount
Upgrading Review Board from 1.6.5 to 1.6.15
There are unapplied evolutions for reviews.
There are unapplied evolutions for scmtools.
Adding baseline version for new models
Project signature has changed - an evolution is required
Installing custom SQL ...
Installing indexes ...
No fixtures found.
Evolution successful.
Resetting in-database caches.
Upgrade complete.
After writing all this, I have just realised that I have LDAP connection
problems on my lab server, which is a bit of a fail on my part. Would that
be enough for ReviewBoard to not populate the authentication drop-down list?
Cheers,
Gavin
On 16 January 2013 14:30, Christian Hammond chip...@chipx86.com wrote:
Hi Gavin,
You'll need the Python ldap module, if you don't have it already.
Even though you're not using easy_install remotely, are you
Re: There are only two Authentication method available.
Cheers for the pointer Stephen, I'll check it out. I welcome any solution that makes life easier. On 16 January 2013 20:30, Stephen Gallagher step...@gallagherhome.comwrote: On 01/16/2013 02:53 AM, Gav Main wrote: Hi Christian, I appreciate you replying so quickly. We have the RH supplied version installed (python-ldap-2.3.10-1.el6.x86_64). To give you a bit more information. We are looking to move from ReviewBoard 1.6.5 - 1.6.15. I have setup a lab instance of ReviewBoard 1.6.5 running on RHEL 6.3, which points to a clone of the production MySQL database, which I created with mysqldump . I am deploying all ReviewBoard dependencies as custom built RPM's via Puppet. 'rb-site upgrade' complained that some of the dependencies were out of date, so I've repackaged those (they are starred). If you are installing on RHEL 6, I *strongly* recommend that you use the ReviewBoard 1.6.15 RPMs I maintain in EPEL (http://fedoraproject.org/wiki/EPEL). They contain all of the appropriate dependencies and can be installed from a yum repository (either directly from EPEL on the internet or using a local repository inside your intranet). I think this will significantly simplify your configuration. -- 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: There are only two Authentication method available.
Hi Christian,
I appreciate you replying so quickly. We have the RH supplied version
installed (python-ldap-2.3.10-1.el6.x86_64).
To give you a bit more information. We are looking to move from ReviewBoard
1.6.5 - 1.6.15. I have setup a lab instance of ReviewBoard 1.6.5 running
on RHEL 6.3, which points to a clone of the production MySQL database,
which I created with mysqldump . I am deploying all ReviewBoard
dependencies as custom built RPM's via Puppet. 'rb-site upgrade' complained
that some of the dependencies were out of date, so I've repackaged those
(they are starred).
python-dateutil-1.5
python-django-1.3.4*
python-django-evolution-0.6.7
python-djblets-0.6.27*
python-flup-1.0.3.dev-20110405
python-feedparser-5.1.2*
python-memcached-1.48
python-paramiko-1.7.7.1
python-pil-1.1.7
python-pycrypto-2.5
python-pygments-1.5
python-pysvn-1.7.6
python-pytz-2012c
python-recaptcha-client-1.0.6
python-reviewboard-1.6.15*
python-setuptools-0.6c11
I've typically been building the RPMS with:
%build
CFLAGS=$RPM_OPT_FLAGS %{__python} -c 'import setuptools;
execfile(setup.py)' build
...
%{__python} -c 'import setuptools; execfile(setup.py)' install
--skip-build --root $RPM_BUILD_ROOT --install-lib
%{_basedir}/%{sw_name}-%{sw_version}/site-packages --install-data
%{_basedir}/%{sw_name}-%{sw_version}/site-packages
When I run rb-site upgrade I get this:
# rb-site -d upgrade /local/apache
Rebuilding directory structure
Updating database. This may take a while.
/opt/local/site-packages/djblets/gravatars/__init__.py:26:
DeprecationWarning: the md5 module is deprecated; use hashlib instead
from md5 import md5
Creating tables ...
Creating table hostingsvcs_hostingserviceaccount
Upgrading Review Board from 1.6.5 to 1.6.15
There are unapplied evolutions for reviews.
There are unapplied evolutions for scmtools.
Adding baseline version for new models
Project signature has changed - an evolution is required
Installing custom SQL ...
Installing indexes ...
No fixtures found.
Evolution successful.
Resetting in-database caches.
Upgrade complete.
After writing all this, I have just realised that I have LDAP connection
problems on my lab server, which is a bit of a fail on my part. Would that
be enough for ReviewBoard to not populate the authentication drop-down list?
Cheers,
Gavin
On 16 January 2013 14:30, Christian Hammond chip...@chipx86.com wrote:
Hi Gavin,
You'll need the Python ldap module, if you don't have it already.
Even though you're not using easy_install remotely, are you using it for
the eggs you download, or are you using another method?
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Jan 15, 2013, at 8:05 PM, Gavin Main gavm...@gmail.com wrote:
I am facing the same issue. I unfortunately don't have the luxury of using
easy_install as this requires a direct connection to the interwebs
(something we can't allow). I have packaged up every ReviewBoard 1.6.15
dependency by hand. 'rb-site' upgrade hinted that I needed the following...
Djblets (0.6.27), Django (1.3.4) and Feedparser (5.1.2), but when I start
Reviewboard after successfully running 'rb-site upgrade /path/to/site', I
lose my LDAP settings. 'DEBUG = True' doesn't give much away.
Any help would be greatly appreciated. Oh and while I'm here... we love
ReviewBoard.
Cheers!
On Wednesday, 10 October 2012 13:05:36 UTC+8, shravanthi s wrote:
I am facing a similar issue. Actually I had successfully configured LDAP
and it was working fine (I am using version 1.6.5). However I had an issue
with uploading jpeg images so I uninstalled PIL and did some modifications
to setup.py (JPEG_ROOT = /usr/lib) and reinstalled PIL along with
libjpeg-devel. I was able to upload jpeg images.
However a new issue popped up, my LDAP configuration was gone and when i
checked Authentication settings, there was no LDAP option at all! Only two
authentication methods were available. Not sure what went wrong. Would an
upgrade of Review Board resolve the issue? Appreciate your help..
On Tuesday, 2 October 2012 02:15:14 UTC+5:30, Christian Hammond wrote:
Running 'easy_install ReviewBoard' won't actually do much of anything.
You'd need to pass -U to do an upgrade.
Christian
--
Christian Hammond - chi...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Sat, Sep 29, 2012 at 12:32 AM, 周培青 zpq...@gmail.com wrote:
Hi Christian,
I remember I used easy_install and I tried running easy_install
ReviewBoard command again and got below information,
easy_install ReviewBoard
Searching for ReviewBoard
Best match: ReviewBoard 1.6.11
Processing ReviewBoard-1.6.11-py2.6.egg
ReviewBoard 1.6.11 is already the active version in easy-install.pth
Installing rb-site script to /usr/bin
Installing rbssh script to /usr/bin
Using /usr/lib/python2.6/site-**packages/ReviewBoard-1.6.11-**py2.6.egg
Processing
Re: Authentication problems with 1.5 api via perl.
Hi Jeff, did you ever get this resolved? I am facing a similar issue.
Christian, I am loving Reviewboard. Thank You!!!
Cheers,
Gav
On Friday, 22 October 2010 02:06:16 UTC+8, Jeff wrote:
I'm trying to write an svn pre-commit hook against a totally new
installation of reviewboard 1.5 (upgraded from the previous version,
but never really used).
As far as I can tell from the documentation, the json login page isn't
used anymore, and I just use basic HTTP authentication.
My perl code looks like this:
#!/usr/bin/perl
use LWP::UserAgent;
my $ua = LWP::UserAgent-new;
#$ua-credentials($rbhost:80,Web API,'user' = 'password');
my $req = HTTP::Request-new(GET = http://reviewboard.local.com/
rboard/api/review-requests/93/last-update/http://reviewboard.local.com/rboard/api/review-requests/93/last-update/);
$req-authorization_basic('user', 'password');
my $res = $ua-request($req);
print $res-as_string;
I've tried both the useragent credential and the request-
authorization_basic.
The result I get back is:
HTTP/1.1 401 UNAUTHORIZED
Cache-Control: max-age=0
Connection: close
Date: Thu, 21 Oct 2010 17:53:43 GMT
ETag: 3818aa0b0928af747aebc006814783fe
Server: Apache/2.2.3 (CentOS)
Vary: Cookie,Accept-Language
WWW-Authenticate: Basic realm=Web API
Content-Language: en-us
Content-Length: 70
Content-Type: application/json
Expires: Thu, 21 Oct 2010 17:53:43 GMT
Last-Modified: Thu, 21 Oct 2010 17:53:43 GMT
Client-Date: Thu, 21 Oct 2010 17:53:43 GMT
Client-Peer: 10.20.30.183:80
Client-Response-Num: 1
{stat: fail, err: {msg: You are not logged in, code: 103}}
If I try and hit the same page in an web browser after authenticating,
I get a 500 error and an email post at the end of this message.
What am I doing wrong? Is there any example perl code that hit's the
new API? I assume the existing stuff that I'm finding on the net
won't work anymore.
Traceback (most recent call last):
File /usr/local/reviewboard/python/Django-1.2.1-py2.7.egg/django/
core/handlers/base.py, line 100, in get_response
response = callback(request, *callback_args, **callback_kwargs)
File /usr/local/reviewboard/python/Django-1.2.1-py2.7.egg/django/
views/decorators/cache.py, line 70, in _wrapped_view_func
add_never_cache_headers(response)
File /usr/local/reviewboard/python/Django-1.2.1-py2.7.egg/django/
utils/cache.py, line 116, in add_never_cache_headers
patch_response_headers(response, cache_timeout=-1)
File /usr/local/reviewboard/python/Django-1.2.1-py2.7.egg/django/
utils/cache.py, line 105, in patch_response_headers
response['ETag'] = '%s' %
md5_constructor(response.content).hexdigest()
File /usr/local/reviewboard/python/Djblets-0.6.4-py2.7.egg/djblets/
webapi/core.py, line 273, in _get_content
content = adapter.encode(self.api_data, request=self.request)
File /usr/local/reviewboard/python/Djblets-0.6.4-py2.7.egg/djblets/
webapi/core.py, line 119, in encode
self.__encode(o, *args, **kwargs)
File /usr/local/reviewboard/python/Djblets-0.6.4-py2.7.egg/djblets/
webapi/core.py, line 136, in __encode
self.__encode(value, *args, **kwargs)
File /usr/local/reviewboard/python/Djblets-0.6.4-py2.7.egg/djblets/
webapi/core.py, line 136, in __encode
self.__encode(value, *args, **kwargs)
File /usr/local/reviewboard/python/Djblets-0.6.4-py2.7.egg/djblets/
webapi/core.py, line 164, in __encode
return self.__encode(result, *args, **kwargs)
File /usr/local/reviewboard/python/Djblets-0.6.4-py2.7.egg/djblets/
webapi/core.py, line 136, in __encode
self.__encode(value, *args, **kwargs)
File /usr/local/reviewboard/python/Djblets-0.6.4-py2.7.egg/djblets/
webapi/core.py, line 162, in __encode
raise TypeError(%r is not XML serializable % (o,))
TypeError: 2L is not XML serializable
WSGIRequest
GET:QueryDict: {},
POST:QueryDict: {},
COOKIES:{'csrftoken': '3c25a25c4c6ced636686afac7a25a4f1',
'rbsessionid': '2aeedaf117ffddcef6c72c0d5a2a407b'},
META:{'DOCUMENT_ROOT': '/usr/local/reviewboard/web/htdocs',
'GATEWAY_INTERFACE': 'CGI/1.1',
'HTTP_ACCEPT': 'text/html,application/xhtml+xml,application/
xml;q=0.9,*/*;q=0.8',
'HTTP_ACCEPT_CHARSET': 'ISO-8859-1,utf-8;q=0.7,*;q=0.7',
'HTTP_ACCEPT_ENCODING': 'gzip,deflate',
'HTTP_ACCEPT_LANGUAGE': 'en-us,en;q=0.5',
'HTTP_CONNECTION': 'keep-alive',
'HTTP_COOKIE': 'rbsessionid=2aeedaf117ffddcef6c72c0d5a2a407b;
csrftoken=3c25a25c4c6ced636686afac7a25a4f1',
'HTTP_HOST': 'reviewboard',
'HTTP_KEEP_ALIVE': '115',
'HTTP_USER_AGENT': 'Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
rv:1.9.2.10) Gecko/20100914 Firefox/3.6.10',
'PATH': '/sbin:/usr/sbin:/bin:/usr/bin',
'PATH_INFO': u'/rboard/api/review-requests/93/last-update/',
'PATH_TRANSLATED': '/usr/local/reviewboard/web/htdocs/
reviewboard.fcgi/rboard/api/review-requests/93/last-update
Re: Upgraded OS , then ReviewBoard failed upgrade
Hi, Deleted that column, and a few more that came up, then got stuck at this one: Evolution could not be simulated, possibly due to raw SQL mutations Error: Error applying evolution: (1091, Can't DROP 'name'; check that column/key exists) Regarding exactly what I did, cant say exactly, but I just followed the usual upgrade procedures, it worked fine when I did 1.5 to 1.5.5. The difference with this one is that I had just done an 'do-release-upgrade' on the underlying OS, this then broke reviewboard as it wanted me to then upgrade which I did, then these issues came up. This is getting urgent now so if I cant recolve it today I may have to just wipe it and start again. Thanks for your help. Gav... On Sunday, June 10, 2012 1:26:38 PM UTC+9:30, Christian Hammond wrote: No, that should never have been reached. That shows you're in some half-modified database state, which shouldn't have happened, given that database transactions are used during the evolution and the earlier error should have prevented the other modifications. At this point, I really wish you had a database upgrade, because things are kind of messed up. Make one now, just in case. Once you have a full backup (SQL dump is best), try deleting that column. You might get a few more like this. Can you tel me exactly what you did, every step of the way, prior to and after the initial rb-site upgrade? Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Sat, Jun 9, 2012 at 8:47 PM, Gav... ipv6g...@gmail.com wrote: On Sunday, June 10, 2012 1:04:30 PM UTC+9:30, Christian Hammond wrote: Your upgrade apparently also upgraded to Review Board 1.6.7, which has many significant changes. And that upgrade failed, because of the django_session issue. I've seen that django_session error before. Not sure what the cause is, but basically, that's a database index that was created, and Django is trying to re-create it now. You can try dropping it and see if that helps. You'll need to connect to your MySQL database and do: drop index django_session_c25c2c28 on django_session; Then re-run the rb-site upgrade command on your site. Hopefully this will work. Christian Thanks for the reply, done that, now I get: Error: Error applying evolution: (1060, Duplicate column name 'is_private') Drop that too? from where? Thanks Gav... -- On Sat, Jun 9, 2012 at 7:43 PM, Gav... ipv6g...@gmail.com wrote: Hi, I was on RB 1.5.5 , then an upgrade of the Ubuntu OS to 12.04 LTS then broke reviewboard (so it wanted to upgrade) so I ran an upgrade which has not been successful. (Note I believe Python was upgraded from 2.6 to 2.7) It seems to work until you go to the /admin/ areas. Rebuilding directory structure Updating database. This may take a while. Creating tables ... There are unapplied evolutions for sessions. There are unapplied evolutions for accounts. There are unapplied evolutions for changedescs. There are unapplied evolutions for reviews. There are unapplied evolutions for scmtools. Project signature has changed - an evolution is required Installing custom SQL ... Installing indexes ... No fixtures found. Evolution could not be simulated, possibly due to raw SQL mutations Error: Error applying evolution: (1061, Duplicate key name 'django_session_c25c2c28') Tried this with the latest version 1.6.7.1 I also get emails with: OperationalError: (1054, Unknown column 'scmtools_repository.extra_**data' in 'field list') Any clues as to what to try next.? As I was not expecting an OS upgrade to interfere with reviewboard, there is no pre-upgrade db dump, and a rb-site manage . dbdump now fails with : _mysql_exceptions.**OperationalError: (1054, Unknown column 'scmtools_repository.extra_**data' in 'field list') Thanks Gav... -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/**donate/http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/**users/http://www.reviewboard.org/users/ -~--~~~~--**~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscribe@* *googlegroups.com reviewboard%2bunsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/** group/reviewboard?hl=enhttp://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
Upgraded OS , then ReviewBoard failed upgrade
Hi, I was on RB 1.5.5 , then an upgrade of the Ubuntu OS to 12.04 LTS then broke reviewboard (so it wanted to upgrade) so I ran an upgrade which has not been successful. (Note I believe Python was upgraded from 2.6 to 2.7) It seems to work until you go to the /admin/ areas. Rebuilding directory structure Updating database. This may take a while. Creating tables ... There are unapplied evolutions for sessions. There are unapplied evolutions for accounts. There are unapplied evolutions for changedescs. There are unapplied evolutions for reviews. There are unapplied evolutions for scmtools. Project signature has changed - an evolution is required Installing custom SQL ... Installing indexes ... No fixtures found. Evolution could not be simulated, possibly due to raw SQL mutations Error: Error applying evolution: (1061, Duplicate key name 'django_session_c25c2c28') Tried this with the latest version 1.6.7.1 I also get emails with: OperationalError: (1054, Unknown column 'scmtools_repository.extra_data' in 'field list') Any clues as to what to try next.? As I was not expecting an OS upgrade to interfere with reviewboard, there is no pre-upgrade db dump, and a rb-site manage . dbdump now fails with : _mysql_exceptions.OperationalError: (1054, Unknown column 'scmtools_repository.extra_data' in 'field list') Thanks Gav... -- 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: Upgraded OS , then ReviewBoard failed upgrade
On Sunday, June 10, 2012 1:04:30 PM UTC+9:30, Christian Hammond wrote: Your upgrade apparently also upgraded to Review Board 1.6.7, which has many significant changes. And that upgrade failed, because of the django_session issue. I've seen that django_session error before. Not sure what the cause is, but basically, that's a database index that was created, and Django is trying to re-create it now. You can try dropping it and see if that helps. You'll need to connect to your MySQL database and do: drop index django_session_c25c2c28 on django_session; Then re-run the rb-site upgrade command on your site. Hopefully this will work. Christian Thanks for the reply, done that, now I get: Error: Error applying evolution: (1060, Duplicate column name 'is_private') Drop that too? from where? Thanks Gav... -- On Sat, Jun 9, 2012 at 7:43 PM, Gav... ipv6g...@gmail.com wrote: Hi, I was on RB 1.5.5 , then an upgrade of the Ubuntu OS to 12.04 LTS then broke reviewboard (so it wanted to upgrade) so I ran an upgrade which has not been successful. (Note I believe Python was upgraded from 2.6 to 2.7) It seems to work until you go to the /admin/ areas. Rebuilding directory structure Updating database. This may take a while. Creating tables ... There are unapplied evolutions for sessions. There are unapplied evolutions for accounts. There are unapplied evolutions for changedescs. There are unapplied evolutions for reviews. There are unapplied evolutions for scmtools. Project signature has changed - an evolution is required Installing custom SQL ... Installing indexes ... No fixtures found. Evolution could not be simulated, possibly due to raw SQL mutations Error: Error applying evolution: (1061, Duplicate key name 'django_session_c25c2c28') Tried this with the latest version 1.6.7.1 I also get emails with: OperationalError: (1054, Unknown column 'scmtools_repository.extra_data' in 'field list') Any clues as to what to try next.? As I was not expecting an OS upgrade to interfere with reviewboard, there is no pre-upgrade db dump, and a rb-site manage . dbdump now fails with : _mysql_exceptions.OperationalError: (1054, Unknown column 'scmtools_repository.extra_data' in 'field list') Thanks Gav... -- 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
Add ASF to users page
Hi, The Apache Software Foundation uses reviewboard (reviews.apache.org) if you feel like adding the ASF to the users page :) -- 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
Review Board and MSSQL
I'm looking to setup Code Review at my workplace which uses a Microsoft SQL Servers. I have had a brief read of your documentation and understand that MSSQL isn't directly supported but given that you work off Django and Python figure it should be possible to get it setup. I was hoping to get some advice on how large of an undertaking this would be, am I better to argue the virtues of an MySQL db for the task? It appears that there are robust solutions for python and connecting to MS databases such as - http://code.google.com/p/pyodbc/. Thanks in advance, can't wait to get this setup! Gav -- 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
