Bug 922432 - Upstream generated spec file references non-existing patches
Summary: Upstream generated spec file references non-existing patches
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: GlusterFS
Classification: Community
Component: build
Version: pre-release
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
Assignee: Kaleb KEITHLEY
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-16 20:47 UTC by Justin Clift
Modified: 2015-07-13 04:35 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-22 20:56:53 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Justin Clift 2013-03-16 20:47:37 UTC
Description of problem:

  Part of the change to glusterfs.spec.in for BZ# 819130 adds references to 3
  non-existing patch files.

  Lines 336 to 338 here:

    http://review.gluster.org/#patch,sidebyside,4454,21,glusterfs.spec.in

  Compiling from the generated spec now fails:

    $ rpmbuild -bb glusterfs.spec 
    error: Bad source: /home/jc/rpmbuild/SOURCES/0001-Use-updated-parallel-install-versions-of-epel-packag.patch: No such file or directory


Version-Release number of selected component (if applicable):

  Upstream git repo, master branch head, as of Sat 16th March 2013.


How reproducible:

  Every time.


Steps to Reproduce:

  1. git clone upstream repo
  2. ./autogen.sh; ./configure
  3. make dist
  4. Try to build from the generated glusterfs.spec
  
Actual results:

  $ rpmbuild -bb glusterfs.spec 
    error: Bad source: /home/jc/rpmbuild/SOURCES/0001-Use-updated-parallel-install-versions-of-epel-packag.patch: No such file or directory


Expected results:

  Compilation to succeed.


Additional info:

Comment 1 Justin Clift 2013-03-22 20:56:53 UTC
It turns out the spec file is for use by the "make glusterrpms" command, to be run from the "extras/LinuxRPM/" directory.

We just need to document the correct rpm building steps better. (in progress)


Note You need to log in before you can comment on or make changes to this bug.