Releases retrieved: 9.18.39 Upstream release that is considered latest: 9.18.39 Current version/release in rawhide: 9.18.38-1.fc44 URL: https://www.isc.org/bind/ 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/242117/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/bind
Created attachment 2104189 [details] Update to 9.18.39 (#2389765)
the-new-hotness/release-monitoring.org's scratch build of bind-9.18.39-1.fc40.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=136271132
FEDORA-2025-1b15972c16 (bind-9.18.39-2.fc44 and bind-dyndb-ldap-11.11-7.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2025-1b15972c16
FEDORA-2025-38c04b3b25 (bind-9.18.39-2.fc43 and bind-dyndb-ldap-11.11-7.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-38c04b3b25
FEDORA-2025-5b1c106084 (bind-9.18.39-2.fc42 and bind-dyndb-ldap-11.11-6.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-5b1c106084
FEDORA-2025-38c04b3b25 has been pushed to the Fedora 43 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-38c04b3b25` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-38c04b3b25 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-5b1c106084 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-5b1c106084` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-5b1c106084 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-5b1c106084 (bind-9.18.39-2.fc42 and bind-dyndb-ldap-11.11-6.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-1b15972c16 (bind-9.18.39-2.fc44 and bind-dyndb-ldap-11.11-7.fc44) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-4922878d8c (bind-9.18.39-3.fc41.1 and bind-dyndb-ldap-11.10-34.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2025-4922878d8c
FEDORA-2025-4922878d8c has been pushed to the Fedora 41 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-4922878d8c` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-4922878d8c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-4922878d8c (bind-9.18.39-3.fc41.1 and bind-dyndb-ldap-11.10-34.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-38c04b3b25 (bind-9.18.39-4.fc43 and bind-dyndb-ldap-11.11-7.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.