-
Notifications
You must be signed in to change notification settings - Fork 85
blogofile build fails with anything but bare #99
Comments
Regarding the first error (init simple_blog): This is becoming a bit of a theme. On some systems, python won't read a file with a filename that has unicode characters in it. Renaming "_posts/003 - post 3 - unicode test - 日本語 test.markdown" to something else without unicode characters has fixed this. I have never been able to reproduce this error myself though (Ubuntu 10.04 python-2.6.5) Regarding the second error (init blogofile.com): Totally my fault, I didn't tag the blogofile.com sources in the 0.7.1 release, so it's just pulling the latest blogofile.com sources, which I've converted to 0.8. You can check out the correct version with:
Even though I'm trying hard to release 0.8, I'll create a 0.7.2 release tonight to fix these issues. Thanks for your patience! |
OK, In the first case I had to delete all unicode characters in the post 3
In the second case in addition to checking out the 0.7.1 tag I had to python-lxml i386 2.2.8-2
python-webob all 0.9.8-1
python-pyquery all 0.6.1-1 or it would fail:
|
Mark from the mailing list finally tracked down the unicode issue down to his shell environment not having a $LANG set. On my machine I have LANG=en_US.utf8 -- unsetting that produces the UnicodeError. |
Yeah so this was my fault for not configuring my system properly. For future Reconfigure locales:
Select the locales your users are likely to use. Leave the default locale to
In your local ssh config (/etc/ssh/ssh_config or ~/.ssh/config) you need to
That should sort out your locale correctly for SSH sessions. On 20 May 2011 14:08, EnigmaCurry <
|
The plugin issue does not appear to be resolved? Or maybe the fix is just unreleased? Using 0.7.1, the config still tries to use the undefined name "plugin", making the blogofile.com template unusable. |
I installed Blogofile through easy_install on my Debian 6.0 VPS which has Python 2.6.6 and "blogofile build" fails on anything but the "bare" init.
On a "simple_blog" init it fails:
On a "blogfile.com" init it fails:
The text was updated successfully, but these errors were encountered: