-
Notifications
You must be signed in to change notification settings - Fork 34
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
Make it easier to detect RPM %post failures #1430
Labels
Comments
Remaining to-do in the RPM specs for all packages after this one in the build:
Also consider making this available to the rest of the project. |
mfeit-internet2
added a commit
that referenced
this issue
Jun 7, 2024
mfeit-internet2
added a commit
that referenced
this issue
Jun 7, 2024
mfeit-internet2
added a commit
that referenced
this issue
Jun 7, 2024
This all works; merge it into 5.1.1 after 5.1.0 is out the door. |
mfeit-internet2
added a commit
that referenced
this issue
Jun 18, 2024
Release Notes: Installation errors on RPM-based systems that previously happened quietly do to a limitation in RPM are now logged to syslog. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Because RPM doesn't stop when a
%post
scriptlet fails, there's no easy way to retroactively know if installation of any packages had a failure without scouring the logs.Write something to wrap the innards of the scriptlets:
Have it write the output of failed installations to a known location, maybe a syslog file.
The text was updated successfully, but these errors were encountered: