Bug 2497174

Summary: tzclock-4.7 is available
Product: [Fedora] Fedora Reporter: Artur Frenszek-Iwicki <fedora>
Component: tzclockAssignee: Mamoru TASAKA <mtasaka>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 45CC: mtasaka
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tzclock-4.9-1.fc46 tzclock-4.9-1.fc45 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2026-08-20 02:11:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2497173    
Bug Blocks:    

Description Artur Frenszek-Iwicki 2026-07-05 17:29:14 UTC 
tzclock-4.7 is now available.
https://theknight.co.uk/download.html

The version currently in Fedora is tzclock-3.1.7-18.fc44.
Comment 1 Aoife Moloney 2026-08-17 15:14:19 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora Linux 45 development cycle.
Changing version to 45.
Comment 2 Fedora Update System 2026-08-20 02:07:46 UTC 
FEDORA-2026-291bbde9a4 (tzclock-4.9-1.fc46) has been submitted as an update to Fedora 46.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-291bbde9a4
Comment 3 Fedora Update System 2026-08-20 02:11:29 UTC 
FEDORA-2026-291bbde9a4 (tzclock-4.9-1.fc46) has been pushed to the Fedora 46 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 4 Fedora Update System 2026-08-20 02:32:17 UTC 
FEDORA-2026-445ddd6a02 (libdial-2.7-1.fc45 and tzclock-4.9-1.fc45) has been submitted as an update to Fedora 45.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-445ddd6a02
Comment 5 Fedora Update System 2026-08-20 02:35:24 UTC 
FEDORA-2026-445ddd6a02 (libdial-2.7-1.fc45 and tzclock-4.9-1.fc45) has been pushed to the Fedora 45 stable repository.
If problem still persists, please make note of it in this bug report.