Re: After installation, I see The page you were looking for does not exist.
Hi, Do you install RB in a directory and not at the root of your virtualhost ? Seems the same problem here : https://groups.google.com/forum/#!topic/reviewboard/cOP9dePrAuI -- 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
problem upgrading 1.5.6 to 1.6.1
I have installed review board with yum (ReviewBoard-1.5.6-1.fc15.noarch) I did the following . I get error while upgrading site. root@localhost conf.d]# easy_install -U ReviewBoard install_dir /usr/lib/python2.7/site-packages/ Searching for ReviewBoard Reading http://pypi.python.org/simple/ReviewBoard/ Reading http://www.reviewboard.org/ Reading http://downloads.reviewboard.org/releases/ReviewBoard/1.6/ Reading http://downloads.reviewboard.org/releases/ReviewBoard/1.5/ Reading http://downloads.reviewboard.org/releases/ReviewBoard/1.0/ Reading http://www.review-board.org/ Reading http://downloads.review-board.org/releases/ Reading http://downloads.review-board.org/releases/ReviewBoard/1.0/ Best match: ReviewBoard 1.6.1 Downloading http://downloads.reviewboard.org/releases/ReviewBoard/1.6/ReviewBoard-1.6.1-py2.7.egg Processing ReviewBoard-1.6.1-py2.7.egg creating /usr/lib/python2.7/site-packages/ReviewBoard-1.6.1-py2.7.egg Extracting ReviewBoard-1.6.1-py2.7.egg to /usr/lib/python2.7/site- packages Adding ReviewBoard 1.6.1 to easy-install.pth file Installing rb-site script to /usr/bin Installing rbssh script to /usr/bin Installed /usr/lib/python2.7/site-packages/ReviewBoard-1.6.1-py2.7.egg Reading http://downloads.reviewboard.org/mirror/ Processing dependencies for ReviewBoard Finished processing dependencies for ReviewBoard [root@localhost conf.d]# rb-site upgrade /var/www/reviewboard/ Rebuilding directory structure Upgrading site settings_local.py Updating database. This may take a while. /usr/lib/python2.7/site-packages/Django-1.3.1-py2.7.egg/django/db/ __init__.py:19: DeprecationWarning: settings.DATABASE_* is deprecated; use settings.DATABASES instead. DeprecationWarning /usr/lib/python2.7/site-packages/Django-1.3.1-py2.7.egg/django/db/ __init__.py:60: DeprecationWarning: Short names for ENGINE in database configurations are deprecated. Prepend default.ENGINE with 'django.db.backends.' DeprecationWarning Creating tables ... Upgrading Review Board from 1.6 to 1.6.1 There are unapplied evolutions for accounts. 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. Error: Error applying evolution: (1060, Duplicate column name 'is_private') [root@localhost conf.d]# -- 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
SVN pre/post commit hooks
All, I have just upgraded to ReviewBoard 1.6 - went cleanly and what an improvement great work. However, Before I embark on this myself I was wondering if anyone had the following: SVN pre commit hook - check for at least 1 ship-it before allowing a commit SVN post commit hook - close a review request if URL specified. I know the second one exists in the contrib/ section but this uses the old style api - So I was wondering if anyone had some new style API versions of these scripts that they would be willing to share? I also have 2 minor requests / questions? Could the new API be extended to give the total number of ship-its rather than just an indication that there is at least 1? Is there an easy way to email all users of a given ReviewBoard instance? Many thanks for a great product Dan -- 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: Upgrading from 1.0 to… well… anything
Ahh, thanks Anton. That's the critical piece of information I was
missing: I didn't realise easy_install was not an RB but a Python
tool. I think, Christian, I may have given you the wrong impression as
to how serious the problem is.
So, it's all going significantly better now: I've upgraded RB to 1.6.1
(successfully, I think), and the install package did, indeed, give me
an rb-site tool with which I then attempted to update my site.
Unfortunately, I got this back:
Rebuilding directory structure
Upgrading site settings_local.py
Updating database. This may take a while.
C:\Python26\lib\site-packages\django-1.3.1-py2.6.egg\django\db
\__init__.py:19: DeprecationWarning: settings.DATABASE_* is
deprecated; use settings.DATABA
SES instead.
DeprecationWarning
C:\Python26\lib\site-packages\django-1.3.1-py2.6.egg\django\db
\__init__.py:60: DeprecationWarning: Short names for ENGINE in
database configurations are
deprecated. Prepend default.ENGINE with 'django.db.backends.'
DeprecationWarning
Traceback (most recent call last):
File c:\Python26\Scripts\rb-site-script.py, line 8, in module
load_entry_point('ReviewBoard==1.6.1', 'console_scripts', 'rb-site')()
File C:\Python26\lib\site-packages\reviewboard-1.6.1-py2.6.egg
\reviewboard\cmdline\rbsite.py, line 1747, in maincommand.run()
File C:\Python26\lib\site-packages\reviewboard-1.6.1-py2.6.egg
\reviewboard\cmdline\rbsite.py, line 1644, in run
site.sync_database()
File C:\Python26\lib\site-packages\reviewboard-1.6.1-py2.6.egg
\reviewboard\cmdline\rbsite.py, line 346, in sync_database
self.run_manage_command(syncdb, params)
File C:\Python26\lib\site-packages\reviewboard-1.6.1-py2.6.egg
\reviewboard\cmdline\rbsite.py, line 472, in run_manage_command
execute_manager(reviewboard.settings, [__file__, cmd] + params)
File C:\Python26\lib\site-packages\django-1.3.1-py2.6.egg\django
\core\management\__init__.py, line 438, in execute_manager
utility.execute()
File C:\Python26\lib\site-packages\django-1.3.1-py2.6.egg\django
\core\management\__init__.py, line 379, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File C:\Python26\lib\site-packages\django-1.3.1-py2.6.egg\django
\core\management\base.py, line 191, in run_from_argv
self.execute(*args, **options.__dict__)
File C:\Python26\lib\site-packages\django-1.3.1-py2.6.egg\django
\core\management\base.py, line 220, in executeoutput =
self.handle(*args, **options)
File C:\Python26\lib\site-packages\django-1.3.1-py2.6.egg\django
\core\management\base.py, line 351, in handlereturn
self.handle_noargs(**options)
File C:\Python26\lib\site-packages\django-1.3.1-py2.6.egg\django
\core\management\commands\syncdb.py, line 56, in handle_noargs
cursor = connection.cursor()
File C:\Python26\lib\site-packages\django-1.3.1-py2.6.egg\django\db
\backends\__init__.py, line 250, in cursorcursor =
self.make_debug_cursor(self._cursor())
File C:\Python26\lib\site-packages\django-1.3.1-py2.6.egg\django\db
\backends\sqlite3\base.py, line 207, in _cursorself.connection =
Database.connect(**kwargs)
sqlite3.OperationalError: unable to open database file
Now, I'm not sure about the rest of this, but I'm pretty sure we're
running a MySQL database (at least I hope we are as that's what's been
backed up) so I don't know what it's trying to open an sqlite db. Any
ideas?
My site seems to still be up and running so nothing too disastrous
just yet.
Sandeep
On Sep 12, 10:56 pm, Anton Cohen an...@antoncohen.com wrote:
I did an upgrade from pre-1.0 SVN to 1.5.5. The instructions are in a
previous post:http://goo.gl/KFIiT
Your steps will be a little different because you are using
easy_install. And you might not have the missing table issue I had.
easy_install is generally easy to get:
Red Hat-based: yum install python-setuptools
Debian-based: apt-get install python-setuptools
Considering how old 1.0 is, the OS could be EOL'd, you might want to
start on a new server. If you don't have spare servers/VMs, at least
do the testing in a VM on your workstation. I would dump the database
and restore it to a test database. And copy the site files to a test
location. Then test doing upgrades of the test DB and files until you
get it right. Then shutdown the real site, do a backup, then upgrade.
-Anton
On Mon, Sep 12, 2011 at 12:33 PM, Christian Hammond chip...@chipx86.com
wrote:
rb-site is provided by the ReviewBoard package, which you should install by
doing easy_install -U ReviewBoard.
You shouldn't need to touch the tatballs. I don't know why it was angry
about setup.py, but perhaps it's just too old.
Best way to back up the database is by doing an SQL dump. That varies
depending on whether you're using MySQL, PostreSQL, etc. It won't be in our
site directory unless you're using SQLite (which we don't recommend).- Hide
quoted text -
- Show quoted text -
--
Want to help the Review Board project? Donate today at
http://www.reviewboard.org/donate/
Happy
Re: Upgrading from 1.0 to… well… anything
Ok, so I made the cardinal sin of not reading everything you sent. I
guess what I need to know is whether that error looks like migrating
this site is the best option or whether to go with generating a new
site and linking it to the old database.
Thanks again for everyone's help.
On Sep 13, 11:56 am, insysion s.tai...@insysion.net wrote:
Ahh, thanks Anton. That's the critical piece of information I was
missing: I didn't realise easy_install was not an RB but a Python
tool. I think, Christian, I may have given you the wrong impression as
to how serious the problem is.
So, it's all going significantly better now: I've upgraded RB to 1.6.1
(successfully, I think), and the install package did, indeed, give me
an rb-site tool with which I then attempted to update my site.
Unfortunately, I got this back:
Rebuilding directory structure
Upgrading site settings_local.py
Updating database. This may take a while.
C:\Python26\lib\site-packages\django-1.3.1-py2.6.egg\django\db
\__init__.py:19: DeprecationWarning: settings.DATABASE_* is
deprecated; use settings.DATABA
SES instead.
DeprecationWarning
C:\Python26\lib\site-packages\django-1.3.1-py2.6.egg\django\db
\__init__.py:60: DeprecationWarning: Short names for ENGINE in
database configurations are
deprecated. Prepend default.ENGINE with 'django.db.backends.'
DeprecationWarning
Traceback (most recent call last):
File c:\Python26\Scripts\rb-site-script.py, line 8, in module
load_entry_point('ReviewBoard==1.6.1', 'console_scripts', 'rb-site')()
File C:\Python26\lib\site-packages\reviewboard-1.6.1-py2.6.egg
\reviewboard\cmdline\rbsite.py, line 1747, in main command.run()
File C:\Python26\lib\site-packages\reviewboard-1.6.1-py2.6.egg
\reviewboard\cmdline\rbsite.py, line 1644, in run
site.sync_database()
File C:\Python26\lib\site-packages\reviewboard-1.6.1-py2.6.egg
\reviewboard\cmdline\rbsite.py, line 346, in sync_database
self.run_manage_command(syncdb, params)
File C:\Python26\lib\site-packages\reviewboard-1.6.1-py2.6.egg
\reviewboard\cmdline\rbsite.py, line 472, in run_manage_command
execute_manager(reviewboard.settings, [__file__, cmd] + params)
File C:\Python26\lib\site-packages\django-1.3.1-py2.6.egg\django
\core\management\__init__.py, line 438, in execute_manager
utility.execute()
File C:\Python26\lib\site-packages\django-1.3.1-py2.6.egg\django
\core\management\__init__.py, line 379, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File C:\Python26\lib\site-packages\django-1.3.1-py2.6.egg\django
\core\management\base.py, line 191, in run_from_argv
self.execute(*args, **options.__dict__)
File C:\Python26\lib\site-packages\django-1.3.1-py2.6.egg\django
\core\management\base.py, line 220, in execute output =
self.handle(*args, **options)
File C:\Python26\lib\site-packages\django-1.3.1-py2.6.egg\django
\core\management\base.py, line 351, in handle return
self.handle_noargs(**options)
File C:\Python26\lib\site-packages\django-1.3.1-py2.6.egg\django
\core\management\commands\syncdb.py, line 56, in handle_noargs
cursor = connection.cursor()
File C:\Python26\lib\site-packages\django-1.3.1-py2.6.egg\django\db
\backends\__init__.py, line 250, in cursor cursor =
self.make_debug_cursor(self._cursor())
File C:\Python26\lib\site-packages\django-1.3.1-py2.6.egg\django\db
\backends\sqlite3\base.py, line 207, in _cursor self.connection =
Database.connect(**kwargs)
sqlite3.OperationalError: unable to open database file
Now, I'm not sure about the rest of this, but I'm pretty sure we're
running a MySQL database (at least I hope we are as that's what's been
backed up) so I don't know what it's trying to open an sqlite db. Any
ideas?
My site seems to still be up and running so nothing too disastrous
just yet.
Sandeep
On Sep 12, 10:56 pm, Anton Cohen an...@antoncohen.com wrote:
I did an upgrade from pre-1.0 SVN to 1.5.5. The instructions are in a
previous post:http://goo.gl/KFIiT
Your steps will be a little different because you are using
easy_install. And you might not have the missing table issue I had.
easy_install is generally easy to get:
Red Hat-based: yum install python-setuptools
Debian-based: apt-get install python-setuptools
Considering how old 1.0 is, the OS could be EOL'd, you might want to
start on a new server. If you don't have spare servers/VMs, at least
do the testing in a VM on your workstation. I would dump the database
and restore it to a test database. And copy the site files to a test
location. Then test doing upgrades of the test DB and files until you
get it right. Then shutdown the real site, do a backup, then upgrade.
-Anton
On Mon, Sep 12, 2011 at 12:33 PM, Christian Hammond chip...@chipx86.com
wrote:
rb-site is provided by the ReviewBoard package, which you should install
by
doing easy_install -U ReviewBoard.
You shouldn't need to touch the tatballs. I don't know why
Re: Preserving diff file sort order
Success! In case it helps anyone else, here's what I had to do: 1. Comment out this line in diffviewer/forms.py: files.sort(cmp=self._compare_files, key=lambda f: f.origFile) 2. Comment out this line in in diffviewer/diffutils.py: files.sort(cmp_file) 3. I'm not sure if this step is necessary, but I deleted and regenerated forms.pyc and diffutils.pyc. I found this link to show how to manually regenerate them after making the changes in steps 1 and 2: http://pyfaq.infogami.com/how-do-i-create-a-pyc-file 4. Restart memcached (on Linux, Debian 6): /etc/init.d/memcached restart 5. Restart apache (on Linux, Debian 6): /etc/init.d/apache2 restart After that, new posts show up in the same order as the posted diff- file. Thanks! Scott On Sep 12, 3:06 pm, Christian Hammond chip...@chipx86.com wrote: Actually, I believe it is at upload time. So new diffs should be fine. diffviewer/forms.py would be the place to look. Christian -- Christian Hammond - chip...@chipx86.com Review Board -http://www.reviewboard.org VMware, Inc. -http://www.vmware.com On Mon, Sep 12, 2011 at 6:50 AM, SCFrench sc...@mathworks.com wrote: I'm pretty sure I tried that (restarting memcached), but I can try again. Do you know if the sorting occurs when posting the review to the database, or only when viewing the diff? That is, once I've commented out sort calls and restarted memcached, would I need to re-post the diff file or would existing reviews revert to the original ordering? And does it make sense to assume that if there were no sorting, the order in the diff-file would be the default ordering used? Thanks for your help, Scott On Sep 10, 3:44 am, Christian Hammond chip...@chipx86.com wrote: Hi, We purposefully reorder the files so that headers will come before implementation files, which aids in the review process in general. I imagine those are the spots you tried to comment out. You can certainly do that (maybe we need an advanced pref for it). However, you likely will need to clear your memcached for it to take effect. Christian -- Christian Hammond - chip...@chipx86.com Review Board -http://www.reviewboard.org VMware, Inc. -http://www.vmware.com On Fri, Sep 9, 2011 at 12:57 PM, SCFrench sc...@mathworks.com wrote: We are currently using Review Board 1.5.6, and have a custom tool which generates cvs diff files in a particular order. When we use post- review to upload that diff file, the contents get reordered. I've tried commenting out two sites (one in diffutils.py, and one in diffviewer/forms.py) which appear to sort the files list, but this seems to be having no effect. I can't find any other places in the code which call sort, but I could easily be missing something. Is there any way (including hacking Python) to get Review Board to honor the file ordering in a diff file? Thanks, Scott -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know athttp://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 athttp://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
PySVN not installed.
I have the configuration below,
Fedora 2.6
Subversion 1.4.6
ReviewBoard 1.5.6
python 2.5.1
When I try to add repositories, I'm getting the following:
The Python module pysvn is not installed. You may need to restart the
server after installing it.
How can I install this?
I downloaded pysvn-1.7.1. it requires Pycxx_5.5.0 (because svn 1.4) but I'm
trying to compile following the instruction in the INSTALL.html
I'm getting the following.
Info: Found PyCXX include in /software/tools/pysvn-1.7.1/Import/pycxx-5.5.0
Info: Found PyCXX Source in
/software/tools/pysvn-1.7.1/Import/pycxx-5.5.0/Src
Info: Found Python include in /software/tools/pysvn-1.7.1/Import/pycxx-5.5.0
/software/tools/pysvn-1.7.1/Import/pycxx-5.5.0/Src /usr/include/python2.5
('Error:', 'cannot find SVN include svn_client.h - use --svn-inc-dir=')
I changed the version of PyCXX from 6.1.1 to 5.5.0 (because of SVN 1.4)
I search for this error and it looks like this file can be installed on
svn_dev package, but I cannot find it download it.
Please help how can I debug this problem.
Thank you
Monica
--
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: Upgrading from 1.0 to… well… anything
On Tue, Sep 13, 2011 at 5:33 AM, insysion s.tai...@insysion.net wrote: Ok, so I made the cardinal sin of not reading everything you sent. I guess what I need to know is whether that error looks like migrating this site is the best option or whether to go with generating a new site and linking it to the old database. I'm not sure about the error. settings_local.py should tell you what DB you are using. I think a new site is the best way to go. By site I mean the directory structure and files created by 'rb-site install'. The directory structure and files of an old SVN pull are totally different than a new easy_install/rb-site created site. After creating the new site you point local settings at the old database (or better, a copy of the old database), and run 'rb-site upgrade' to evolve the database. You also need to copy any persistent data stored in the file system, from the old site to the new site, which as far as I know is only the stuff in htdocs/media/uploaded. -Anton -- 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: After installation, I see The page you were looking for does not exist.
That's right. The problem is fixed by setting it to root. But I would disable that configuration to avoid confusion . On Sep 13, 5:43 am, Nicolas VINOT ae...@imirhil.fr wrote: Hi, Do you install RB in a directory and not at the root of your virtualhost ? Seems the same problem here :https://groups.google.com/forum/#!topic/reviewboard/cOP9dePrAuI -- 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: rb-site install failed - ImportError: Entry point ('console_scripts', 'rb-site') not found
Do I need to remove
python-setuptools
python-devel
ReviewBoard
from Python 2.4?
And install them int Python 2.7?
How do I remove these egg files?
Thanks,
On Sep 13, 9:16 pm, Nelson Jones huawen@gmail.com wrote:
when I ran rb-site install. I got the following error.
$ rb-site install /var/www/myrb
Traceback (most recent call last):
File /usr/bin/rb-site, line 7, in ?
sys.exit(
File /usr/lib/python2.4/site-packages/pkg_resources.py, line 236,
in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File /usr/lib/python2.4/site-packages/pkg_resources.py, line 2096,
in load_entry_point
raise ImportError(Entry point %r not found % ((group,name),))
ImportError: Entry point ('console_scripts', 'rb-site') not found
What might be my problem?
The followings had been installed
python-setuptools
python-devel
memcached
patch
ReviewBoard
Python was 2.4 before these installation, and then upgraded to 2.7
after the above installations.
Thanks,
--
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: problem upgrading 1.5.6 to 1.6.1
I tried upgrading it to 1.5.6 to 1.6. It gave error. Then came 1.6.1 immediately. How can upgrade RB to 1.6 instead of 1.6.1 On Sep 14, 5:48 am, Christian Hammond chip...@chipx86.com wrote: At one point or another, you installed 1.6, not 1.6.1, but I'm guessing something went wrong. Basically, your database already has the columns that 1.6.1 thinks needs to be installed, but due to whatever happened, RB's settings in your database didn't have that knowledge recorded. If I know what you attempted before, it'll help me to figure out the solution. Christian -- Christian Hammond - chip...@chipx86.com Review Board -http://www.reviewboard.org VMware, Inc. -http://www.vmware.com On Tue, Sep 13, 2011 at 2:40 AM, Rohini Kumar Tharigonda rok...@gmail.comwrote: I have installed review board with yum (ReviewBoard-1.5.6-1.fc15.noarch) I did the following . I get error while upgrading site. root@localhost conf.d]# easy_install -U ReviewBoard install_dir /usr/lib/python2.7/site-packages/ Searching for ReviewBoard Readinghttp://pypi.python.org/simple/ReviewBoard/ Readinghttp://www.reviewboard.org/ Readinghttp://downloads.reviewboard.org/releases/ReviewBoard/1.6/ Readinghttp://downloads.reviewboard.org/releases/ReviewBoard/1.5/ Readinghttp://downloads.reviewboard.org/releases/ReviewBoard/1.0/ Readinghttp://www.review-board.org/ Readinghttp://downloads.review-board.org/releases/ Readinghttp://downloads.review-board.org/releases/ReviewBoard/1.0/ Best match: ReviewBoard 1.6.1 Downloading http://downloads.reviewboard.org/releases/ReviewBoard/1.6/ReviewBoard... Processing ReviewBoard-1.6.1-py2.7.egg creating /usr/lib/python2.7/site-packages/ReviewBoard-1.6.1-py2.7.egg Extracting ReviewBoard-1.6.1-py2.7.egg to /usr/lib/python2.7/site- packages Adding ReviewBoard 1.6.1 to easy-install.pth file Installing rb-site script to /usr/bin Installing rbssh script to /usr/bin Installed /usr/lib/python2.7/site-packages/ReviewBoard-1.6.1-py2.7.egg Readinghttp://downloads.reviewboard.org/mirror/ Processing dependencies for ReviewBoard Finished processing dependencies for ReviewBoard [root@localhost conf.d]# rb-site upgrade /var/www/reviewboard/ Rebuilding directory structure Upgrading site settings_local.py Updating database. This may take a while. /usr/lib/python2.7/site-packages/Django-1.3.1-py2.7.egg/django/db/ __init__.py:19: DeprecationWarning: settings.DATABASE_* is deprecated; use settings.DATABASES instead. DeprecationWarning /usr/lib/python2.7/site-packages/Django-1.3.1-py2.7.egg/django/db/ __init__.py:60: DeprecationWarning: Short names for ENGINE in database configurations are deprecated. Prepend default.ENGINE with 'django.db.backends.' DeprecationWarning Creating tables ... Upgrading Review Board from 1.6 to 1.6.1 There are unapplied evolutions for accounts. 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. Error: Error applying evolution: (1060, Duplicate column name 'is_private') [root@localhost conf.d]# -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know athttp://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: Issue 1862 in reviewboard: reviewboard running patch against empty files
Comment #3 on issue 1862 by nait...@gmail.com: reviewboard running patch against empty files http://code.google.com/p/reviewboard/issues/detail?id=1862 I've got what appears to be the same issue with an install of 1.5.6. We were having the same issue under the old 1.5rc install, which was what prompted the upgrade. I have debug logs going, but see nothing unusual. The repository we're using is Perforce. I can spin up a new report if you'd prefer. -- 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 2283 in reviewboard: Leaving page warning
Status: New Owner: Labels: Type-Enhancement Priority-Medium New issue 2283 by pierregi...@gmail.com: Leaving page warning http://code.google.com/p/reviewboard/issues/detail?id=2283 *NOTE: If you have a patch, please submit it to http://reviews.reviewboard.org/ What version are you running? 1.5.5 What's the URL of the page this enhancement relates to, if any? Describe the enhancement and the motivation for it. I'd like Rally to warn me when I'm about to leave the current page while I have modifications in progress, such as a review comment I haven't committed with the OK button yet. What operating system are you using? What browser? Windows 7, Firefox 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 2283 in reviewboard: Leaving page warning
Comment #2 on issue 2283 by pierregi...@gmail.com: Leaving page warning http://code.google.com/p/reviewboard/issues/detail?id=2283 Good to know, 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.
