Bug 2212846

Summary: python-cs-3.2.0 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: python-csAssignee: Roman Inflianskas <rominf>
Status: CLOSED ERRATA QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: italo.garcia+fedora, paul.wouters, rj.layco, rominf
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-cs-3.2.0-1.fc39 python-cs-3.2.0-1.fc37 python-cs-3.2.0-1.fc38 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-06-22 10:24:06 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 Flags
Update to 3.1.0 (#2212846)
none
Update to 3.2.0 (#2212846) none

Description Upstream Release Monitoring 2023-06-06 14:13:42 UTC
Releases retrieved: 3.1.0
Upstream release that is considered latest: 3.1.0
Current version/release in rawhide: 3.0.0-8.fc38
URL: https://pypi.org/project/cs/3.0.0

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://docs.fedoraproject.org/en-US/package-maintainers/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/93807/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/python-cs

Comment 1 Upstream Release Monitoring 2023-06-06 14:13:56 UTC
Created attachment 1969317 [details]
Update to 3.1.0 (#2212846)

Comment 2 Upstream Release Monitoring 2023-06-06 14:22:19 UTC
the-new-hotness/release-monitoring.org's scratch build of python-cs-3.1.0-1.fc38.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=101871861

Comment 3 Roman Inflianskas 2023-06-21 09:44:54 UTC
Failing tests prevent me from packaging: https://github.com/exoscale/cs/issues/125.

Comment 4 Upstream Release Monitoring 2023-06-22 08:08:42 UTC
Releases retrieved: 3.2.0
Upstream release that is considered latest: 3.2.0
Current version/release in rawhide: 3.0.0-8.fc38
URL: https://pypi.org/project/cs/3.0.0

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://docs.fedoraproject.org/en-US/package-maintainers/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/93807/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/python-cs

Comment 5 Upstream Release Monitoring 2023-06-22 08:08:47 UTC
Created attachment 1972019 [details]
Update to 3.2.0 (#2212846)

Comment 6 Upstream Release Monitoring 2023-06-22 08:13:11 UTC
the-new-hotness/release-monitoring.org's scratch build of python-cs-3.2.0-1.fc38.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=102443405

Comment 7 Fedora Update System 2023-06-22 10:22:45 UTC
FEDORA-2023-ff5ff97aa6 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-ff5ff97aa6

Comment 8 Fedora Update System 2023-06-22 10:24:06 UTC
FEDORA-2023-ff5ff97aa6 has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2023-06-22 10:33:03 UTC
FEDORA-2023-408e96e55a has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-408e96e55a

Comment 10 Fedora Update System 2023-06-22 10:39:21 UTC
FEDORA-2023-63fb44f7db has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-63fb44f7db

Comment 11 Fedora Update System 2023-06-23 01:51:01 UTC
FEDORA-2023-408e96e55a has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-408e96e55a`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-408e96e55a

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 12 Fedora Update System 2023-06-23 01:51:36 UTC
FEDORA-2023-63fb44f7db has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-63fb44f7db`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-63fb44f7db

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 13 Fedora Update System 2023-07-01 00:37:17 UTC
FEDORA-2023-63fb44f7db has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 14 Fedora Update System 2023-07-01 01:44:46 UTC
FEDORA-2023-408e96e55a has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.