similar to: RPM .spec files in NUT source tree

I am trying to build an rpm for nut-2.2.2 on 64 bit opensuse 11.0. 0. Packages previously built for opensuse 10.x have to be rebuilt since opensuse 11.0 now compresses package payloads using lzma, which according to the opensuse 11.0 release notes makes 10.x rpms unusable. 1. I downloaded nut-2.2.2.tar.gz 2. I recompressed as a bz2 as expected by rpmbuild 3. I extracted and copied

Network UPS Tools version 2.2.2-pre2 has been released. http://www.networkupstools.org/ Direct access: - Download: http://www.networkupstools.org/source/2.2/testing/nut-2.2.2-pre2.tar.gz - News: http://www.networkupstools.org/source/2.2/testing/new-2.2.2-pre2.txt - ChangeLog: http://www.networkupstools.org/source/2.2/testing/ChangeLog Arnaud and the NUT team -- Linux / Unix Expert R&D -

Arjen, all I don't know if there is some prohibition against it, but the packages.html link for SuSE RPMs should be changed from: http://software.opensuse.org/ To something useful that will get the site visitors to the actual rpms. For the packages that were part of the distribution: http://download.opensuse.org/distribution/ or for updated packages on build service:

Citeren Arjen de Korte <adkorte-guest op alioth.debian.org>: > Log: > Use the 'nss_compat_ossl' compatibility layer to use the Mozilla NSS > library instead of OpenSSL (we might want to include native support > in the future, but this will at least allow a quick migration for > testing purposes) I don't recall that we ever discussed the possibility of

Stan, I'm very pleased to see you back to work with us on enhancing nut in that many areas ;-) 2008/4/30 Stanislav Brabec <sbrabec at suse.cz>: > Stanislav Brabec wrote: > > > Please note that 2.2.2-pre3 installs hald addons by default to / on > > openSUSE 11.0 beta 2 x86_64. Not a big problem. > > Here is a patch, which fixes openSUSE 11.0 beta 2 x86_64:

FYI (mostly Charles and Arjen), a2x version has just been bumped to 8.6.3 in their trunk. So we will be able revert r2686 cheers, Arno 2010/11/12 Stuart Rackham > > > On 12/11/10 10:45, Arnaud Quette wrote: > >> Hi Stuart, >> >> 2010/11/10 Stuart Rackham >> >> The planned 28-Oct release date has slipped by, in the mean time I >> think all

I guess this means we won't have access to SVN, right? Is there a timeline available when this will be fixed? Sadly enough, my keys were generated on an openSUSE system and are probably not affected by this vulnerability anyway. Best regards, Arjen -- Eindhoven - The Netherlands Key fingerprint - 66 4E 03 2C 9D B5 CB 9B 7A FE 7E C1 EE 88 BC 57 -------------- next part -------------- An

On opensuse 10.3, i installed nut and configured my ups.conf like i did it on opensuse 10.2 by putting (10.3 , nut 2.2.0): [MGEpc675] driver = usbhid-ups port = auto desc = "MGEpc675" instead of (10.2 , nut 2.0.4) : [MGEpc675] driver = newhidups port = auto desc = "MGEpc675" But it doesn't work. It appears that upsdrvctl

Hi Dag 2010/2/28 Dag Atle Nettum <dagatle at innit.no> > Hello > > > > I understand you are the project leader of Nut. > > > > In my company we have a Eaton 9135 6000 UPS, we are running NUT 2.4.1 > (Debian squeeze) > > > > The ups is connected with a USB cable but it reports a temperature of 300 > degredes. > > > > Can I send you

I found the following comment in the ChangeLog for the openSUSE nut package: > * Mon Apr 14 14:00:00 2008 schwab at suse.de > > - Work around misuse of libtool. Find attached the diff's that are applied. Is there any merit in this and/or should we be port this back into the trunk/Testing? Best regards, Arjen -------------- next part -------------- A non-text attachment was

Dear List, The driver usbhid-ups does not detect my MGE Ellipse 1500. I'm running openSuSE Linux 10.3, kernel 2.6.22 with mgeups-psp-3.0.4-2, nut-2.2.0-20 installed from MGE's rpm's. (Merci MGE!) lsusb shows: Bus 001 Device 004: ID 0463:ffff MGE UPS Systems UPS /etc/ups/ups.conf says: [myups] driver = usbhid-ups port = auto desc = "Local UPS"

Until the release of nut-2.0.5 it was possible to have a working configuration without configuring anything in 'ups.conf'. Since then, this no longer works, as the server will only look for driver sockets for UPSes that have been configured in 'ups.conf' (since the socket is named after the UPSname). Drivers will use the old naming scheme '<driver>-<port>' if

I just committed the --with-group option for configure. One thing is not quite what I like, but I have no idea how to script this in autoconf. Currently both RUN_AS_USER and RUN_AS_GROUP have the defaults "nobody" and "nogroup" respectively. I think this really should be changed to the following: - if neither --with-user, nor --with-group are specified, we apply the defaults

Charles, When running autoreconf in the trunk, I get a couple of additional files since I upgraded to openSUSE 11.1. Most likely, this is due to a newer version of the auto(whatever) tools that are used. Or I never looked at this more closely before. libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'. libtoolize: copying file `m4/libtool.m4' libtoolize: copying file

Dear List, I'm running NUT 2.4.1 on openSUSE 11.3 64 bits, kernel 2.6.34. The UPS is an Eaton Ellipse ASR 1500 USBS. With driver usbhid-ups NUT works perfectly _until_ I turn off IPv6. By default IPv6 is turned on in openSUSE 11.3. I visited YaST -> Network Settings -> Global options and deselected "Enable IPv6". I then restarted the box. When I entered the command

Hi, I tried in vain to find an answer for my question, so let's post it here. I've got a seemingly perfectly well running setup with NUT and a APC SmartUPS 750. However, my log is being filled with messages like this: Oct 13 12:13:08 alkmene kernel: usb 3-1: usbfs: process 16588 (usbhid-ups) did not claim interface 0 before use Oct 13 12:13:40 alkmene last message repeated 43 times

Alex and the list, Alexey Morozov (Powercom sales manager for Russia) has contacted me to propose demo units and information on the new Powercom protocol. This is preferably for a Russian team member... Anyone up? 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 -

Alex and the list, Alexey Morozov (Powercom sales manager for Russia) has contacted me to propose demo units and information on the new Powercom protocol. This is preferably for a Russian team member... Anyone up? 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 -

Arjen, I just installed openSuSE 11.1. I though it would be simple to setup the same CyberPower CP1000AVRLCD on the same machine that we worked through the 20+ voltage issue with, but usbhis-ups driver is failing for some reason. I have gotten the output I remember you needing from the last issue for you. What do you think the problem might be? Here is the information: First the logs from the

Hallo group, I am running openSUSE 10.3 with nut-2.2.0-20 installed. I have configured it as mentioned in /usr/share/doc/packages/nut/README.SUSE. on starting nut using "rcupsd start" i get following: # Starting NUT UPS monitor done Broadcast Message from root at pane (somewhere) at 22:27 ... Communications with UPS myups at localhost