One more PR popped up from recent discussions: https://github.com/networkupstools/nut/pull/2899 - to address better detection of paths involved in `./configure --enable-inplace-runtime` or `./ci_build.sh inplace` builds, as well as to resolve some confusion in build scripts and recipes. I hope its eventual merge would be v2.8.3-rc4 and unless some other blockers crop up - the final release as well.
So while CI is chewing it, you may try so too :) :; git clone https://github.com/jimklimov/nut -b issue-2895 nut-issue-2895 :; cd nut-issue-2895 :; ./ci_build.sh inplace One of the discoveries (better late than never, and certainly better before a release than after one), regarded public library API bump, which was not handled well in development (with new symbols, the "current" value = equivalent of "major" semantic version must be bumped). Contributions of some automation to track such changes better for future releases would be great (maybe a more elaborate library script than a regex used currently?) - no rush, but PRs would be welcome :) Jim On Fri, Mar 28, 2025 at 10:27 AM Jim Klimov <[email protected]> wrote: > Hello all, > > It has been too long that I was feeling a release is just around the > corner, just gotta tie up a few loose ends. The significant ones we had are > finally tied, some others delayed to v2.8.4 trail, and a documentation > refresh remains. Thanks to some package maintainers taking a look at the > master branch, some issues with "dist" archive creation and parallel builds > were also located and addressed. > > So, it is that time of the year again, folks, when flowers bloom and > code gets ripe for picking a new release snapshot -- so everybody is > welcome to give it a round during the weekend. After too many hopeful > deadlines missed, I hope to at least not exceed a year since the last > release snapshot :) > > As usual, > https://github.com/networkupstools/nut/wiki/Building-NUT-for-in%E2%80%90place-upgrades-or-non%E2%80%90disruptive-tests > (and the build prerequisites linked from there as > https://networkupstools.org/docs/user-manual.chunked/_build_prerequisites_to_make_nut_from_scratch_on_various_operating_systems.html) > should help you get started. > > Hoping for good news and no blocker issues, > Jim Klimov > > PS: One known problem remains with the recently introduced apc_modbus > driver and/or the libmodbus (core or our fork with rtu_usb branch) - that > the USB connections tend to fall apart, as tracked at > https://github.com/networkupstools/nut/issues/2609 and others linked from > it - for now I've exhausted the hardware-less ideas and the time I had; > help is welcome. >
_______________________________________________ Nut-upsdev mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev
