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 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 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

Reply via email to