[Nut-upsdev] [nut-commits] buildbot failure in Network UPS Tools on Ubuntu-maverick-x86 [nutscan-snmp.h]

[Arnaud Quette]

2011/7/14 Charles Lepple <clepple at gmail.com>

> On Wed, Jul 13, 2011 at 3:18 PM, Arnaud Quette <aquette.dev at gmail.com>
> wrote:
> >
> >
> > 2011/7/8 Charles Lepple <clepple at gmail.com>
> >>
> >> On Jul 7, 2011, at 5:05 AM, Arnaud Quette wrote:
> >>
> >> 2011/7/7 Charles Lepple <clepple at gmail.com>
> >>>
> >>> On Jul 4, 2011, at 10:58 AM, Charles Lepple wrote:
> >>>
> >>>>> The Buildbot has detected a new failure of Ubuntu-maverick-x86 on
> >>>>> Network UPS Tools.
> >>>>> Full details are available at:
> >>>>>
> >>>>>
> http://buildbot.networkupstools.org/public/nut/builders/Ubuntu-maverick-x86/builds/39
> >>>>
> >>>> Looks like the nutscan-snmp.h file has not been checked into the
> branch:
> >>>>
> >>>> make[3]: Entering directory
> >>>>
> `/var/lib/buildbot/buildbot-slave-cayenne/Ubuntu-maverick-x86/build/tools/nut-scanner'
> >>>> make[3]: *** No rule to make target `nutscan-snmp.h', needed by
> >>>> `distdir'.  Stop.
> >>>
> >>> Looks like a similar problem in r3126:
> >>>
> >>> make[4]: Entering directory
> >>>
> `/var/lib/buildbot/buildbot-slave-cayenne/Ubuntu-maverick-x86/build/tools'
> >>> Regenerating the SNMP helper files.
> >>> /bin/bash: line 2:
> >>> ../../nut-2.6.0-r3126/tools/nut-scanner/nut-snmpinfo.py: No such file
> or
> >>> directory
> >>
> >> right, I still have not been able to find something that suits the
> compile
> >> time (nut-scanner) needs while still satisfying the "dist" rules...
> >> the issue above is due to tools/nut-scanner requiring
> >> nutscan-{usb,snmp}.h, called from the same directory, but with a
> >> "top_srcdir" having an extraneous "..", so not suitable for
> >> tools/Makefile.am execution.
> >>
> >> I'm still investigating for a solution. If someone has an idea...
> >>
> >> So how does this get compiled in a non-dist situation?
> >
> > should be good now, with r3134.
>
> Looking good:
>
>
> http://buildbot.networkupstools.org/public/nut/builders/Ubuntu-maverick-x86/builds/48
>

indeed.
I've abandoned optimization for now, and focused on making it work.
so there are duplicated rules, just to be able to address the previous
issues.

I've not yet looked much at the code, but there are at least few bugs that
need fixing.
I've tested it, and it currently takes under 5 seconds to scan local USB,
SNMP, XML/HTTP and NUT (non avahi method) and identify an hundred devices.
Not that bad ;)
I'll now be able to look into nut-config (command line) and also gluing this
with Python + Augeas + NUT-Monitor

cheers,
Arnaud
-- 
Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/
--
Conseiller Municipal - Saint Bernard du Touvet
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20110714/3bda0f95/attachment.html>