Bug#706345: more info
I lead up the team for Lunaserv; for the upstream author, go with "LROC SOC " A few of us on the team have done Debian packing work before; although none of us are currently on the Debian team, but if whoever picks this request up needs something from upstream, we're happy to help. Also, Lunaserv 3 will be out in the next couple of weeks and it should be much easier to deploy than the current version as it drops the old rails dependency and moves to rack. It also simplifies the database stuff (the minimum setup in Lunaserv3 will require no database at all). --Nick -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/bd9863af7296aec38b2dbf2b9544b...@secure.nickstoys.com
Bug#86242: I'll adopt upsd, packaged new upstream release 2.6, fixed bug #188282
> >How is it compared to Network UPS Tools, > >http://www.exploits.org/nut/>? Will it support more UPSes? > > I haven't used Network UPS Tools yet, so I can't compared it to > upsd. BTW the new maintaner of upsd will be Nick Estes. NUT is a much larger system than what upsd is meant to do. Basically, if you are resource limited, or just need something simple to use init's powerfail events then upsd might be what you're looking for. If you want a full featured setup with integration into other monitoring tools, web interfaces, etc then go with NUT, it does everything you need. Hope that helps, if you have any other questions, feel free to e-mail me directly. --Nick
Bug#86242: I'll adopt upsd, packaged new upstream release 2.6, fixed bug#188282
> I thought Nick Estes wanted to adopt the package... but I'll leave it > up to the two of you to decide who is going to take the package... That I do, which is why I renamed the wnpp bug from O: to ITA:, made a new package, and found a sponsor... I have a lintian clean package ready including the new upstream version and a fix to bug #188282. It also cleans up a few other things in the package. I found a sponsor for it since I am not yet a Debian developer, and assuming he doesn't find problems with it, he thought he would be able to upload it for me sometime today (tho I havn't heard anything further since yesterday). I suppose I should have posted an update to the bug when I renamed it to prevent confusion. (-= --Nick
