Bug 1595244
Summary: | python-PyGithub-1.43.7 is available | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> |
Component: | python-PyGithub | Assignee: | Carl George <carl> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | brian.murrell, carl, ekohlvan, jperrin, jpopelka, mscherer, phracek |
Target Milestone: | --- | Keywords: | FutureFeature, Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | python-PyGithub-1.43.8-1.fc30 | Doc Type: | Enhancement |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-08-15 18:09:52 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Upstream Release Monitoring
2018-06-26 12:27:06 UTC
Please note however bug #1633197 for a patch that fixes a bug since the 1.40 release. It would be much appreciated if that patch could be applied to any update in advance of upstream making another release that includes the fix. This update adds a requirement on requests>=2.14.0, meaning we won't be able to do it for the EPEL branch (only has python-requests-2.6.0-4 and python34-requests-2.12.5-1). Why can't python-requests be updated? It's not that it can't, my statement was a reflection of the current state of things. It would require Red Hat update python-requests in base RHEL 7 to at least 2.14.0. Feel free to open a support case with them to advocate for that. To be clear the update can still take place in the Fedora branches. It would also require EPEL's python3-requests (SRPM of the python34-requests package) to get bumped to at least 2.14.0. The EPEL maintainer could likely be convinced of the need to do that, but it's wasted effort if python-requests in base doesn't get bumped as well. Ahhh. Right. Forgot that python-requests was in base. I wonder if pygithub really does need something as new as 2.14 or if that was just the current version of requests at the time that pygithub was released. Is it worth relaxing the version requirement and see if it works? As an aside, v1.43.2 is the latest now. Latest upstream release: 1.43.2 Current version/release in rawhide: 1.39-3.fc29 URL: https://pypi.python.org/pypi/PyGithub Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/3988/ Blaming setup.py [0] shows the commit that added the requests requirement [1]. That commit is a squash of pull request #664 [2], which contains a commit with a message of "pin requests to 2.14.0 or greater in prep for no_proxy" [3]. Sounds like they are using 2.14+ functionality and not just picking an arbitrary version. [0]: https://github.com/PyGithub/PyGithub/blame/v1.40/setup.py#L107 [1]: https://github.com/PyGithub/PyGithub/commit/9aed19ddbe829af116d7b47494a597f98994a2bc [2]: https://github.com/PyGithub/PyGithub/pull/664 [3]: https://github.com/PyGithub/PyGithub/pull/664/commits/3bbf05c388fa2351c06dc7e8da48dd6ec16aebd8 Latest upstream release: 1.43.5 Current version/release in rawhide: 1.39-5.fc30 URL: https://pypi.python.org/pypi/PyGithub Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/3988/ Latest upstream release: 1.43.6 Current version/release in rawhide: 1.39-6.fc30 URL: https://pypi.python.org/pypi/PyGithub Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/3988/ Latest upstream release: 1.43.7 Current version/release in rawhide: 1.39-6.fc30 URL: https://pypi.python.org/pypi/PyGithub Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/3988/ Could at least the Fedora package be updated to the latest version? I'm missing support for repository topics which 1.43 introduced. Been trying to update Rawhide to the latest (1.43.8) and realized that it requires Deprecated (https://pypi.org/project/Deprecated/) since 1.43.2 (https://github.com/PyGithub/PyGithub/commit/d92389be07e5683d943a23bae2bd5aaa327c5c0a) which is not packaged in Fedora. Review request for https://pypi.org/project/Deprecated/ is here: https://bugzilla.redhat.com/show_bug.cgi?id=1733508 I would be glad for review. Finally, I packaged and build deprecated project. Bodhi updates are available here: Rawhide build: https://koji.fedoraproject.org/koji/buildinfo?buildID=1344025 F30: https://bodhi.fedoraproject.org/updates/FEDORA-2019-36125b005b F29 https://bodhi.fedoraproject.org/updates/FEDORA-2019-1566111aa0 Tests also need httpretty==0.9.6 (https://github.com/PyGithub/PyGithub/blob/master/test-requirements.txt) so waiting for https://src.fedoraproject.org/rpms/python-httpretty/pull-requests as well. FEDORA-2019-aa6a4f29a7 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-aa6a4f29a7 python-PyGithub-1.43.8-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-aa6a4f29a7 python-PyGithub-1.43.8-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report. |