Bug 2244390

Summary: update Noto Serif CJK to 2.002 release
Product: [Fedora] Fedora Reporter: Jens Petersen <petersen>
Component: google-noto-serif-cjk-vf-fontsAssignee: Peng Wu <pwu>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 39CC: pwu
Target Milestone: ---Flags: petersen: mirror+
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: google-noto-serif-cjk-vf-fonts-2.002-2.fc38 google-noto-serif-cjk-vf-fonts-2.002-2.fc39 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-10-20 00:41:17 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:

Description Jens Petersen 2023-10-16 10:41:19 UTC 
https://github.com/notofonts/noto-cjk/releases/tag/Serif2.002

See also https://github.com/notofonts/noto-cjk/issues/252 for more context.

Reproducible: Always
Comment 1 Peng Wu 2023-10-17 02:19:24 UTC 
Bodhi URL:
https://bodhi.fedoraproject.org/updates/FEDORA-2023-67ec21519f
https://bodhi.fedoraproject.org/updates/FEDORA-2023-7ecd9f2bfc
Comment 2 Jens Petersen 2023-10-17 11:30:42 UTC 
Thanks for the quick turnaround, Peng :-)
Comment 3 Fedora Update System 2023-10-18 03:47:11 UTC 
FEDORA-2023-67ec21519f has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-67ec21519f
Comment 4 Fedora Update System 2023-10-18 03:52:14 UTC 
FEDORA-2023-7ecd9f2bfc has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-7ecd9f2bfc
Comment 5 Fedora Update System 2023-10-20 00:41:17 UTC 
FEDORA-2023-67ec21519f has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 6 Fedora Update System 2023-11-03 18:35:10 UTC 
FEDORA-2023-7ecd9f2bfc has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.