On 6 Aug, 2009, at 16:12 , Jeff Albertine wrote:
> Hey Andrea Hi Jeff :-) > I downloaded the windows zip file from Agile42 site, it’s named > binary_agilo-1.0_PRO-py2.5.egg.zip dated 8/5/2009. I copied it into > my Python25\Scripts folder, and ran easy_install: > > C:\Python25\Scripts>easy_install binary_agilo-1.0_PRO-py2.5.egg > Processing binary_agilo-1.0_PRO-py2.5.egg > removing 'c:\python25\lib\site-packages\binary_agilo-1.0_PRO- > py2.5.egg' (and eve > rything under it) > creating c:\python25\lib\site-packages\binary_agilo-1.0_PRO-py2.5.egg > Extracting binary_agilo-1.0_PRO-py2.5.egg to c:\python25\lib\site- > packages > binary-agilo 1.0-PRO is already the active version in easy-install.pth > Installing agilo_svn_hook_commit.py script to c:\Python25\Scripts > Installing create_agilo_project.py script to c:\Python25\Scripts > > Installed c:\python25\lib\site-packages\binary_agilo-1.0_pro-py2.5.egg > Processing dependencies for binary-agilo==1.0-PRO > Finished processing dependencies for binary-agilo==1.0-PRO > > Then I ran trac-admin for the upgrade: > > C:\Python25\Scripts>trac-admin.exe c:\tracprojects\encore upgrade > Database is up to date, no upgrade necessary. Before this you need to change the trac.ini and add the: [components] agilo.* = enabled agilo_common.* = enabled agilo_pro.* = enabled than do the trac-admin upgrade thing > Then when I enable Agilo Scrum in the ini file, it gets the same > database table not found error. I agree there must be something > wrong in my installation here, but being new at this Python thing > I’m not sure what to do. Any suggestions? Also, after the > installation, the plugins on the admin page still name the Agilo > plugin as RC2. Is that any help? Could be that you have both versions installed, in which case may create confusion, have you checked in the /plugins folder of your project, or in the site-packages of Python? Should be c:\python25\lib \site-packages according to your log :-) The best you could do is to enable the logging to DEBUG in the trac.ini, and try to run the upgrade again, and see if it is logging something interesting... [logging] log_type = file log_level = DEBUG log_file = logs/trac.log Than try to run the upgrade again, clean possibly, that should log out pretty much :-) HTH Best ANdreaT --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Agilo for Scrum" group. This group is moderated by agile42 GmbH http://www.agile42.com and is focused in supporting Agilo for Scrum users. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/agilo?hl=en -~----------~----~----~----~------~----~------~--~---
