Bug 1426321 - Explicitly enable tar wildcard support when repacking proguard. r=nalexander
authorMike Hommey <mh+mozilla@glandium.org>
Wed, 20 Dec 2017 16:01:51 +0900
changeset 397044 2913983fd2f5357be9dd4c8a779bcdcebcf388a5
parent 397043 7c7b2f1d488aed629c0f8bdc7c3a38a29a84b540
child 397045 04fc5cd2091681b2e50b758827cb0b8669af8e64
push id33123
push userncsoregi@mozilla.com
push dateThu, 21 Dec 2017 10:00:47 +0000
treeherdermozilla-central@06a19fbe2581 [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewersnalexander
bugs1426321
milestone59.0a1
first release with
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
last release without
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
Bug 1426321 - Explicitly enable tar wildcard support when repacking proguard. r=nalexander While on Centos --wildcards is the default, it is not on Debian.
taskcluster/scripts/misc/repack-proguard-jar.sh
--- a/taskcluster/scripts/misc/repack-proguard-jar.sh
+++ b/taskcluster/scripts/misc/repack-proguard-jar.sh
@@ -16,17 +16,17 @@ SHA256SUM=95bf9580107f00d0e26f01026dcfe9
 
 mkdir -p $UPLOAD_DIR $STAGE
 
 cd $WORKSPACE
 wget $URL
 echo "$SHA256SUM  $ARCHIVE" | sha256sum -c -
 
 # Just the file we need.
-tar zxvf $ARCHIVE '*/proguard.jar'
+tar --wildcards -zxvf $ARCHIVE '*/proguard.jar'
 
 # The archive is to satisfy source distribution requirements.
 mv $ARCHIVE $UPLOAD_DIR
 
 # This leaves us with $STAGE/lib/proguard.jar.
 mv $DIR/lib $STAGE
 
 cat >$STAGE/README<<EOF