Bug 482968 - Source0 missing from SPEC file
Summary: Source0 missing from SPEC file
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Publican
Classification: Community
Component: publican
Version: 1.6
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jeff Fearn 🐞
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 476471
TreeView+ depends on / blocked
 
Reported: 2009-01-29 03:20 UTC by eric
Modified: 2010-11-24 04:17 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-01-29 05:10:53 UTC
Embargoed:


Attachments (Terms of Use)

Description eric 2009-01-29 03:20:19 UTC
Description of problem: The Source0 entry in the SPEC file should point to where the developer has stored the tarball.


Version-Release number of selected component (if applicable): publican-0.40-0.fc10.noarch

Actual results: Source0:	%{name}-%{version}.tgz


Expected results: Source0:      <actual path and file name>

Comment 1 Jeff Fearn 🐞 2009-01-29 03:49:41 UTC
Changing the file name used in the automated spec building system would create a lot of extra work changing that whole subsystem, so I'm not going to do that at this time.

I'll add a new parameter, SRC_URL, which will be setable in the books Makefile and will be prepended to Source0.

So it will look something like:

In Makefile:
SRC_URL = http://foo.bar/sources/

In *-spec.xsl:

Source0: $SRC_URL%{name}-%{version}.tgz

Comment 2 eric 2009-01-29 03:57:32 UTC
That should work.  Thanks!

Comment 3 Jeff Fearn 🐞 2009-01-29 05:10:53 UTC
Added SRC_URL Makefile variable.

Comment 4 Fedora Update System 2009-03-18 23:57:22 UTC
publican-fedora-0.18-0.fc10,publican-0.44-0.fc10 has been submitted as an update for Fedora 10.
http://admin.fedoraproject.org/updates/publican-fedora-0.18-0.fc10,publican-0.44-0.fc10

Comment 5 Fedora Update System 2009-03-26 14:53:33 UTC
publican-fedora-0.18-0.fc10, publican-0.44-0.fc10 has been pushed to the Fedora 10 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.