Bug 1768164 - python-async-timeout-4.0.1 is available
Summary: python-async-timeout-4.0.1 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: python-async-timeout
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Igor Raits
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1759906
TreeView+ depends on / blocked
 
Reported: 2019-11-03 04:55 UTC by Upstream Release Monitoring
Modified: 2021-12-30 01:42 UTC (History)
3 users (show)

Fixed In Version: python-async-timeout-4.0.1-1.fc36 python-async-timeout-4.0.1-1.fc34
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-25 07:28:18 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
[patch] Update to 4.0.0a0 (#1768164) (1.17 KB, patch)
2019-11-03 04:55 UTC, Upstream Release Monitoring
no flags Details | Diff
[patch] Update to 4.0.0a1 (#1768164) (1.17 KB, patch)
2019-11-11 21:53 UTC, Upstream Release Monitoring
no flags Details | Diff
[patch] Update to 4.0.0a2 (#1768164) (1.17 KB, patch)
2019-11-11 22:05 UTC, Upstream Release Monitoring
no flags Details | Diff

Description Upstream Release Monitoring 2019-11-03 04:55:10 UTC
Latest upstream release: 4.0.0a0
Current version/release in rawhide: 3.0.1-6.fc32
URL: https://github.com/aio-libs/async-timeout

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/12525/

Comment 1 Upstream Release Monitoring 2019-11-03 04:55:15 UTC
Created attachment 1632044 [details]
[patch] Update to 4.0.0a0 (#1768164)

Comment 2 Upstream Release Monitoring 2019-11-03 04:58:44 UTC
the-new-hotness/release-monitoring.org's scratch build of python-async-timeout-4.0.0a0-1.fc29.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=38726343

Comment 3 Upstream Release Monitoring 2019-11-11 21:53:52 UTC
Latest upstream release: 4.0.0a1
Current version/release in rawhide: 3.0.1-6.fc32
URL: https://github.com/aio-libs/async-timeout

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/12525/

Comment 4 Upstream Release Monitoring 2019-11-11 21:53:56 UTC
Created attachment 1635083 [details]
[patch] Update to 4.0.0a1 (#1768164)

Comment 5 Upstream Release Monitoring 2019-11-11 22:05:04 UTC
Latest upstream release: 4.0.0a2
Current version/release in rawhide: 3.0.1-6.fc32
URL: https://github.com/aio-libs/async-timeout

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/12525/

Comment 6 Upstream Release Monitoring 2019-11-11 22:05:09 UTC
Created attachment 1635092 [details]
[patch] Update to 4.0.0a2 (#1768164)

Comment 7 Upstream Release Monitoring 2020-10-24 16:12:49 UTC
Latest upstream release: 4.0.0a3
Current version/release in rawhide: 3.0.1-10.fc33
URL: https://github.com/aio-libs/async-timeout

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/12525/

Comment 8 Upstream Release Monitoring 2021-11-11 10:57:45 UTC
Latest upstream release: 4.0.1
Current version/release in rawhide: 3.0.1-14.fc35
URL: https://github.com/aio-libs/async-timeout

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/12525/

Comment 9 Fedora Update System 2021-11-25 07:25:36 UTC
FEDORA-2021-d4986cb594 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2021-d4986cb594

Comment 10 Fedora Update System 2021-11-25 07:28:18 UTC
FEDORA-2021-d4986cb594 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 11 Fedora Update System 2021-12-21 19:37:17 UTC
FEDORA-2021-4a0ac5bbee has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-4a0ac5bbee

Comment 12 Fedora Update System 2021-12-21 19:37:58 UTC
FEDORA-2021-03f88f11f6 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-03f88f11f6

Comment 13 Fedora Update System 2021-12-22 01:20:00 UTC
FEDORA-2021-03f88f11f6 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-03f88f11f6`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-03f88f11f6

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

Comment 14 Fedora Update System 2021-12-22 01:37:17 UTC
FEDORA-2021-4a0ac5bbee 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-4a0ac5bbee`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-4a0ac5bbee

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

Comment 15 Fedora Update System 2021-12-30 01:42:40 UTC
FEDORA-2021-03f88f11f6 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.