This is an automated email from the ASF dual-hosted git repository.

gurwls223 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/spark.git


The following commit(s) were added to refs/heads/master by this push:
     new f164e4ae53ca [SPARK-48425][INFRA][FOLLOWUP] Do not copy the base spark 
folder
f164e4ae53ca is described below

commit f164e4ae53ca333c49baa65b9f4d332a0a7ec4c8
Author: Wenchen Fan <[email protected]>
AuthorDate: Tue May 28 16:48:39 2024 +0900

    [SPARK-48425][INFRA][FOLLOWUP] Do not copy the base spark folder
    
    ### What changes were proposed in this pull request?
    
    This is a followup of https://github.com/apache/spark/pull/46769 to fix a 
mistake. The release scripts use a base `spark` folder to build tarballs and it 
shouldn't be copied with the tarballs.
    
    ### Why are the changes needed?
    
    fix mistake
    
    ### Does this PR introduce _any_ user-facing change?
    
    no
    
    ### How was this patch tested?
    
    manual
    
    ### Was this patch authored or co-authored using generative AI tooling?
    
    no
    
    Closes #46771 from cloud-fan/script.
    
    Authored-by: Wenchen Fan <[email protected]>
    Signed-off-by: Hyukjin Kwon <[email protected]>
---
 dev/create-release/release-build.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev/create-release/release-build.sh 
b/dev/create-release/release-build.sh
index cf9c146e081a..0435960c93cd 100755
--- a/dev/create-release/release-build.sh
+++ b/dev/create-release/release-build.sh
@@ -382,7 +382,7 @@ if [[ "$1" == "package" ]]; then
     mkdir -p "svn-spark/${DEST_DIR_NAME}-bin"
 
     echo "Copying release tarballs"
-    cp spark* "svn-spark/${DEST_DIR_NAME}-bin/"
+    cp spark-* "svn-spark/${DEST_DIR_NAME}-bin/"
     cp pyspark* "svn-spark/${DEST_DIR_NAME}-bin/"
     cp SparkR* "svn-spark/${DEST_DIR_NAME}-bin/"
     svn add "svn-spark/${DEST_DIR_NAME}-bin"


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to