Modify ↓
#377 closed defect (fixed)
Column "build,step" does not exist when running trac-admin upgrade
| Reported by: | stou@… | Owned by: | cmlenz |
|---|---|---|---|
| Priority: | major | Milestone: | 0.6 |
| Component: | General | Version: | dev |
| Keywords: | Cc: | ||
| Operating System: | Linux |
Description
When attempting to upgrade the trac environment I get the following error:
# trac-admin . upgrade --no-backup
Add filename column to log table to save where log files are stored.
Traceback (most recent call last):
File "/usr/bin/trac-admin", line 7, in ?
sys.exit(
File "/usr/lib/python2.4/site-packages/Trac-0.11.3_modified-py2.4.egg/trac/admin/console.py", line 1317, in run
return admin.onecmd(command)
File "/usr/lib/python2.4/site-packages/Trac-0.11.3_modified-py2.4.egg/trac/admin/console.py", line 133, in onecmd
rv = cmd.Cmd.onecmd(self, line) or 0
File "/usr/lib/python2.4/cmd.py", line 219, in onecmd
return func(arg)
File "/usr/lib/python2.4/site-packages/Trac-0.11.3_modified-py2.4.egg/trac/admin/console.py", line 1154, in do_upgrade
self.__env.upgrade(backup=do_backup)
File "/usr/lib/python2.4/site-packages/Trac-0.11.3_modified-py2.4.egg/trac/env.py", line 462, in upgrade
participant.upgrade_environment(db)
File "/usr/lib/python2.4/site-packages/Bitten-0.6dev_r0-py2.4.egg/bitten/main.py", line 74, in upgrade_environment
function(self.env, db)
File "/usr/lib/python2.4/site-packages/Bitten-0.6dev_r0-py2.4.egg/bitten/upgrades.py", line 297, in add_filename_to_logs
cursor.execute(stmt)
File "/usr/lib/python2.4/site-packages/Trac-0.11.3_modified-py2.4.egg/trac/db/util.py", line 51, in execute
return self.cursor.execute(sql)
File "/usr/lib/python2.4/site-packages/Trac-0.11.3_modified-py2.4.egg/trac/db/util.py", line 51, in execute
return self.cursor.execute(sql)
psycopg2.ProgrammingError: column "build,step" does not exist
Attachments (0)
Change History (3)
comment:1 Changed 17 years ago by Remy Blank <remy.blank@…>
comment:2 Changed 17 years ago by stou@…
Yes that's the problem, I was just about to submit a patch to trac. You can close this ticket =)
comment:3 Changed 17 years ago by dfraser
- Resolution set to fixed
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.

I assume you're using PostgreSQL, judging from the --no-backup? This is most probably due to a bug in Trac 0.11.3. See #7600 for the details, and r7923 for the fix.
It will be included in 0.11.4, due... in a few hours.