https://bugzilla.redhat.com/show_bug.cgi?id=2092637
--- Comment #2 from Major Hayden 🤠 mhayden@redhat.com --- (In reply to Benson Muite from comment #1)
FURTHER COMMENTS
- Can
rm -f %{buildroot}%{_bindir}/fixup*.py be replaced by rm -f %{buildroot}%{_bindir}/fixup_pubsub_v1_keywords.py to indicate the specific file being removed
Fixed that. I had copied that over from another spec while I was testing this one.
- A copr build would be helpful to verify it works on more architectures
Done! https://copr.fedorainfracloud.org/coprs/mhayden/python-google-cloud/build/44...
- Is libcst needed for extras?
Fixed.
- Seems not compatible with Fedora 35:
https://github.com/googleapis/python-pubsub/blob/main/setup.py#L36 https://packages.fedoraproject.org/pkgs/python-google-api-core/python3- google-api-core/
Yes, there's an ongoing issue in F35 right now that has something to do with protobuf, proto-plus, or iam-v1. I've been talking to the folks in #fedora-python to hunt that down.
- There is more documentation at
https://github.com/googleapis/python-pubsub/tree/main/docs which is also online at https://cloud.google.com/python/docs/reference/pubsub/latest though the README provides basic information, so this need not be packaged.
I was packaging the docs previously for these google cloud packages, but then I ended up in some challenging situations with sphinx trying to refer to other bits of documentation that it couldn't reach during an RPM build.
SRPM URL: https://download.copr.fedorainfracloud.org/results/mhayden/python-google-clo... Spec URL: https://download.copr.fedorainfracloud.org/results/mhayden/python-google-clo...