ferdnyc left a comment (rpm-software-management/rpm#3661)
So, I rebuilt `glibc` (there's two hours of your life you'll want back) --
twice, actually. The first time I changed the `%global` to a `%define`, which
made no difference. The second time I doubled all of the backslashes in the
`%{expand: ...}` arguments, which got them to show up in the `rpm -q
--filetriggers -p glibc-common-*.rpm` output.
I'm prepared to consider this user error, it appears the backslashes _really
are_ getting lost in translation, and `rpm -q` is actually displaying the
correct information. I'll open a PR against `glibc` @ Fedora to fix that.
Closing this as invalid, sorry for the noise.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/3661#issuecomment-2731686476
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/issues/3661/[email protected]>
_______________________________________________
Rpm-maint mailing list
[email protected]
https://lists.rpm.org/mailman/listinfo/rpm-maint
