Bug 1908662 - update to Emoji 13.1
Summary: update to Emoji 13.1
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: 2020-12-17 09:46 UTC by Jens Petersen
Modified: 2021-01-02 01:09 UTC (History)
2 users (show)

Fixed In Version: google-noto-emoji-fonts-20200916-1.fc33
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-02 01:09:03 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Jens Petersen 2020-12-17 09:46:27 UTC 
Description of problem:
The current Fedora package should correspond to Emoji 13.0.

The latest upstream release is Emoji 13.1.
https://github.com/googlefonts/noto-emoji/releases/tag/v2020-09-16-unicode13_1

It would be good to update the package to the latest release.
Comment 1 Peng Wu 2020-12-28 07:48:42 UTC 
Switched to use %pypi_source macro in the nototools package.
Comment 2 Fedora Update System 2020-12-28 07:54:23 UTC 
FEDORA-2020-174120729f has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-174120729f
Comment 3 Fedora Update System 2020-12-29 01:57:48 UTC 
FEDORA-2020-174120729f has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-174120729f`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-174120729f

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 4 Fedora Update System 2021-01-02 01:09:03 UTC 
FEDORA-2020-174120729f has been pushed to the Fedora 33 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.