Fedora Account System
Red Hat Associate
Red Hat Customer
With support for Unicode 17. I suggest we stop using the snapshot versioning and follow the upstream release versions, which are being released consistently. https://github.com/googlefonts/noto-emoji/releases Reproducible: Always
https://bodhi.fedoraproject.org/updates/FEDORA-2026-c0baf8d5c9 (In reply to Jens Petersen from comment #0) > With support for Unicode 17. > > I suggest we stop using the snapshot versioning and follow the upstream > release versions, which are being released consistently. > > https://github.com/googlefonts/noto-emoji/releases Oh, I didn't read carefully enough and forgot about changing the snapshot versioning. The black and white font included has a different version number: commit 110e2bf10d729a67c323bf11ebdfbb1cb97a9950 (HEAD -> rawhide, origin/rawhide, origin/main, mfabian/rawhide) Author: Mike FABIAN <mfabian> Date: Tue May 26 11:04:43 2026 +0200 Update to v2.051 - and update the black and white font Noto Emoji from Version 3.003 to 3.005.
(In reply to Mike FABIAN from comment #1) > The black and white font included has a different version number: : > Update to v2.051 > > - and update the black and white font Noto Emoji from Version 3.003 to 3.005. I see - but i feel it is okay to use the version tagged in upstream github and used for the tarball. Our current versioning is also incompatible with Anitya (https://release-monitoring.org/project/10556/) and so we do not get notified about new releases.
(In reply to Jens Petersen from comment #2) > (In reply to Mike FABIAN from comment #1) > > The black and white font included has a different version number: > : > > Update to v2.051 > > > > - and update the black and white font Noto Emoji from Version 3.003 to 3.005. > > I see - but i feel it is okay to use the version tagged in upstream github > and used for the tarball. > > Our current versioning is also incompatible with Anitya > (https://release-monitoring.org/project/10556/) and so we do not get > notified about new releases. Yes, especially because the black and white font with the different version comes from elsewhere. I found the updated Noto_Emoji.zip for the black and white font for Unicode 17 here: https://fonts.google.com/noto/specimen/Noto+Emoji I didn't yet find a git repo where that black and white font comes from. If I change the version number scheme, do I need to introduce `Epoch: 1` in the .spec file? Or does that work without?
I think we should actually repackage then: splitting into 2 source packages. We should ask upsteam about the Mono fonts. Yes, Epoch will be required. Please check with Akira.
(In reply to Jens Petersen from comment #4) > I think we should actually repackage then: splitting into 2 source packages. > We should ask upsteam about the Mono fonts. Yes, Epoch will be required. > > Please check with Akira. Maybe we should as the black-and-white emoji font is no longer shipped with the same archive file.
Jens’ upstream issue asking for a repo for the monochrome font: https://github.com/googlefonts/noto-emoji/issues/548
Pull request to remove the color font from google-noto-emoji-fonts: https://src.fedoraproject.org/rpms/google-noto-emoji-fonts/pull-request/19 Review request for the new google-noto-color-emoji-fonts package: https://bugzilla.redhat.com/show_bug.cgi?id=2510687
This bug appears to have been reported against 'rawhide' during the Fedora Linux 45 development cycle. Changing version to 45.
FEDORA-2026-bf5fba986d (google-noto-color-emoji-fonts-2.051-1.fc46 and google-noto-emoji-fonts-3.005-1.fc46) has been submitted as an update to Fedora 46. https://bodhi.fedoraproject.org/updates/FEDORA-2026-bf5fba986d
FEDORA-2026-bf5fba986d (google-noto-color-emoji-fonts-2.051-1.fc46 and google-noto-emoji-fonts-3.005-1.fc46) has been pushed to the Fedora 46 stable repository. If problem still persists, please make note of it in this bug report.