Bug 1377933

Summary:	builddep fails when specfile doesn't end in .spec
Product:	[Fedora] Fedora	Reporter:	wibrown <wibrown>
Component:	dnf	Assignee:	rpm-software-management
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	25	CC:	jsilhan, mluscon, mmraka, packaging-team-maint, pnemade, rpm-software-management, vmukhame
Target Milestone:	---
Target Release:	---
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:	2016-09-21 07:56:34 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 wibrown@redhat.com 2016-09-21 05:16:14 UTC

Description of problem:
In my project I have a specfile that has the name:

389-ds-base.spec.in

As a result of this, builddep fails to operate on this claiming:

sudo dnf builddep -y ds/rpm/389-ds-base.spec.in
Last metadata expiration check: 0:00:03 ago on Wed Sep 21 15:09:55 2016.
no package matched: ds/rpm/389-ds-base.spec.in

This is incorrect, as the specfile is valid.

Expected results:

Dnf uses the specfile correctly to install dependencies.

Comment 1 Michael Mráka 2016-09-21 06:43:53 UTC

Does

 dnf builddep -y --spec ds/rpm/389-ds-base.spec.in

help?

Comment 2 Igor Gnatenko 2016-09-21 07:56:34 UTC

(In reply to Michael Mráka from comment #1)
> Does
> 
>  dnf builddep -y --spec ds/rpm/389-ds-base.spec.in
> 
> help?
This is definitely solution.

Unfortunately there is no way how to automatically detect except check if it's text file then assume that it's spec.