Skip to content

Conversation

@jimklimov
Copy link
Member

Support the goals of issue #1209 and #1316 by refining and upstreaming the 42ITy RPM and DEB packaging recipes used with a private Open Build Service instance a decade ago, to be useful with the public service available today.

There is likely more work ahead about GH-OBS integration, recipe revision to deliver files and features that appeared in NUT trunk over the years, less reliance on custom scripting after a make install run, and possibly some progress about use of make dist tarballs (or other ways of NUT SEMVER tracking)?..

Such packages can help community members evaluate non-release builds (maybe even PRs) without a required local build, and they did already help in CI sense by adding another opinion on code and recipe quality, as reflected in recently merged PRs.

jimklimov and others added 30 commits October 24, 2025 06:12
… dmfnutscan resource dirs delivered by both packages

Signed-off-by: Jim Klimov <[email protected]>
…iles - they were tested in Jenkins NUT-master job (remove build dependency on pycparser and speed up the build)

Signed-off-by: Jim Klimov <[email protected]>
…configuration and checking the build with NUT Integration Tests suite, and strip binaries of debug symbols

Signed-off-by: Jim Klimov <[email protected]>
…to mkdir it in build area to match our logrotate configuration

Signed-off-by: Jim Klimov <[email protected]>
@jimklimov jimklimov added this to the 2.8.5 milestone Oct 24, 2025
@jimklimov jimklimov added packaging CI Entries related to continuous integration infrastructure (here CI = tools + scripts + recipes) portability We want NUT to build and run everywhere possible documentation labels Oct 24, 2025
@AppVeyorBot
Copy link

@AppVeyorBot
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI Entries related to continuous integration infrastructure (here CI = tools + scripts + recipes) documentation packaging portability We want NUT to build and run everywhere possible

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants