[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lustre-devel
Subject:    [Lustre-devel] [Bug 12224] New: Incorrect tarball built on RHEL 4
From:       scjody () clusterfs ! com (scjody () clusterfs ! com)
Date:       2007-04-12 10:13:21
Message-ID: 200704121613.l3CGDJvg024512 () shell ! clusterfs ! com
[Download RAW message or body]

Please don't reply to lustre-devel. Instead, comment in Bugzilla by using the following link:
https://bugzilla.lustre.org/show_bug.cgi?id=12224



When a Lustre tarball is built on RHEL 4 (at least),
ext3-disable-write-barrier-by-default-2.6-sles10.patch is not included but 'make
dist' succeeds.  The following undetected error can be seen:

ia1: /bin/sh /testsuite/lustre/lbuild-v1_4_10_90-2.6-rhel4-ia64/missing --run
tar chof - lustre-1.4.10.90 | GZIP=--best gzip -c >lustre-1.4.10.90.tar.gz
ia1: tar:
lustre-1.4.10.90/lustre/kernel_patches/patches/ext3-disable-write-barrier-by-default-2.6-sles10.patch:
file name is too long (max 99); not dumped
ia1: tar: Error exit delayed from previous errors
ia1: gtar:
lustre-1.4.10.90/lustre/kernel_patches/patches/ext3-disable-write-barrier-by-default-2.6-sles10.patch:
file name is too long (max 99); not dumped
ia1: gtar: Error exit delayed from previous errors

This is because tar is being run with the 'chof' options.  These come from
/usr/share/automake-1.7/am/distdir.am.  SLES 10's automake gets it right, so a
tarball built on SLES 10 can be used successfully on SLES 10, but a tarball
built on RHEL 4 can not.

To fix, I propose we rename the patch.

[prev in list] [next in list] [prev in thread] [next in thread]