error: Can not enable WITH_CHANGELOG_HTML_SINGLE due to build settings or environment

[bigon]

Hello

When trying to build nut just with ./configure --with-doc=man, I get the following error in configure:

configure: error: Can not enable WITH_CHANGELOG_HTML_SINGLE due to build settings or environment

This is new in 2.8.4 and causes the build to fail on debian

An idea?

[jimklimov]

Thanks, looks like a bug and probably fallout of #3019. Gave it a shot while commuting, and could not reproduce :\ Could your build environment lack some tools? By logic in configure.ac this error happens if html-single was neither enabled nor skipped.

I agree this should not matter if we only care for man pages. Will try to spin up a less featured build env in the coming days, if you don't come up with a patch earlier ;)

[jimklimov]

This may be complicated by that being a release build, so stricter to deliverables (also for dist tarball), maybe something spilled over the top there. Retrying with a local fake release tagged commit...

[jimklimov]

Fake v2.8.5 tag did not help, beside emitting

configure: This is a (pre-)release build and original --enable-docs-changelog=auto -- consider setting to "yes"

and then warning about WITH_CHANGELOG_HTML_SINGLE

Rechecking with a checkout of v2.8.4, maybe something here was already fixed?..

[jimklimov]

also no banana reproducing the problem

will try tarball

[jimklimov]

Same thing, release tarball passed the build.

@bigon : Do you have any ideas about what could make your build environment special in ways of reproducing the issue? :\

[bigon]

A missing build-dependency maybe?

The only difference when building the documentation package in debian or not are the following packages (with these packages it succeeds)

Build-Depends-Indep: asciidoc-dblatex <!nodoc>,
                     dblatex <!nodoc>,
                     docbook-xsl <!nodoc>

[bigon]

Hello,

So I had more time to test, adding these 3 dependencies is not helping

The full configure command is:

dh_auto_configure: error: ./configure --build=x86_64-linux-gnu --prefix=/usr --includedir=${prefix}/include --mandir=${prefix}/share/man --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --disable-option-checking --disable-silent-rules --libdir=${prefix}/lib/x86_64-linux-gnu --runstatedir=/run --disable-maintainer-mode --disable-dependency-tracking --prefix=/usr --sysconfdir=/etc/nut --includedir=/usr/include --mandir=/usr/share/man --libdir=${prefix}/lib/x86_64-linux-gnu --libexecdir=/usr/libexec --with-ssl --with-nss --with-cgi --with-dev --enable-static --with-statepath=/run/nut --with-altpidpath=/run/nut --with-drvpath=/usr/libexec/nut --with-cgipath=/usr/lib/cgi-bin/nut --with-htmlpath=/usr/share/nut/www --with-pidpath=/run/nut --datadir=/usr/share/nut --with-pkgconfig-dir=/usr/lib/x86_64-linux-gnu/pkgconfig --with-user=nut --with-group=nut --with-udev-dir=/usr/lib/udev --with-systemdsystemunitdir=/usr/lib/systemd/system --with-systemdshutdowndir=/usr/lib/systemd/system-shutdown --with-systemdtmpfilesdir=/usr/lib/tmpfiles.d --with-python=python3 --with-python3=/usr/bin/python3 --with-libsystemd --with-doc=man returned exit code 1

[jimklimov]

Facepalm, my side.

TLDR: You'd need to update what your recipes see as "NUT v2.8.4".

Long version:

Looked at https://salsa.debian.org/debian/nut and in tag upstream/2.8.4 it has a ChangeLog that says NOTE: This change log section represents git commits in range 'v2.6.0..HEAD' (commits '8103b4e5c..434cb36a3') (newly, to help identify mishaps like this).

The commit 434cb36a3 is actually v2.8.4-rc1 in the NUT git repo, and there were some changes after it specifically around this issue. I thought your copy of NUT had it covered, but it was an older one (where I hit similar problems, and so "knew" they were solved).

:; git log --oneline v2.8.4-rc1..v2.8.4 configure.ac
541c2ecf0 (tag: v2.8.4-rc4, tag: v2.8.4) configure.ac: for now do not require (pre-)release tagged commits to build changelog by default - keep doing it on systems where we can though
a58c77a04 configure.ac: rephrase the message about --enable-docs-changelog [#3019, #3053]
d1fa9471a (tag: v2.8.4-rc2) configure.ac: for (pre-)release builds we default nut_enable_docs_changelog auto=>yes - do so loudly, and default --with-doc man=>auto as well for all builds to have a chance to try this

The out-of-band issue was that these problems were only hit when building a (pre-)release tagged version, and the logic did not fire (nor mis-fire) in usual iterations. As the master-branch code seemed healthy in all builds, it was tagged and released as v2.8.4 - only to surprisingly crash on CI (due to problems such as these). Several rounds of re-tagging, fixing and re-releasing followed same day (all under crunch to pack bags and catch the flight to a vacation far far away... and hoping that trip would not be the end of me) until v2.8.4-rc4 was okay and also-tagged as the final v2.8.4. The resulting tarballs were uploaded to GitHub and NUT-Website sources, but apparently did not propagate to the rendered website (which kept the earlier tarballs until early September, when I got back online, saw and fixed that).

Re-tested in practice that re-tagging is wrong (was in a hurry, hoped that a the short time frame would make it better, but due to that website thing it became a month for some downloaders).

Sorry for the mess...

[jimklimov]

@bigon : any news? Did bumping to what the v2.8.4 tag currently is (or to respective current tarball from github or nut-website) help?

[bigon]

@jimklimov yep the new tarball from https://networkupstools.org/source/ is OK and the package builds in debian

https://buildd.debian.org/status/package.php?p=nut