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
Replacing kernel-automotive
with kernel-automotive-debug
package fails during %posttrans
#4057
Comments
Image appears to be left in a bad state as uname -r should return {version} + debug |
Is |
this is what I got back from dev team on kernel-automotive... |
This should be fixed by https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2097. |
The proper fix for this is in kernel packaging. I added a more detailed explanation in https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2097#note_1134727559. That said, we should probably consider in rpm-ostree also neutering |
As this has been fixed upstream and is one year old now, I think it should be safe to close. Let us know if this is still an issue. Thanks |
MR: https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/1494 Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2134215 Upstream Status: RHEL-only The other scriptlets which inspect or delete this file expect it to have the `+SUBPKG` suffix. Looking at the original patch introducing this line, I think that was the intent, but here we need to use `%{?-v}` instead of `%{?1}` since unlike in the other places the file is referenced, the subpackage is a flagged macro parameter rather than positional. Fixes e815131473e4 ("redhat: spec: trigger dracut when modules are installed separately"). Fixes: coreos/rpm-ostree#4057 Signed-off-by: Scott Weaver <scweaver@redhat.com> Approved-by: Jan Stancek <jstancek@redhat.com> Approved-by: Herton R. Krzesinski <herton@redhat.com> Signed-off-by: Scott Weaver <scweaver@redhat.com>
Host system details
this is applicable to both x86_64 and aarch64
Actual behavior
Expected:
Additional log info
Would you like to work on the issue?
someone else
The text was updated successfully, but these errors were encountered: