Everything looks decent doing a find.

/usr/lib/python2.4/site-packages/kaa/notifier/main.py
/usr/lib/python2.4/site-packages/kaa/notifier/main.pyc
/usr/lib/python2.4/site-packages/kaa/notifier/main.pyo
/usr/lib/python2.4/site-packages/kaa/popcorn/backends/xine/main.py
/usr/lib/python2.4/site-packages/kaa/popcorn/backends/xine/main.pyc
/usr/lib/python2.4/site-packages/kaa/popcorn/backends/xine/main.pyo
/usr/lib/python2.4/site-packages/kaa/popcorn/backends/gstreamer/main.py
/usr/lib/python2.4/site-packages/kaa/popcorn/backends/gstreamer/main.pyc
/usr/lib/python2.4/site-packages/kaa/popcorn/backends/gstreamer/main.pyo


On Tue, Mar 11, 2008 at 10:09 AM, Duncan Webb <[EMAIL PROTECTED]> wrote:

> Justin Wetherell said the following, on 11.03.2008 14:56:
> > I just did a python setup.py clean/build/install in both kaa and freevo
> and
> > I'm still getting the same problem but I think the traceback is slightly
> > different here.
> >
> File "../base/build/lib.linux-i686-2.4/kaa/notifier/main.py", line 110,
> in loop
>    import skin    # The skin class
>
> really does mean that main.py is the freevo main.py and it is in the
> notifier directory.
>
> In this case do a:
> find /usr/lib/python-2.4/site-packages/kaa /path/to/kaa -name "main.py*"
>
> I think that you will find a freevo main.py somewhere in these
> directories, if you don't then I'll need to investigate this further.
> I'll check later this evening when I'm home.
>
> The best way to clean out the kaa stuff is:
> cd /path/to/kaa
> find . -type d -name build -exec rm -r {} \;
> rm -r /usr/lib/python-2.4/site-packages/kaa
>
> It's easy to forget that the build gets copied to the site-packages
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Freevo-devel mailing list
Freevo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-devel

Reply via email to