<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
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 . . . <br>
<br>
- TIm<br>
<br>
<div class="moz-cite-prefix">On 08/02/2017 11:09 AM, Song Teck
wrote:<br>
</div>
<blockquote
cite="mid:CAKyAZD5rZFZ=8nsmiD4FR8QV8EehK55M=gdJ0e1a=Mk1Dau2Hw@mail.gmail.com"
type="cite">
<div dir="ltr">Hi Charles,
<div><br>
</div>
<div>thanks for the clarification on the libusb. that indeed
does work to get the value in ./configure. </div>
<div><br>
</div>
<div>I've tried installing a .deb </div>
<div><br>
</div>
<div>sudo dpkg -i nut_2.7.4-5_all.deb</div>
<div>(Reading database ... 103447 files and directories
currently installed.)</div>
<div>Preparing to replace nut 2.6.4-2.3+deb7u1 (using
nut_2.7.4-5_all.deb) ...</div>
<div>Unpacking replacement nut ...</div>
<div>Setting up nut (2.7.4-5) ...</div>
<div><br>
</div>
<div>which doesn't return an error but starting upsdrvctl after
still shows v2.6.4 so that didn't work.</div>
<div><br>
</div>
<div>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...</div>
<div><br>
</div>
<div>Thanks again for your patience</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 2 August 2017 at 10:02, Charles
Lepple <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:clepple@gmail.com" target="_blank">clepple@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span
class="">On Aug 1, 2017, at 12:01 PM, Song Teck <<a
moz-do-not-send="true" href="mailto:songteck@gmail.com"><a class="moz-txt-link-abbreviated" href="mailto:songteck@gmail.com">songteck@gmail.com</a></a>>
wrote:<br>
><br>
> Hi Charles,<br>
><br>
> Ok, I missed the absence from the backports as well.
Again, some unfamiliarity here, so<br>
><br>
> 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?<br>
<br>
</span>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).<br>
<span class=""><br>
> 2) If not and I use the 2.7.4 tar found at <a
moz-do-not-send="true"
href="http://networkupstools.org/download.html"
rel="noreferrer" target="_blank"><a class="moz-txt-link-freetext" href="http://networkupstools.org/">http://networkupstools.org/</a><wbr>download.html</a>,
do i just run the classical process? i.e.<br>
><br>
> ./configure<br>
> make<br>
> sudo make install<br>
<br>
</span>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.<br>
<span class=""><br>
><br>
> ./configure has a no under "install USB drivers" and
when I add that handle (--with-usb) in, it prompts for
libusb.<br>
><br>
> 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?<br>
><br>
<br>
</span>The OpenUPS2 is connected via USB, so you'll need the
libusb dependencies.<br>
<span class=""><br>
> here is some info on that process: <a
moz-do-not-send="true"
href="http://lists.alioth.debian.org/pipermail/nut-upsuser/2016-October/010389.html"
rel="noreferrer" target="_blank"><a class="moz-txt-link-freetext" href="http://lists.alioth.debian">http://lists.alioth.debian</a>.<wbr>org/pipermail/nut-upsuser/<wbr>2016-October/010389.html</a><br>
><br>
> 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: <a moz-do-not-send="true"
href="http://networkupstools.org/download.html#_stable_tree_2_7"
rel="noreferrer" target="_blank">http://networkupstools.org/<wbr>download.html#_stable_tree_2_7</a><br>
><br>
</span>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).</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Nut-upsuser mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Nut-upsuser@lists.alioth.debian.org">Nut-upsuser@lists.alioth.debian.org</a>
<a class="moz-txt-link-freetext" href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser</a></pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Tim Dawson
972-567-9360
</pre>
</body>
</html>