European Bob's Hula Hoopla!

Again, new packages. I still found I was getting problems with the Indexer with the last lot, but Peter seems to have fixed it now :) I still suffered from stale locks though - so, if you have files like:

/tmp/lucene-1f90313e5849e5c2ab12d9f723836364-write.lock

(The number could be all sorts of things)

... you'll want to remove them. Stop Hula, rm /tmp/lucene* and be on your merry way.

Other bugs:

• I think my Sunbird doesn't state the Status on entries properly - anyway, this means I can't update entries that are already on the calendar :( Even setting the Status to (eg.) "Confirmed" still results in an error, which is what makes me think it is Sunibrd at fault;
• Adding tasks to the calendar doesn't seem to work just yet.

You should find that you're able to connect, add events and stuff like that, though. Please let me know if you have any trouble; it's likely that the packages still aren't quite right about getting things up and running for everyone.

I just uploaded my r641 packages. These will automatically upgrade your schema when you install it, and if you install the new .NET agents it will use mdbtool to automatically add the Agents to your tree. It pretty much now mostly works for me; Sunbird is behaving with it fairly well. But, there are some gotchas. Here's what I learned:

• If you just installed hula-cil-agents and hula wasn't restarted, restart it - it needs to start up the new agents
• Debian stable doesn't have a mono. This isn't great, because we need it. So, I found this apt line:

  deb http://people.debian.org/~formorer/mono backports main

  ... which is a semi-official backport, I guess. This allows you to run the new hotness on sarge.
• There are very many bugs in the new code. The main one I ran into was with the indexer, and deleting:

  /var/lib/hula/netmail/index/<username>/

  ... fixed it up for me.
• the best way to debug these is to use tcpflow or a similar tool to capture the network traffic - oftentimes the error is in there. A typical invocation for the caldav stuff might be:

  tcpflow -i lo port 8081

  I tend to run it in it's own directory, since it generates a fair few files and I don't want them overrunning and breeding. The usual error to look for in these files is some kind of mono back trace in a HTML comment.
• there are/were odd problems with the actual version of mono in use. I think I got rid of it, but if your new mono agents don't start, that's probably the problem. Try invoking one manually:

  mono /usr/lib/hula/HulaWeb.exe

  If it falls over in a heap, it's a mono version problem, most likely.