Experiences with migrating an existing Trac project to work with Agilo?
Bernd Schmeil
I'm currently trying to evaluate Agilo. We have a 2+ years old Trac
project with a couple of modifications (plugins, custom fields, etc.)
during that time.
I thought I just give Agilo a quick try by copying the database and
Trac project and running the update command. Besides a couple of
issues regarding missing python libraries I saw something like a
foreign key constraint violation in relation to the milestone table.
This sounds to me like using Agilo requires an empty / new Trac
project (or drops the existing tables / data).
If anyone managed to migrate an existing Trac project, can you please
let me know what steps you did to succeed?
Thanks in advance! - Bernd Schmeil
ANdreaT
On Aug 20, 3:05 pm, Bernd Schmeil <be...@thebernd.de> wrote:
> Hello,
Hi Bernd
> I'm currently trying to evaluate Agilo. We have a 2+ years old Trac
> project with a couple of modifications (plugins, custom fields, etc.)
> during that time.
Ok, that should not be a problem...
> I thought I just give Agilo a quick try by copying the database and
> Trac project and running the update command. Besides a couple of
> issues regarding missing python libraries I saw something like a
> foreign key constraint violation in relation to the milestone table.
I don't think that is coming from agilo... we follow the trac
principle that is, there are no Foreign Keys and all the relations are
solved via name binding... ugly but works with all databases. Related
to the upgrade, there may be some problem related to other plugins
using table name that are used by agilo too, in any case, the BETA is
provided to be used on new project only and for testing purposes,
because there is no advanced upgrade process implemented yet, not even
from agilo 0.6
> This sounds to me like using Agilo requires an empty / new Trac
> project (or drops the existing tables / data).
Not really, but the BETA at the moment has no migration/upgrade
process in place, if you happen to have a DB with no tablename
duplication there should be no problem.
> Thanks in advance! - Bernd Schmeil
YAW
ANdreaT
Bernd Schmeil
thanks a lot. In this case it makes sense for us to check for
dependencies caused by other plugins and fix the issues.
- Bernd
Joerg
i'm continuing Bernd's work on our testdrive of agilo. I managed to
get the trac-admin upgrade process finishing. I had to drop the
milestone table and recreate it (and restore the data)
So by now, I am struck at two problems.
First, I can't see any charts. No image is shown. I believe it is
caused by missing graphics libraries at compile time of matplotlib or
pil. Can you tell me which kind of image formats are used so i can
recompile matplotlib and pil with the required libraries?
Second: when i try to open a "Sprint Backlog for Sprint" on the scrum
dashboard, I get the following error:
[BurndownTableModule]: 'ascii' codec can't encode character u'\xfc' in
position 48: ordinal not in range(128)
do have any idea how to solve it? We are running on postgres...
A tip on how to activate/install the agilo theme would be nice to...
Thanks for your help,
Joerg
Andrea Tomasini
On 21 Aug, 2008, at 18:48 , Joerg wrote:
> Hi Andrea,
Hi Joerg :-)
> i'm continuing Bernd's work on our testdrive of agilo. I managed to
> get the trac-admin upgrade process finishing. I had to drop the
> milestone table and recreate it (and restore the data)
Great :-)
> So by now, I am struck at two problems.
>
> First, I can't see any charts. No image is shown. I believe it is
> caused by missing graphics libraries at compile time of matplotlib or
> pil. Can you tell me which kind of image formats are used so i can
> recompile matplotlib and pil with the required libraries?
Images are generated as PNG, you normally need:
- zlib
- libpng
- freetype2 (for the writings)
and this should be enough, of course you will need to compile PIL
first, and than matplotlib again... normally numpy is the hardest
part :-)
> Second: when i try to open a "Sprint Backlog for Sprint" on the scrum
> dashboard, I get the following error:
> [BurndownTableModule]: 'ascii' codec can't encode character u'\xfc' in
> position 48: ordinal not in range(128)
> do have any idea how to solve it? We are running on postgres...
:-? BurndownTableModule is in agilo 0.6 not in the BETA 0.7... I
thought you were trying the BETA version? The error can be caused by a
unicode character in the summary of a ticket, but normally should
work... I would need to have the full log block to give you more
information :-) \xfc should be the german u-umlaut ;-)
> A tip on how to activate/install the agilo theme would be nice to...
You need to have the ThemeEngine installed, there is a link on where
to get it here: http://www.agile42.com/cms/pages/download-install/#third-parties
Once installed you should see in the Admin interface (WebAdmin) a new
Theme module, and there you can find the Agilo Theme.
> Thanks for your help,
YAW
> Joerg
ANdreaT
Joerg
> > First, I can't see any charts. No image is shown. I believe it is
> > caused by missing graphics libraries at compile time of matplotlib or
> > pil. Can you tell me which kind of image formats are used so i can
> > recompile matplotlib and pil with the required libraries?
>
> Images are generated as PNG, you normally need:
> - zlib
> - libpng
> - freetype2 (for the writings)
solved
> :-? BurndownTableModule is in agilo 0.6 not in the BETA 0.7... I
> thought you were trying the BETA version? The error can be caused by a
> unicode character in the summary of a ticket, but normally should
> work... I would need to have the full log block to give you more
> information :-) \xfc should be the german u-umlaut ;-)
solved (by installing agilo 0.7 beta).
So we "upgraded" to agilo 0.7. It was a little surprising, that
easy_install upgraded our complete trac installation with all trac
environments to 0.11. We had to update several plugins and themes. But
we are working on it.
We have Errors when activating on of these agilo plugin components:
- LinksModule:agilo.links.web_ui
- BacklogAdminPanel:agilo.admin.backlog
Whenever we enable one of these two, we get:
Traceback (most recent call last):
File "/usr/lib/python2.4/site-packages/Trac-0.11.1-py2.4.egg/trac/
web/api.py", line 339, in send_error
'text/html')
File "/usr/lib/python2.4/site-packages/Trac-0.11.1-py2.4.egg/trac/
web/chrome.py", line 684, in render_template
data = self.populate_data(req, data)
File "/usr/lib/python2.4/site-packages/Trac-0.11.1-py2.4.egg/trac/
web/chrome.py", line 592, in populate_data
d['chrome'].update(req.chrome)
File "/usr/lib/python2.4/site-packages/Trac-0.11.1-py2.4.egg/trac/
web/api.py", line 169, in __getattr__
value = self.callbacks[name](self)
File "/usr/lib/python2.4/site-packages/Trac-0.11.1-py2.4.egg/trac/
web/chrome.py", line 460, in prepare_request
for category, name, text in contributor.get_navigation_items(req):
File "/usr/lib/python2.4/site-packages/Trac-0.11.1-py2.4.egg/trac/
admin/web_ui.py", line 64, in get_navigation_items
panels, providers = self._get_panels(req)
File "/usr/lib/python2.4/site-packages/Trac-0.11.1-py2.4.egg/trac/
admin/web_ui.py", line 159, in _get_panels
for provider in self.panel_providers:
File "/usr/lib/python2.4/site-packages/Trac-0.11.1-py2.4.egg/trac/
core.py", line 67, in extensions
return filter(None, [component.compmgr[cls] for cls in
extensions])
File "/usr/lib/python2.4/site-packages/Trac-0.11.1-py2.4.egg/trac/
core.py", line 204, in __getitem__
component = cls(self)
File "/usr/lib/python2.4/site-packages/Trac-0.11.1-py2.4.egg/trac/
core.py", line 108, in maybe_init
init(self)
File "/usr/lib/python2.4/site-packages/agilo-0.7-BETA1.egg/agilo/
admin/backlog.py", line 47, in __init__
calculated = LinksConfiguration(self.env).get_calculated()
File "/usr/lib/python2.4/site-packages/Trac-0.11.1-py2.4.egg/trac/
core.py", line 108, in maybe_init
init(self)
File "/usr/lib/python2.4/site-packages/agilo-0.7-BETA1.egg/agilo/
links/model.py", line 94, in __init__
self.initialize()
File "/usr/lib/python2.4/site-packages/agilo-0.7-BETA1.egg/agilo/
links/model.py", line 122, in initialize
opts = tc.get_options()[__ALLOW__]
KeyError: 'allow'
Do you have any idea how to solve it?
Thanks,
Joerg
Joerg
When I click on new Ticket, i get:
2008-08-25 20:55:41,298 Trac[env] WARNING: base_url option not set in
configuration, generated links may be incorrect
in the logfile and an error stating some error with link allow on the
gui.
found here: agilo-0.7-BETA1.egg_usr_lib/agilo/ticket/
model.py: raise TracError("The Links Configurations
didn't initialize correctly! => %s" % str(e))
Joerg
Andrea Tomasini
On 25 Aug, 2008, at 20:59 , Joerg wrote:
> And another bug showed up:
Is the same as the other one... looks like you agilo did't initialize
the configuration correctly... in the trac.ini there should be a:
[agilo-links]
allow = requirement-story, story-task, bug-task
and other properties, normally are created when you run the trac-admin
upgrade on the project... did you do that? If yes, can you try to set
the version of agilo in the system db table to 0.6 and run the upgrade
again?
HTH
ANdreaT