On 10/8/24 10:09 AM, Barry Scott wrote:
Now I have systemd .src.rpm installed next I needed the build deps
so that I can do a rpmbuild.
$ sudo dnf builddep systemd.spec
[sudo] password for barry:
Updating and loading repositories:
Fedora 41 - aarch64 100% | 99.3 KiB/s | 18.3 KiB | 00m00s
Fedora 41 - aarch64 - Test Updates 100% | 122.6 KiB/s | 19.9 KiB | 00m00s
Fedora 41 - aarch64 - Updates 100% | 47.0 KiB/s | 20.9 KiB | 00m00s
Copr repo for tools owned by barryascott 100% | 3.7 KiB/s | 1.5 KiB | 00m00s
Copr repo for tools-testing owned by barryascott 100% | 10.0 KiB/s | 1.5 KiB | 00m00s
Fedora 41 - aarch64 100% | 2.8 MiB/s | 3.9 MiB | 00m01s
Fedora 41 - aarch64 - Test Updates 100% | 1.8 MiB/s | 1.7 MiB | 00m01s
Repositories loaded.
Failed to parse spec file "systemd.spec".
Failed to parse some inputs.
I worked around this by editing out the build deps from the rpmbuild error output.
I have not tried for any other .src.rpm.
Apart from just working, it would have been helpful to know where in the .spec file
it has encountered a problem.
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.
--
_______________________________________________
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