RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

Hello, 

While I build & install my rpm, I see few pointers to a hidden file /usr/lib/.build-id getting listed as below. 

# rpm -qpl guru-12.50.00-0.rhel8.x86_64.rpm
/usr/lib/.build-id
/usr/lib/.build-id/0a
/usr/lib/.build-id/0a/e2b0fa0b36c131d586785cde6804511a654680
/usr/lib/.build-id/17
/usr/lib/.build-id/17/7d74c59c428133c08c7d4716401a08541f88d4
/usr/lib/.build-id/1a
/usr/lib/.build-id/1a/485eefe7f401c8a6f7c3ea3818767888953815
.
.
.
/usr/local/cmcluster
/usr/local/cmcluster/bin

Not just my rpm, I see few others too but it does not bother me. 
# rpm --query --file /usr/lib/.build-id | head -10
libgcc-8.2.1-3.5.el8.x86_64
pcre2-10.32-1.el8.x86_64
libselinux-2.8-6.el8.x86_64
ncurses-libs-6.1-7.20180224.el8.x86_64
glibc-common-2.28-42.el8.x86_64


Version-Release number of selected component (if applicable):
rpm-4.14
4.18.0-80.el8.x86_64


My questions:
1. Can I avoid or disable packaging these files in my rpm?
2. Can you also explain(or point) the purpose of this change in behavior?

Thanks,
Prabhanjan

Their precense is not a bug but an intended feature, see https://fedoraproject.org/wiki/Changes/ParallelInstallableDebuginfo for the rationale.

You can filter them out from rpm -q query results with --noartifact switch, and the generation + location of the build-id links can be controlled at package build-time by %_build_id_links macro, see https://github.com/rpm-software-management/rpm/blob/4a9440006398646583f0d9ae1837dad2875013aa/macros.in#L506 for the supported values. Just beware that changing the default will have side-effects.