Bug 2129272 - update Noto Emoji to Unicode 15
Summary: update Noto Emoji to Unicode 15
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: google-noto-emoji-fonts
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peng Wu
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-23 07:32 UTC by Jens Petersen
Modified: 2022-10-03 00:20 UTC (History)
2 users (show)

Fixed In Version: google-noto-emoji-fonts-20220916-2.fc37
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-10-03 00:20:05 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FC-614 0 None None None 2022-09-23 07:37:57 UTC

Description Jens Petersen 2022-09-23 07:32:32 UTC
Description of problem:
I see upstream released a new version for Unicode 15 a week ago.
It would be good to update Fedora to it now.

https://github.com/googlefonts/noto-emoji/releases/tag/v2.038

Comment 2 Fedora Update System 2022-09-29 08:06:01 UTC
FEDORA-2022-fc92b461b4 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-fc92b461b4

Comment 3 Fedora Update System 2022-09-30 01:13:51 UTC
FEDORA-2022-fc92b461b4 has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-fc92b461b4`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-fc92b461b4

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 4 Fedora Update System 2022-10-03 00:20:05 UTC
FEDORA-2022-fc92b461b4 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.