Bug 1311349

Summary: rpmspec behaves strangely
Product: [Fedora] Fedora Reporter: Zbigniew Jędrzejewski-Szmek <zbyszek>
Component: rpmAssignee: Packaging Maintenance Team <packaging-team-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: jzeleny, lkardos, novyjindrich, packaging-team-maint, pknirsch
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-24 08:24:47 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:

Description Zbigniew Jędrzejewski-Szmek 2016-02-24 00:58:56 UTC
Description of problem:
I was trying to use rpmspec to extract some information from a spec file. rpmspec does two strange things:
1. It looks for files in ~/rpmbuild/SOURCES/ even though it doesn't need them for anything. I guess it's trying to be helpful but it's just annoying.

2. It prints things twice.

Version-Release number of selected component (if applicable):
rpm-build-4.13.0-0.rc1.11.fc23.x86_64

Steps to reproduce:
$ fedpkg clone elasticsearch && cd elasticsearch
$ rpmspec -q --queryformat=x%{version}x elasticsearch.spec

Actual results:
error: File /home/zbyszek/rpmbuild/SOURCES/elasticsearch-1.3.2-remove-sigar-service.patch: No such file or directory
error: File /home/zbyszek/rpmbuild/SOURCES/unbundleBase64.patch: No such file or directory
error: File /home/zbyszek/rpmbuild/SOURCES/localhostByDefault.patch: No such file or directory
error: File /home/zbyszek/rpmbuild/SOURCES/netty-version.patch: No such file or directory
x1.7.5xx1.7.5x
        
Expected results:
x1.7.5x

Comment 1 Ľuboš Kardoš 2016-02-24 08:24:47 UTC
1. This has been already reported and fixed in rawhide (bug 1293687).

2. That is correct because your spec file contains two packages:
$ rpmspec -q elasticsearch.spec 
elasticsearch-1.7.1-2.fc20.noarch
elasticsearch-javadoc-1.7.1-2.fc20.noarch

So the version of each package from spec file is showed.

*** This bug has been marked as a duplicate of bug 1293687 ***