<div dir="ltr"><div>Hi Jim,</div><div><br></div><div>I was able to test it on Arch linux on RPI3 against my Tripplite SMC1000LCD. It Works.</div><div>P.S: on Arch Linux there is libusb-compat (0.1) and libusb (1.0) .</div><div>Also the git version is still 2.7.4 ~ v2.7.4.r3891.gea87c8c7.</div><div><br></div><div>Good Luck and a Happy new year.</div><div><br></div><div>Cheers,</div><div><br></div><div>Yogi<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Dec 26, 2021 at 10:51 AM Jim Klimov via Nut-upsuser <<a href="mailto:nut-upsuser@alioth-lists.debian.net">nut-upsuser@alioth-lists.debian.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto">Reminder: I plan to merge <a href="https://github.com/networkupstools/nut/tree/fightwarn-libusb-1.0+0.1" target="_blank">https://github.com/networkupstools/nut/tree/fightwarn-libusb-1.0+0.1</a> as "libusb-1.0+0.1" branch and as master after that, early next week.<div dir="auto"><br></div><div dir="auto">If anyone has tested this codebase against hardware, or needs a few more days to do so, please let me know here or in issue #300.</div><div dir="auto"><br></div><div dir="auto">Happy holidays,</div><div dir="auto">Jim</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Dec 21, 2021, 21:42 Jim Klimov <<a href="mailto:jimklimov%2Bnut@gmail.com" target="_blank">jimklimov+nut@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hello fellow NUTs :)</div><div><br></div><div> It seems the magic of the season might just help us finish some long story arcs and tie up loose ends... oh, wait, that is wording about other "seasons" ;)</div><div><br></div><div> In our case, the "fightwarn" effort is reaching a major milestone to finally pass the builds with "medium" level of warnings treated as fatal errors - with zero warnings. This achievement took a bit over a year, and almost 3000 commits to analyze and stomp out different small bugs, and it allows to set that tolerance level as default and insist on non-regressions with future iterations - as well as to work towards clearing the "hard" level eventually. And this became one of the criteria for cutting a new official NUT release (especially as new platforms refused to build release 2.7.4 with their default settings).<br></div><div><br></div><div> This work has originally delayed merging of libusb-1.0 support (from issue <a href="https://github.com/networkupstools/nut/issues/300" rel="noreferrer" target="_blank">https://github.com/networkupstools/nut/issues/300</a> and several candidate branches to pick from), in particular because with the original codebase sporting thousands of build warnings, it was hard to notice any new "offences" introduced by this large set of changes. I was afraid that merging it would even have to wait until after the next NUT release, but in the end found that some remaining warnings in the original USB-related NUT codebase made those branches' changes the better solution.</div><div><br></div><div> Now, before we find the hard way if the cure is worse than the disease, I would like to ask people with USB-connected UPSes (and also those using the MGE SHUT protocol) to build and test <a href="https://github.com/networkupstools/nut/tree/fightwarn-libusb-1.0+0.1" rel="noreferrer" target="_blank">https://github.com/networkupstools/nut/tree/fightwarn-libusb-1.0+0.1</a> branch with their setups - hopefully hitting as many OSes and CPU types as feasible, as well as trying both libusb-0.1, libusb-1.0 (and not sure about libusb-0.1-compat).</div><div><br></div><div> For building from scratch, note we now have a list of prerequisite packages for several platforms at <a href="https://github.com/networkupstools/nut/blob/master/docs/config-prereqs.txt" rel="noreferrer" target="_blank">https://github.com/networkupstools/nut/blob/master/docs/config-prereqs.txt</a> - and as for other code, PRs there are welcome too. <br></div><div>Note also the new `ci_build.sh` script to automate a number of configurations and setups, usually reducing the typing needed to reproduce build attempts :)<br></div><div><br></div><div> I understand that some people would be away for holidays, but also realize that for others
these days may be among the few times in the year that can be dedicated to such experiments and other hobbies. It would be much appreciated if you can help bring the official new confident NUT release date closer ;)</div><div><br></div><div> The NUT CI farm is busy testing hundreds of build combinations formally in software, but it is no replacement for tests against actual hardware.</div><div><br></div><div> Also, great thanks to dozens of individual and corporate contributors adding and fixing NUT drivers and other features (a few are still being tested and may become part of the new release too), and sharing findings and ideas in the issue tracker -- you guys and gals are our real heroes!<br></div><div><br></div><div> Finally, on behalf of the NUT core team, please let me wish you all a happy holiday season and some quality time to rest, walk, ski and be with family and friends!</div><div><br></div><div>Jim Klimov</div><div><br></div><div><br></div></div>
</blockquote></div>
_______________________________________________<br>
Nut-upsuser mailing list<br>
<a href="mailto:Nut-upsuser@alioth-lists.debian.net" target="_blank">Nut-upsuser@alioth-lists.debian.net</a><br>
<a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser" rel="noreferrer" target="_blank">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser</a><br>
</blockquote></div>