Bug 2252482

Summary: python-drgn-0.0.25 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: python-drgnAssignee: Davide Cavalca <davide>
Status: CLOSED ERRATA QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: davide, filbranden, michel, osandov
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-drgn-0.0.25-1.fc40 python-drgn-0.0.25-1.fc39 python-drgn-0.0.25-1.fc38 python-drgn-0.0.25-1.el8 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-12-02 00:00:46 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 2023-12-01 23:16:03 UTC
Releases retrieved: 0.0.25
Upstream release that is considered latest: 0.0.25
Current version/release in rawhide: 0.0.24-1.fc40
URL: https://pypi.org/project/drgn/0.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/62624/


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

Comment 1 Fedora Update System 2023-12-01 23:59:49 UTC
FEDORA-2023-39e9e94df7 has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2023-39e9e94df7

Comment 2 Fedora Update System 2023-12-02 00:00:46 UTC
FEDORA-2023-39e9e94df7 has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 3 Fedora Update System 2023-12-02 00:01:55 UTC
FEDORA-2023-1f42616621 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-1f42616621

Comment 4 Fedora Update System 2023-12-02 00:02:04 UTC
FEDORA-2023-4bc723312e has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-4bc723312e

Comment 5 Fedora Update System 2023-12-02 00:02:09 UTC
FEDORA-2023-e22d1fdb6d has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-e22d1fdb6d

Comment 6 Fedora Update System 2023-12-02 00:02:23 UTC
FEDORA-EPEL-2023-aa1d881f6a has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-aa1d881f6a

Comment 7 Fedora Update System 2023-12-02 00:02:34 UTC
FEDORA-EPEL-2023-ecf364281d has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-ecf364281d

Comment 8 Fedora Update System 2023-12-02 01:34:02 UTC
FEDORA-2023-4bc723312e 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-4bc723312e`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-4bc723312e

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

Comment 9 Fedora Update System 2023-12-02 01:35:55 UTC
FEDORA-EPEL-2023-aa1d881f6a has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-aa1d881f6a

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

Comment 10 Fedora Update System 2023-12-02 02:09:13 UTC
FEDORA-2023-1f42616621 has been pushed to the Fedora 39 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-1f42616621`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-1f42616621

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

Comment 11 Fedora Update System 2023-12-02 02:42:32 UTC
FEDORA-EPEL-2023-ecf364281d 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-2023-ecf364281d

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

Comment 12 Fedora Update System 2023-12-02 02:45:40 UTC
FEDORA-2023-e22d1fdb6d 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-e22d1fdb6d`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-e22d1fdb6d

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

Comment 13 Fedora Update System 2023-12-06 01:40:20 UTC
FEDORA-2023-1f42616621 has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 14 Fedora Update System 2023-12-06 01:46:22 UTC
FEDORA-2023-4bc723312e has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 15 Fedora Update System 2023-12-06 02:00:59 UTC
FEDORA-EPEL-2023-ecf364281d has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.