[Nut-upsdev] smart1050slt by tripp lite

[Alexey Loukianov]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

01.02.2010 05:11, chance fulton wrote:
> # svn co svn://svn.debian.org/nut/trunk nut 
> # cd nut 
> # autoreconf --install 
> # ./configure --with-user=nut --with-group=nut --with-usb

Sorry for interfering with your conversation but wouldn't it be easier for 
Chance to use tarballs directly from buildbot instead of building up from SVN? 

It would assure that the sources are just as they are expected to be 
by Charles, so it would protect yourselves from the errors like the 
one happened.

Chance, there's a web page here:
http://buildbot.ghz.cc/public/nut/waterfall?branch=branches%2Ftripplite-proto-3004&builder=Debian-etch-x86&reload=none

Timelime goes from downside upwards. Each yellow line shows up the start of the 
new build. In case it was successful there will be a green line "copied tarball"
several lines upwards. You can just click on the link "tarball" and fetch the 
sources you should use for testing.

In case you still want to use SVN you should be sure to use the correct branch 
for testing (svn://svn.debian.org/nut/branches/tripplite-proto-3004 for now, 
Charles will inform you in case it should be changed). There's no need to checkout
full sources each time you're going to conduct the tests. Just be sure not to make 
any changes to the sources (I mean, do not edit any .c/.h file unless you were 
requested to do so by devteam). 
Before updating sources to a new SVN revision be sure to change working
directory to nut and issue:
# make clean

Then, still being in nut directory, use the command:
# svn update

To switch to another branch use:
# svn switch <branch-URL-goes-here>

After updating/switching you should check if the sources are "in a good state":
# svn status -u

It might give you an output like this:
[lexa2 at lx2linux nut-trunk]$ svn status -u
       *     2265   m4/nut_report_feature.m4
       *     2265   m4/nut_check_libhal.m4
       *     2265   include/common.h
       *     2265   common/common.c
       *     2265   tools/Makefile.am
       *            tools/device-recorder.sh
       *     2265   tools
       *     2265   drivers/explore-hid.c
       *     2265   drivers/cps-hid.c
       *     2265   drivers/liebert-hid.c
       *     2265   drivers/belkin-hid.c
       *     2265   drivers/clone-outlet.c
       *     2265   drivers/powercom-hid.c
       *     2265   drivers/mge-xml.c
       *     2265   drivers/megatec.c
       *     2265   drivers/tripplite-hid.c
       *     2265   drivers/mge-hid.c
       *     2265   drivers/tripplite_usb.c
       *     2265   drivers/apc-hid.c
M            2265   INSTALL
       *     2265   configure.in
Status against revision:   2300

In this case there are two things to notice:
1) Lines with an asterisk mean that there were some changes to this files since
the last time the svn update was issued. So I have to use "svn update" to freshen
up the source files.
2) Lines starting with any latin letter shows up the files that have been somehow altered
by you in your local working copy. This might happen for ex. after using "autoreconf --install".
You should use "svn revert <filename>" command to revert files to the original version from the
repository. Filename must be specified with a path component relative to the root of 
checked out nut source tree (for ex. svn revert drivers/megatec.c).

You should update and revert changed files until you get a clean output from "svn status -u".
As long as you achieve this state proceed as stated in "compiling from SVN" docs:

# autoreconf --install
# ./configure <blablabla>
# make

You may skip "sudo make install" part when you're just about to test a single driver.
Just changedir to drivers and run the binary from there using sudo:

# cd drivers
# sudo ./blazer_usb -a <upsid> ...

I hope this info will be useful in your investigations.

- -- 
Best regards,
Alexey Loukianov                          mailto:mooroon2 at mail.ru
System Engineer,                            Mob.:+7(926)218-1320
*nix Specialist

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJLZqslAAoJEPB9BOdTkBULTx0H/2kI7kumN1Vo8fiAjwpW5lFP
HFwRFxL7TyZeIpkeVouStw1BLM6QIKD/W1wXwB2Ykfsnl/gAQo3EC3XNk1+MBDVs
CclrRn45fsubFLJnOnxUy67m3rXx51wieWxR+H/qGOo0JQ114rHcZPzE50KaBjjd
PwfGwUlluFXgEn2YIaaRbRYcCIQpQ84WvvEYVvVIUR6akhI4oaZYBG3I9aFxgiUf
8qaR8X60WtrXMvp/t5msO5zhEK2z/6mtzl+Yi3l7jb2v86To6+O1DxNc81xW61Lc
doPI4LBaABfCa0kOw1cRMmt8ZSIGMLWFm/xOEc7t75FIjg+/RmqJKTEurI4dr9U=
=FsZq
-----END PGP SIGNATURE-----