#9700 closed defect (fixed)
Issue in using hotcopy functionality
| Reported by: | Owned by: | Christian Boos | |
|---|---|---|---|
| Priority: | high | Milestone: | 1.0 |
| Component: | database backend | Version: | 0.13dev |
| Severity: | trivial | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
Hi folks,
Excuse me if this is a duplicate, but I haven't found any about this one. Using trac 0.13dev in production environment (yeah not good idea but too late), on an ubuntu 10.04 LTS workstation. Using Apache as web server, I want to run a daily hotcopy of my instance. when launching the command as specified in the help topic, I got this error:
AttributeError: EnvironmentAdmin' object has no attribute 'db_transaction'
Tried to run as root but no better results.
Thanks for listening me
Attachments (0)
Change History (6)
comment:1 by , 14 years ago
| Component: | general → database backend |
|---|---|
| Owner: | set to |
| Priority: | normal → high |
comment:2 by , 14 years ago
| Resolution: | → fixed |
|---|---|
| Severity: | normal → trivial |
| Status: | new → closed |
Fixed in r10262. Thanks for reporting and … thanks for trusting us and running trunk!
follow-up: 4 comment:3 by , 14 years ago
thank you for your impressing reactivity! will continue to run trunk for sure!! would you please answer an additional dummy question about the fix? how may I apply the fix? re-install everything? don't wanna loose data.(sorry for being dumb :) )
comment:4 by , 14 years ago
Replying to ludovic.reenaers@…:
thank you for your impressing reactivity! will continue to run trunk for sure!! would you please answer an additional dummy question about the fix? how may I apply the fix? re-install everything? don't wanna loose data.(sorry for being dumb :) )
I guess the easiest way would be to manually doing the change from the changeset linked in cboos answer. The hardest thing would be locating env.py ;) It's probably somewhere under site-packages/ from your python installation.
comment:5 by , 14 years ago
Patching directly site-packages is not advised, you can have multiple virtualenvs, or install targets. If you need to do manual modifications, always do the modifications in the source and then re-install. In this case, as the fix is already committed, an upgrade would be enough.
How to do the upgrade mainly depends on how you initially installed Trac trunk.
If you did a checkout, then you just go there, take note of the version you're currently using (svn info >> LAST), do an svn up to get the latest, and re-install by doing a python setup.py install (or develop even). Be sure to have a quick look at the changes that happened between the last revision you used (as given by svn info before the update), and the current (as given by svn info after the update), we usually note in bold if there's any db upgrade or other upgrade steps that shouldn't be missed by people running trunk. There can also be some upgrade informations in the 0.13 page.
If you did an easy_install Trac==dev, then you can just redo it with the -u flag, but this gives you less control as the procedure detailed above (with the former, if anything goes wrong you can easily do an svn up -r<previously-used-revision>, re-install, to recover a stable version).
comment:6 by , 14 years ago
I applied the procedure with svn up an d it worked fine! thank you once again, for fast answering.
No, it is a good idea, how would we discover flaws in new code otherwise? :-)