similar to: [nut-commits] svn commit r1358 - in branches/Testing: . clients drivers m4 man scripts/hal server

2010/12/22 Arjen de Korte <adkorte-guest at alioth.debian.org> > Author: adkorte-guest > Date: Wed Dec 22 20:31:42 2010 > New Revision: 2777 > URL: http://trac.networkupstools.org/projects/nut/changeset/2777 > > Log: > Don't version generated files > > Deleted: > trunk/scripts/hal/ups-nut-device.fdi.in > trunk/scripts/hotplug/libhid.usermap >

Citeren Arjen de Korte <adkorte-guest at alioth.debian.org>: > Author: adkorte-guest > Date: Thu Jan 15 20:02:22 2009 > New Revision: 1734 > > Log: > Freshly generated USB helper files > > Modified: > trunk/scripts/hal/ups-nut-device.fdi.in > trunk/scripts/hotplug/libhid.usermap > trunk/scripts/udev/nut-usbups.rules.in Questions is, should we try

Citeren Arjen de Korte <adkorte-guest op alioth.debian.org>: > Author: adkorte-guest > Date: Wed Nov 11 10:44:46 2009 > New Revision: 2102 > > Log: > Properties changed > > Modified: [...] > trunk/drivers/netxml-ups.c Oops, this accidentally slipped in as well. This update changed the behavior of the netxml-ups driver to allow a NSM-client only mode. In

On Feb 1, 2008 6:11 PM, Arnaud Quette <aquette at alioth.debian.org> wrote: > Author: aquette > Date: Fri Feb 1 23:11:33 2008 > New Revision: 1264 > > Log: > fix HAL support installation [Alioth Bug #304156] Arnaud, I tried to fix some of the errors that I was seeing in buildbot, but I still get the following error on "make distcheck", and I don't know how

Hi Arjen, there is a small glitch with r1376: upsd.c: In function ?mainloop": upsd.c:857: warning: too few argument for the format 2008/3/18, Arjen de Korte <adkorte-guest at alioth.debian.org>: > Author: adkorte-guest > Date: Tue Mar 18 19:59:15 2008 > New Revision: 1376 > ... > + if (ret == 0) { > + upsdebugx(2, "%s: no data

2010/11/4 Arjen de Korte > Author: adkorte-guest > Date: Thu Nov 4 20:00:25 2010 > New Revision: 2668 > URL: http://trac.networkupstools.org/projects/nut/changeset/2668 > > Log: > Checking whether or not we should use the 'regex' library should be done > for all USB connected devices (since we use this in the matcher function). > In that case it is much cleaner

On Nov 4, 2010, at 6:21 PM, Arjen de Korte wrote: > Author: adkorte-guest > Date: Thu Nov 4 22:21:51 2010 > New Revision: 2669 > URL: http://trac.networkupstools.org/projects/nut/changeset/2669 > > Log: > Add checking minimum required version for AsciiDoc tools I noticed that somewhere around this commit, the documentation stopped being built by default in BuildBot.

2010/11/4 Arjen de Korte > Author: adkorte-guest > Date: Thu Nov 4 22:40:51 2010 > New Revision: 2671 > URL: http://trac.networkupstools.org/projects/nut/changeset/2671 > > Log: > Exclude -I. and extra developer warning flags with Net-SNMP support enabled > (using them is the responsibility of the NUT developers) > > Modified: >

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 8/10/07, Arjen de Korte <adkorte-guest at alioth.debian.org> wrote: > Author: adkorte-guest > Date: Fri Aug 10 19:16:48 2007 > New Revision: 1040 > > Log: > From the ChangeLog: [...] > - Use snprintf instead of sprintf where possible. In general, this is a good idea, but what if the resulting string is exactly sizeof(buf) ? Shouldn't it be sizeof()-1 with a

On Mon, Jul 20, 2009 at 3:33 PM, Arjen de Korte<adkorte-guest at alioth.debian.org> wrote: > Author: adkorte-guest > Date: Mon Jul 20 19:33:33 2009 > New Revision: 1866 > > Log: > Resolve naming conflict Arjen, should drivers/Makefile.am be changed from: virtual_SOURCES = virtual.c to: clone_SOURCES = clone.c as well? -- - Charles Lepple

Hi Arjen 2007/7/28, Arjen de Korte <adkorte-guest at alioth.debian.org>: > Author: adkorte-guest > Date: Sat Jul 28 16:45:04 2007 > New Revision: 1029 > > Log: > Add Belkin F6C1200-UNV (older model) to supported devices. > > Apparently this is (internally) identical to the F6C1100-UNV. Not surprisingly, they also share the same productid (1100). It also seems to come

On Dec 31, 2009, at 8:45 AM, Arjen de Korte wrote: > Author: adkorte-guest > Date: Thu Dec 31 13:45:16 2009 > New Revision: 2218 > > Log: > Add pkg-config as method to retrieve CFLAGS and LDFLAGS (but fall > back to libusb-config) > > Modified: > trunk/m4/nut_check_libusb.m4 Arjen, I'm not sure you want parentheses in the shell script fragments. Search for

On Thu, Dec 4, 2008 at 4:51 PM, Arjen de Korte <adkorte-guest at alioth.debian.org> wrote: > Author: adkorte-guest > Date: Thu Dec 4 21:51:28 2008 > New Revision: 1596 > > Log: > Added new richcomm_usb driver based on the lakeview_usb driver (using libusb). Sorry if I wasn't clear - I was advocating *renaming* the lakeview_usb driver to richcomm_usb. Is there another

Charles, It looks like the buildbot no longer builds (if it ever did, I don remember) the HAL addons, even if the requirements are met: configure:9680: checking for libhal version via pkg-config (0.5.8 minimum required) configure:9690: result: 0.5.11 found configure:9694: checking for libhal cflags via pkg-config configure:9703: result: -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/hal

I've tried several recipes found with google, but hal likes to grab the USB ups before nut can get it. There are a number of klugey workarounds, like turn off port power until ready to start nut (so that hal doesn't see the UPS). Or killall hal-addon-hid-ups before starting nut. Here is one of recipes I googled: https://github.com/sdgathman/trippfix/blob/master/halpolicy.fdi It

Hi, is there anybody understanding HAL? I use CentOS 4 (RHEL 4) I need set specific mount options for USB flash disk. I found I can do it in /usr/share/hal/fdi/95userpolicy/storage-policy.fdi <?xml version="1.0" encoding="ISO-8859-1"?><!-- -*- SGML -*- --> <deviceinfo version="0.2"> <device> <match key="volume.fstype"

I bought a new CyberPower CP850AVRLCD ups, connected it to a usb port and I'm trying to use it with hal. I installed [root at phoenix ~]# rpm -q nut nut-client nut-2.2.0-6.1.fc8 nut-client-2.2.0-6.1.fc8 lsusb sees it: [root at phoenix docs]# lsusb Bus 001 Device 001: ID 0000:0000 Bus 005 Device 002: ID 0c45:1050 Microdia Bus 005 Device 001: ID 0000:0000 Bus 004 Device 001: ID 0000:0000

Hey Charles, adding Arjen to the list and upsdev for info... 2008/12/17 Charles Lepple <clepple at gmail.com>: > I noticed Arjen deleted the packaging/debian directory as well. > > I suppose the same argument applies to packaging/debian/ as to the *.spec > files: it should track the specific distribution as well as NUT changes. > > However, it might make sense to keep

Arjen, Wow, that was quick... Thanks! (It was taking me a while to sort out all of the different CFLAGS settings; hence, the tracker item.) I would take issue with the following assertion in Makefile.am: "In any case, CFLAGS are only -I options, so there is no harm." since this is what got us into trouble in the first place... but I guess that was there before you edited it as