hutch3232 opened a new issue, #40227:
URL: https://github.com/apache/arrow/issues/40227

   ### Describe the bug, including details regarding any error messages, 
version, and platform.
   
   I used `create_package_with_all_dependencies` on a Windows machine and then 
copied the tarball to a Linux machine. When I went to install the tarball, I 
received this error:
   ```R
   ERROR: 'configure' exists but is not executable -- see the 'R Installation 
and Administration Manual' [r]
   ```
   
   Reviewing the code, we see the files are simply `tar`'d back after 
downloading the dependencies into the untarred package:
   
https://github.com/apache/arrow/blob/b8fff043c6cb351b1fad87fa0eeaf8dbc550e37c/r/R/install-arrow.R#L254
   
   I found that if I replace the above line with a `pkgbuild::build` call, the 
missing executable bits are automatically fixed:
   ```R
   pkgbuild::build(path = "arrow", dest_path = dest_file)
   ── R CMD build 
──────────────────────────────────────────────────────────────────────────────────────────────────────────
   ✔  checking for file 
'C:\Users\hutch3232\AppData\Local\Temp\RtmpodDbIB\file37344a4258a8\arrow/DESCRIPTION'
 (986ms)
   ─  preparing 'arrow': (32.5s)
   ✔  checking DESCRIPTION meta-information ... 
   ─  cleaning src
   ─  checking for LF line-endings in source and make files and shell scripts 
(1.3s)
   ─  checking for empty or unneeded directories (579ms)
   ─  building 'arrow_14.0.2.1.tar.gz' (494ms)
      Warning: file 'arrow/cleanup' did not have execute permissions: corrected
      Warning: file 'arrow/configure' did not have execute permissions: 
corrected
   ```
   
   After making this change, the install on the Windows and Linux machines 
worked great. Perhaps there could be a step that sets these as executable 
manually, or replace `tar` with `build`, which includes other checks to ensure 
a valid package build.
   
   BTW thanks for making this script, it's incredibly useful!
   
   ### Component(s)
   
   R


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