zanmato1984 commented on issue #49768:
URL: https://github.com/apache/arrow/issues/49768#issuecomment-4258915758

   > The release tar.gz does not ship submodules I think we copy from your 
local clone if the submodules are present, otherwise we just clone from main. 
Is this a problem with your local clone submodule being slightly out-dated? 
This is the currently handling on the verification script:
   > 
   > 
[arrow/dev/release/verify-release-candidate.sh](https://github.com/apache/arrow/blob/0ce017bf9ddfc6b5439770cd28982b3e5f272bed/dev/release/verify-release-candidate.sh#L749-L773)
   > 
   > Lines 749 to 773 in 
[0ce017b](/apache/arrow/commit/0ce017bf9ddfc6b5439770cd28982b3e5f272bed)
   > 
   >  # Ensure that the testing repositories are prepared 
   >  if [ ! -d ${ARROW_SOURCE_DIR}/testing/data ]; then 
   >    if [ -d ${SOURCE_DIR}/../../testing/data ]; then 
   >      cp -a ${SOURCE_DIR}/../../testing ${ARROW_SOURCE_DIR}/ 
   >    else 
   >      git clone \ 
   >        https://github.com/apache/arrow-testing.git \ 
   >        ${ARROW_SOURCE_DIR}/testing 
   >    fi 
   >  fi 
   >  if [ ! -d ${ARROW_SOURCE_DIR}/cpp/submodules/parquet-testing/data ]; then 
   >    if [ -d ${SOURCE_DIR}/../../cpp/submodules/parquet-testing/data ]; then 
   >      cp -a \ 
   >         ${SOURCE_DIR}/../../cpp/submodules/parquet-testing \ 
   >         ${ARROW_SOURCE_DIR}/cpp/submodules/ 
   >    else 
   >      git clone \ 
   >        https://github.com/apache/parquet-testing.git \ 
   >        ${ARROW_SOURCE_DIR}/cpp/submodules/parquet-testing 
   >    fi 
   >  fi 
   >   
   >  export ARROW_TEST_DATA=$ARROW_SOURCE_DIR/testing/data 
   >  export 
PARQUET_TEST_DATA=$ARROW_SOURCE_DIR/cpp/submodules/parquet-testing/data 
   >  export ARROW_GDB_SCRIPT=$ARROW_SOURCE_DIR/cpp/gdb_arrow.py
   
   That's why. Now verification passed. Closing. Thanks @raulcd !


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to