This is probably just pathing issues . . . the .deb likely put the 2.7.4
distro in a different place, and if you can find it and run the newly
installed "upsdrvctl" instead of the old one, it may well work. That,
or deinstall the old version first, then install 2.7.4 cleanly . . .
- TIm
On 08/02/2017 11:09 AM, Song Teck wrote:
Hi Charles,
thanks for the clarification on the libusb. that indeed does work to
get the value in ./configure.
I've tried installing a .deb
sudo dpkg -i nut_2.7.4-5_all.deb
(Reading database ... 103447 files and directories currently installed.)
Preparing to replace nut 2.6.4-2.3+deb7u1 (using nut_2.7.4-5_all.deb) ...
Unpacking replacement nut ...
Setting up nut (2.7.4-5) ...
which doesn't return an error but starting upsdrvctl after still shows
v2.6.4 so that didn't work.
Does ./configure, make, sudo make install have to be carried out in a
particular directory? I've run it from a /usr/local both with and
without the user/group/usb switches and again it seems to run fine but
when the upsdrvctl is called, it still remains as 2.6.4 so evidently
I'm missing something here...
Thanks again for your patience
On 2 August 2017 at 10:02, Charles Lepple <clep...@gmail.com
<mailto:clep...@gmail.com>> wrote:
On Aug 1, 2017, at 12:01 PM, Song Teck <songt...@gmail.com
<mailto:songt...@gmail.com>> wrote:
>
> Hi Charles,
>
> Ok, I missed the absence from the backports as well. Again, some
unfamiliarity here, so
>
> 1) I presume I cannot use a metapackage meant for jessie or
stretch on wheezy? Or if I can, is there a way to deploy it from
console?
The "nut" metapackage just depends on "nut-client" and
"nut-server". The drivers are in the server package - you'd need
to find a way to install a newer nut-server package, and I don't
know if I would want to try and mix .deb versions like that (if it
is even possible).
> 2) If not and I use the 2.7.4 tar found at
http://networkupstools.org/download.html
<http://networkupstools.org/download.html>, do i just run the
classical process? i.e.
>
> ./configure
> make
> sudo make install
You could, but the paths would be slightly different from the .deb
version, and it won't necessarily integrate with the system
shutdown. However, the driver-to-upsd interface hasn't changed
between 2.6.5 and 2.7.4, as long as you use the same paths for
./configure that the 2.6.5 Debian package used.
>
> ./configure has a no under "install USB drivers" and when I add
that handle (--with-usb) in, it prompts for libusb.
>
> Does that mean I actually have to do the process referenced in
your link? Or is it fine to go ahead with that as USB drivers as a no?
>
The OpenUPS2 is connected via USB, so you'll need the libusb
dependencies.
> here is some info on that process:
http://lists.alioth.debian.org/pipermail/nut-upsuser/2016-October/010389.html
<http://lists.alioth.debian.org/pipermail/nut-upsuser/2016-October/010389.html>
>
> In your case, you probably don't need the libusb-1.0 branch
snapshot, so you could just use a NUT tarball from the downloads
page: http://networkupstools.org/download.html#_stable_tree_2_7
<http://networkupstools.org/download.html#_stable_tree_2_7>
>
To clarify: that thread was talking about a snapshot of a NUT
branch that uses libusb-1.0, versus the original libusb-0.1
support. If you set things up to do "apt-get build-dep nut", it
will pull in the libusb-dev package (which would cause the
./configure output to say yes for building USB drivers).
_______________________________________________
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
--
Tim Dawson
972-567-9360
_______________________________________________
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
