[Nut-upsdev] RFC: new variable battery.status (was: [PATCH] upscode2: Report ABM Status)

Charles Lepple clepple at gmail.com
Sat Nov 8 13:23:12 UTC 2014

On Nov 3, 2014, at 6:25 PM, thomas schorpp <thomas.schorpp at gmail.com> wrote:

>> For now, I've tracked your patch here:
>> https://alioth.debian.org/tracker/index.php?func=detail&aid=313541&group_id=30602&atid=411544
> Thanks, but no anonymous read access, so not very useful linking on public lists:
> "You've been redirected to this login page because you have tried accessing a page that was not available to you as an anonymous user."

Note that you replied to an email from two years ago. We tried to make things work with the Alioth tracker, but the admins were not very responsive when issues cropped up. In the time since that patch was posted, we tried to move everything to Github, and it looks like we missed at least one patch. (I'm listed as an administrator on the Alioth NUT project, and I even get that error when I'm logged in, so there seems to be an inconsistency in their database.) Try not to assume that we are intentionally making things difficult.

We're happy to integrate this patch in to NUT, especially since many users are not compiling NUT from source anymore. It looks like the "battery.status.abm" variable is new, though, so to get back to Arnaud's original question, should we have a more general "battery.status"?


Charles Lepple
clepple at gmail

More information about the Nut-upsdev mailing list