Dirk Meyer wrote:
Reinoud Elhorst wrote:
As soon as I a try to open the root (/) directory, a
message appeared ( InProgress exception: maximum recursion depth
exceeded in cmp ). Took some time to figure out where things were
going wrong (but learned a ton on the freevo project
vo 2.0 the default player on my mediabox this
afternoon, if I don't find anything else.
Having followed the discussion on ml/tracker for the 1.6 branch, Dischi
and Jason, what's your preference for bugs like the above in the 2.0
branch?
Reinoud
Reinoud Elhorst wrote:
Hey,
Hey,
I felt brave and free today (or, actually, I've just given up buidling
my own media server and pitch in a little on freevo 2.0 :-) ).
I learned that the best way to understand the project is not by
reporting bugs, but solving them, so I spent tonight on a little
problem I had. As soon a
Jason Tackaberry wrote:
[snip]
Beacon complaining about not being able to find inotify_init sounds like
a bug. Was it a python exception? Or a linker problem?
Since it has been some time since I did the first glibc-recompile, I
can't be really sure of what happened, but this is as I
Today I tried to get beacon up and running on my Gentoo system. I ran
into some troubles, some discussed on the list before, some not. This is
a reference of them and how I solved them - it might help someone else
trying to do the same, or some checks might be added to the install
scripts befor
In r1767 an ifdef was introduced that broke my kaa.display build:
building 'kaa.display._X11module' extension
i686-pc-linux-gnu-gcc -pthread -fno-strict-aliasing -DNDEBUG -fPIC
-I/usr/include/python2.4 -c src/x11display.c -o
build/temp.linux-i686-2.4/src/x11display.o -Wall
src/x11display.c: In
It took me a couple ofd minutes to figue that one out as well. Running
setup.py without arguments in any of the subdirs returns a nice error
telling you you need to specify a commandline argument. Runing it in the
root just tells you it failed right after the inotify message -- I
couldn't resis
