Bug 1377933 - builddep fails when specfile doesn't end in .spec
Summary: builddep fails when specfile doesn't end in .spec
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: rpm-software-management
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-21 05:16 UTC by wibrown@redhat.com
Modified: 2016-09-21 07:56 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-21 07:56:34 UTC
Type: Bug


Attachments (Terms of Use)

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.


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