Modify

Opened 6 years ago

Closed 5 years ago

#2519 closed defect (duplicate)

trac upgrade after installation of plugin

Reported by: theterminator Owned by: bobbysmith007
Priority: normal Component: TimingAndEstimationPlugin
Severity: normal Keywords:
Cc: Trac Release: 0.11

Description

after installing timing and estimation plugin, and enabling all the components it asks for trac upgrade, but even after upgrading it ample times it keeps on persisting about upgrading the environment
this is wat i get after i upgrade it the first time:

C:\>trac-admin c:\proj\Redsuit\project upgrade
C:\Python25\lib\site-packages\tracwikirename-1.2-py2.5.egg\wikirename\util.py:6

DeprecationWarning: The sre module is deprecated, please import re.

import sre

Timing and Estimation needs an upgrade
Upgrading Database
Creating bill_date table
Creating report_version table
Upgrading report_version table to v4
Dropping report_version table
Upgrading reports
Upgrading usermanual
Done Upgrading
Upgrade done.

even after the upgrading is done it still keeps asking for an upgrade

Attachments (0)

Change History (10)

comment:1 Changed 6 years ago by bobbysmith007

Can you please post your trac log and which database backend you are using?

Thanks,
Russ

comment:2 follow-up: Changed 6 years ago by theterminator

Trac[api] DEBUG: Estimator needs upgrade? False [installed version:1 pluginversion:1
2008-02-05 10:20:51,671 Trac[api] DEBUG: Estimator needs upgrade? False [installed version:1 pluginversion:1
2008-02-05 10:20:51,671 Trac[api] DEBUG: Estimator needs upgrade? False [installed version:1 pluginversion:1
2008-02-05 10:20:51,750 Trac[api] DEBUG: NEEDS UP?: sys:False, rep:True, stats:False, fields:False, man:False
2008-02-05 10:20:51,750 Trac[api] DEBUG: NEEDS UP?: sys:False, rep:True, stats:False, fields:False, man:False
2008-02-05 10:20:51,750 Trac[api] DEBUG: NEEDS UP?: sys:False, rep:True, stats:False, fields:False, man:False
2008-02-05 10:20:51,812 Trac[env] WARNING: Component <timingandestimationplugin.api.TimeTrackingSetupParticipant object at 0x0596C0F0> requires environment upgrade
2008-02-05 10:20:51,812 Trac[env] WARNING: Component <timingandestimationplugin.api.TimeTrackingSetupParticipant object at 0x0596C0F0> requires environment upgrade
2008-02-05 10:20:51,812 Trac[env] WARNING: Component <timingandestimationplugin.api.TimeTrackingSetupParticipant object at 0x0596C0F0> requires environment upgrade

DEBUG: Estimator needs upgrade? False [installed version:1 pluginversion:1
2008-02-05 10:21:27,967 Trac[api] DEBUG: NEEDS UP?: sys:False, rep:True, stats:False, fields:False, man:False
2008-02-05 10:21:28,015 Trac[env] WARNING: Component <timingandestimationplugin.api.TimeTrackingSetupParticipant object at 0x017EF590> requires environment upgrade
2008-02-05 10:21:28,015 Trac[init] DEBUG: SELECT value FROM system WHERE name='discussion_version'
2008-02-05 10:21:28,015 Trac[db] DEBUG: SELECT value FROM system WHERE name='fullblog_version'
2008-02-05 10:21:28,015 Trac[api] DEBUG: Estimator needs upgrade? False [installed version:1 pluginversion:1
2008-02-05 10:21:28,092 Trac[api] DEBUG: NEEDS UP?: sys:False, rep:True, stats:False, fields:False, man:False
2008-02-05 10:21:28,140 Trac[manager] DEBUG: SubscriptionManager: Found db version 1, current is 1
2008-02-05 10:21:28,140 Trac[api] DEBUG: TracforgeAdminSystem: Found db version 8, current is 8
2008-02-05 10:21:28,140 Trac[providers] DEBUG: TracMarksSystem: Found db version 1, current is 1
2008-02-05 10:21:28,296 Trac[api] DEBUG: Beginning Reports Upgrade
2008-02-05 10:22:09,375 Trac[env] INFO: Reloading environment due to configuration change

Even after upgrading i get this :

Estimator needs upgrade? False [installed version:1 pluginversion:1
2008-02-05 10:22:09,983 Trac[api] DEBUG: NEEDS UP?: sys:False, rep:True, stats:False, fields:False, man:False
2008-02-05 10:22:10,046 Trac[env] WARNING: Component <timingandestimationplugin.api.TimeTrackingSetupParticipant object at 0x05FB9E90> requires environment upgrade

iam using a sqlite db

comment:3 in reply to: ↑ 2 Changed 6 years ago by bobbysmith007

I am tweaking the logic to make more sense and adding more logging statements. I will post a new version of the plugin for you in a few minutes (hopefully).

-- Russ

comment:4 Changed 6 years ago by bobbysmith007

(In [3179]) re #2519 T&E for trac 11 version 0.6.1

I concluded that the logic to figure out when to upgrade reports was fairly incorrect and so rewrote what I hope will be a better fucntion for this. I also added some more logging statements to help debug this in the future

comment:5 Changed 6 years ago by theterminator

  • Priority changed from normal to low

russ, i think there is a syntax error in the in the new version (0.6.1) , in api.py, line 140 its:
#diff = db_reports.symmetric_difference(py_reports)

do u think if the "#" shouldnt be there? because variable diff is defined elsewhere and results in a syntax error

comment:6 Changed 6 years ago by theterminator

sorry russ my mistake, there is a syntax error on line 148 of api.py, not on line 140 as i previously said

comment:7 Changed 6 years ago by bobbysmith007

(In [3182]) re #2519 version 0.6.2

Sorry, I had this file open in two windows and corrected that syntax error in one and not the other.

Doh, syntax error in api.py should be fixed now

comment:8 Changed 6 years ago by bobbysmith007

  • Resolution set to fixed
  • Status changed from new to closed

Fixed?

comment:9 Changed 5 years ago by felipe@…

  • Priority changed from low to normal
  • Resolution fixed deleted
  • Status changed from closed to reopened

The error still happens to me... it is really fixed?

comment:10 Changed 5 years ago by felipe@…

  • Resolution set to duplicate
  • Status changed from reopened to closed

Actually, reading the current bugs list I believe the bug is already being issued in #4184.

Add Comment

Modify Ticket

Action
as closed .
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from bobbysmith007. Next status will be 'closed'.
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.