[Nut-upsdev] [Nut-upsuser] NUT v2.8.4 coming up

[Jim Klimov]

Regarding the timeframe, I did mention the idea of a release before or
early in August (specifically as before vacations) in a few discussions
here and there, but yes - that plan got clearer as the flight gets closer.

How is a pkgsrc build significantly different? Notably, which sed does it
have?
I am all for having proper POSIX constructs, that's what the diverse farm
and wild recipes are for, but these iterations have all passed sed et al on
GNU/BSD/Solarish/... ecosystems of various ages...

And perhaps - any quick hints how I could set it up for NUT CI farm builds?

Jim


On Fri, Aug 1, 2025 at 3:49 PM Greg Troxel via Nut-upsdev <
nut-upsdev at alioth-lists.debian.net> wrote:

> I'm getting a build failure  under pkgsrc.   This is likely due to
> introduction of a sed construct not specified by POSIX.  Posting first
> before thinking due to threatened short timeframe :-)
>
>   /usr/bin/make  all-recursive
>   Making all in .
>   Making all in NIT
>     SUBDIR-MAKE   SUCCESS: 'make all' in tests
>     SUBDIR-MAKE   STARTING: 'make prep-src-docs' in docs ...
>     SUBDIR-MAKE   SUCCESS: 'make prep-src-docs' in docs
>     SUBDIR-MAKE   STARTING: 'make all' in docs ...
>   Making all in cables
>     DOCS_NO_MAN   SKIP: all-optional called in docs/man/Makefile:
> requested to not work in this code path
>     DOC-FOLLOW-UP Basic 'make all' in
> /tmp/work/wip/ups-nut/work/nut-2.8.3.724/docs is done, following up with
> 'make doc' to ensure complex document types
>     DOC-CHANGELOG-GENERATE-WRAPPER        ../ChangeLog : call parent
> Makefile to decide if (re-)generation is needed
>     DOC-CHANGELOG-GENERATE
> /tmp/work/wip/ups-nut/work/nut-2.8.3.724/ChangeLog : SKIP (keep existing)
>   Using distributed ChangeLog file from sources (and builddir is srcdir)
>     DOC-NOT-MAN   SKIP: man-man called in docs/Makefile
>     DOC-CHANGELOG-ASCIIDOC        ../ChangeLog => ../ChangeLog.adoc :
> Block for up to 10 sec, maybe another thread will make the file first
>     DOC-CHANGELOG-ASCIIDOC        ../ChangeLog => ../ChangeLog.adoc :
> GENERATE
>     DOC-CHANGELOG-ASCIIDOC        ../ChangeLog => ../ChangeLog.adoc :
> PROCEED, waited for 10 sec
>   sed: 1: "s,^\(\s\s*\)\([0-9]\),\ ...": RE error: trailing backslash (\)
>   *** [../ChangeLog.adoc] Error code 1
>
>   make[3]: stopped in /tmp/work/wip/ups-nut/work/nut-2.8.3.724/docs
>   1 error
>
>   make[3]: stopped in /tmp/work/wip/ups-nut/work/nut-2.8.3.724/docs
>   *** [all] Error code 2
>
>   make[2]: stopped in /tmp/work/wip/ups-nut/work/nut-2.8.3.724/docs
>   1 error
>
>   make[2]: stopped in /tmp/work/wip/ups-nut/work/nut-2.8.3.724/docs
>     SUBDIR-MAKE   FAILURE: 'make all' in docs
>   *** [all/docs] Error code 2
>
>   make[1]: stopped in /tmp/work/wip/ups-nut/work/nut-2.8.3.724
>   1 error
>
>   make[1]: stopped in /tmp/work/wip/ups-nut/work/nut-2.8.3.724
>   *** [all-fanout-maybe] Error code 2
>
>   make: stopped in /tmp/work/wip/ups-nut/work/nut-2.8.3.724
>   1 error
>
>   make: stopped in /tmp/work/wip/ups-nut/work/nut-2.8.3.724
>   *** Error code 2
>
>   Stop.
>   make[1]: stopped in /n0/gdt/pkgsrc-current/pkgsrc/wip/ups-nut
>   *** Error code 1
>
>   Stop.
>   make: stopped in /usr/pkgsrc/wip/ups-nut
>
>
>
>
> Other issues:
>
>   -with-doc is very confusing.    There is talk of "traditional",
>    "legacy", and other mumbo jumbo, but I can't tell from reading
>    configure.ac what is the documented, preferred option, and what  is
>    accepted for compatibility.   I also can't tell if, when building
>    from a tarball with docs, this results in not getting docs
>    (unacceptable in a package), or installing the ones that were built
>    and not rebuilding.
>
> _______________________________________________
> Nut-upsdev mailing list
> Nut-upsdev at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20250801/51ddfbd9/attachment.htm>