similar to: Problems checking out SVN repository

Displaying 20 results from an estimated 20000 matches similar to: "Problems checking out SVN repository"

2008 Jun 28
1
[nut-commits] svn commit r1502 - in trunk: . drivers man
Hi, When running a driver with "-h" or without parameters, the upsdrv_cleanup function seems to be called (which caused the warning I mention in the ChangeLog). This doesn't seem right. Regards, On Sat, Jun 28, 2008 at 7:47 PM, Carlos Rodrigues <carlosefr-guest at alioth.debian.org> wrote: > Author: carlosefr-guest > Date: Sat Jun 28 18:47:17 2008 > New Revision:
2006 Jun 06
1
Re: [nut-commits] svn commit r430 - in branches/Testing: . docs drivers man
On 6/6/06, Carlos Rodrigues wrote: > Author: carlosefr-guest > Date: Tue Jun 6 21:16:30 2006 > New Revision: 430 > > Added: > branches/Testing/docs/megatec.txt > branches/Testing/drivers/megatec.c > branches/Testing/drivers/megatec.h > branches/Testing/man/megatec.8 Just a note on adding drivers to the Testing branch: if you use 'svn copy' instead
2007 Dec 29
1
[nut-commits] svn commit r1204 - in trunk: . drivers
Carlos Rodrigues wrote: > Author: carlosefr-guest > Date: Sat Dec 29 20:17:01 2007 > New Revision: 1204 > > Log: > - drivers/megatec.c: detect OB status while OFF. You've changed a bit more than this line suggests. [...] > @@ -565,10 +575,16 @@ > dstate_setinfo("input.voltage.fault", "%.1f", query.fvolt); >
2007 Jun 21
2
[nut-commits] svn commit r971 - in trunk: . drivers
> Author: aquette > Date: Thu Jun 21 07:43:46 2007 > New Revision: 971 > > Log: > fix communication lost status handling > > Modified: > trunk/ChangeLog > trunk/drivers/usbhid-ups.c > > Modified: trunk/ChangeLog > ============================================================================== > --- trunk/ChangeLog (original) > +++ trunk/ChangeLog
2007 Aug 13
2
[nut-commits] svn commit r1049 - in trunk: . drivers
Alexander Gordeev wrote: > Author: agordeev-guest > Date: Mon Aug 13 13:09:43 2007 > New Revision: 1049 > > Log: > drivers/megatec_usb.c: added credits to the banner message. Is this really needed/desirable? I think this kind of information needs to be put in the AUTHORS document. There are many more people on this list that put a lot of effort in NUT, without claiming credit
2007 Jun 18
2
Fwd: Megatec - modem control lines [impact to megatec_usb]
Hi, Sorry for the forwarding. I sent this with the wrong "from" address and got rejected by the list. ---------- Forwarded message ---------- From: Carlos Rodrigues <cefrodrigues at mail.telepac.pt> Date: Jun 18, 2007 9:34 PM Subject: Re: Megatec - modem control lines [impact to megatec_usb] To: Arjen de Korte <nut+devel at de-korte.org> Cc: ups-dev-list <nut-upsdev at
2005 Oct 10
1
Re: About blazer, powermust and mustek
Arnaud Quette wrote: > Anyhow, I would more see this as a merge of all these drivers, with > some autodetection or flag/param to switch the mfr/model and maybe > capabilities... Whatever the driver name is, a good thing would be the > name of the protocol or something generic enough, though powermust is > fine. Ok, I made some minor changes to powermust, to make it less
2008 Feb 03
2
broken build with default configure flags
Hi, Currently, "configure.in" in both testing and the trunk have libupsclient disabled by default, which means the build is broken if the user doesn't explicitly enable it when running configure. Why was it like this and can I commit the fix? -- Carlos Rodrigues
2006 Dec 04
4
megatec and some changes to cmdvartab and new-names.txt
I had some free time this weekend, and made some long overdue changes to "megatec". The thing is, these changes lead to a couple of questions that I must ask before I go on and "svn commit" them: 1) The blazer, fentonups, esupssmart, ippon, sms and mustek drivers are now completely covered and all of their functionality should now be present in megatec, and also every model
2007 Sep 12
2
PowerWalker and megatec_usb
Hi! I've (finally) decided to try and make my PowerWalker work with megatec_usb. So far it seems the agiler subdriver is the way to go, but it doesn't work. The initial detection process sometimes succeeds in 1 out of 5 "Q1" commands, but that's about it (which is better than what the krauler subdriver can do... absolutely nothing). So, what needs to be done to obtain more
2007 Jan 06
1
Re: [nut-commits] svn commit r710 - in trunk: . clients server
Great, thanks Arjen! Now we need an autoconf test to set HAVE_IPV6 automatically. I will look into what functionality needs to be tested; the test can be refined as problems arise later. -- Peter Arjen de Korte wrote: > > Author: adkorte-guest > Date: Sat Jan 6 19:39:08 2007 > New Revision: 710 > > Modified: > trunk/ChangeLog > trunk/clients/upsc.c >
2007 May 26
3
[nut-commits] svn commit r924 - in trunk: . data
Does this require a new entry in scripts/hotplug/* and scripts/udev/*? -- Peter Alexander Gordeev wrote: > > Author: agordeev-guest > Date: Sat May 26 12:04:26 2007 > New Revision: 924 > > Log: > data/driver.list: added SVEN Power Smart RM 2000 to the list. > > Modified: > trunk/ChangeLog > trunk/data/driver.list > > Modified: trunk/ChangeLog >
2007 Feb 12
4
Fwd: NUT on FreeBSD
I'm forwarding this to the list, as I'm not quite sure what's going on here. Never seen this on Linux, don't know if it is a FreeBSD thing or not. ---------- Forwarded message ---------- From: Herman J van der Merwe <herman@mercygate.com> Date: Feb 11, 2007 9:50 PM Subject: NUT on FreeBSD To: carlos.efr@mail.telepac.pt Hello Carlos Maybe you can assist me with NUT 2.0.5
2010 Jan 23
1
[nut-commits] svn commit r2260 - trunk/drivers
Citeren Arjen de Korte <adkorte-guest op alioth.debian.org>: > Author: adkorte-guest > Date: Sat Jan 23 10:06:51 2010 > New Revision: 2260 > > Log: > Need to define _XOPEN_SOURCE for strptime() prototype in glibc2 > > Modified: > ? ? trunk/drivers/mge-hid.c Arnaud, Apparently this solves the problem for the strptime() function, but now breaks the snprintf()
2007 Nov 26
1
[nut-commits] svn commit r1164 - in trunk: . drivers
On Nov 26, 2007 6:38 PM, Arjen de Korte <adkorte-guest at alioth.debian.org> wrote: > Author: adkorte-guest > Date: Mon Nov 26 18:38:18 2007 > New Revision: 1164 > > Log: > Allow longer commands in the 'phoenix' subdriver. > > Modified: > trunk/ChangeLog > trunk/drivers/megatec_usb.c FYI, the shutdown still doesn't work. -- Carlos Rodrigues
2007 Jul 06
3
energizerups and bestups -> megatec?
Hi! I don't know how I missed it before, but "bestups" seems to implement mostly the same protocol as megatec. Is anybody out there using this driver willing to try "megatec" to see if it works? AFAIK, the only difference seems to be the command that gets the UPS identification data ("I" on "megatec", "ID" on "bestups"), but
2007 Jul 06
3
energizerups and bestups -> megatec?
Hi! I don't know how I missed it before, but "bestups" seems to implement mostly the same protocol as megatec. Is anybody out there using this driver willing to try "megatec" to see if it works? AFAIK, the only difference seems to be the command that gets the UPS identification data ("I" on "megatec", "ID" on "bestups"), but
2007 Jun 10
3
can't make mustek powermust 600usb work
Disclaimer: I've setup APC UPS monitoring and it works... ... but when it comes to mustek powermust 600usb (connected via com-port), I can't make it work. Got NUT installed via aptitude in ubuntu feisty and a basic setup, exactly the same as for the apc, except for the name of the ups and the corresponding section of ups.conf -- [mustek] driver = megatec port = /dev/ttyS1
2007 Jul 04
0
[LLVMdev] SVN Repository Layout.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Reid Spencer schreef: > All, > > There's been much email traffic and discussion about the repository > layout, top level stuff, etc. Additionally, Tanya, Chris, Gordon and I > had an IRC discussion last evening and worked through some of the issues > and confusion. As a result, I've prepared a web page that contains the >
2007 Nov 25
1
[nut-commits] svn commit r1156 - in trunk: . drivers
On Nov 25, 2007 11:50 AM, Arjen de Korte <adkorte-guest at alioth.debian.org> wrote: > Limit detection of UPS to minimum required number of successful attempts. Flush input- and output buffers before sending any command. Can you explain the reasoning behind these changes please? The detection phase didn't stop after the minimum number of required replies to check for models that