Releases retrieved: 4.17.12, 4.18.8, 4.19.1 Upstream release that is considered latest: 4.19.1 Current version/release in rawhide: 4.19.0-1.fc40 URL: https://www.samba.org/ 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/4758/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/samba
Created attachment 1993264 [details] Update to 4.19.1 (#2243073)
the-new-hotness/release-monitoring.org's scratch build of samba-4.19.1-1.fc38.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=107319069
FEDORA-2023-99444e494b has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-99444e494b
FEDORA-2023-7eb8cbf1a5 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-7eb8cbf1a5
FEDORA-2023-99444e494b 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-99444e494b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-99444e494b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-8c9251e479 has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.