Bug 2404204

Summary: samba-4.23.2 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: sambaAssignee: Guenther Deschner <gdeschner>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: abokovoy, anoopcs, asn, gdeschner, pfilipen, sbose, ssorce
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: samba-4.23.2-1.fc44 samba-4.23.2-1.fc43 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-10-21 00:36:39 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 4.23.2 (#2404204)
none
Update to 4.23.2 (#2404204) none

Description Upstream Release Monitoring 2025-10-15 14:34:45 UTC 
Releases retrieved: 4.21.9, 4.22.5, 4.23.2
Upstream release that is considered latest: 4.23.2
Current version/release in rawhide: 4.23.1-1.fc44
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
Comment 1 Upstream Release Monitoring 2025-10-15 14:35:13 UTC 
Created attachment 2109838 [details]
Update to 4.23.2 (#2404204)
Comment 2 Upstream Release Monitoring 2025-10-15 14:45:14 UTC 
the-new-hotness/release-monitoring.org's scratch build of samba-4.23.2-1.fc40.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=138170672
Comment 3 Upstream Release Monitoring 2025-10-16 15:23:27 UTC 
Created attachment 2109948 [details]
Update to 4.23.2 (#2404204)
Comment 4 Upstream Release Monitoring 2025-10-16 15:31:31 UTC 
the-new-hotness/release-monitoring.org's scratch build of samba-4.23.2-1.fc40.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=138202665
Comment 5 Fedora Update System 2025-10-20 17:22:26 UTC 
FEDORA-2025-5f46b27e1c (samba-4.23.2-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-5f46b27e1c
Comment 6 Fedora Update System 2025-10-20 18:04:17 UTC 
FEDORA-2025-3ddbddd7e2 (samba-4.23.2-1.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-3ddbddd7e2
Comment 7 Fedora Update System 2025-10-21 00:36:39 UTC 
FEDORA-2025-3ddbddd7e2 (samba-4.23.2-1.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 8 Fedora Update System 2025-10-21 01:59:24 UTC 
FEDORA-2025-5f46b27e1c 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-5f46b27e1c`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-5f46b27e1c

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 9 Fedora Update System 2025-10-25 21:11:53 UTC 
FEDORA-2025-5f46b27e1c (samba-4.23.2-1.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.