Releases retrieved: 5.012 Upstream release that is considered latest: 5.012 Current version/release in rawhide: 5.011-2.fc42 URL: https://metacpan.org/dist/DBD-mysql/ 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/2807/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/perl-DBD-MySQL
FEDORA-2025-24e1bad309 (perl-DBD-MySQL-5.012-1.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-24e1bad309
FEDORA-2025-8f443ddcab (perl-DBD-MySQL-5.012-1.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-8f443ddcab
FEDORA-2025-24e1bad309 (perl-DBD-MySQL-5.012-1.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-8f443ddcab has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-8f443ddcab` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-8f443ddcab See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-8f443ddcab (perl-DBD-MySQL-5.012-1.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.