Bug 1416873 – Add libXfont2 to comps file for release

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1416873 - Add libXfont2 to comps file for release

Summary:	Add libXfont2 to comps file for release

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	releng (Show other bugs)
Sub Component:
Version:	7.4
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	rc
Target Release:	---
Assigned To:	Lubos Kocman
QA Contact:	Release Test Team
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	1401691
	Show dependency tree / graph

Reported:	2017-01-26 11:46 EST by Eng Ops Maitai User
Modified:	2017-08-01 13:32 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2017-08-01 13:32:24 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2017:1850	normal	SHIPPED_LIVE	redhat-release update	2017-08-01 14:03:01 EDT

Groups: None (edit)

Comment 3 Lubos Kocman 2017-01-31 08:04:10 EST

Hello Jon,

buildrequires is fine, as long as we build it it will end up in optional, no distill config needed. We just made it a "supported package".

Thoughts?


Lubos

Comment 5 Jon Disnard 2017-01-31 08:52:55 EST

Hiya Lubos,

So long as this is pulled in as a BR at package level,then yes I would agree it would NOT need to go in the Distill/Pungi configs. Are you saying it would go to optional if we did nothing? If yes, I'll gladly revert the above commit.

Comment 7 errata-xmlrpc 2017-08-01 13:32:24 EDT

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:1850

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