Hi Christian,
Thanks very much for your help, I think it's worked! I don't think this is
relevant but thought I should include it nonetheless - as I'm working on a new
machine, I mysqldumped the database from the old system into a file and
replaced the database on the new system using that script (I took a backup
first of course even though the new system would have had an empty database).
I didn't copy over the old site's settings_local.py - I think some of the
contents have changed format slightly (e.g. DATABASE_ENGINE is now ENGINE
inside a DATABASE section?), but the values I entered when creating the new
site were identical in any case.
I used the django evolution 2.6 you referred to, installed and ran without any
problems.
The manual steps I assume you refer to are /static in apache's config? No
problem, will get on to that - can I simply copy the old /media files into
/htdocs/static on the new system? We had a bunch of screen grabs and diagrams
primarily.
If it's helpful to you, here's the output from the running it:
root@asok2:~# rb-site upgrade /var/www/reviews-em-software/
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 log output> ------------------
Creating tables ...
Creating table extensions_registeredextension
Creating table accounts_localsiteprofile
Creating table attachments_fileattachment
Creating table diffviewer_filediffdata
Creating table hostingsvcs_hostingserviceaccount
Creating table reviews_fileattachmentcomment
Creating table site_localsite_users
Creating table site_localsite_admins
Creating table site_localsite
Upgrading Review Board from 1.0rc2 to 1.7.6
There are unapplied evolutions for auth.
There are unapplied evolutions for sessions.
There are unapplied evolutions for accounts.
There are unapplied evolutions for changedescs.
There are unapplied evolutions for diffviewer.
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 ...
Installed 0 object(s) from 0 fixture(s)
Registering new SCM Tool Plastic SCM (reviewboard.scmtools.plastic.PlasticTool)
in
database
Registering new SCM Tool ClearCase
(reviewboard.scmtools.clearcase.ClearCaseTool
) in database
Evolution could not be simulated, possibly due to raw SQL mutations
Evolution successful.
------------------- <end log output> -------------------
Resetting in-database caches.
Upgrade complete!
The location of static media files (CSS, JavaScript, images)
has changed. You will need to make manual changes to
your web server configuration.
For Apache, you will need to add:
<Location "/static">
SetHandler None
</Location>
Alias /static "/var/www/reviews-em-software/htdocs/static"
For lighttpd:
alias.url = (
...
"/static" => "/var/www/reviews-em-software/htdocs/static",
...
)
url.rewrite-once = (
...
"^(/static/.*)$" => "$1",
...
)
Once you have made these changes, type the following
to resolve this:
$ rb-site manage /var/www/reviews-em-software resolve-check static-media
Certainly, myself and another user have succeeded in logging in, posting a new
patch, viewing the diff, etc... Thanks again for all your help, I really really
appreciate it!
Cheers,
Justin
From: reviewboard@googlegroups.com [mailto:reviewboard@googlegroups.com] On
Behalf Of Christian Hammond
Sent: 11 March 2013 19:44
To: reviewboard@googlegroups.com
Subject: Re: Upgrading from ReviewBoard 1.0rc2.1
Hi Justin,
In theory, you should be able to upgrade from a 1.0rc2.1 install.
What you'd do is configure a new install to point to the same database, and do
'rb-site upgrade' on the database. You can start this off by creating a site
(rb-site install), copying over your old site's settings_local.py file, and
then running 'rb-site upgrade' on the site.
In your case, BACK UP YOUR DATABASE FIRST! Can't stress this enough :)
Now, there is a bug some people have hit in the upgrade process for the
database, which you may be able to fix by installing the version of Django
Evolution from http://downloads.reviewboard.org/temp/django-evolution/
I'm still trying to figure out if we have all the right logic in there, and are
looking for people to test. Since you're likely to run into the issue, you're a
good candidate. So, on the new machine, install the appropriate package from
there, then do the above steps to migrate over your install.
(Note: This is where the backup comes in. If the upgrade fails, it's possible
that your database will be in a mixed state, and, depending on how mixed, you
may need to restore it. Hopefully this does not happen.)
The upgrade process may possibly tell you about a manual step or two you have
to make as well. If you got that far, the database upgrade, at least in theory,
went smoothly, though you'll need to spend some time experimenting with aspects
of the site to be sure.
Christian
--
Christian Hammond - chip...@chipx86.com<mailto:chip...@chipx86.com>
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Mon, Mar 11, 2013 at 9:55 AM,
<justin.ha...@pgs.com<mailto:justin.ha...@pgs.com>> wrote:
Hi there,
At my office, a few of us have been using ReviewBoard 1.0rc2.1 for a few years
without much complaint and recently had to upgrade the system it was running
on. Needless to say, ReviewBoard wasn't too happy about this.
We're desparately trying to resolve the situation so that we can either:
a) get the same version of ReviewBoard working again, or
b) get a slightly similar (but perhaps slightly newer) version working
c) get the latest version working
We successfully installed the newest version on a clean install, but don't
expect to be able to migrate our data very easily - any suggestions?
We've failed to get the same version installed again, because it seems that
Debian wants everything to be Python 2.6 now, and the original version seems to
be Python 2.5 (have I expressed that correctly?), at least in the egg file name.
Any suggestions at all would be welcome...
Cheers,
Justin
--
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<mailto:reviewboard%2bunsubscr...@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<mailto:reviewboard%2bunsubscr...@googlegroups.com>.
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<mailto: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<mailto:reviewboard+unsubscr...@googlegroups.com>.
For more options, visit https://groups.google.com/groups/opt_out.
This e-mail, including any attachments and response string, may contain
proprietary information which is confidential and may be legally privileged. It
is for the intended recipient only. If you are not the intended recipient or
transmission error has misdirected this e-mail, please notify the author by
return e-mail and delete this message and any attachment immediately. If you
are not the intended recipient you must not use, disclose, distribute, forward,
copy, print or rely on this e-mail in any way except as permitted by the author.
--
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.
