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? 2) If not and I use the 2.7.4 tar found at http://networkupstools.org/download.html, do i just run the classical process? i.e. ./configure make sudo make install ./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? Thanks again for the assistance. On 1 August 2017 at 20:43, Charles Lepple <clepple at gmail.com> wrote:> On Aug 1, 2017, at 7:56 AM, Song Teck Ng <st.ng at leading-edge- > automation.com> wrote: > > > > Hi Charles, > > > > Thanks for your reply. So the Jessie or stretch versions will work then > since those are 2.7.2 and 2.7.4... > > > > I will have to update my sources.list and follow this? > > > > https://backports.debian.org/Instructions/ > > That was the thought, but I mistakenly thought that there was a NUT > package in wheezy-backports. https://packages.debian.org/ > search?suite=wheezy-backports&keywords=nut-server does not list anything. > (Debian only does backports by request, and that could take a while - > especially for something in oldoldstable.) > > Agreed that upgrading to jessie or stretch would work. > > If you can install build-essential and the NUT build-deps, you could build > a newer version from source. > > here is some info on that process: 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-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170802/51c86f67/attachment.html>
On Aug 1, 2017, at 12:01 PM, Song Teck <songteck at 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, do i just run the classical process? i.e. > > ./configure > make > sudo make installYou 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 > > 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 >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).
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 <clepple at gmail.com> wrote:> On Aug 1, 2017, at 12:01 PM, Song Teck <songteck at 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, 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 > > > > 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 > > > 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).-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170803/79d600b9/attachment.html>