Bug 481279

Summary: Missing obsoletes statement for %{fontname}-common-fonts
Product: [Fedora] Fedora Reporter: Quentin Armitage <quentin>
Component: baekmuk-ttf-fontsAssignee: Caius Chance <K9>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: fonts-bugs, i18n-bugs, K9, petersen
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-01-24 21:18:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Quentin Armitage 2009-01-23 12:11:23 UTC
Description of problem:
Attempting yum update of baekmuk-ttf-fonts-common fails sating conflict against baekmuk-ttf-common-fonts 2.2.13

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

How reproducible:
Always

Steps to Reproduce:
1.yum update
2.
3.
  
Actual results:
Reports conflict eror described above

Expected results:
Successful update

Additional info:
in the %package -n %{fontname}-fonts-common section of the .spec file, should there be an obsoletes %{fontname}-common-fonts < 2.2.13(or is it 2.2.14 - common-fonts was last in version 2.2.13).

I also noticed that when I had 2.2.13 installed, there was a baekmuk-fonts-common version 2.2.10 still installed, and presumably that should have been obsoleted by a previous update?

Comment 1 Christopher Beland 2009-01-24 20:54:03 UTC
This is apparently part of the packaging changes requested at bug 477332.

Comment 2 Nicolas Mailhot 2009-01-24 21:18:22 UTC

*** This bug has been marked as a duplicate of bug 477332 ***