Bug 1282587 - subpackage fontawesome-web should provide font(fontawesome-web)
subpackage fontawesome-web should provide font(fontawesome-web)
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: fontawesome-fonts (Show other bugs)
rawhide
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Petr Vobornik
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-11-16 14:56 EST by Piotr Popieluch
Modified: 2015-11-17 03:50 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-11-17 03:50:36 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Piotr Popieluch 2015-11-16 14:56:49 EST
Description of problem:

fontawesome provides font(fontawesome) but subpackage fontawesome-web does not provide a font() package:

rpm --provides -qp fontawesome-fonts-4.4.0-2.fc24.noarch.rpm
config(fontawesome-fonts) = 4.4.0-2.fc24
font(fontawesome)
fontawesome-fonts = 4.4.0-2.fc24

rpm --provides -qp noarch/fontawesome-fonts-web-4.4.0-2.fc24.noarch.rpm
fontawesome-fonts-web = 4.4.0-2.fc24


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
provide font(fontawesome-web)

Additional info:
Comment 1 Nicolas Mailhot 2015-11-17 02:49:06 EST
Please never do that, the font() provides have very specific meaning: the font is installed in the system font repository in a general-purpose format applications can use which is *definitely* *not* the case of fontawesome-web

(besides font() provides are automatically computed if fonts are correctly installed, if not font() provides are computed by rpm that means there are no usable files in the package)
Comment 2 Piotr Popieluch 2015-11-17 03:50:36 EST
Ok, thanks for clarification.

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