Bug 880538 - drop obsoletes/Provides
Summary: drop obsoletes/Provides
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: samyak-fonts
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Pravin Satpute
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-27 09:32 UTC by Parag Nemade
Modified: 2012-12-11 06:01 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-12-11 06:01:14 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
spec cleanup (2.50 KB, patch)
2012-11-27 09:32 UTC, Parag Nemade
no flags Details | Diff

Description Parag Nemade 2012-11-27 09:32:01 UTC
Created attachment 652560 [details]
spec cleanup

Description of problem:
Please drop obsoletes/provides as we have a rule of http://fedoraproject.org/wiki/Packaging:Guidelines#Renaming.2FReplacing_Existing_Packages

Version-Release number of selected component (if applicable):
samyak-fonts-1.2.2-8.fc18

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Fedora Update System 2012-11-27 10:44:50 UTC
samyak-fonts-1.2.2-9.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/samyak-fonts-1.2.2-9.fc18

Comment 2 Fedora Update System 2012-11-28 02:06:26 UTC
Package samyak-fonts-1.2.2-9.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing samyak-fonts-1.2.2-9.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-19144/samyak-fonts-1.2.2-9.fc18
then log in and leave karma (feedback).

Comment 3 Fedora Update System 2012-12-11 06:01:16 UTC
samyak-fonts-1.2.2-9.fc18 has been pushed to the Fedora 18 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.