You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I understand that the dnf5 builddep may be different, and from the --help output it only accepts .spec files so --spec is redundant, but it might make the transition from dnf4 easier if it accepted --spec without an error.
The text was updated successfully, but these errors were encountered:
Yeah, this is reasonable and will make it easier for people bringing scripts and commands to dnf5 from legacy dnf. I've added --spec and --srpm as no-op arguments for the builddep command. It's true the behavior is different and dnf5 doesn't require the explicit argument anymore, but the no-op commands are fine.
dcantrell
added a commit
to dcantrell/dnf5
that referenced
this issue
Aug 9, 2023
Under dnf4 the builddep command accepted the --spec or --srpm argument
(mutually exclusive) to tell dnf what the input to the command was.
With dnf5 the command is more intelligent and the arguments are not
required. However, if you are bringing a script over from an existing
system and you have --spec or --srpm for the builddep dnf command, you
will get this error:
Unknown argument "--spec" for command "builddep". Add "--help" for more information about the arguments.
This patch addes the --spec and --srpm arguments to the builddep
command, but they are ignored. They exist for backwards
compatibility.
Fixes: rpm-software-management#799
Signed-off-by: David Cantrell <dcantrell@redhat.com>
See https://github.com/osbuild/weldr-client/actions/runs/5752335719/job/15593094835?pr=114
I understand that the dnf5 builddep may be different, and from the --help output it only accepts .spec files so
--spec
is redundant, but it might make the transition from dnf4 easier if it accepted--spec
without an error.The text was updated successfully, but these errors were encountered: