On 02/02/2008, David Anderson <[EMAIL PROTECTED]> wrote:
> I've been trying for about 3 hours now to get 0.11b1 installed on
> either of Debian Etch or Lenny, and have failed in both cases.
>
> After much fighting, here are the latest symptoms:
>  - The trac egg is created and deployed properly in site-packages
>  - trac-admin and tracd are properly copied to /usr/bin
>  - *no* data files are installed. That includes templates,
> configurations, cgi-bin...

Are you sure? Moving the core of Trac to setuptools has changed the way
data is installed, and it is now bundled with the Trac egg. For example,
after doing python setup.py install I get this:

  [EMAIL PROTECTED]:~]find
/usr/lib/python2.5/site-packages/Trac-0.11dev_r6402-py2.5.egg/ -regex
'.*.\(html\|css\|png\)'  | wc -l
  94

This was always how plugins worked, and now Trac itself uses the same mechanism.

Obviously, mapping this data through your web server is quite annoying
though, so we also now have the copystatic trac-admin command. This
dumps all static resources for Trac and any plugins in the environment,
into a directory:

[EMAIL PROTECTED]:~/p/trac/trunk]trac-admin ../env/trunk help copystatic
copystatic <directory>
  -- Extract static resources from Trac and all plugins.

> The last point is obviously the one messing with me. Everything seems
> to work, except that the data files are never gathered and copied by
> setuptools. Attempting to run install_data manually results in:
>
> # python2.5 setup.py install_data
> running install_data
> Traceback (most recent call last):
>   File "setup.py", line 89, in <module>
>     """,
>   File "/usr/lib/python2.5/distutils/core.py", line 151, in setup
>     dist.run_commands()
>   File "/usr/lib/python2.5/distutils/dist.py", line 974, in
> run_commands
>     self.run_command(cmd)
>   File "/usr/lib/python2.5/distutils/dist.py", line 994, in
> run_command
>     cmd_obj.run()
>   File "/usr/lib/python2.5/distutils/command/install_data.py", line
> 50, in run
>     for f in self.data_files:
> TypeError: 'NoneType' object is not iterable

This though, I have no idea about. The setup.py contains the
package_data directive so it should get picked up I would think.

-- 
Evolution: Taking care of those too stupid to take care of themselves.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
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/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to