Bug 2077274

Summary: python-bloom-0.11.1 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: python-bloomAssignee: Scott K Logan <logans>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: logans, richmattes, robotics
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-bloom-0.11.1-1.fc37 python-bloom-0.11.1-1.fc34 python-bloom-0.11.1-1.fc35 python-bloom-0.11.1-1.el7 python-bloom-0.11.1-1.el8 python-bloom-0.11.1-1.fc36 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-04-22 17:42:53 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 0.11.0 (#2077274)
none
Update to 0.11.1 (#2077274) none

Description Upstream Release Monitoring 2022-04-20 20:45:21 UTC
Latest upstream release: 0.11.0
Current version/release in rawhide: 0.10.7-4.fc36
URL: https://github.com/ros-infrastructure/bloom

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

Comment 1 Upstream Release Monitoring 2022-04-20 20:45:26 UTC
Created attachment 1873953 [details]
Update to 0.11.0 (#2077274)

Comment 2 Upstream Release Monitoring 2022-04-20 20:50:40 UTC
the-new-hotness/release-monitoring.org's scratch build of python-bloom-0.11.0-1.fc34.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=85989496

Comment 3 Upstream Release Monitoring 2022-04-22 01:54:08 UTC
Latest upstream release: 0.11.1
Current version/release in rawhide: 0.10.7-4.fc36
URL: https://github.com/ros-infrastructure/bloom

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

Comment 4 Upstream Release Monitoring 2022-04-22 01:54:11 UTC
Created attachment 1874303 [details]
Update to 0.11.1 (#2077274)

Comment 5 Upstream Release Monitoring 2022-04-22 02:00:23 UTC
the-new-hotness/release-monitoring.org's scratch build of python-bloom-0.11.1-1.fc34.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=86054565

Comment 6 Fedora Update System 2022-04-22 17:41:50 UTC
FEDORA-2022-4de59c74c5 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-4de59c74c5

Comment 7 Fedora Update System 2022-04-22 17:42:53 UTC
FEDORA-2022-4de59c74c5 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2022-04-22 18:33:10 UTC
FEDORA-2022-33fb292819 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-33fb292819

Comment 9 Fedora Update System 2022-04-22 18:33:11 UTC
FEDORA-2022-08f6ff6f61 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-08f6ff6f61

Comment 10 Fedora Update System 2022-04-22 18:33:12 UTC
FEDORA-2022-3ab13c2c5f has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-3ab13c2c5f

Comment 11 Fedora Update System 2022-04-22 18:33:13 UTC
FEDORA-EPEL-2022-2dbb87348b has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-2dbb87348b

Comment 12 Fedora Update System 2022-04-22 18:33:14 UTC
FEDORA-EPEL-2022-6f21edf44a has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-6f21edf44a

Comment 13 Fedora Update System 2022-04-23 17:13:54 UTC
FEDORA-2022-33fb292819 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-33fb292819`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-33fb292819

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

Comment 14 Fedora Update System 2022-04-23 18:42:24 UTC
FEDORA-2022-08f6ff6f61 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-2022-08f6ff6f61`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-08f6ff6f61

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

Comment 15 Fedora Update System 2022-04-23 19:06:53 UTC
FEDORA-2022-3ab13c2c5f 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-2022-3ab13c2c5f`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-3ab13c2c5f

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

Comment 16 Fedora Update System 2022-04-23 19:51:02 UTC
FEDORA-EPEL-2022-6f21edf44a 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-2022-6f21edf44a

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

Comment 17 Fedora Update System 2022-04-23 19:56:49 UTC
FEDORA-EPEL-2022-2dbb87348b has been pushed to the Fedora EPEL 7 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-2dbb87348b

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

Comment 18 Fedora Update System 2022-05-01 19:23:13 UTC
FEDORA-2022-08f6ff6f61 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 19 Fedora Update System 2022-05-01 19:39:18 UTC
FEDORA-2022-3ab13c2c5f has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 20 Fedora Update System 2022-05-01 20:26:23 UTC
FEDORA-EPEL-2022-2dbb87348b has been pushed to the Fedora EPEL 7 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 21 Fedora Update System 2022-05-01 20:37:52 UTC
FEDORA-EPEL-2022-6f21edf44a has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 22 Fedora Update System 2022-05-07 04:30:03 UTC
FEDORA-2022-33fb292819 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.