Bug 763356 (GLUSTER-1624) - RPM build failed because libglusterfsclient.h not in distribution tarball
Summary: RPM build failed because libglusterfsclient.h not in distribution tarball
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-1624
Product: GlusterFS
Classification: Community
Component: build
Version: nfs-beta
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Lakshmipathi G
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-17 00:42 UTC by Bernard Li
Modified: 2015-12-01 16:45 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Bernard Li 2010-09-17 00:42:34 UTC 
I was trying to build RPM from glusterfs-nfs_beta_rc13.tar.gz found here: ftp://ftp.gluster.org/pub/gluster/glusterfs/qa-releases/nfs-beta/ and it failed with the following errors:

RPM build errors:
    File not found: /var/tmp/glusterfs-nfs_beta_rc13-1-root/usr/include/libglusterfsclient.h

Should just be a matter of including that file in the distribution tarball.

Thanks,

Bernard
Comment 1 Bernard Li 2010-09-29 16:21:20 UTC 
Any chance this could be looked at soon?  I've been testing the nfs_beta_rc's and it's just a tad annoying that I had to manually fix the spec file each time.

Or should I be testing the 3.1 qa snapshots instead...?

Thanks!
Comment 2 Amar Tumballi 2010-09-30 00:39:14 UTC 
Hi Bernard,

Please use 3.1 qa releases. We have made NFS up to date in 3.1 branch (ie, same as NFS beta rc releases).
Comment 3 Bernard Li 2010-09-30 01:47:03 UTC 
(In reply to comment #2)
> Hi Bernard,
> 
> Please use 3.1 qa releases. We have made NFS up to date in 3.1 branch (ie, same
> as NFS beta rc releases).

Sounds good, I'll test the 3.1 qa releases then -- you can close this ticket, thanks.
Comment 4 Amar Tumballi 2010-10-04 04:40:30 UTC 
With 3.1.0beta onwards, NFS is kept up to date  in mainline, hence users need not worry on NFSBeta branch anymore.
Note You need to log in before you can comment on or make changes to this bug.