similar to: BuildBots - config.log from compile

On Sunday 19 October 2014 22:03:23 Charles Lepple did opine And Gene did reply: > Hi Gene, > > On Oct 18, 2014, at 7:35 PM, Gene Heskett <gheskett at wdtv.com> wrote: > > Greetings; > > > > I found pdf user manual which explains a few things that might help. > > > > However, for a ubuntu flavor, the various .conf etc files seem to be > > in

On Sunday 19 October 2014 23:28:38 Gene Heskett did opine And Gene did reply: Ping? > On Sunday 19 October 2014 22:03:23 Charles Lepple did opine > > And Gene did reply: > > Hi Gene, > > > > On Oct 18, 2014, at 7:35 PM, Gene Heskett <gheskett at wdtv.com> wrote: > > > Greetings; > > > > > > I found pdf user manual which explains a

Greetings people; The section of drakeconf that pclos uses has two problems. First is several screens full of complaints about deprecated syntax in "/etc/udev/rules.d/70-nut-usbups.rules" at each reboot. So I pulled the current 2.5 svn trunk, then found I was missing quite a few build tools needed here that aren't used when building a kernel, currently running a 32 bit

Hi Gene, On Oct 21, 2014, at 9:12 PM, Gene Heskett <gheskett at wdtv.com> wrote: >> configure: error: libgd not found, required for CGI build >> >> And gdlib does not appear to be available from the repo's. > Sorry, I must have missed that message. This is still with Ubuntu 10.04, right? http://packages.ubuntu.com/source/lucid/nut lists the build dependencies,

I have the following UPS that I'm trying to get to work with NUT: SU3000RTXL3U I have it connected via USB. My ups.conf looks like: [test] driver = usbhid-ups vendorid = 09ae port = auto When I run upsdrvctl -DD start, I get: Network UPS Tools - UPS driver controller 2.4.1 Starting UPS: test exec: /lib/nut/usbhid-ups -a test Network UPS Tools - Generic HID driver 0.34 (2.4.1)

Citeren Arjen de Korte <adkorte-guest at alioth.debian.org>: > Author: adkorte-guest > Date: Sun Nov 16 13:00:30 2008 > New Revision: 1560 > > Log: > Generated by libtool and should not be versioned. > > Modified: > trunk/ (props changed) Right, that didn't work out quite the way I intended. Can someone please set the svn:ignore property on

Citeren Arjen de Korte <adkorte-guest op alioth.debian.org>: > Log: > Use the 'nss_compat_ossl' compatibility layer to use the Mozilla NSS > library instead of OpenSSL (we might want to include native support > in the future, but this will at least allow a quick migration for > testing purposes) I don't recall that we ever discussed the possibility of

On Thu, Aug 13, 2020 at 21:16:42 +0200, Arjen de Korte wrote: > Citeren Timo Sirainen <timo at sirainen.com>: > > !include_try ssl-keys.conf > > That will only work to include an optional configuration file and > suppress errors if it doesn't exist. I put > > ssl_key = </etc/ssl/private/de-korte.org.key > > in a separate configuration file and it

Citeren Arnaud Quette <aquette op alioth.debian.org>: > Author: aquette > Date: Sat Dec 11 12:31:21 2010 > New Revision: 2731 > URL: http://trac.networkupstools.org/projects/nut/changeset/2731 > > Log: > Complete the list of Subversion ignored files, with AsciiDoc > generated contents (no functional changes) Is there a particular reason for having both the man/

FYI (mostly Charles and Arjen), a2x version has just been bumped to 8.6.3 in their trunk. So we will be able revert r2686 cheers, Arno 2010/11/12 Stuart Rackham > > > On 12/11/10 10:45, Arnaud Quette wrote: > >> Hi Stuart, >> >> 2010/11/10 Stuart Rackham >> >> The planned 28-Oct release date has slipped by, in the mean time I >> think all

Hi, I've been trying to get my new Tripplite OmniVS100 UPS (USB Connection) to work on my system. What I have is: Ubuntu 10.04 Server Nut 2.4.3 /etc/nut/ups.conf [omni] Driver = usbhid-ups Port = auto Desc = "My Server" /etc/nut/nut.conf MODE=standalone I followed the instructions at this link:

I would like to report a working device to add to the hardware compatibility list, but cannot find a way on the website. Would this list be OK for that purpose? Best regards, Ernest

Citeren clepple+buildbot op ghz.cc: > The Buildbot has detected a new failure of FreeBSD-i686. > Full details are available at: > http://buildbot.ghz.cc/public/nut/FreeBSD-i686/builds/35 Charles, It seems that m4/nut_check_libhal.m4 fails to detect the proper path where to install the .fdi files. I have no idea where these files live on FreeBSD, so could you please find out what

Dear Sirs, First of all I would like to thank you for support PCM product in your project. Kindly please be informed that POWERCOM launch new USB-controller with productID 0X04. Updated USB-controller compatible with previous version which supported by your usbhid-ups driver. There is added some command and changed idProduct. Vendor ID stay the same 0X0d9f without changes. Detailed information

On 13. Aug 2020, at 11.29, Timo Sirainen <timo at sirainen.com> wrote: > > On 13. Aug 2020, at 11.00, Arjen de Korte <build+dovecot at de-korte.org> wrote: >> >> I allow users to run 'doveadm' for mailbox maintenance (to expunge mail for instance). Since the upgrade to 2.3.11.3, this no longer works and results in the following error message: >>

Citeren Arjen de Korte <adkorte-guest at alioth.debian.org>: > Author: adkorte-guest > Date: Thu Jan 15 11:54:05 2009 > New Revision: 1728 > > Log: > Another stab at this. > > Modified: > trunk/tools/Makefile.am And failing miserably... :-( Can someone more fluent in 'autotoolish' fix this problem? Currently the BuildBot is broken by update r1718

Citeren Alexander Gordeev <lasaine op lvk.cs.msu.su>: > I've received the units. Are there any special things I should test or > just the standard NUT setup? They should be detected out of the box (with the latest version from the trunk) through the 'usbhid-ups' driver. Note that I just added some additional commands to enable|disable|mute the beeper of the UPS.

Citeren Arnaud Quette <aquette op alioth.debian.org>: > Log: > Optionaly enable silent build rules, using AM_SILENT_RULES, only if > it's supported (requires automake 1.11) Why do we need a new branch for this? As far as I can see, only the below lines are really needed > +dnl Currently, we only (force) enable silent rules if available > +dnl Verbose mode can be

Charles, Do you have any idea why the buildbots don't update drivers/Makefile.am? The ones they are using seem to be different from the version from the trunk. Best regards, Arjen -- Please keep list traffic on the list

Hi, I tried in vain to find an answer for my question, so let's post it here. I've got a seemingly perfectly well running setup with NUT and a APC SmartUPS 750. However, my log is being filled with messages like this: Oct 13 12:13:08 alkmene kernel: usb 3-1: usbfs: process 16588 (usbhid-ups) did not claim interface 0 before use Oct 13 12:13:40 alkmene last message repeated 43 times