Recently (happened today and happened a month ago), whenever I try to run fedora-review for a Review Request that includes a C/C++ program, the mock build fails immediately due to gcc/g++ not being able to find the annobin plugin. > cc1plus: fatal error: inaccessible plugin file plugin/annobin.so expanded from short plugin name annobin: No such file or directory Downloading the SRPM of the package I want to review, adding "BuildRequires: annobin" and running fedora-review on this modified SRPM works, though obviously it's a rather tedious workaround.

Recently (happened today and happened a month ago), whenever I try to run fedora-review for a Review Request that includes a C/C++ program, the mock build fails immediately due to gcc/g++ not being able to find the annobin plugin. > cc1plus: fatal error: inaccessible plugin file plugin/annobin.so > expanded from short plugin name annobin: No such file or directory Downloading the SRPM of the package I want to review, adding "BuildRequires: annobin" and running fedora-review on this modified SRPM works, though obviously it's a rather tedious workaround. Does anyone else have this problem, or should I be worried about something being broken in my setup?

I had this issue a month ago when reviewing sane-airscan: https://bugzilla.redhat.com/show_bug.cgi?id=1859207 Also a week later, when reviewing wev: https://bugzilla.redhat.com/show_bug.cgi?id=1860772 And today, when I tried to review spirv-llvm-translator: https://bugzilla.redhat.com/show_bug.cgi?id=1869907

Today I tried reviewing some Python packages: - x-tile: https://bugzilla.redhat.com/show_bug.cgi?id=1861020 - python-iptools: https://bugzilla.redhat.com/show_bug.cgi?id=1870907 And the mock build done by fedora-review failed. The error message I got was: > line XX: fg: no job control Which means that RPM didn't recognize the "%py3_build" macro and left it as-is, so bash then saw "%" and tried to do job control and failed. I checked the logs for both failed reviews, and looking at root.log, neither review installed python3-rpm-macros, which is where "%py3_build" and "%py3_install" come from. Now, looking at python3.9.spec, there's this bit: > Requires: (python3-rpm-macros if rpm-build) So right now I'm inclined to think that maybe when fedora-review calls mock, and mock installs BuildRequires, it doesn't install them in the rpm-build context? This would explain both the Python and the C/C++ failures, since like python3-rpm-macros, annobin isn't required for "user" builds, but is used for RPM builds.

- Do you have custom mock configuration in ~/.config/mock.cfg?

- Are files in /etc/mock/ up-to-date, or are there lots of .rpmnew files?

- Does running "mock -r fedora-rawhide-x86_64 clean --scrub all" help?

On Fri, 2020-08-21 at 10:19 +0000, Artur Iwicki wrote: > > - Do you have custom mock configuration in ~/.config/mock.cfg? > No, I don't even have that file. > > > - Are files in /etc/mock/ up-to-date, or are there lots of > > .rpmnew > > files? > mock-core-configs is up to date (32.7-1.fc32), there's no .rpmnew > files. > > > - Does running "mock -r fedora-rawhide-x86_64 clean --scrub all" > > help? > Yes, that helped. I tried nuking /var/lib/mock before, which didn't > help, so I guess clean+scrub-all does something more. Or maybe I > nuked that before updating the mock-core-configs package, so it got > rebuilt using the outdated config. So it is fixed ?

-- Sérgio M. B. _______________________________________________ devel mailing list -- devel(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org 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@lists.fedoraproject.org