Re: pyblosxom 1.5rc2 released!

Will Kahn-Greene <[email protected]> Tue, 28 Sep 2010 01:15:04 +0000 (UTC)
Newsgroups gmane.comp.web.pyblosxom.user
Message-ID <[email protected]>
So let's work through your issues one at a time:

1. The INSTALL file is different than the instructions on the web-site. 
That's because I did the 1.5rc2 release and then we did some documentation 
changes which I pushed to the web-site.  The changes should be persisted 
in git, but they haven't made it to a release tarball yet.

It's also possible that you were looking at the wrong site.  Were you 
looking at the instructions on http://pyblosxom.bluesock.org/ or 
http://pyblosxom.sourceforge.net/ ?

2. Python/Ruby/Perl have their own packaging system which is different 
than the Ubuntu/Fedora/OpenSUSE/etc packaging systems.  There are people 
who build packages of Python/Ruby/Perl modules.

If you prefer to use your system's packaging system, then you'll have to 
either build the PyBlosxom package yourself or you'll have to wait for 
some other contributor to build it for you.

Last time I checked Tollef was maintaining the PyBlosxom package for 
Debian and I think that's the package that Ubuntu has as well.  You should 
create a Debian/Ubuntu bug to get him to update it.

3. There are a couple of different ways to install PyBlosxom because there 
are two different packaging systems for Python.  Yes, it's kind of a pain 
in the ass.  There are a lot of really great Python devs working on the 
situation currently and figuring out better solutions.

4. You couldn't get it to work with virtualenv.  It sounds like you missed 
a step when setting up the virtual environment.  Incidentally, using 
virtual environments makes it really easy to encapsulate PyBlosxom and 
it's dependencies into a directory that you can wipe away if you don't 
want it around anymore.  Then it doesn't poison your system.  Also, when 
you upgrade system packages, PyBlosxom won't break.

I don't see any evidence of you being in a virtual environment in your 
emails, but I can only guess at what you did.  It's possible the 
instructions need some more work, but they're pretty basic, so I'm not 
sure what we could improve.

5. You've now got a situation where you don't know what you've got on your 
system.  Ubuntu packages Python 2.6 such that all site packages are stored 
in the same place (might be dist packages--I know they changed the name 
between Python 2.5 and 2.6, but I don't remember the details offhand). 
Find that directory and you can just delete the pyblosxom related 
directory trees.  Then it won't be on your system anymore.

6. You used easy_install _AND_ pip.  You don't want to mix and match 
easy_install/setuptools and pip/distribute because they don't play well 
with each other's metadata.  I'll try to make that clearer in the 
instructions.  Honestly, I didn't expect anyone to try both.


I'm sorry that it's so frustrating.

If anyone has any ideas on how to alleviate the confusion in the 
installation instructions, I'm interested in hearing them.  The source for 
the instructions is the INSTALL file in the git repository.

/will


On Tue, 28 Sep 2010, seanh wrote:

> On Tue, Sep 28, 2010 at 12:49:53AM +0100, seanh wrote:
>>     $ cd pyblosxom-1.5rc2
>>     $ bin/pyblosxom-cmd create ./myblog
>>     ...
>>     $ cd myblog
>>     $ sudo aptitude install python-pastescript
>>     $ paster serve blog.ini
>>     Starting server in PID 2675.
>>     serving on 0.0.0.0:5000 view at http://127.0.0.1:5000
>>
>> That is, _if_ I understand things correctly and the paster server is
>> running pyblosxom from the source code files in the extracted tarball,
>> and not finding it elsewhere on my system as a result of all those
>> failed install commands. I don't know how to get back to a clean system
>> to find that out.
>
> Ok, I had a spare laptop with Ubuntu 10.04 on it so I tried the above on
> a clean system and the paster command failed with "No module named
> Pyblosxom.pyblosxom". So the reason it's working on my desktop must be
> that one of the various different install attempts succeeded. Whichever
> one it was, it required my terminal to be restarted before things would
> work.
>
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
> _______________________________________________
> pyblosxom-users mailing list
> pyblosxom-users-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/pyblosxom-users
>

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev