On Sat, 2017-09-30 at 16:46 +0530, Dristi Butola wrote:
> Hi :)
>
> I am facing the problem in the command just above the command you pointed
> have an error.
>
> sudo dnf builddep --setopt=strict=False 389-ds-base/rpm/389-ds-base.spec.in
>
> it gives me this error
>
> no package matched: 389-ds-base/rpm/389-ds-base.spec.in.
>
> How to solve this ?
>
> Thanks.
>
According to my own notes I don't even use that command. I think it's a
mistake on the website. The issue is with dnf that it expects specfiles
to end in ".spec", where as this is ".in". So it thinks it's a package
name.
A way around it is:
sudo dnf install --setopt=strict=False `grep -E "^(Build)?Requires"
389-ds-base/rpm/389-ds-base.spec.in lib389/python-lib389.spec | grep -v
-E '(name|MODULE)' | awk '{ print $2 }' | sed
's/%{python3_pkgversion}/3/g' | grep -v "^/" | grep -v pkgversion | sort
| uniq | tr '\n' ' '`
This is a command that should be run on a single line,
Hope that helps,
--
Sincerely,
William Brown
Software Engineer
Red Hat, Australia/Brisbane
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
