Bug 1215488

Summary:	configure: automake defaults to Unix V7 tar, w/ max filename length=99 chars
Product:	[Community] GlusterFS	Reporter:	Kaleb KEITHLEY <kkeithle>
Component:	build	Assignee:	Kaleb KEITHLEY <kkeithle>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.7.0	CC:	bugs, gluster-bugs
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1215486	Environment:
Last Closed:	2015-05-14 17:27:25 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1215486
Bug Blocks:

Description Kaleb KEITHLEY 2015-04-27 00:49:48 UTC

+++ This bug was initially created as a clone of Bug #1215486 +++

Description of problem:

When `make dist` is run, several tests in .../tests/bugs/... are omitted because the length of the FQ pathname is > 99 chars.

By default automake forces tar to use old Unix V7 tar file format with a limit on the length of file nams.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from Anand Avati on 2015-04-26 20:44:45 EDT ---

REVIEW: http://review.gluster.org/10392 (build: configure: automake defaults to max filename length=99 chars) posted (#1) for review on master by Kaleb KEITHLEY (kkeithle)

Comment 1 Anand Avati 2015-04-27 00:54:53 UTC

REVIEW: http://review.gluster.org/10393 (build: configure: automake defaults to max filename length=99 chars) posted (#1) for review on release-3.7 by Kaleb KEITHLEY (kkeithle)

Comment 2 Anand Avati 2015-04-28 04:58:24 UTC

COMMIT: http://review.gluster.org/10393 committed in release-3.7 by Vijay Bellur (vbellur) 
------
commit 00b02d1f18308016fa9a134bea593d3095b1157f
Author: Kaleb S. KEITHLEY <kkeithle>
Date:   Sun Apr 26 20:53:27 2015 -0400

    build: configure: automake defaults to max filename length=99 chars
    
    automake's default rule for making tar files invokes tar with options
    to use Unix V7 tar file format, which has a maximum FQ pathname length
    of 99 characters. Some of the new tests in .../tests/bugs/... have names
    that are longer than 99 chars. These files are dropped from the dist
    tarfile.
    
    automake can be configured to use a newer (POSIX 2001) tar format that
    does not have limits on the length of file names.
    
    Change-Id: I8c178880ebce7d83277ba2ee133f161036958785
    BUG: 1215488
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle>
    Reviewed-on: http://review.gluster.org/10393
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Justin Clift <justin>
    Reviewed-by: Niels de Vos <ndevos>

Comment 3 Niels de Vos 2015-05-14 17:27:25 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.

glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 4 Niels de Vos 2015-05-14 17:28:47 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.

glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 5 Niels de Vos 2015-05-14 17:35:20 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.

glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user