Hide Forgot
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.
Does dnf builddep -y --spec ds/rpm/389-ds-base.spec.in help?
(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.