uninstall time and estimation plugin

[anonymous]

After using easy_install is there anyway to remove the time and estimation plugin from the machine. I don't want to just disable i want to remove it.

[Russ Tyndall]

I do not know of an easy_uninstall.

You should be able to delete the egg out of your python site-packages directory however. On windows this is typically something like C:\Python2.4\site-packages on Debian this is /usr/lib/python2.4/site-packages/.

Hope this helps,

Russ

ps. any particular reason you were unhappy with this plugin?

[Stefan]

I also had to uninstall the tming estimation plugin. Mainly because

a) There were no intuitive way to figure out the $NEW variable stuff in the added reports.

b) Because of a) I deleted the reports (by hand because disabling the causing parts did not delete them)

c) After b) and something else I had to do a trac upgrade, in which all the reports re-spawned.

d) after doing b and c a couple of times, I had to trac-admin upgrade and restart apache a couple of times becore trac was back up (timing and estimation kept saying it needed upgrade).

However, whenever this plugin sorts out its issues (zero configuration etc), it will be really great!

[jon.stockdill@…]

I am using the mylar xmlrpc plugin which broke when I installed timingandestimation, it throws a "dictionary key must be string" error now.

I disabled the plugin which didn't fix the error. Could it be something w/ the DB tables?

Is there anyway to easily remove the tables?

[Russ Tyndall]

I don't think it is possible for database tables to throw python errors, but I could be wrong. As noted above, there is not an uninstall script or anything.

This plugin does not actually modify the database very much. It mostly just uses the existing database structure. Are you using sqlite?

Below is the sql that I think you will need to run to remove all traces of my plugin.

One thought that I had is that it is possible that the "mylar xmlrpc plugin" uses a custom field in trac that has the same name as one of my custom fields. This could explain why it suddenly started getting errors. This would also make it much harder to fix what was wrong with out doing some digging in the database yourself.

The only table I added is report_version, so :

DROP TABLE report_version

The thing that is causing problems is probably the custom fields, though I have had no other reports as such. This data can be removed by:

DELETE FROM ticket_custom where name in ( 'hours', 'billable', 'estimatedhours', 'totalhours', 'lastbilldate')

If you want to remove all ticket changes related to the plugin try the next statement. If you never got the plugin to work however, you probably dont have any associated ticket changes.

DELETE FROM ticket_change where field in ( 'hours', 'billable', 'estimatedhours', 'totalhours', 'lastbilldate')

I hope this solves your problems and gets you up and running again. If you find what was causing the problem, please leave a note here or in an email that lets me know where the incompatibility is,

Russ

[jon.stockdill@…]

Thank you for your help. The above SQL statements helped, but ultimately I had to run:

delete from report where id>8;
}}

to remove the reports and then the mylar problem disappeared.

From my limited exposure to the project, I bet the $NEW variables are somehow causing problems with mylar.  It doesn't make sense for mylar to be calling reports, since it executes custom queries.

Oddly enough, mylar and timing and estimation works fine for two of my projects, but for two it doesn't.

[anonymous]

Where can I delete the Fields in the Ticket?

[jon.stockdill@…]

The 05/16/07 08:37:09 comment shows how to remove the custom fields in the ticket.

[anonymous]

In fact, to get rid of the fields in ticket, you have to edit trac/proj/conf/trac.ini and erase all fileds & fields parameters here. Restart apache and you are done.

Note to the dev: that would have been more convenient to put all these fieds in /etc/trac.ini instaead of in each of the projetcs trac.ini files.

[Russ Tyndall]

Note to anon:

Because these are added programatically, and might be installed on a single of many tracs, and because the global config file is in different places on different systems, it seems prudent to leave it adding to each individual trac. Sorry for the inconvenience.

The information in this is ticket is somewhat dated at this point. On recent versions, the report_version table has been replaced with a custom_report table.

[macgngsta]

to uninstall for 0.10 I found that these steps work well to uninstall the tePlugin

1. remove the timingandestimationplugin from the plugins folder
2. edit trac.ini and remove all traces of te from components
3. edit trac.ini and remove all fields from ticket-custom
4. go into the sql db and remove the custom-reports table
5. go into the sql db and remove entries with id > 8 and author being timing and estimation plugin
6. go into the sql db, the system table, and remove the 2 entries: custom_report_manager_version and TimingAndEstimationPlugin_DB_version

using these steps i have been able to uninstall and reinstall the te plugin

[rune@…]

Remebember to disable the notify.notify component in trac-admin if you want to disable this plugin for a specific trac-install.

[anonymous]

Uninstalling this plugin is a major issue. We installed it evaluate it for our needs, and found it wasn't suitable. It took half a day to go through all of the tables and the configuration files to remove all traces. This is not good enough, and I would advise anyone else not try the plugin purely because of this alone.

[Geoff Wagner <gwagner@…>]

Uninstalling has been a complete nightmare.

My configuration is using MySQL. Upon initial install everything worked great. I then added this plugin and that is when everything went wrong. I wanted to remove it and i went through all of the steps listed above and i keep seeing.

Warning: Can't synchronize with repository "(default)" (Unsupported database type "sqlite"). Look in the Trac log for more information.

and

Unsupported database type "sqlite"

I have gone as far as to completely remove all references to trac, blow away my mysql DB, and completely rebuild my env and all i see is:

Unsupported database type "sqlite"

What can i do to put this nightmarish mistake behind me so i never need to look at this ever again. I would rather never track any time than even think of going through this mess again!

[Russ Tyndall]

Replying to Geoff Wagner <gwagner at fourscorellc.com>:

What can i do to put this nightmarish mistake behind me so i never need to look at this ever again. I would rather never track any time than even think of going through this mess again!

Well I am terribly sorry your experience has been so terrible. I have never had that specific error reported in the 3 versions of trac I have been maintaining this through. It sounds very much like you have a problem with trac unrelated to this plugin (though perhaps coinciding with its install).

A cursory googling of the error message you receive has lead me to the following post, which suggests that perhaps you have a too-old version of genshi installed. (But really thats just a shot in the dark from the first google result for your error message).

• ​http://www.mail-archive.com/trac-users@googlegroups.com/msg13385.html

• How did you install this plugin?
  • Did you install and download the latest from version control?
  • What revisions of major software, and operating system are you running on?

I would very much like you have a better impression of all this software, but you haven't given me much to go on. I will try to help you out, but please provide enough information to do so.

Hope this helps, Russ

---

Removing cc as they probably dont actually care anymore.

[Russ Tyndall]

Replying to anonymous:

Uninstalling this plugin is a major issue. We installed it evaluate it for our needs, and found it wasn't suitable. It took half a day to go through all of the tables and the configuration files to remove all traces. This is not good enough, and I would advise anyone else not try the plugin purely because of this alone.

#. There is a demo available #. Installing a fresh trac or a copy of your trac for evaluation purposes might have made this easier #. You should be able to disable this plugin without uninstalling it with something like 10 lines of configuration change, though this would leave residual database records around.

I'm sorry if this didn't work for you, it does for many people.

Russ

[Russ Tyndall]

sigh... wrong wiki syntax no matter which one I am in. I am working on an install script since, this seems to inspire a huge amount of vitriol.

[Russ Tyndall]

eghads UNinstall script

[Russ Tyndall]

There is an uninstall script​ in the scripts​ folder now. If you have further issues, please open a ticket about them.