Bug 1344553

Summary: Build golang-github-cpuguy83-go-md2man on aarch64/ppc64le/s390x
Product: Red Hat Enterprise Linux 7 Reporter: Yaakov Selkowitz <yselkowi>
Component: golang-github-cpuguy83-go-md2manAssignee: Lokesh Mandvekar <lsm5>
Status: CLOSED ERRATA QA Contact: Martin Cermak <mcermak>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 7.3CC: bbreard, hannsj_uhl, imcleod, jcm, jwboyer, lsm5, mcermak, nhorman, qe-baseos-tools-bugs, snagar, yselkowi
Target Milestone: rcKeywords: Patch
Target Release: 7.4   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: golang-github-cpuguy83-go-md2man-1.0.4-4.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-01 19:36:12 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:
Bug Depends On: 1330711, 1405587, 1414500    
Bug Blocks: 1405448, 1406046, 1406054, 1406090, 1406095, 1411763, 1418899, 1419752, 1419763, 1478982    
Attachments:
Description Flags
Patch for rhel-7.3 none

Description Yaakov Selkowitz 2016-06-10 03:17:25 UTC 
golang has been enabled on aarch64 for 7.3 in bug 1330711.  Therefore, this package too can and should be enabled on RHELSA for feature parity.

Please let us know if you need any help getting this on the ACL.
Comment 1 Yaakov Selkowitz 2016-06-10 03:19:10 UTC 
Created attachment 1166453 [details]
Patch for rhel-7.3

Scratch build:

https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=11164666
Comment 2 Jon Masters 2016-08-30 07:44:05 UTC 
What's the impact of this landing in 7.4?
Comment 4 Yaakov Selkowitz 2017-02-01 04:12:32 UTC 
*** Bug 1406053 has been marked as a duplicate of this bug. ***
Comment 32 errata-xmlrpc 2017-08-01 19:36:12 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2168