Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A question on mailing list was raised about testing NUT for someone still running CentOS 6, so here goes... spoils of experimental reconnaissance:
"Surprisingly, it works!" (mostly regarding feature/dependency availability)
With container setup as documented in this PR and downshift to allow autoconf-2.63 (also in the PR),
./ci_build.sh
built and successfully NIT-tested the codebase (without C++11 support due to old GCC-4.4.x; clang-3.4.x refuses to use system-provided C++ headers).Although the older
python2.6
is the only one available on the system,PyNUT
successfully participated in the test; the NUT-Monitor GUI was not tried (headless system).Java 11 was not available for the platform, so for the time being it can not directly run a Jenkins agent and will not be part of regular NUT CI farm testing.