Skip to content

NMS-19535: Don't disable rpm's internal dependency generator#8306

Merged
dino2gnt merged 2 commits intodevelopfrom
dcy/fixreallynewrpm
Mar 27, 2026
Merged

NMS-19535: Don't disable rpm's internal dependency generator#8306
dino2gnt merged 2 commits intodevelopfrom
dcy/fixreallynewrpm

Conversation

@dino2gnt
Copy link
Copy Markdown
Contributor

Setting %define _use_internal_dependency_generator 0 is broken as of rpm v6, and will result in failure:

error: External dependency generator is incompatible with v6 packages

External dependency generation has been removed in rpm format v6, hence internal dependency generation must be allowed.

I frequently build in an environment that packages using a much newer rpm and setting this to 0 broke those builds. Removing _use_internal_dependency_generator 0 allows the rpm build to complete and doesn't appear to have any deleterious effects aside from the two fixes noted below.

This adds a specific exclude for an ancient libstdc++-libc6.2 that "something" we're packing depends on that I assume the internal dependency generator discovered, and in addition adds an explicit Provides: for the user and group for core, minion, and sentinel, the lack of which appeared to cause an issue where we somehow Requires: user(opennms) that couldn't resolve because none of the packages Provides: it.

External References

Copy link
Copy Markdown
Contributor

@mershad-manesh mershad-manesh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@dino2gnt dino2gnt merged commit b736885 into develop Mar 27, 2026
15 checks passed
@dino2gnt dino2gnt deleted the dcy/fixreallynewrpm branch March 27, 2026 21:09
dino2gnt added a commit that referenced this pull request Apr 1, 2026
dino2gnt added a commit that referenced this pull request Apr 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants