The release managers are going to kill me.

At least if modlogan makes it into testing in time and any problem shows up.

I’ve been running a backport of modlogan on woody for some time, and this version has bugs. Ugly bugs. Every now and then it just eats up cpu cycles until i notice and nuke it. Well, there have been a couple of upstream releases in the meantime, including some fixes i contributed. I don’t want that version in sarge.

This is why i decided to hijack modlogan on a short term: the last maintainer upload was more than a year ago, the application build process is clean (standard autotools cdbs build now, i only moved the libraries to a subdir to not clutter the normal lib path and replaced a few configuration files with better example files)

During my testing of the package i also fixed two minor things: i removed some useless but annoying debug output and fixed a segfault when run with an invalid configuration. Oh, and i added better OS and Browser detection strings.