-
Notifications
You must be signed in to change notification settings - Fork 198
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[skip-ci] RPM: ensure config files are patched #2026
Conversation
@edsantiago @Luap99 @jnovy PTAL |
The script exits 0 when I execute in the repo root here despite not having all the files, the reason is that the code does |
moved zstd:chunked to rawhide and rhel > 10. |
LGTM |
This commit copies over shortnames.conf, registries.conf and storage.conf to the rpm build dir before running the patching script. Prior to this, the script would complain about not finding those files but the rpmbuild process itself didn't fail. Signed-off-by: Lokesh Mandvekar <lsm5@redhat.com>
Signed-off-by: Lokesh Mandvekar <lsm5@redhat.com>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: edsantiago, lsm5 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@Luap99 In general RPM scriptlets should never fail as a it would break the whole transaction leaving the system in inconsistent state - it can put a message in the log though. |
But we are not talking about a rpm scriptlet are we? This here patches the config files at rpm build time so we very much want to know if if failed to patch the file otherwise we install invalid config files |
let's make sure to get this one in before the new c/common cut tomorrow. |
/lgtm This is specfile, not scriptlet. Failing in rpmbuild is the right thing to do. |
/cherrypick v0.59 |
LGTM |
See: 5c5b112#r143013047 |
This comment was marked as outdated.
This comment was marked as outdated.
➡️ #2048 |
This commit copies over shortnames.conf, registries.conf and storage.conf to the rpm build dir before running the patching script.
Prior to this, the script would complain about not finding those files but the rpmbuild process itself didn't fail.