[Nut-upsdev] NUT v2.8.4 coming up

[Jim Klimov]

FWIW, I did merge the previously queued "small PRs", now probably gotta
figure out what Greg found with pkgsrc's `sed` (or await his PR with a fix
that would work everywhere - can't reproduce the problem so far), and
planned changes will be done.

If there's something to clarify about dcs - PRs are always welcome, though
not sure this would hold up a release.

Regarding `configure --with-doc(s)` and related options -- there indeed is
a big can of worms due to portability and tools availability and standard
expectations.

TLDR summary of decades-long history, legacy and recent:

On one hand, a build is expected to deliver man pages. Historically *roff
files were directly edited and served by projects; nowadays it is asciidoc
or similar, rendered into man pages as one of many output formats.  Dist
tarballs include those page files so they can be installed even where
asciidoc renderer is not available. So some options manage this part.

Another issue is the codes assigned to man page sections in different OSes
- this was previously bolted to what is seen in Linux and FreeBSD; now can
be amended for package builds (especially on other platforms), to avoid
clumsy distro-specific patch files or scripts in their recipes.

And another aspect regards other rendering formats (HTML*, PDF).

Hope this helps,
Jim Klimov

On Fri, Aug 1, 2025, 10:19 Jim Klimov <jimklimov+nut at gmail.com> wrote:

> Hello all,
>
>   Due to some issues uncovered with NUT v2.8.3 release on one hand
> (fixable, but cumbersome for packagers to extract and patch in their
> recipes), and an upcoming hiatus due to vacation travels on another, I've
> pushed much of the more-ambitious plan slated for NUT v2.8.4 back to
> v2.8.5, and plan to release what has cropped up until now as a smaller
> v2.8.4 increment, just a few months after a preceding release. This is
> probably how things should be (aiming for smaller quicker releases), too :)
>
>   Even so, it is by no means a trivial hot-fixing release - there were
> many contributions that have already landed, including new drivers, updates
> to existing drivers and other programs, recipes, CI tests, etc.
>
>   While a few smaller PRs are still queued and iterated, it would be wise
> of the community to run some builds of the current master against their
> devices in their OS ecosystems of choice, to make sure we do not get big
> facepalms within a week after a release :)
>
>   The plan is to cut off a snapshot of the `master` branch (slightly
> pre-doctored as usual) into a NUT v2.8.4 release, and so begin the v2.8.5
> timeline, during the first week of August, probably before next Friday. Or
> forever hold our silence (that is, until September or later).
>
> Cheers,
> Jim Klimov
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20250802/263185eb/attachment.htm>