Comment 5 for bug 701471

I have tried rebuilding all the packages in both main and universe against the libevent 2.0.10 in the https://launchpad.net/~kklimonda/+archive/libevent2 PPA.
All but four did fine, but the failure of one in its unit tests make me think that at least part of the packages that did build may not work correctly. As for the packages that did fail:

* honeyd -- inactive upstream (ironically he's the author of libevent). I have attempted porting it to libevent2, and I've done it but I can't really test it as I have no idea how to use it so I can't tell if the port was successful. I didn't have luck contacting upstream author (but will try again)
* ladvd -- this is the one with failing tests (or rather a single test). We can attempt fixing it, as it shouldn't be hard.
* python-event -- this one has inactive upstream, no packages depend on it, we already have a python-gevent which is more popular and working
* lua-event -- this one is tricky. lua-event that we ship is a fork of lua-event that has been made with single package in mind (prosody). Apparently all changes from this fork has been already merged upstream, and the upstream lua-event builds fine with libevent2, but Debian maintainer is concerned with whether prosody works with it, so he asked for some time to do tests. I also did not hear from him since then.

There is not much time before the feature freeze but, if I could get one more person who knows C interested in helping me with ladvd, and proofreading honeyd changes I've made, and if I got answer about lua-event, we could make this transition.

My main concern is the fact that we'd have to check as many reverse dependencies for whether they actually work - and even that may not be enough, someone would have to subscribe to all those packages and investigate problems (probably with the help of upstream) for the possibility that their cause is the new libevent.