python-pyftdi fails to build in Fedora rawhide:

Executing(%license): /bin/sh -e /var/tmp/rpm-tmp.9GjBXM
+ umask 022
+ cd /builddir/build/BUILD
+ cd pyftdi-0.44.2
+ LICENSEDIR=/builddir/build/BUILDROOT/python-pyftdi-0.44.2-1.fc33.noarch/usr/share/licenses/python3-pyftdi
+ export LC_ALL=C
+ LC_ALL=C
+ export LICENSEDIR
+ /usr/bin/mkdir -p /builddir/build/BUILDROOT/python-pyftdi-0.44.2-1.fc33.noarch/usr/share/licenses/python3-pyftdi
+ cp -pr pyftdi/doc/licenses.rst /builddir/build/BUILDROOT/python-pyftdi-0.44.2-1.fc33.noarch/usr/share/licenses/python3-pyftdi
cp: cannot stat 'pyftdi/doc/licenses.rst': No such file or directory
+ :
+ RPM_EC=0
++ jobs -p
+ exit 0
error: File not found: /builddir/build/BUILDROOT/python-pyftdi-0.44.2-1.fc33.noarch/usr/share/licenses/python3-pyftdi/licenses.rst
RPM build errors:
    File not found: /builddir/build/BUILDROOT/python-pyftdi-0.44.2-1.fc33.noarch/usr/share/doc/python3-pyftdi/README.rst
    File not found: /builddir/build/BUILDROOT/python-pyftdi-0.44.2-1.fc33.noarch/usr/share/licenses/python3-pyftdi/licenses.rst


It seems like the recent commit was never tested -- please try to test if a package builds before you push it.


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/01260175-python-pyftdi/

For all our attempts to build python-pyftdi with Python 3.9, see:
https://copr.fedorainfracloud.org/coprs/g/python/python3.9/package/python-pyftdi/

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.