[Nut-upsuser] Usbhip-ups going wild
Antoine Gatineau
antoine.gatineau at alcatel-lucent.com
Mon Aug 3 17:36:16 UTC 2009
I tried to recompile without xorg-x11-devel and I get this error :
configure: error: libgd not found, required for CGI build.
It is indeed required for nut-cgi
udev-devel, however, is not required.
Anyway I made it build correctly.
I attached nut.spec (modified for RHEL4) and nut.spec.ori (original spec
file for RHEL5) for info.
There were no %files entry for libhidups, libhid.usermap and
20-ups-nut-device.fdi in the original spec file, so I added them. I'm not an
rpm building expert but I wonder how it could work...
I also removed hal, powerman and netxml-ups man page and related files as
they are not used in this package.
I didn't test it running yet but I expect it to be OK. I'll come back to you
with results.
BTW, in the first answer to this (too?) long thread, Arjen said that there
were lot of bug fixes and performance improvement done since nut-2.2.0. Is
there a bug tracker to seek if my issues will be solved with this new one?
Thanks
_____
De : Antoine Gatineau [mailto:antoine.gatineau at alcatel-lucent.com]
Envoyé : lundi 3 août 2009 18:11
À : 'Arnaud Quette'
Cc : 'nut-upsuser'; antoine.gatineau at alcatel-lucent.com
Objet : RE: [Nut-upsuser] Usbhip-ups going wild
Looking at the configure output, I though nut-cgi was using X11 and glib
stuff. I will check.
It looks good other wise. I had to disable hal, powerman and neonxml feature
to get it wotk.
I still got some with installed but unpackaged file that need some
modification in the spec file. I will update soon.
Patrick doesn't work anymore on this project but yes indeed we work in the
same dept. He contributed a bit to nut project some time ago if I remember
well. So I am continuing part of is job now.
Antoine
_____
De : Arnaud Quette [mailto:aquette.dev at gmail.com]
Envoyé : lundi 3 août 2009 16:16
À : Antoine Gatineau
Cc : nut-upsuser
Objet : Re: [Nut-upsuser] Usbhip-ups going wild
just to complete a bit Manuel's answer
2009/8/3 Manuel Wolfshant
Antoine Gatineau wrote:
Ok,
Now I am rebuilding an el4 rpm based on el5 src.rpm.
I will remove the --with-hal option in the configure part. In order a full
featured rpm, I'm trying to keep every option unless hal.
But I am having problems with dependencies. libX11-devel,
xorg-x11-devel
libXpm-devel,
still xorg-x11-devel, if I am not mistaken
dbus-glib-devel
dbus-devel
you can drop this one since it's for the nut-hal package
(note that you might need to remove the nut-hal package definitions
throughout the .spec...)
and powerman-devel
not available, afaik
IIRC, I had to compile it for RHEL-5, and in turn it required some other
packages (a newer curl, for instance)
I suggest to drop its usage
yup, this part is for the powerman (external PDU) support.
just in case you want it: http://sourceforge.net/projects/powerman/files/
btw, are you working with Patrick Agrain?
Arnaud
--
Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/
do not exist in RHEL 4... These are for RHEL5.
Does anyone know the equivalent dependencies for RHEL4?
Another possibility is to disable the option that requires thoses
dependencies. I didn't find a document explaining that so could you help.
By disabling the troublemaker options, I can build a package for my
particuliar configuration. Of course it will not help others...
I put the RHEL5 spec file in attachement also.
Merci,
Antoine
------------------------------------------------------------------------
*De :* Arnaud Quette [mailto:aquette.dev at gmail.com]
*Envoyé :* lundi 3 août 2009 11:09
*À :* Antoine Gatineau
*Cc :* Charles Lepple; nut-upsuser
*Objet :* Re: [Nut-upsuser] Usbhip-ups going wild
salut Antoine
2009/8/3 Antoine Gatineau <antoine.gatineau at alcatel-lucent.com
<mailto:antoine.gatineau at alcatel-lucent.com>>
Thanks for the info.
I use the first approach.
So, if I understood well, the nut-hal support (ie, the --with-hal)
is used only for the 2nd approach. Udev rules are dealt when using
--with-usb.
Is that correct?
mostly! the udev rules are used in both cases...
If so, I might be able to rebuild the nut-2.4.1 pachage for RHEL4.
For packaging help (I think I might need some for the next stage
;-) ) do I continue this thread or use the nut-packaging list (or
both).
no, continue using the present thread.
nut-packaging is not really active, and I've created it originally as a
placeholder for packagers discussions (related to the NUT Packaging Standard
- NPS - topic)
cheers,
Arnaud
--
Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/
------------------------------------------------------------------------
*De :* Arnaud Quette [mailto:aquette.dev at gmail.com
<mailto:aquette.dev at gmail.com>]
*Envoyé :* vendredi 31 juillet 2009 21:41
*À :* Antoine Gatineau
*Cc :* Charles Lepple; nut-upsuser
*Objet :* Re: [Nut-upsuser] Usbhip-ups going wild
salut Antoine,
2009/7/31 Antoine Gatineau <antoine.gatineau at alcatel-lucent.com
<mailto:antoine.gatineau at alcatel-lucent.com>>
I might ask a stupid question but isn't hal used to manage the
UPS device
and connection through udev rules?
I though that hal was mostly usefull with usb...
In the nut-hal document, it is said that HAL "allows NUT
drivers to feed the
HAL system, which will itself feeds
applications such as the Gnome Power Manager"
Does that mean hal is not used for managing the battery itself
but sees the
nut driver as a "pseudo real battery"? In this case, indeed,
I do not need
it.
I use upsmon for power management.
not at all. there are 2 approaches:
- the standard one, where you have a driver (usbhid-ups), upsd and
upsmon.
udev only applies the device privileges rules.
- the Integrated Power Management approach, where NUT USB driver
can feed data to HAL (instead of upsd), replacing the basic
USB/HID support in HAL.
Note that HAL is being superseded by DeviceKit and DeviceKit-power.
This approach will probably be abandonned...
-----Message d'origine-----
De : Charles Lepple [mailto:clepple at gmail.com
<mailto:clepple at gmail.com>]
Envoyé : vendredi 31 juillet 2009 15:08
À : Antoine Gatineau
Cc : 'nut-upsuser'
Objet : Re: [Nut-upsuser] Usbhip-ups going wild
On Jul 31, 2009, at 9:03 AM, Antoine Gatineau wrote:
> Indeed, nut depends on some packages not the distribution
itself.
> You are surely right.
>
> Anyway, here are the links :
> RHEL 4 : ftp://rpmfind.net/linux/EPEL/4ES/SRPMS/
> nut-2.2.0-4.el4.src.rpm
> RHEL 5 : nut-2.4.1 found only on this one
> http://wolfy.fedorapeople.org/nut/SRPM/
use that one.
install it and edit the spec.
modifying --with-all by --with-usb should be sufficient.
cheers,
Arnaud
-- Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops
Network UPS Tools (NUT) Project Leader -
http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/
_______________________________________________
Nut-upsuser mailing list
Nut-upsuser at lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20090803/0eb008e5/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nut.spec.ori
Type: application/octet-stream
Size: 21536 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20090803/0eb008e5/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nut.spec
Type: application/octet-stream
Size: 20881 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20090803/0eb008e5/attachment-0003.obj>
More information about the Nut-upsuser
mailing list