id,summary,reporter,owner,description,type,status,priority,component,severity,resolution,keywords,cc,release
9521,New install impossible on Trac 0.13dev/1.0,hasienda,hasienda,I've conducted Trac `trunk` testing lately and installed TagsPlugin into a fresh environment created and used with Trac t:r10850.\r\n\r\nThe plugin constantly failed to create the required db table `tags`:\r\n{{{\r\nTraceback (most recent call last):\r\n  File "<shortened>/Trac-0.13dev_r10849-py2.6.egg/trac/env.py"_ line 810_ in open_environment\r\n    needs_upgrade = env.needs_upgrade()\r\n  File "<shortened>/Trac-0.13dev_r10849-py2.6.egg/trac/env.py"_ line 646_ in needs_upgrade\r\n    if participant.environment_needs_upgrade(db):\r\n  File "build/bdist.linux-i586/egg/tractags/model.py"_ line 23_ in environment_needs_upgrade\r\n    if self._need_migration(db):\r\n  File "build/bdist.linux-i586/egg/tractags/model.py"_ line 47_ in _need_migration\r\n    db.rollback()\r\n  File "<shortened>/Trac-0.13dev_r10849-py2.6.egg/trac/db/util.py"_ line 107_ in __getattr__\r\n    raise AttributeError\r\nAttributeError:\r\n}}}\r\nNote: `<shortened>` has been edited by myself for traceback readability. The code resides in a virtualenv_ but that seems to be unrelated here.\r\n\r\nNever seen that before_ and especially the empty error looks suspicious.\r\n\r\nNot only it renders the whole plugin unusable but consequently leaves ugly traces in Trac itself like `'OperationalError: no such table: tags'` everywhere tags are expected_ like every wiki page.\r\n\r\n''Hint:'' Trac version reference below should be read as ''0.13dev''.,defect,assigned,high,TagsPlugin,critical,,install db rollback,rjollos_ otaku42_ jun66j5_ netjunki,1.0