Bug 525592 - lohit-hindi-fonts, etc should not obsolete itself
Summary: lohit-hindi-fonts, etc should not obsolete itself
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: lohit-hindi-fonts
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Pravin Satpute
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F12Target
TreeView+ depends on / blocked
 
Reported: 2009-09-25 00:43 UTC by Jens Petersen
Modified: 2009-09-29 05:00 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-09-29 05:00:48 UTC


Attachments (Terms of Use)

Description Jens Petersen 2009-09-25 00:43:51 UTC
Description of problem:
When I yum updated rawhide today I see that some new
lohit fonts package are obsoleting themselves.
This seems wrong: no reason to do this IMHO
as there is no name change.

Please drop the self-obsoletes.

Version-Release number of selected component (if applicable):
lohit-hindi-fonts-2.4.3-1.fc12

Steps to Reproduce:
1. install lohit-hindi-fonts-2.4.2-1.fc12 in rawhide
2. yum update
  
Actual results:
yum says installing lohit-hindi-fonts-2.4.3-1.fc12 replacing
lohit-hindi-fonts-2.4.2-1.fc12

Expected results:
It should just be a normal transparent update with no
visible change of package to users.

Additional info:
I assume similar problem for all the other lohit-*-fonts.

The source url is also wrong:
http://pravins.fedorapeople.org/lohit/gujarati/%{fontname}-%{version}.tar.gz
                                      ^^^^^^^^
Please take care.

Are you going to move the packages back to fedorahosted too?

Comment 1 Pravin Satpute 2009-09-25 04:18:54 UTC
yes, i have started moving source package to fedorahosted.org, i moved recent version of malayala, tamil, tegulu and kannada 2.4.4, to fedorahosted

so now only obsolute will be only lohit-fonts-common

Comment 2 Pravin Satpute 2009-09-29 05:00:48 UTC
built corresponding packages for rawhide
thanks for notifying same :)


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