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 1246453 - It is not possible to build src.rpm on TPS stable systems
Summary: It is not possible to build src.rpm on TPS stable systems
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: nmap
Version: 7.2
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Michal Hlavinka
QA Contact: Jaroslav Aster
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-24 11:00 UTC by Jaroslav Aster
Modified: 2015-11-19 12:49 UTC (History)
1 user (show)

Fixed In Version: nmap-6.40-7.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-19 12:49:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2137 0 normal SHIPPED_LIVE nmap bug fix update 2015-11-19 11:13:18 UTC

Description Jaroslav Aster 2015-07-24 11:00:27 UTC
Description of problem:

It is not possible to build src.rpm on TPS stable systems. The problem is in the configure script. There is auto detect option --with-nmap-update which is enabled when there is subversion library and header file in the system, otherwise this option is disabled. If this option is enabled new files are created, but they are not packaged, so build fails. There are full installation on the stable systems.

I suggest to add option --without-nmap-update into the nmap.spec file.


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

nmap-6.40-6.el7.src.rpm

How reproducible:

100%

Steps to Reproduce:
1. Install packages subversion-devel and subversion-libs.
2. Build src.rpm package: rpmbuild -ba _PATH_/nmap.spec

Actual results:

...
Checking for unpackaged file(s): /usr/lib/rpm/check-files /root/rpmbuild/BUILDROOT/nmap-6.40-6.el7.x86_64
error: Installed (but unpackaged) file(s) found:
   /usr/bin/nmap-update
   /usr/share/man/man1/nmap-update.1.gz


RPM build errors:
    Installed (but unpackaged) file(s) found:
   /usr/bin/nmap-update
   /usr/share/man/man1/nmap-update.1.gz


Expected results:

No errors.

Additional info:

Workaround is uninstall subversion-devel and subversion-libs packages.

Comment 4 errata-xmlrpc 2015-11-19 12:49:21 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://rhn.redhat.com/errata/RHBA-2015-2137.html


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