+++ 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)
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)
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>
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