The same problem is reported in TimingAndEstimationPlugin from time to time (e.g. #9519). I wonder if it's possible that the file ownership problem (which is the actual problem) is signalled by the GUI as warning or error.

Hello, I've been having this problem too. Checked the permissions both of the .ini file and the sqlite db file and they were fine. It is something within the plugin which I built with python setup.py bdist_egg ...

If I disable TracHours and restart apache the upgrade message goes away. I'm attaching my log file in case that it can come helpful.

What version should I try? The branch for 0.11 or the trunk? Remember I'm using 0.11.4

You'll want to use the 0.11 branch for now. I'm working to get the trunk compatible with Trac 0.11.

Everything looks normal in your log file. Do you have the exact same symptoms as reported in comment:description? That is, does trac-admin $TRACENV upgrade seem to have no effect and you just get repeatedly prompted to upgrade? Some more details about your configuration would also be helpful (Database, Python version, ...).

Just curious, what keeps you on 0.11.4 rather than upgrading to at least 0.11.7?

What version should I try? The branch for 0.11 or the trunk? Remember I'm using 0.11.4

You'll want to use the 0.11 branch for now. I'm working to get the trunk compatible with Trac 0.11.

Everything looks normal in your log file. Do you have the exact same symptoms as reported in comment:description? That is, does trac-admin $TRACENV upgrade seem to have no effect and you just get repeatedly prompted to upgrade? Some more details about your configuration would also be helpful (Database, Python version, ...).

Just curious, what keeps you on 0.11.4 rather than upgrading to at least 0.11.7?

Ok, I'm gonna try on another fresh env since this one seems to be pretty messed up. The reason I'm staying in 0.11.4 is because I have those envs in a dreamhost account and they offer this "one click" no hassle installation so that's what I did, tried 0.12.x by hand but many plugins still don't work so I sticked with 0.11.x branch, did not noticed that there is a 0.11.7 update though (the one click installer don't show updates, guess I'm gonna have to update it manually)

.. tried 0.12.x by hand but many plugins still don't work so I sticked with 0.11.x branch, did not noticed that there is a 0.11.7 update though (the one click installer don't show updates, guess I'm gonna have to update it manually)

I'd highly recommend you go with 0.12 or even 1.0. Both represent major improvements over the previous release.

What plugins aren't working for you with 0.12? My experience is that 0.12 support is pretty equivalent to 0.11 support by now, if not better. Many newer plugins only support 0.12 and greater. If a plugin has not been adapted to 0.12 by now, in most cases it is unmaintained and has numerous unfixed issues by now.

If you point me to the plugins that you are having trouble with on 0.12, I might be able to help with getting the 0.12 issues resolved. In many cases a plugin only requires an hour or two of work to get it up and running on 0.12.

Add Comment

This ticket has been modified since you started editing. You should review the
other modifications which have been appended above,
and any conflicts shown in the preview below.
You can nevertheless proceed and submit your changes if you wish so.