Greg Troxel
2025-Apr-08 17:16 UTC
[Nut-upsuser] [Nut-upsdev] NUT testing for v2.8.3 (hopefully imminent)
I took v2.8.3-rc in git, bootstrapped autoconf, build, make check, make dist, (on NetBSD 10) and then used that tarball as the source for pkgsrc, built a package, installed it on machine with a Best Fortress (NetBSD 9), rebooted, and both upsc and a program that uses the pyNUT interface code seem fine. So I see no problems. (Of course, I always like there to be a multiday interval from rc to release so I don't mean to hurry you. Just that it looks good to me.)
Jim Klimov
2025-Apr-09 16:21 UTC
[Nut-upsuser] [Nut-upsdev] NUT testing for v2.8.3 (hopefully imminent)
Sounds great, thanks! A number of other community members raised a few issues from the RC testing that finally took off, so I guess there will be an rc3 at least... There may also be some issues with upssched as discussed in another mailing list thread and https://github.com/networkupstools/nut/issues/2890 (may be or not be same problem underneath) but I am not ready to investigate that deeply. Jim On Tue, Apr 8, 2025 at 7:16?PM Greg Troxel <gdt at lexort.com> wrote:> I took v2.8.3-rc in git, bootstrapped autoconf, build, make check, make > dist, (on NetBSD 10) and then used that tarball as the source for > pkgsrc, built a package, installed it on machine with a Best Fortress > (NetBSD 9), rebooted, and both upsc and a program that uses the pyNUT > interface code seem fine. > > So I see no problems. (Of course, I always like there to be a multiday > interval from rc to release so I don't mean to hurry you. Just that it > looks good to me.) > > > > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20250409/dbf4bdbf/attachment.htm>