Minor problems during 2.5.4 upgrade
Just an FYI -- I did run into a few minor problems upgrading reviewboard from 2.0.5 (yes, I haven't upgraded in a while) to 2.5.4. They'd been previously reported (here or other places online), and the work-arounds given worked for me too. When I first ran the "rb-site upgrade /var/www/reboard.com" command I got an error: ImportError: No module named PIL The advice I found was uninstall PIL, install Pillow: easy_install -m pil rm -Rf PIL-1.1.7-py2.7-linux-x86_64.egg Next, I got a problem when I ran "easy_install -U Pillow": ValueError: jpeg is required unless explicitly disabled using --disable-jpeg, aborting The fix for this was to install the missing package, then Pillow: zypper install libjpeg8-devel easy_install Pillow Next, I got the following error when I re-tired "rb-site upgrade /var/www/reboard.com": CommandError: Error applying evolution: relation "scmtools_repository_8c446842" already exists I'm using postgresql, so the suggested fix was to manually drop this table using: psql -U postgres -d reviewboard -q -c "DROP index scmtools_repository_8c446842;" After this, the upgrade worked fine. The new version looks good so far. -- Peter -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://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: Rb upgrade to 2.0 and extensions
On Monday, June 23, 2014 4:19:49 PM UTC-4, Christian Hammond wrote: Oh, huh. Turns out there’s some incompatible Ruby fork of lessc with the same version scheme. Awesome. You want the one installed by 'npm -g install less’, not the one from gem. Christian Thanks - that was it. It was a bit of an adventure to get everything installed (npm had issues with openssl on my installation, I had to turn that off), but in the end, once I got the system set up properly (gem uninstall less, npm -g install less, ...), it was just: cd rb-extension-pack-master/rbmotd sudo ./setup.py install And the motd seems to work properly too. Thanks again. -- Peter -- 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.
Rb upgrade to 2.0 and extensions
I just upgraded reviewboard from 1.7.11 to 2.0.2 on a Suse linux machine.
The upgrade went fine -- I like the look of the changes so far, but I did
have a couple of questions.
I enabled the new search (I'd never installed PyLucene before, but now that
it's not required, I decided to try enabling search). That also worked fine
(once I realized you needed to do a rb-site manage site rebuild_index
first, or it would fail and disable searching). The only problem I had was
that the first thing I tried searching for was a file name that I'd
recently modified, and that wasn't found. It looks like the search only
searches descriptions, tests, etc., is that right? So if the file name
isn't in the description, it won't be found? The only other issue I noticed
was just a minor documentation issue: the example crontab supplied used the
index command that your documentation said was deprecated / replaced by
update_index / rebuild_index, so I used those instead in my crontab.
The one other thing I tried was to install the rbmotd extension, which
sounded like a good way to communicate with users, the next time I want to
do an upgrade. I haven't installed any extensions before, so I may have
missed something here, but here's what I did:
- copied the latest rb-extension-pack-master.zip file onto my reboard
site
- installed a few missing libraries (rubygems, lessc, g++, ...)
- cd rb-extension-pack-master/rbmotd
- sudo ./setup.py install
But that gave me the following error. Any idea what this means?
Traceback (most recent call last):
File ./setup.py, line 29, in module
'templates/rbmotd/*.html',
File
/usr/local/lib/python2.7/site-packages/ReviewBoard-2.0.2-py2.7.egg/reviewboard/extensions/packaging.py,
line 48, in setup
setuptools_setup(**setup_kwargs)
File /usr/lib64/python2.7/distutils/core.py, line 152, in setup
dist.run_commands()
File /usr/lib64/python2.7/distutils/dist.py, line 953, in run_commands
self.run_command(cmd)
File /usr/lib64/python2.7/distutils/dist.py, line 972, in run_command
cmd_obj.run()
File /usr/lib/python2.7/site-packages/setuptools/command/install.py,
line 73, in run
self.do_egg_install()
File /usr/lib/python2.7/site-packages/setuptools/command/install.py,
line 93, in do_egg_install
self.run_command('bdist_egg')
File /usr/lib64/python2.7/distutils/cmd.py, line 326, in run_command
self.distribution.run_command(command)
File /usr/lib64/python2.7/distutils/dist.py, line 972, in run_command
cmd_obj.run()
File /usr/lib/python2.7/site-packages/setuptools/command/bdist_egg.py,
line 179, in run
cmd = self.call_command('install_lib', warn_dir=0)
File /usr/lib/python2.7/site-packages/setuptools/command/bdist_egg.py,
line 166, in call_command
self.run_command(cmdname)
File /usr/lib64/python2.7/distutils/cmd.py, line 326, in run_command
self.distribution.run_command(command)
File /usr/lib64/python2.7/distutils/dist.py, line 972, in run_command
cmd_obj.run()
File
/usr/lib/python2.7/site-packages/setuptools/command/install_lib.py, line
20, in run
self.build()
File /usr/lib64/python2.7/distutils/command/install_lib.py, line 109,
in build
self.run_command('build_py')
File /usr/lib64/python2.7/distutils/cmd.py, line 326, in run_command
self.distribution.run_command(command)
File /usr/lib64/python2.7/distutils/dist.py, line 972, in run_command
cmd_obj.run()
File
/usr/local/lib/python2.7/site-packages/Djblets-0.8.5-py2.7.egg/djblets/extensions/packaging.py,
line 270, in run
self.run_command('build_static_files')
File /usr/lib64/python2.7/distutils/cmd.py, line 326, in run_command
self.distribution.run_command(command)
File /usr/lib64/python2.7/distutils/dist.py, line 972, in run_command
cmd_obj.run()
File
/usr/local/lib/python2.7/site-packages/Djblets-0.8.5-py2.7.egg/djblets/extensions/packaging.py,
line 139, in run
self._build_static_media(extension)
File
/usr/local/lib/python2.7/site-packages/Djblets-0.8.5-py2.7.egg/djblets/extensions/packaging.py,
line 206, in _build_static_media
call_command('collectstatic', interactive=False, verbosity=2)
File
/usr/local/lib/python2.7/site-packages/Django-1.6.5-py2.7.egg/django/core/management/__init__.py,
line 159, in call_command
return klass.execute(*args, **defaults)
File
/usr/local/lib/python2.7/site-packages/Django-1.6.5-py2.7.egg/django/core/management/base.py,
line 285, in execute
output = self.handle(*args, **options)
File
/usr/local/lib/python2.7/site-packages/Django-1.6.5-py2.7.egg/django/core/management/base.py,
line 415, in handle
return self.handle_noargs(**options)
File
/usr/local/lib/python2.7/site-packages/Django-1.6.5-py2.7.egg/django/contrib/staticfiles/management/commands/collectstatic.py,
line 173, in handle_noargs
collected = self.collect()
File
Re: Rb upgrade to 2.0 and extensions
On Monday, June 23, 2014 3:10:02 PM UTC-4, Christian Hammond wrote: Hi Peter, Would you mind filing bugs for the Search brokenness and the crontab/docs inconsistency? That’ll help us track it for future releases. (It’s possible it’s just an old crontab from before the upgrade though.) Sure can do. I wouldn't say search was broken, just not exactly as complete as I was hoping for. You're right, it might just be an old example crontab from my old installation. The time stamp on search-cron.conf is old. So for rbmotd, we don’t yet have it released as a .egg. That’d be the ideal way to get it, so that you don’t have to set up a build environment for it, since it contains static media that must be compiled. Yes, an .egg would be much easier. But I was thinking I might try some extensions myself someday, so thought I'd try setting this up. Can you verify your version of lessc? It should support that option. Less C reports: lessc --version lessc 1.7.0 (LESS Compiler) [Ruby] 2.6.0 I can put up eggs soon. Christian -- Christian Hammond - chri...@beanbaginc.com javascript: Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com -- Peter -- 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: Rb upgrade to 2.0 and extensions
On Monday, June 23, 2014 3:27:44 PM UTC-4, Christian Hammond wrote: On June 23, 2014 at 12:20:54 PM, Peter Snelling (usenet@gmail.com javascript:) wrote: Less C reports: lessc --version lessc 1.7.0 (LESS Compiler) [Ruby] 2.6 Hmm, that version works here (well, 1.7.3). I’m on Ruby 1.9.3, though. Maybe that’s relevant. Christian -- Christian Hammond - chri...@beanbaginc.com javascript: Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com So --global-var is an option for lessc? Here's what lessc --help reports to me: lessc --help Usage: lessc [options] [INPUT] -h, --helpprint this help -v, --version print version -s, --silent --strict-imports -x, --compress --yui-compress --no-color --paths, --include-path PATHS paths to include separated by ':' --optimization [0, 1 or 2]default: 1 --00 optimization: 0 --01 optimization: 1 --02 optimization: 2 -- Peter -- 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: Moving Reviewboard Server
Thanks Christian, that worked. There were a couple of small issues. After importing the database, I initially got a message that they couldn't find the directory: /var/www/OldServer/htdocs/media/uploaded/images on the new server. I fixed this by creating a soft link from OldServer directory to the NewServer. I think the images directory is probably specified in some admin page, but I can't find it. The second issue is that some users couldn't log in to the new server. I suspect they'd forgotten their password, but I'm not certain. They tried using the recover link on the password screen, but that got them a message: Something broke! (Error 500) It appears something broke when you tried to go to here. This is either a bug in Review Board or a server configuration error. Please report this to your administrator. I got that same error when I tried that myself. Perhaps that's a real bug? In any case, I just used the admin interface and reset their passwords. Good idea on using DNS to hide the server change from users, but unfortunately, there were DNS issues on the old server, so most users used the numerical IP. If anyone's interested, here are my exact steps (except for the ones I forgot to record): # On the old server: /etc/init.d/apache2 stop easy_install -U ReviewBoard # Or did I do rb-site upgrade /var/www/OldServer? I can't recall. Are they the same thing? su postgres pg_dump reviewboard /tmp/rb.dump exit scp /tmp/rb.dump [NewServer] more conf/settings_local.py # On New Server (with an identical ReviewBoard and temporary database installed) /etc/init.d/apache2 stop systemctl stop postgresql.service vim conf/settings_local.py [add SECRET_KEY] su - postgres dropdb reviewboard createdb reviewboard psql reviewboard /tmp/rb.dump exit /etc/init.d/apache2 restart systemctl restart postgresql.service ln -s reboard.genband.com s3lab2dell1.genband.com rb-site upgrade /var/www/NewServer # Probably another restart, then things worked... - Peter On Tuesday, July 2, 2013 2:14:43 PM UTC-4, Christian Hammond wrote: Hi Peter, Your plan sounds about right. Let me give you a few more tidbits of info. First, you don't want to use dumpdb/loaddb. Those are slow, last-resort methods for going in-between database types (and are not guaranteed to be bug-free). Instead, you do want psql's native commands. You can minimize downtime by setting up the latest 1.7 release on the new server first. Create a temporary database that's used, then copy over the SECRET_KEY from the old site's conf/settings_local.py into the new one. Then, when you're ready, you can stop Apache, dump the database, import on the new server, run 'rb-site upgrade' (to upgrade the database schema), and then start Apache back up. I don't know what your DNS setup is like, but you could just set the old name to point to the new server. If you're using VMs for any of this, you could put postgres on its own VM, and then in the future it'll be easier to move Review Board instances around without dumping/loading the database. Hope that helps. Christian Peter Snelling wrote: I been trying out reviewboard for about 6 weeks, and it's working pretty well (only real issue is I haven't been able to get e-mails working properly). Now I've got a new better server to install it on. I'd like to copy the existing review and users from the existing database before I move it -- about 60 users and 135 review requests. I'm using pgsql, apache, and currently version 1.7.7.1. I don't see anything on http://www.reviewboard.org/docs/manual/1.7/admin/ on how to do this, but I see there have been a few questions about it in this group. It looks like some of the problems have been moving to a different database (eg: mysql to pgsql) or a different version of RB, so to keep things easy, I'll keep the same pgsql, apache, OS, and RB instance (by upgrading just before exporting?). I'm thinking I should probably: - Send users a outage notice - Stop apache - Upgrade to the latest 1.7 version - Export the database - Install on a new server - Import the database - Send users a notice about the new server. Maybe also put a redirect on the old server, pointing to the new one. I'm not sure in particular about how to do the db export/import. I see some people here used rb-site manage /var/oldRbPath dumpdb dumpdb.json , then copy that file over and do rb-site manage /var/newRbPath loaddb dumpdb.json. Is that the best way? Or is it better to use psql commands to dump the database? -- 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...@googlegroups.com javascript: For more options
Re: Moving Reviewboard Server
Thanks Christian, that worked. There were a couple of small issues. After importing the database, I initially got a message that they couldn't find the directory: /var/www/OldServer/htdocs/media/uploaded/images on the new server. I fixed this by creating a soft link from OldServer directory to the NewServer. I think the images directory is probably specified in some admin page, but I can't find it. The second issue is that some users couldn't log in to the new server. I suspect they'd forgotten their password, but I'm not certain. They tried using the recover link on the password screen, but that got them a message: Something broke! (Error 500) It appears something broke when you tried to go to here. This is either a bug in Review Board or a server configuration error. Please report this to your administrator. I got that same error when I tried that myself. Perhaps that's a real bug? In any case, I just used the admin interface and reset their passwords. Good idea on using DNS to hide the server change from users, but unfortunately, there were DNS issues on the old server, so most users used the numerical IP. If anyone's interested, here are my exact steps (except for the ones I forgot to record): # On the old server: /etc/init.d/apache2 stop easy_install -U ReviewBoard # Or did I do rb-site upgrade /var/www/OldServer? I can't recall. Are they the same thing? su postgres pg_dump reviewboard /tmp/rb.dump exit scp /tmp/rb.dump [NewServer] more conf/settings_local.py # On New Server (with an identical ReviewBoard and temporary database installed) /etc/init.d/apache2 stop systemctl stop postgresql.service vim conf/settings_local.py [add SECRET_KEY] su - postgres dropdb reviewboard createdb reviewboard psql reviewboard /tmp/rb.dump exit /etc/init.d/apache2 restart systemctl restart postgresql.service cd /var/www ln -s NewServer OldServer rb-site upgrade /var/www/NewServer # Probably another restart, then things worked... - Peter On Tuesday, July 2, 2013 2:14:43 PM UTC-4, Christian Hammond wrote: Hi Peter, Your plan sounds about right. Let me give you a few more tidbits of info. First, you don't want to use dumpdb/loaddb. Those are slow, last-resort methods for going in-between database types (and are not guaranteed to be bug-free). Instead, you do want psql's native commands. You can minimize downtime by setting up the latest 1.7 release on the new server first. Create a temporary database that's used, then copy over the SECRET_KEY from the old site's conf/settings_local.py into the new one. Then, when you're ready, you can stop Apache, dump the database, import on the new server, run 'rb-site upgrade' (to upgrade the database schema), and then start Apache back up. I don't know what your DNS setup is like, but you could just set the old name to point to the new server. If you're using VMs for any of this, you could put postgres on its own VM, and then in the future it'll be easier to move Review Board instances around without dumping/loading the database. Hope that helps. Christian Peter Snelling wrote: I been trying out reviewboard for about 6 weeks, and it's working pretty well (only real issue is I haven't been able to get e-mails working properly). Now I've got a new better server to install it on. I'd like to copy the existing review and users from the existing database before I move it -- about 60 users and 135 review requests. I'm using pgsql, apache, and currently version 1.7.7.1. I don't see anything on http://www.reviewboard.org/docs/manual/1.7/admin/ on how to do this, but I see there have been a few questions about it in this group. It looks like some of the problems have been moving to a different database (eg: mysql to pgsql) or a different version of RB, so to keep things easy, I'll keep the same pgsql, apache, OS, and RB instance (by upgrading just before exporting?). I'm thinking I should probably: - Send users a outage notice - Stop apache - Upgrade to the latest 1.7 version - Export the database - Install on a new server - Import the database - Send users a notice about the new server. Maybe also put a redirect on the old server, pointing to the new one. I'm not sure in particular about how to do the db export/import. I see some people here used rb-site manage /var/oldRbPath dumpdb dumpdb.json , then copy that file over and do rb-site manage /var/newRbPath loaddb dumpdb.json. Is that the best way? Or is it better to use psql commands to dump the database? -- 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...@googlegroups.com javascript: For more options, visit this group at http://groups.google.com
Moving Reviewboard Server
I been trying out reviewboard for about 6 weeks, and it's working pretty well (only real issue is I haven't been able to get e-mails working properly). Now I've got a new better server to install it on. I'd like to copy the existing review and users from the existing database before I move it -- about 60 users and 135 review requests. I'm using pgsql, apache, and currently version 1.7.7.1. I don't see anything on http://www.reviewboard.org/docs/manual/1.7/admin/ on how to do this, but I see there have been a few questions about it in this group. It looks like some of the problems have been moving to a different database (eg: mysql to pgsql) or a different version of RB, so to keep things easy, I'll keep the same pgsql, apache, OS, and RB instance (by upgrading just before exporting?). I'm thinking I should probably: - Send users a outage notice - Stop apache - Upgrade to the latest 1.7 version - Export the database - Install on a new server - Import the database - Send users a notice about the new server. Maybe also put a redirect on the old server, pointing to the new one. I'm not sure in particular about how to do the db export/import. I see some people here used rb-site manage /var/oldRbPath dumpdb dumpdb.json , then copy that file over and do rb-site manage /var/newRbPath loaddb dumpdb.json. Is that the best way? Or is it better to use psql commands to dump the database? -- 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 --- 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/groups/opt_out.
Configuration with gitweb
I've just installed ReviewBoard 1.7.7.1 on a Suse linux server (with git, apache, postgresql, modswgi, memcached, ...). I had some trouble adding our central git repository using the admin web interface. What finally seemed to work was using a gitweb interface to our repository. I set the Path to: http://172.16.27.63/cgi-bin/gitweb/gitweb.cgi?p=TCD.git;a=blob_plain;f=filename;h=revision and nothing else (no mirror path, raw file url mask, etc.). But now I'm having trouble doing post-review from my linux desktop. My local git is cloned from that repository: snelling@172.16.27.63:/localdisk/git/repositories/TCD.git When I try to post a review from my desktop, I get: There was an error creating this review request. The repository path snelling@172.16.27.63:/localdisk/git/repositories/TCD.git is not in the list of known repositories on the server. Any idea what I'm doing wrong? Is the userid or absolute path /localdisk causing a problem? -- 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 --- 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/groups/opt_out.
Re: Configuration with gitweb
When I try that, the admin web interface says: Unable to authenticate against this repository using one of the supported authentication types. - Peter On Friday, May 24, 2013 5:08:45 PM UTC-4, David Trowbridge wrote: In the repository configuration, you'll want to set your path to snelling@172.16.27.63:/localdisk/git/repositories/TCD.git and the raw file url to the gitweb url that you currently have as the path. -David On Fri, May 24, 2013 at 1:53 PM, Peter Snelling usenet@gmail.comjavascript: wrote: I've just installed ReviewBoard 1.7.7.1 on a Suse linux server (with git, apache, postgresql, modswgi, memcached, ...). I had some trouble adding our central git repository using the admin web interface. What finally seemed to work was using a gitweb interface to our repository. I set the Path to: http://172.16.27.63/cgi-bin/gitweb/gitweb.cgi?p=TCD.git;a=blob_plain;f=filename;h=revision and nothing else (no mirror path, raw file url mask, etc.). But now I'm having trouble doing post-review from my linux desktop. My local git is cloned from that repository: snelling@172.16.27.63:/localdisk/git/repositories/TCD.git When I try to post a review from my desktop, I get: There was an error creating this review request. The repository path snelling@172.16.27.63:/localdisk/git/repositories/TCD.git is not in the list of known repositories on the server. Any idea what I'm doing wrong? Is the userid or absolute path /localdisk causing a problem? -- 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...@googlegroups.com javascript: For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- 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/groups/opt_out. -- 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 --- 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/groups/opt_out.
