similar to: NUT development infrastructure and SCM

Dear NUT developers and contributors, time has come to shed more light on 2.8.0 roadmap! Ubuntu Developer Summit attendance has helped to clarify things. several of 2.8.0 tasks are detailed here: https://wiki.ubuntu.com/ServerOneiricInfraPower I'm conscious that our development infrastructure (Alioth) is not that suitable to track roadmaps, "Agile" specs and developments, as we do

If you don't use 'CERTVERIFY 1', then this will at least make sure that nobody can sniff your sessions without a large effort (...) > So, do I misunderstand CERTVERIFY directive ? Or is there a bug ? >> Can you reproduce such behaviour ? >> > > I'm not sure what is going on. Can you try running 'upsmon' with debugging > enabled? The following are

Dear fellows, As you have probably seen, NUT has had a recent boost through the help of Eaton. Frederic Bohe (contractor for Eaton France) has worked on Augeas, and is now working the Windows port. Chetan Agarwal, seconded by Prashi Gandi (both from Eaton India) are working on XCP and quality / validation related projects. I'm now pleased to announce that Emilien Kia (contractor for Eaton

2012/10/12 Emilien Kia <kiae.dev at gmail.com> > Hi guys, > Hi Emilien and the list, This is a pull request to finally merge NSS feature in nut trunk: > https://github.com/clepple/nut/pull/3 > I'd like to take a moment to shed some more light on this important development, which lasted 3 years: - the initial

Hi Charles and the list here is an update on 2.7.3 2015-03-20 3:33 GMT+01:00 Charles Lepple <clepple at gmail.com>: > On Mar 19, 2015, at 2:00 PM, Arnaud Quette <arnaud.quette at gmail.com> > wrote: > > * #158: the branch has been collapsed into one commit, but additional >> documentation (nut-names.txt) is needed: >>

?Hello fellow developers, as you may have noticed from a few e-mails in the past, there is a new NUT library in development these days. It should be part of the NUT platform API in the future and I'd like to present the status of work, hereby. 1/ The library shall be responsible of NUT configuration management. It shall encapsulate access and manipulation with all the configuration

?Hello everybody, just a few notes to the doxygen X man issue: 1/ AFAIK doxygen can generate man pages, so why don't we just generate them and decide then whether they are ill fitted or usable... 2/ I'd definitely use doxygen when possible; I mean I don't know any alternative that's able to do (at least partial) validation of the documentation with the source 3/ I

Hi Michal, I've cc'ed -upsdev, since some info could be interesting for everybody. 2011/5/27 Michal Soltys <soltys at ziu.info> > On 11-05-25 09:35, Arnaud Quette wrote: > > Hi Michal, > > > > 2011/5/25 Michal Soltys <soltys at ziu.info <mailto:soltys at ziu.info>> > >(...) > > > > I'm preparing larger patchset with

2015-04-27 15:02 GMT+02:00 Charles Lepple <clepple at gmail.com>: > On Apr 27, 2015, at 2:48 AM, Nick Ma. <nick.mayerhofer at enchant.at> wrote: > > > But it still doesn't compile any executable: ~/nut/tests% ls > > cpputest.cpp example.cpp Makefile Makefile.am Makefile.in > > I think it is only intended to produce an executable when running "make

Hi Charles, 2015-04-11 21:22 GMT+02:00 Charles Lepple <clepple at gmail.com>: > On Apr 8, 2015, at 9:44 AM, Arnaud Quette <arnaud.quette at gmail.com> wrote: > > - #190: upsd: NSS SSL only working in debug mode => NEED TESTING before > merging > Emilien has made a fix and PR (#199: Initialize SSL after deamonize and > downgrade to user.) > The user (Melkor

On Jan 15, 2014, at 10:18 AM, Emilien KIA wrote: > 2014/1/15 Charles Lepple <clepple at gmail.com>: >> Emilien, >> >> just saw your commit in Buildbot for testing some Windows changes. That's great that someone is working on this again! >> We have had a few users ask for updates to the 2.6.5+ version of NUT for Windows. > > I am just fixing some bugs

Hi all, on proposal by Arnaud Quette and sponsored by Eaton, I will work on a port on Java of client, discovery and config API. As I have already suggested (mail of 2011-06-14 of this ml), instead of developping another port of nut protocol, I suggest to develop a higher level API in C/C++ uppon existing upsclient, inspirated by existing C-based tools and python and perl rewrites. The second

Hello all, In order to prepare the merge of the NSS branch to the trunk, I have validated the code in this branch by passing this validation document written by Emilien Kia : http://www.networkupstools.org/tmp/NUT-NSS_Mini_DVT_Plan-final.pdf The testing has been done on rev 3685 of the ssl-nss-port branch. As you can read, I have found no issue. Let me know if you have any comments on this.

Hi All, Perhaps you have seen, a few weeks ago, a release of jNut-0.2 which introduces nut-scanner capability to jNut java library, see http://networkupstools.org/download.html#_java_packages. With this package have been released jNutWebApi, a java web archive which uses jNut to present some UPSD and nut-scanner data on the form of a web service. This package is a maven-based project

Hey, I'm scheduling a 2.6.2 release for max. September 15. The content will be lighter than first expected with 2.8.0 (see below). This includes the current trunk plus: - merge the nut-scanner branch, - some snmp-ups improvements (sysOID matching for init stage) and some more MIBs, - a first complete version of the nut-ipmipsu driver, - the new jNut Java binding, - preliminary support of

2014/1/15 Charles Lepple <clepple at gmail.com>: > Emilien, > > just saw your commit in Buildbot for testing some Windows changes. That's great that someone is working on this again! > We have had a few users ask for updates to the 2.6.5+ version of NUT for Windows. I am just fixing some bugs and implementing some minor windows-specific features. > The problem is that

On Apr 8, 2015, at 9:44 AM, Arnaud Quette <arnaud.quette at gmail.com> wrote: > - #190: upsd: NSS SSL only working in debug mode => NEED TESTING before merging > Emilien has made a fix and PR (#199: Initialize SSL after deamonize and downgrade to user.) > The user (Melkor Lord) has ack'ed the fix. > The fix is indeed trivial but I want to ensure that there is no

2012/11/9 <VaclavKrpec at eaton.com> > Hello gentlemen, > Hi Vasek, I'm moving the thread to -upsdev, since it has not to be private... please note that revisions 3771 and 3772 conclude nut_clock_* > development (including UTs): > interestingly enough, we were talking about that 5 mn ago with Emilien ;) my conclusion was that nut_clock devs were completed with 3772, and

2015-07-06 10:40 GMT+02:00 Sergey Talchuk <tals1975 at gmail.com>: > Dear developers, > > libnutclient has been added as a C++ alternative to libupsclient in 2.7.1. > As a result I can't compile nut 2.7.3 with gcc-3.3.6. There wasn't such a > problem with nut-2.6.5. > > Is it possible to add a configuration parameter like > '-without-libnutclient' to

Some precisions: we are not alone, some projects had similar problem: http://bugs.bitlbee.org/bitlbee/ticket/785 And the problem is really coming from NSS initialization. Discussion about the issue here : http://osdir.com/ml/mozilla.crypto/2002-08/msg00016.html There is a workaround to use NSS with fork but it is more setting a flag to share some resources (primarily sockets) but must