On Tue, Oct 08, 2024 at 09:39:49PM -0700, Samuel Sieb wrote: > The problem is that you're using "sudo" for this. dnf5 doesn't print the > reason for the failure, which is unfortunate. If you do it with "dnf4", you > do get the reason. > > $ sudo dnf4 builddep SPECS/systemd.spec > RPM: error: Unable to open /root/rpmbuild/SOURCES/triggers.systemd: No such > file or directory > Failed to open: 'SPECS/systemd.spec', not a valid spec file: can't parse > specfile > > Error: Some packages could not be found. > > The easiest workaround is to use the source rpm to get the build deps > instead of the spec file. It'd be worth filing a bug for this. There were some bugs about dnf5 not reporting things, but this one seems egregious. Zbyszek -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
