Bug 878321

Summary: spec cleanup needed
Product: [Fedora] Fedora Reporter: Parag Nemade <pnemade>
Component: ttmkfdirAssignee: Pravin Satpute <psatpute>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: i18n-bugs, psatpute
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-11-27 09:52:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
spec cleanup none

Description Parag Nemade 2012-11-20 05:47:35 UTC
Created attachment 648287 [details]
spec cleanup

Description of problem:
Attaching patch for spec cleanup. Please review it and apply and build a new package.

Version-Release number of selected component (if applicable):
ttmkfdir-3.0.9-36.fc18.x86_64

How reproducible:


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


Expected results:


Additional info:

Comment 1 Fedora Update System 2012-11-20 09:15:55 UTC
ttmkfdir-3.0.9-37.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/ttmkfdir-3.0.9-37.fc18

Comment 2 Fedora Update System 2012-11-20 20:22:14 UTC
Package ttmkfdir-3.0.9-37.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 ttmkfdir-3.0.9-37.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-18618/ttmkfdir-3.0.9-37.fc18
then log in and leave karma (feedback).

Comment 3 Fedora Update System 2012-11-27 09:53:01 UTC
ttmkfdir-3.0.9-37.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.