search for: 012126

...y requires making some changes deep in the core USB HID code (that would require a lot of testing on other vendors' equipment) for what is basically a cosmetic issue: > > https://github.com/networkupstools/nut/issues/439 https://alioth-lists.debian.net/pipermail/nut-upsuser/2020-October/012126.html

...some changes deep in the core USB HID code (that would require a lot of testing on other vendors' equipment) for what is basically a cosmetic issue: >> >> https://github.com/networkupstools/nut/issues/439 > > https://alioth-lists.debian.net/pipermail/nut-upsuser/2020-October/012126.html >

...rgdal, a package providing bindings for the Geospatial Data Abstraction Library for reading and writing spatial data, has reached CRAN. This release changes the error handling mechanisms, and is more fully described in a posting on R-sig-geo: https://stat.ethz.ch/pipermail/r-sig-geo/2011-July/012126.html If any users observe unexpected behaviour following update, please revert to the 0.6-* series, and report with full details to the package maintainer. Extensive checking has been carried out, and no unexpected behaviour observed, but it is not feasible to check all possible use cases, esp...

...rgdal, a package providing bindings for the Geospatial Data Abstraction Library for reading and writing spatial data, has reached CRAN. This release changes the error handling mechanisms, and is more fully described in a posting on R-sig-geo: https://stat.ethz.ch/pipermail/r-sig-geo/2011-July/012126.html If any users observe unexpected behaviour following update, please revert to the 0.6-* series, and report with full details to the package maintainer. Extensive checking has been carried out, and no unexpected behaviour observed, but it is not feasible to check all possible use cases, esp...

On Sat, Oct 31, 2020 at 2:42 PM Tim Dawson <tadawson at tpcsvc.com> wrote: > I'm going to guess that since your test runtime of 305 is very close to > the low limit of 300, that's the warning. Not yet a fail, but very, very > close. > I tried setting override.battery.runtime.low = 60 in ups.conf, and waited for the UPS to reach 100% charge, and ups.status to report only