Comment 13 for bug 378416

I have neither the time nor enough knowledge about its internals to even consider taking over the project. I just want things to work smoothly: Thinkfinger is stable enough that it only takes minimal effort to keep up with minor kernel or X changes that happen over time. But one thing is for sure: Having a basically unmaintainable package is not going to help improve the quality or the security of the system and we don't lose anything by replacing the current mess by something more manageable.

It really doesn't make any sense to shove fprint down people's throats before it has reached feature parity with thinkfinger. If fprint developers feel that thinkfinger's solution to the password problem is not acceptable to them, they need to push for improvements in pam. If they can't do that, I consider the project just as dead as thinkfinger. I'm certainly not going to spend my time writing a patch that upstream won't accept and then try getting it into ubuntu, I'd rather fight for thinkfinger to stay until they (fprint) get this basic usability issue sorted out.