Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 675741

Summary: pkgconfig files have wrong version information
Product: Red Hat Enterprise Linux 6 Reporter: Steven Dake <sdake>
Component: corosyncAssignee: Steven Dake <sdake>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 6.1CC: cluster-maint, djansa, jkortus, syeghiay
Target Milestone: betaKeywords: Regression
Target Release: 6.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: corosync-1.2.3-25.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-19 14:24:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
patch to spec file to resolve regression none

Description Steven Dake 2011-02-07 15:36:34 UTC
Description of problem:
A regression in the 6.1 build of corosync results in an incorrect build of corosync.  Left unfixed, this would break ABI compatibility.

Version-Release number of selected component (if applicable):
corosync-1.2.3-24.el6

How reproducible:
check rpmdiff results

Steps to Reproduce:
1.
2.
3.
  
Actual results:
rpmdiff warns about version number information changed.

Expected results:
rpmdiff should not warn about version number information changed in shared objects.

Additional info:

Comment 2 Steven Dake 2011-02-07 15:53:15 UTC
The original analysis on this bugzilla was wrong, instead its the pkgconfig (.pc) files which are incorrect.  This still causes serious problems.  An example pc file from the build is:

[root@cast x86_64]# more /usr/lib64/pkgconfig/coro*
prefix=/usr
exec_prefix=${prefix}
libdir=/usr/lib64
includedir=${prefix}/include
lcrsodir=/usr/libexec/lcrso
socketdir=/var/run

Name: corosync
Version: UNKNOWN
Description: corosync
Requires:
Cflags: -I${includedir}


The version field should be 1.2.3.

Comment 3 Steven Dake 2011-02-07 16:02:37 UTC
Created attachment 477442 [details]
patch to spec file to resolve regression

Comment 7 Jaroslav Kortus 2011-03-02 13:51:28 UTC
$ more /usr/lib64/pkgconfig/corosync.pc
prefix=/usr
exec_prefix=${prefix}
libdir=/usr/lib64
includedir=${prefix}/include
lcrsodir=/usr/libexec/lcrso
socketdir=/var/run

Name: corosync
Version: 1.2.3
Description: corosync
Requires:
Cflags: -I${includedir}

rpm -q corosync
corosync-1.2.3-26.el6.x86_64


marking as verified.

Comment 8 errata-xmlrpc 2011-05-19 14:24:21 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0764.html