similar to: Patch to always install libupsclient-config

Tags: patch, upstream Hi, when configuring nut 2.2.0 the variable/symbol `@SSL_LDFLAGS@' is not resolved by the libupsclient-config script. The attached patch changes `@SSL_CFLAGS@' to `@LIBSSL_CFLAGS@' `@SSL_LDFLAGS@' to `@LIBSSL_LDFLAGS@' which should solve this issue. Regards, -octo -- Florian octo Forster Hacker in training GnuPG: 0x91523C3D http://verplant.org/

tags 439986 upstream thanks Hi Florian, 2007/8/29, Florian Forster <octo at verplant.org>: > Package: nut-dev > Version: 2.2.0-1 > Severity: minor > > After upgrading from version 2.0.something to version 2.2.0-1 the type > `UPSCONN' had been renamed to `UPSCONN_t'. This is a problem for > software that is supposed to work with different versions of this >

Hi, Made a test build of the Testing branch. The problem is that upsmon and upsc is not respecting the revision change of libupsclient.so. It is now libupsclient.so.1, but i get this. /usr/sbin/upsmon: error while loading shared libraries: libupsclient.so.0: cannot open shared object file: No such file or directory and: upsc: error while loading shared libraries: libupsclient.so.0: cannot

Hello together, after upgrading from nut 2.2.1 to nut 2.2.2, I noticed there's a (new?) libupsclient.so library. On my Redhat based system, f.e. the "upsc" binary links against it and is unhappy as the library is not included in the current RPM file. If you look at the .spec file for Redhat, the libupsclient.* stuff is included in the "nut-devel" package only. The SuSE

Hi, Below is a log of what I did. In summary, I think the problem lies in that I can't build libupsclient: e.g. make[1]: *** No rule to make target `libupsclient.la', needed by `upsc'. Stop. I'm not very familiar with autoconf, aclocal, automake, I tried hacking it a bit, but couldn't get it to fix the errors... Thanks, Edwin $ svn update At revision 845. $ autoreconf

I upgraded an operating system to openSUSE 42.2, kernel 4.4 and recompiled nut 2.7.4. ./configure, make clean and make went well, but make install failed. Make reports Making install in clients make[1]: Entering directory '/mnt/home/rprice/nut/nut-2.7.4.dev/clients' make[2]: Entering directory '/mnt/home/rprice/nut/nut-2.7.4.dev/clients' /usr/bin/mkdir -p '/usr/lib64'

Hi, Thanks for help. - I download the last version of NUT, 2.7.2.6 - I install library: nss-devel gcc-c++ So now I didn't get last errors on make. But I get a new one when I try to do - make install --------------------------- *[root at artesano nut-2.7.2.6]# make install* Making install in include make[1]: Entering directory `/home/artesano/Downloads/nut-2.7.2.6/include'

Arnaud, We've stumbled on a regression in nut-2.2.1 (also in nut-2.2.2-pre2) with regards to Tripplite USB devices. It turns out these devices will always indicate they have data available on the interrupt pipeline, no matter what. So we must limit the number of input reports we process to a single one in upsdrv_updateinfo() and leave any remaining ones to the next call in order to prevent

[I took the liberty of replying on nut-upsdev - not many people are using github yet since the NUT repository native format is still SVN.] On Sep 4, 2012, at 10:17 AM, Emilien Kia wrote: > This is a proposal for a new client library which scopes an higher level than the existing libupsclient. > > It needs less dependencies to be compiled than the libupsclient and can be easier to

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 provide better compatibility with older gcc versions please (since libnutclient is an alternative to

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 provide better compatibility with older gcc versions please (since libnutclient is an alternative to

Hi Charles, Yes, it looks like my g++ does contain STL library which might be just my specific case... However, as a temporary solution I disabled nutclient in Makefile (please find the file attached). And nut-2.7.3 can be compiled now. Thanks, Sergey On Wed, Jul 8, 2015 at 4:13 AM, Charles Lepple <clepple at gmail.com> wrote: > On Jul 6, 2015, at 10:32 AM, Sergey Talchuk

Hi, Currently, "configure.in" in both testing and the trunk have libupsclient disabled by default, which means the build is broken if the user doesn't explicitly enable it when running configure. Why was it like this and can I commit the fix? -- Carlos Rodrigues

Hi, I've stumbled upon a problem which I can't solve easily with the available options in tinc - at least as far as I see. If enlightenment is all I need, I'll happily accept pointers ;) I try to establish a connection between two hosts. Each host has multiple addresses assigned to it's internet interface. A stripped down list would be: Host 1: 2001:780:0:1e::1

Hello all, There is a new Windows package of NUT. It now contains nut-scanner binary. Note that there is a known issue with libupsclient.dll with nut-scanner. The scan of NUT servers using nut-scanner will not work for now. You can find it at : http://www.networkupstools.org/source/2.6/NUT-Installer-2.6.3-1.msi Please send feedback to the list. Regards, Fred -- Team Open Source Eaton -

Hi Charles, I try to do from a new clean installations after reset my server (some changes need it), and now the make install seems to works. Now i going to configure and test it. I attached the logs files from the last run. If i have any other problem I write to the list. Thanks a lot for your help. Have a good day. 2015-02-13 17:45 GMT-06:00 Charles Lepple <clepple at gmail.com>: >

Hi Charles, I forgot add attaches.[?] I try to do from a new clean installations after reset my server (some changes need it), and now the make install seems to works. Now i going to configure and test it. I attached the logs files from the last run. If i have any other problem I write to the list. Thanks a lot for your help. Have a good day. 2015-02-13 17:45 GMT-06:00 Charles Lepple

Hello all, I come back to request comments (and merge) on my pull request of the libnutclient. https://github.com/clepple/nut/pull/2 All previous comments have been addressed (some fixes and documentation). For memory, the libnutclient is an high-level C++ and C client library allowing to dialog with upsd. The addressed model is oriented around devices, variables and commands; unlike

On 04/04/17 15.19, Arnaud Quette wrote: > > > 2017-04-04 14:18 GMT+02:00 Jon Bendtsen <jon.bendtsen at jonix.dk > <mailto:jon.bendtsen at jonix.dk>>: [cuuuuut] > > there is a Github issue: https://github.com/networkupstools/nut/issues/415 > + a branch with the implementation: > https://github.com/networkupstools/nut/tree/upsmon_alarm > > For now: > -

On Sun, Nov 16, 2008 at 11:08 AM, Arnaud Quette <aquette.dev at gmail.com> wrote: >>> The remainder, until the -pre stage, will be: >>> - the Powerman support (through the powerman driver) for more PDUs >>> - the possible RRD integration into upslog >> >> It would be nice to have native RRD support in upslog, but we may also >> want to point