Skip to content

Run rpm-datarepair 4007 on upgrade - #1099

Open
phess wants to merge 1 commit into
theforeman:v1.13.xfrom
phess:run-rpm-datarepair-4007
Open

Run rpm-datarepair 4007 on upgrade#1099
phess wants to merge 1 commit into
theforeman:v1.13.xfrom
phess:run-rpm-datarepair-4007

Conversation

@phess

@phess phess commented Aug 20, 2026

Copy link
Copy Markdown

Cherry-picking into foreman-maintain-1.13.x.

(cherry picked from commit 1806d4f)

(cherry picked from commit 1806d4f)
@phess

phess commented Aug 20, 2026

Copy link
Copy Markdown
Author

For clarification: this PR is being paired with an upgrade to pulp-rpm so that the pulp-rpm version handled with foreman_maintain-1.13.x contains the appropriate repair_4007 command for foreman_maintain to call.

@ianballou

Copy link
Copy Markdown
Contributor

pulp_rpm 3.29.2 (packaged in pulpcore-packaging), is too old to work with this change. We'd need to bump pulp_rpm to 3.29.11 in pulpcore-packaging for this to work with Foreman 3.17.

@phess

phess commented Aug 21, 2026

Copy link
Copy Markdown
Author

pulp_rpm 3.29.2 (packaged in pulpcore-packaging), is too old to work with this change. We'd need to bump pulp_rpm to 3.29.11 in pulpcore-packaging for this to work with Foreman 3.17.

@ianballou , pulp_rpm is bumped to 3.29.11 in pulpcore-packaging. But this is so it'll work with Foreman 3.16, not 3.17.

@ianballou

Copy link
Copy Markdown
Contributor

https://github.com/theforeman/pulpcore-packaging/blob/rpm/3.73/packages/python-pulp-rpm/python-pulp-rpm.spec needs a bump, which we can do (I think). Let's merge this in with the expectation that it will be bumped. I'll put in a PR if someone doesn't beat me to it.

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.

3 participants