Bug 1371027 - Request to add google-noto-cjk-fonts to EPEL 7
Summary: Request to add google-noto-cjk-fonts to EPEL 7
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: google-noto-cjk-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: 2016-08-29 08:02 UTC by fenglc
Modified: 2016-09-19 03:19 UTC (History)
1 user (show)

Fixed In Version: google-noto-cjk-fonts-1.004-5.el7
Clone Of:
Environment:
Last Closed: 2016-09-19 03:19:36 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description fenglc 2016-08-29 08:02:10 UTC
Description of problem:

The package is not available for EPEL 7.

Version-Release number of selected component (if applicable):

none

How reproducible:

100%

Steps to Reproduce:
1. yum install epel-release
2. yum search google-noto-cjk-fonts

Actual results:

"No matches found for: google-noto-cjk-fonts."

Expected results:

Being able to install google-noto-cjk-fonts.

Additional info:

CentOS Linux 7

Comment 1 Fedora Update System 2016-08-30 07:29:39 UTC
google-noto-cjk-fonts-1.004-5.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-1819dfcce4

Comment 2 Fedora Update System 2016-08-31 13:49:26 UTC
google-noto-cjk-fonts-1.004-5.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-1819dfcce4

Comment 3 Fedora Update System 2016-09-19 03:19:34 UTC
google-noto-cjk-fonts-1.004-5.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, 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.