Richard Shaw wrote on 2022/07/21 10:52:
Looking at brasero I can build "fine" doing a fedpkg mockbuild but adding "--enablerepo=local" replicates the failure seen in koji[1]. I tried comparing the root logs between the two to see what's different but I don't find the results particularly helpful: lua-libs-5.4.4-3.fc37.x86_64 vs lua-libs-5.4.4-2.fc37.x86_64 setup-2.14.1-1.fc37.noarch vs setup-2.13.10-1.fc37.noarch python-srpm-macros-3.11-3.fc37.noarch vs python-srpm-macros-3.11-1.fc37.noarch The error messages themselves seem like something that should have been caught some time ago (not just newer gcc error checking). Any ideas? Thanks, Richard [1] https://kojipkgs.fedoraproject.org//work/tasks/7772/89767772/build.log
Would you check what "nautilus" is used when build of brasero gets fine? koji says "nautilus" goes 42.2 -> 43~alpha, with switching gtk3 -> gtk4. And brasero seems to be compiling with gtk3, but when compiling nautilus-burn-extension.c in brasero, it tries to include gtk4 header, while successful build (on eln: https://koji.fedoraproject.org/koji/buildinfo?buildID=1992598) tries to include gtk3 header when compiling nautilus-burn-extension.c . Regards, Mamoru _______________________________________________ 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 on the list, report it: https://pagure.io/fedora-infrastructure
