Bug 1996607
| Summary: | python-flexmock-0.10.8 is available | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> | ||||||
| Component: | python-flexmock | Assignee: | Lumír Balhar <lbalhar> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | rawhide | CC: | hcsomort, jpopelka, kevin, lbalhar, python-sig, slavek.kabrda | ||||||
| Target Milestone: | --- | Keywords: | FutureFeature, Triaged | ||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | python-flexmock-0.10.8-1.fc36 python-flexmock-0.10.8-1.el8 python-flexmock-0.10.8-1.fc34 python-flexmock-0.10.8-1.fc33 python-flexmock-0.10.8-1.fc35 | Doc Type: | If docs needed, set a value | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2021-08-30 09:49:54 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: | |||||||||
| Attachments: |
|
||||||||
|
Description
Upstream Release Monitoring
2021-08-23 10:10:06 UTC
Created attachment 1816807 [details]
[patch] Update to 0.10.7 (#1996607)
the-new-hotness/release-monitoring.org's scratch build of python-flexmock-0.10.7-1.fc32.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=74382596 This introduces some issues when mocking 'os' and 'sys': https://github.com/flexmock/flexmock/issues/73 Let's wait for the next minor release to become available. Latest upstream release: 0.10.8 Current version/release in rawhide: 0.10.6-1.fc36 URL: https://pypi.python.org/pypi/flexmock Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/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/3871/ Created attachment 1818505 [details]
[patch] Update to 0.10.8 (#1996607)
the-new-hotness/release-monitoring.org's scratch build of python-flexmock-0.10.8-1.fc32.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=74653825 FEDORA-2021-c72f4e0679 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2021-c72f4e0679 FEDORA-2021-c72f4e0679 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2021-614e9c7afc has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-614e9c7afc FEDORA-2021-eab09ff86e has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-eab09ff86e FEDORA-2021-e805f839f3 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-e805f839f3 FEDORA-EPEL-2021-dd8645ca16 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-dd8645ca16 FEDORA-2021-614e9c7afc has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-614e9c7afc` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-614e9c7afc See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2021-dd8645ca16 has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-dd8645ca16 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-e805f839f3 has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-e805f839f3` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-e805f839f3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-eab09ff86e has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-eab09ff86e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-eab09ff86e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2021-dd8645ca16 has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2021-eab09ff86e has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2021-e805f839f3 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2021-eab09ff86e has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2021-614e9c7afc has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report. |