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 1303551 - the go-md2man is not a correct BuildRequires in atomic SPEC file
Summary: the go-md2man is not a correct BuildRequires in atomic SPEC file
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: atomic
Version: 7.4
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: rc
: ---
Assignee: Lokesh Mandvekar
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-01 09:52 UTC by Alex Jia
Modified: 2016-02-16 20:23 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-16 20:23:23 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Alex Jia 2016-02-01 09:52:28 UTC 
Description of problem:
We only have a golang-github-cpuguy83-go-md2man RPM package in brew system, but the atomic needs a go-md2man BuildRequires in SPEC file.

Version-Release number of selected component (if applicable):
atomic-1.8-6.git1bc3814.el7.src.rpm

How reproducible:
always

Steps to Reproduce:
1. rpm -ivh atomic-1.8-6.git1bc3814.el7.src.rpm
2. grep go- /root/rpmbuild/SPECS/atomic.spec


Actual results:

# grep go- /root/rpmbuild/SPECS/atomic.spec
BuildRequires: go-md2man

Expected results:
BuildRequires: /usr/bin/go-md2man    (Daniel suggests this)

OR

BuildRequires: golang-github-cpuguy83-go-md2man


Additional info:

The k8s has a BuildRequires looks like this.
BuildRequires: golang-github-cpuguy83-go-md2man
Comment 2 Lokesh Mandvekar 2016-02-01 15:18:26 UTC 
hmm, golang-github-cpuguy83-go-md2man should have a "Provides: go-md2man" which should take care of this bug, but I'll look what's up.
Comment 3 Lokesh Mandvekar 2016-02-01 15:39:28 UTC 
I don't see any issue with the way we're specifying BuildRequires: go-md2man (see paste below). Is there some other problem that's caused because of this?


$ sudo yum-builddep atomic.spec
Getting requirements for atomic.spec
 --> Already installed : python-devel-2.7.5-34.el7.x86_64
 --> Already installed : python-requests-2.6.0-1.el7_1.noarch
 --> Already installed : python-setuptools-0.9.8-4.el7.noarch
 --> Already installed : python-tools-2.7.5-34.el7.x86_64
 --> Already installed : dbus-python-1.1.1-9.el7.x86_64
 --> Already installed : policycoreutils-python-2.2.5-20.el7.x86_64
 --> golang-github-cpuguy83-go-md2man-1.0.4-1.el7.x86_64
 --> Already installed : python-docker-py-1.6.0-1.el7.noarch
 --> Already installed : rpm-python-4.11.3-17.el7.x86_64
--> Running transaction check
---> Package golang-github-cpuguy83-go-md2man.x86_64 0:1.0.4-1.el7 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

=================================================================================================================================================================
 Package                                              Arch                       Version                         Repository                                 Size
=================================================================================================================================================================
Installing:
 golang-github-cpuguy83-go-md2man                     x86_64                     1.0.4-1.el7                     External-Repository-2                     558 k

Transaction Summary
=================================================================================================================================================================
Install  1 Package

Total download size: 558 k
Installed size: 2.3 M
Is this ok [y/d/N]: y
Downloading packages:
golang-github-cpuguy83-go-md2man-1.0.4-1.el7.x86_64.rpm                                                                                   | 558 kB  00:00:00     
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
  Installing : golang-github-cpuguy83-go-md2man-1.0.4-1.el7.x86_64                                                                                           1/1 
  Verifying  : golang-github-cpuguy83-go-md2man-1.0.4-1.el7.x86_64                                                                                           1/1 

Installed:
  golang-github-cpuguy83-go-md2man.x86_64 0:1.0.4-1.el7                                                                                                          

Complete!
Comment 4 Lokesh Mandvekar 2016-02-01 15:45:16 UTC 
Also, see the mock logs for the build scheduled for release https://download.eng.bos.redhat.com/brewroot/packages/atomic/1.8/6.git1bc3814.el7/data/logs/x86_64/root.log <- golang-github-cpuguy83-go-md2man was correctly picked up as a build dep.
Note You need to log in before you can comment on or make changes to this bug.