Bug 1650587

Summary:	rpmdiff: Execshield complaints that pltcl.so has some annobin issues [postgresql:10]
Product:	Red Hat Enterprise Linux 8	Reporter:	Pavel Raiskup <praiskup>
Component:	postgresql	Assignee:	Patrik Novotný <panovotn>
Status:	CLOSED WONTFIX	QA Contact:	RHEL CS Apps Subsystem QE <rhel-cs-apps-subsystem-qe>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.0	CC:	databases-maint, hhorak, odubaj, pkubat, praiskup
Target Milestone:	rc	Keywords:	Reopened
Target Release:	8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-02-01 07:30:33 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Pavel Raiskup 2018-11-16 14:57:36 UTC

Detecting usr/lib/pgsql/pltcl.so with not-hardened warnings '
Hardened: pltcl.so: FAIL: Gaps were detected in the annobin coverage.  Run with -v to list.
' on i686

Comment 1 Ondrej Dubaj 2019-05-28 10:05:57 UTC

This bug seems to be already fixed, as a scratch build from the current version was built and no errors were detected.

Scratch build here: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=21859946

new RPMDiff results here: https://rpmdiff.engineering.redhat.com/run/407284/18/

compared to old RPMDiff: https://rpmdiff.engineering.redhat.com/run/388125/7/

Due to this reasons, the bug will be closed as NOTABUG. If you consider this is a bug, feel free to reopen this issue.

Comment 2 Pavel Raiskup 2019-05-28 10:33:42 UTC

So maybe some build problem has been fixed, but isn't the problem already
compiled into the shipped binaries?

Comment 3 Ondrej Dubaj 2019-05-28 11:03:15 UTC

Yes, you are right. This is the last version used by customers. It would be rather better to reopen this bug and wait for the next build. If the RPMDiff will be OK, then it will be closed, since it is not so critical to make release dump and a new build for this issue.

Thank you for your advise!

Comment 4 Honza Horak 2020-06-29 14:35:28 UTC

Moving to postgresql component where the problem actually was.

Comment 7 RHEL Program Management 2021-02-01 07:30:33 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.