Bug 835488 - Shouldn't google-croscore-fonts package replace/obsolete Liberation font packages?
Shouldn't google-croscore-fonts package replace/obsolete Liberation font pack...
Product: Fedora
Classification: Fedora
Component: google-croscore-fonts (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Parag Nemade
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-06-26 06:41 EDT by Matěj Cepl
Modified: 2018-04-11 08:26 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-06-26 07:56:04 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Matěj Cepl 2012-06-26 06:41:44 EDT
Description of problem:
Following http://lwn.net/Articles/502371/ I have installed google-croscore-fonts and to my surprise they haven't replaced/obsoleted (https://fedoraproject.org/wiki/Packaging:Guidelines#Renaming.2FReplacing_Existing_Packages)?

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

How reproducible:

Steps to Reproduce:
1.install Liberation fonts
2.install google-croscore-fonts
Actual results:
both fonts are present in the system

Expected results:
only google-croscore-fonts should be

Additional info:
Comment 1 Parag Nemade 2012-06-26 07:56:04 EDT
I have yet not got time to read lwn page but its already decided that google-croscore-fonts will going to either orphaned/retired or kept as it is as initial import.

Pravin Satpute (maintainer of liberation fonts) started work of creating next version of liberation fonts which will incorporate additional changes in google-croscore-fonts as compared to liberation fonts.

See http://lists.fedoraproject.org/pipermail/devel/2012-May/167227.html

till then both fonts will be present.

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