Description of problem: Package openvswitch fails to build from source in Fedora rawhide. Not sure if this is the actual problem, since it says "warning" and not "error": troff: /usr/share/groff/1.22.4/tmac/troffrc:53: warning: can't find macro file 'pdfpic.tmac' troff: /usr/share/groff/1.22.4/tmac/troffrc:53: warning: can't find macro file 'pdfpic.tmac' troff: /usr/share/groff/1.22.4/tmac/troffrc:53: warning: can't find macro file 'pdfpic.tmac' troff: /usr/share/groff/1.22.4/tmac/troffrc:53: warning: can't find macro file 'pdfpic.tmac' troff: /usr/share/groff/1.22.4/tmac/troffrc:53: warning: can't find macro file 'pdfpic.tmac' troff: /usr/share/groff/1.22.4/tmac/troffrc:53: warning: can't find macro file 'pdfpic.tmac' make[2]: *** [Makefile:7760: manpage-check] Error 1 Version-Release number of selected component (if applicable): 2.12.0-2.fc33 2.13.0-1.fc33 Steps to Reproduce: fedpkg build --scratch Additional info: This package is tracked by Koschei. See: https://koschei.fedoraproject.org/package/openvswitch This blocks the Python 3.9 rebuild. For the build logs with Python 3.9, see: https://copr-be.cloud.fedoraproject.org/results/@python/python3.9/fedora-rawhide-x86_64/01330259-openvswitch/ For all our attempts to build openvswitch with Python 3.9, see: https://copr.fedorainfracloud.org/coprs/g/python/python3.9/package/openvswitch/ Testing and mass rebuild of packages is happening in copr. You can follow these instructions to test locally in mock if your package builds with Python 3.9: https://copr.fedorainfracloud.org/coprs/g/python/python3.9/ Let us know here if you have any questions. Python 3.9 will be included in Fedora 33. To make that update smoother, we're building Fedora packages with early pre-releases of Python 3.9. A build failure prevents us from testing all dependent packages (transitive [Build]Requires), so if this package is required a lot, it's important for us to get it fixed soon. We'd appreciate help from the people who know this package best, but if you don't want to work on this now, let us know so we can try to work around it on our side.
Could you please have a look?
It was already fixed in https://koji.fedoraproject.org/koji/buildinfo?buildID=1491064
Indeed. Sorry for the noise.