Bug 1499240 - Remove dependency on ghostscript-fonts - use urw-base35-fonts
Summary: Remove dependency on ghostscript-fonts - use urw-base35-fonts
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: hylafax+
Version: 27
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lee Howard
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1500105
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-06 12:34 UTC by Zdenek Dohnal
Modified: 2017-11-11 02:52 UTC (History)
2 users (show)

Fixed In Version: hylafax+-5.5.9-4.fc27
Clone Of:
Environment:
Last Closed: 2017-11-11 02:52:23 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1500104 0 unspecified CLOSED urw-base35-fonts only partially provides urw-fonts and should at least obsolete ghostscript-fonts, too. 2021-02-22 00:41:40 UTC

Internal Links: 1500104

Description Zdenek Dohnal 2017-10-06 12:34:00 UTC
Hi,

I am going to remove ghostscript-fonts package because it is deprecated and it is replaced by urw-bas35-fonts package. Would you mind applying this change into F27 cycle?

Comment 1 Lee Howard 2017-10-12 20:13:37 UTC
I have made an update (hylafax+-5.5.9-4.fc27).  I don't know why the update isn't automatically updating the bug report here, although I told it to.

Comment 3 Fedora Update System 2017-10-13 23:23:25 UTC
hylafax+-5.5.9-4.fc27 has been pushed to the Fedora 27 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-2017-b20e04f6ce

Comment 4 Fedora Update System 2017-11-11 02:52:23 UTC
hylafax+-5.5.9-4.fc27 has been pushed to the Fedora 27 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.