[Trac] upgrade db failed from 0.9.4 to 0.10b1

8 views
Skip to first unread message

nomorsad

unread,
Sep 13, 2006, 10:41:34 AM9/13/06
to trac-...@googlegroups.com
Hi,

I try to upgrade my Trac from 0.9.4 to 0.10b1 but the "trac-admin
uprgade" fails.

Here is the verbose log:

[...]
# /usr/isis/Trac-rct/share/trac-0.10b1/trac/upgrades/db17.pyc matches
/usr/isis/Trac-rct/share/trac-0.10b1/trac/upgrades/db17.py
import trac.upgrades.db17 # precompiled from
/usr/isis/Trac-rct/share/trac-0.10b1/trac/upgrades/db17.pyc
Command failed: no such column: kind


My db is in version 16:
sqlite> select * from system;
database_version|16
[...]


I add that I didn't install Trac by setup.py. I only untar the package
and edit siteconfig.py.
(cause I don't like installers)

thanks for help
vince

Daniel Hilton

unread,
Sep 13, 2006, 10:48:04 AM9/13/06
to trac-...@googlegroups.com
We had this problem on Mac OSx but not on freeBSD.
We moved our install across to our server as we wanted the time and estimation plugin to work.
Dan
--
Dan Hilton
============================
DanHilton.co.uk                              
============================

Christian Boos

unread,
Sep 13, 2006, 11:04:24 AM9/13/06
to trac-...@googlegroups.com
nomorsad wrote:
> Hi,
>
> I try to upgrade my Trac from 0.9.4 to 0.10b1 but the "trac-admin
> uprgade" fails.
>
> ...

> Command failed: no such column: kind
>
>
> My db is in version 16:
> sqlite> select * from system;
> database_version|16
> [...]
>
>
What do you get with:
sqlite> .schema node_change

Anyway, a quick workaround would be to comment out the `cursor.execute`
statements
(but the one dropping the 'node_change' table, if the table still
exists), redo an 'upgrade',
then a 'resync'.

It would still be interesting to understand why you had a 'node_change'
table without a 'kind' column...

-- Christian

nomorsad

unread,
Sep 13, 2006, 11:33:14 AM9/13/06
to trac-...@googlegroups.com
I tried to understand why there's no "kind" column, although it's a
first install.

In fact, the db17 is working well, but db18 fails !!
But if I do an upgrade again, the db17 fails because the "system"
table claim the db is always in version 16...

So here is the "real" message :

# /usr/isis/Trac-rct/share/trac-0.10b1/trac/upgrades/db17.pyc matches
/usr/isis/Trac-rct/share/trac-0.10b1/trac/upgrades/db17.py
import trac.upgrades.db17 # precompiled from
/usr/isis/Trac-rct/share/trac-0.10b1/trac/upgrades/db17.pyc

# /usr/isis/Trac-rct/share/trac-0.10b1/trac/upgrades/db18.pyc matches
/usr/isis/Trac-rct/share/trac-0.10b1/trac/upgrades/db18.py
import trac.upgrades.db18 # precompiled from
/usr/isis/Trac-rct/share/trac-0.10b1/trac/upgrades/db18.pyc
Command failed: columns sid, authenticated, name are not unique

nomorsad

unread,
Sep 14, 2006, 5:08:49 AM9/14/06
to trac-...@googlegroups.com
OK I deleted all the line from the 'session' table and upgrade works now.

I hope there is no consequence...

vince

Christian Boos

unread,
Sep 14, 2006, 5:32:25 AM9/14/06
to trac-...@googlegroups.com
nomorsad wrote:
> OK I deleted all the line from the 'session' table and upgrade works now.
>
> I hope there is no consequence...
>
>

You've lost the previous sessions and most probably all the user
settings too,
but that's probably not a big deal.

> vince
>
> On 9/13/06, nomorsad <nomo...@gmail.com> wrote:
>
>> I tried to understand why there's no "kind" column, although it's a
>> first install.
>>
>> In fact, the db17 is working well, but db18 fails !!

>> ...


>> Command failed: columns sid, authenticated, name are not unique
>>
>>

I've created #3720 for this.

-- Christian

Reply all
Reply to author
Forward
0 new messages