Bug 484621 - culmus-fonts needs compat package for upgrades
Summary: culmus-fonts needs compat package for upgrades
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: culmus-fonts
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Pravin Satpute
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-02-09 02:46 UTC by Jens Petersen
Modified: 2010-01-27 05:39 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-01-27 05:39:54 UTC


Attachments (Terms of Use)

Description Jens Petersen 2009-02-09 02:46:59 UTC
Description of problem:
Since culmus-fonts has now been subpackaged for F11 it needs a compat subpackage for smooth updating from F10, etc.

Version-Release number of selected component (if applicable):
culmus-fonts-0.102-1.fc11

Actual results:
No culmus-fonts-compat so can't upgrade.

Expected results:
culmus-fonts-compat which obsoletes previous culmus-fonts correctly.

Additional info:
http://fedoraproject.org/wiki/Packaging/NamingGuidelines#Renaming.2Freplacing_existing_packages

Comment 1 Rahul Bhalerao 2009-02-09 09:53:55 UTC
Added the -compat subpackage.

Comment 2 Bug Zapper 2009-06-09 11:09:09 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Jens Petersen 2009-06-29 07:28:56 UTC
It has not been done right: compat not common should obsolete the old package.

Comment 5 Pravin Satpute 2009-12-14 11:23:26 UTC
is this fixed, after updating this package as per the new font packaging guideline?

Comment 6 Jens Petersen 2009-12-23 07:05:45 UTC
I don't see any update in cvs.

Comment 7 Pravin Satpute 2010-01-19 09:50:09 UTC
fixed in culmus-fonts-0.103-5.fc13

Comment 8 Pravin Satpute 2010-01-27 05:39:54 UTC
closing for now, please reopen if any problem


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