This isn't just a templates problem, it's everything managed in mercurial that isn't python code.
The tarball lacks a satchmo/apps/Satchmo.egg-info/SOURCES.txt. The tarball and zipballs really need to be created with hg clone http://bitbucket.org/chris1610/satchmo satchmo_gold cd satchmo_gold hg co v0.9 python setup.py sdist --formats=bztar,zip -d /path/to/dist/files (Stick gztar in there if you REALLY need a gzipped tarball, but these days they are pretty useless). And there will be nice Satchmo-0.9-0.* files in /path/to/dist/files For the more adventurous sorts, it would appear that pip can handle similar packaging which could be leveraged to provide a URL holding all of the components at the proper versions for satchmo. On Oct 26, 7:54 am, Iain Mac Donald <[email protected]> wrote: > On a fresh system an install of 0.9 fails to create any of the > templates. On the same system with 0.9-pre (an hg clone from a couple > of weeks ago) the templates were created. I did a grep through the > copious install output but didn't see any errors but neither were there > any creating/copying lines for the templates. > > Regards, > Iain. > > Using: Django 1.1.1, Python 2.5, Satchmo 0.9 tarball and the install > instructions athttp://www.satchmoproject.com/docs/svn/new_installation.html --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Satchmo users" 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/satchmo-users?hl=en -~----------~----~----~----~------~----~------~--~---
