Bug 985058 - bodhi source RPM spec doesn't define where source tarball comes from
Summary: bodhi source RPM spec doesn't define where source tarball comes from
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: bodhi
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Luke Macken
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-16 16:52 UTC by Eric Smith
Modified: 2016-09-20 02:45 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-18 21:29:38 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Eric Smith 2013-07-16 16:52:34 UTC 
Description of problem:

The Source0 tag in the bodhi RPM spec file gives only a local filename, not a URL, and there is no information (e.g., comments or scripts) as to how to obtain the tarball or generate it from a source repository.  This is a violation of the SourceURL policy: http://fedoraproject.org/wiki/Packaging:SourceURL

Version-Release number of selected component (if applicable):
bodhi-0.9.5-2
Comment 1 Eric Smith 2013-07-16 16:57:15 UTC 
It appears that the source repository for bodhi is on git.fedorahosted.org, and there are tarballs of some snapshots, e.g.:

https://git.fedorahosted.org/cgit/bodhi.git/snapshot/bodhi-0.9.3.zip

However, it appears that there is not a tarball for 0.9.5.  If the RPM is based on an unreleased snapshot, the RPM spec should document that and give instructions (or a script) for extracting the correct tag from the repository (or, if it isn't tagged, otherwise getting the correct files) and building the tarball.
Comment 2 Luke Macken 2014-03-18 21:29:38 UTC 
Fixed in rawhide. Thanks!
Note You need to log in before you can comment on or make changes to this bug.