Bug 205050

Summary: Spec file alterations
Product: [Fedora] Fedora Reporter: Paul F. Johnson <paul>
Component: f-spotAssignee: Christopher Aillon <caillon>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhide   
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: 2007-12-26 14:03:12 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:
Attachments:
Description Flags
f-spot spec file patch none

Description Paul F. Johnson 2006-09-02 23:48:35 UTC 
Description of problem:
Attached patch file patches the spec file to bring it into line with the
packaging guidelines

It just adds the %{?dist} onto the release tag
Comment 1 Paul F. Johnson 2006-09-02 23:48:35 UTC 
Created attachment 135440 [details]
f-spot spec file patch
Comment 2 Toshio Kuratomi 2006-09-03 05:01:45 UTC 
The dist tag is not a mandatory requirement.

It is recommended as the easiest way to make sure that a package on a newer
release of Fedora Core will upgrade an older release but it is up to the
maintainer to decide if they want to make use of the tag to help them do this or
if they are going to manually make sure that an update release for an older FC
does not break the upgrade path to newer releases' packages.

http://www.fedoraproject.org/wiki/Packaging/DistTag
Comment 3 Paul F. Johnson 2006-09-03 08:48:55 UTC 
Given it's a mono package and therefore only going to hit FC5 and above (unless
mono is back ported that is), surely the dist tag should be used.