id,summary,reporter,owner,description,type,status,priority,component,severity,resolution,keywords,cc,release
10293,New install impossible on Trac 1.0beta1,netjunki,netjunki,I was trying to evaluate test manager for trac on a fresh install of 1.0beta1 and ran into the following error:\r\n\r\n{{{\r\n19:53:36 Trac[env] ERROR: Exception caught while checking for upgrade: \r\nTraceback (most recent call last):\r\n  File "build/bdist.macosx-10.7-intel/egg/trac/env.py"_ line 832_ in open_environment\r\n    needs_upgrade = env.needs_upgrade()\r\n  File "build/bdist.macosx-10.7-intel/egg/trac/env.py"_ line 665_ in needs_upgrade\r\n    if participant.environment_needs_upgrade(db):\r\n  File "build/bdist.macosx-10.7-intel/egg/tracgenericclass/model.py"_ line 1276_ in environment_needs_upgrade\r\n    return (self._need_initialization(db) or self._need_upgrade(db))\r\n  File "build/bdist.macosx-10.7-intel/egg/tracgenericclass/model.py"_ line 1311_ in _need_initialization\r\n    return self._need_upgrade(db)\r\n  File "build/bdist.macosx-10.7-intel/egg/tracgenericclass/model.py"_ line 1322_ in _need_upgrade\r\n    db.rollback()\r\n  File "build/bdist.macosx-10.7-intel/egg/trac/db/util.py"_ line 107_ in __getattr__\r\n    raise AttributeError\r\nAttributeError:\r\n}}}\r\n\r\nLooking into this it looks like a common problem that many plug-ins have been having during the 1.0 release cycle. #10230 #9742 Looking at the solution used in #10230 I've produced a patch for test manager that at least allows it to install. I'm not sure if this is the right way to deal with this since it looks like #9742 uses a slightly more complex approach.,defect,closed,normal,TestManagerForTracPlugin,normal,fixed,AttributeError upgrade db,hasienda,1.0