trac-admin upgrade failed

[Garrett McGrath]

I've run into an odd error in my attempts to update to 1.0.  I've got 2 Trac environments which give me the following when I run an update:

trac-admin /usr/local/data/trac/env/Internal upgrade
The upgrade failed. Please fix the issue and try again.

AttributeError:

Sadly, the script never tells me what the attribute error actually is, and since this isn't yet at 1.0, there is no trac.log file being created for me to peruse on my own (or was this introduced in 0.12?).

I've successfully upgraded another environment that was similar to the referred to 'internal' env.  However that one had been upgraded from 0.11 -> 0.12 -> 1.0.  These are attempting to go from 0.11->1.0.  I'm wondering if this is possibly caused by an addon that has altered the database layout (tags?).  Has anybody else run into this issue before?

-Garrett McGrath

[Patrick Schaaf]

On Wed, 2012-09-26 at 11:51 -0400, Garrett McGrath wrote:
> I've run into an odd error in my attempts to update to 1.0. I've got
> 2 Trac environments which give me the following when I run an update:
>
> trac-admin /usr/local/data/trac/env/Internal upgrade
> The upgrade failed. Please fix the issue and try again.
>
> AttributeError:

Do you have the TracAnnouncer plugin? Upgrading it fails with exactly
that very informative error.

See http://trac-hacks.org/ticket/10230 which also includes a workaround
in the description.

best regards
Patrick

[Garrett McGrath]

We don't use the announcer plugin but I suspect this can be traced back
to having had 'something' installed at some point. To that end I have a
question. Is there a way to remove all the new db tweaks made by
plugins and restore an env back to 'stock', specifically in an sqlite db
setup?

Making the leap in versions will require redoing all of our plugins and
some significant tweaking / updating of the pages anyway so scrubbing it
off all the plugin cruft doesn't seem 'too' expensive.

As an alternative I'll have to find a way to temporarily invoke 0.12
trac to do an upgrade from 0.11 then go to 1.0 from there.
-Garrett

[RjOllos]

On Thursday, September 27, 2012 9:17:56 AM UTC-7, Garrett McGrath wrote:

We don't use the announcer plugin but I suspect this can be traced back
to having had 'something' installed at some point.  To that end I have a
question.  Is there a way to remove all the new db tweaks made by
plugins and restore an env back to 'stock', specifically in an sqlite db
setup?

Have you tried just disabling the plugins?

Trac.log has been around forever. You can enable logging to get more information, such as a traceback on the error: http://trac.edgewall.org/wiki/TracLogging

[Steffen Hoffmann]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 27.09.2012 18:17, Garrett McGrath wrote:
> We don't use the announcer plugin but I suspect this can be traced
> back to having had 'something' installed at some point.

Yes, possible.

> To that end I have a question. Is there a way to remove all the new
> db tweaks made by plugins and restore an env back to 'stock',
> specifically in an sqlite db setup?

There is no automatic clean-up procedure. Someone might have written a
hack for it, but I've not seen such code by now.

I'd initialize a new Trac environment and manually compare table list,
then inspect and purge/drop additional tables from your (production)
environment. This is even not specific to the used db backend.

Steffen Hoffmann
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlBmMwAACgkQ31DJeiZFuHeWJACgwtLta4M93TzooD1NUko+QErO
xz8AoIBUKVtaFxgrZqlVvte4bsAwxoHS
=grDA
-----END PGP SIGNATURE-----