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.
Bug 618706 - rpm doesn't include rpm-4.4.2.3-no-buildid-warning.patch
Summary: rpm doesn't include rpm-4.4.2.3-no-buildid-warning.patch
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: rpm
Version: 6.1
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Panu Matilainen
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-27 14:59 UTC by Martin Poole
Modified: 2018-10-27 13:31 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-09-28 08:39:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Martin Poole 2010-07-27 14:59:55 UTC
Description of problem:

According to find-debuginfo.sh of rpm on RHEL6 beta2, there isn't the patch
rpm-4.4.2.3-no-buildid-warning.patch that resolves IT#269860.

A part of the shell script to look into is below.
 ...
 id=$(/usr/lib/rpm/debugedit -b "$RPM_BUILD_DIR" -d /usr/src/debug \
                             -i -l "$SOURCEFILE" "$f") || exit
 if [ -z "$id" ]; then
 ...

If debugedit fails, find-debuginfo.sh exits.  debugedit fails whenever
"//" is included in the path specified for itself.

A part of the patch to look into is below.
...
 id=$(/usr/lib/rpm/debugedit -b "$RPM_BUILD_DIR" -d /usr/src/debug \
-                            -i -l "$SOURCEFILE" "$f") || exit
-  if [ -z "$id" ]; then
+                            -i -l "$SOURCEFILE" "$f")
+  if $strict && [ -z "$id" ]; then
...

With the above patch, even if "//" is included in the path specified
for debugedit, find-debuginfo.sh won't exit.


Version-Release number of selected component (if applicable):

 Red Hat Enterprise Linux Version Number: Red Hat Enterprise Linux 6.0
 Release Number: Beta2 snapshot7
 Architecture: x86_64
 Kernel Version: kernel-2.6.32-44.el6.x86_64
 Related Package Version: rpm-4.8.0-10.el6.x86_64

Comment 1 Panu Matilainen 2010-09-28 08:39:13 UTC
The patch to suppress buildid warnings was only added to RHEL 5 to avoid significant behavior change within a released distro version, and was intentionally omitted from RHEL 6.

Best option is to fix the package, but if that's not feasible for whatever reason the strict build-id behavior can be turned off through a macro, either in spec of the affected package(s):

%global _missing_build_ids_terminate_build 0

or in the macro configuration of the build environment (eg ~/.rpmmacros):

%_missing_build_ids_terminate_build 0


Note You need to log in before you can comment on or make changes to this bug.