That did it. I just started over fresh with a new site directory,
copied the database over and it went flawlessly. I had a debian
package installed for django-evolution that was older so easy_install
didn't install it as a dependency.

Thanks,
Dan

On Jan 20, 4:18 pm, Christian Hammond <chip...@chipx86.com> wrote:
> I think the problem may be your version of django-evolution.
>
> Try to:
>
> 1) Remove the django_evolution* files/directories in
> /usr/lib/python2.5/site-packages (or python2.4, depending on the version
> you're using)
>
> 2) easy_install --upgrade django_evolution
>
> I think you just have an out-of-date version of this.
>
> Christian
>
> --
> Christian Hammond - chip...@chipx86.com
> VMware, Inc.
>
> On Tue, Jan 20, 2009 at 8:42 AM, Dan Savilonis <d...@n-cube.org> wrote:
>
> > I don't think I modified anything intentionally. I just copied the
> > sqlite3 database file to the new location. The hint wasn't
> > particularly helpful, it just stated 'field_type'.
>
> > I wasn't aware that there was even anything in ReviewBoard about a bug
> > tracker. I did build the install from the debian source package which
> > has a few minor modifications, but it shouldn't affect this. The
> > schema for the table is:
>
> > CREATE TABLE "scmtools_repository" (
> >    "id" integer NOT NULL PRIMARY KEY,
> >    "name" varchar(64) NOT NULL UNIQUE,
> >    "path" varchar(128) NOT NULL UNIQUE,
> >    "mirror_path" varchar(128) NOT NULL,
> >    "username" varchar(32) NOT NULL,
> >    "password" varchar(128) NOT NULL,
> >    "tool_id" integer NOT NULL REFERENCES "scmtools_tool" ("id"),
> >    "bug_tracker" varchar(200) NOT NULL,
> >    "encoding" varchar(32) NOT NULL
> > );
> > CREATE INDEX "scmtools_repository_tool_id" ON
> > "scmtools_repository" ("tool_id");
>
> > I tried changing it as well as dropping the table altogether and it
> > still gives me the same error.
>
> > Dan
>
> > On Jan 19, 4:54 pm, Christian Hammond <chip...@chipx86.com> wrote:
> > > You can use:
>
> > > rb-site manage /path/to/site evolve -- --hint
>
> > > (note the "--" before any parameters passed to manage)
>
> > > Did you at any point modify your models.py by hand? You shouldn't really
> > be
> > > seeing this error.
>
> > > When you copied the database over, was this through a file copy or a
> > > database dump?
>
> > > Christian
>
> > > --
> > > Christian Hammond - chip...@chipx86.com
> > > VMware, Inc.
>
> > > On Mon, Jan 19, 2009 at 8:40 AM, Dan Savilonis <d...@n-cube.org> wrote:
>
> > > > I've run rb-site upgrade to try to upgrade an older ~svn1520
> > > > installation database. I have the a fresh easy_install installation
> > > > from yesterday and copied the old database over, but I ran into the
> > > > issue below. How do I get manage.py to run now that I'm on an egg
> > > > installation toi debug this? I can't get it to find settings_local.py.
>
> > > > Rebuilding directory structure
> > > > Updating database
> > > > There are unapplied evolutions for reviews.
> > > > There are unapplied evolutions for reviews.
> > > > There are unapplied evolutions for scmtools.
> > > > There are unapplied evolutions for scmtools.
> > > > Project signature has changed - an evolution is required
> > > > Project signature has changed - an evolution is required
> > > > Installing json fixture 'initial_data' from '/usr/lib/python2.5/site-
> > > > packages/ReviewBoard-0.9.dev_20090118-py2.5.egg/reviewboard/scmtools/
> > > > fixtures'.
> > > > Installed 6 object(s) from 1 fixture(s)
> > > > The stored evolutions do not completely resolve all model changes.
> > > > Run `./manage.py evolve --hint` to see a suggestion for the changes
> > > > required.
>
> > > > The following are the changes that could not be resolved:
> > > > In model scmtools.Repository:
> > > >    In field 'bug_tracker':
> > > >        Property 'field_type' has changed
>
> > > > Thanks,
> > > > Dan
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To post to this group, send email to reviewboard@googlegroups.com
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