Opened 19 years ago
Closed 15 years ago
#1741 closed defect (worksforme)
Cannot upgrade environment with Postgres backend
Reported by: | Owned by: | Jonas Borgström | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | admin/console | Version: | devel |
Severity: | major | Keywords: | trac_admin environment |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
We use the 0.9.0pre code, and the Postgres backend. changeset:1871 seems to have broken something for us - the macros.environment_needs_upgrade returns true, requesting us to use trac_admin to upgrade. Unfortunately trac_admin refuses to upgrade, complaining that it cannot backup a postgres database.
Attachments (0)
Change History (3)
comment:1 by , 19 years ago
Component: | general → trac-admin |
---|---|
Resolution: | → worksforme |
Status: | new → closed |
comment:2 by , 17 years ago
Resolution: | worksforme |
---|---|
Status: | closed → reopened |
It would be helpful if the error message noted that the —no-backup option has to be placed at the end of the command-line, instead of after the trac-admin command but before any pathnames as is usual for boolean flags on Unix.
Or even better, it would be nice if trac-admin used standard Unix option parsing.
comment:3 by , 15 years ago
Milestone: | 0.9 |
---|---|
Resolution: | → worksforme |
Status: | reopened → closed |
This is documented in TracUpgrade.
(OT: No idea why this ticket suddenly reappeared with a milestone, when it probably didn't have one before…)
Use
trac-admin upgrade --no-backup
. Note that we probably won't be providing automated database upgrade scripts for PostgreSQL until after 0.9 is released.