Answers.Body: <p>UPDATE: This is now fixed in 5.31.</p>
  <hr />
  <p>I see what you're saying. Thanks for reporting. I've never used that alternative before. I believe it's coming from this line where it excludes the docs folder so the symlink is no longer valid.</p>
  <p><a href="https://github.com/civicrm/civicrm-core/blob/5.19.1/distmaker/dists/common.sh#L166" rel="nofollow noreferrer">https://github.com/civicrm/civicrm-core/blob/5.19.1/distmaker/dists/common.sh#L166</a></p>
  <p>I've made a ticket at <a href="https://lab.civicrm.org/dev/core/issues/1393" rel="nofollow noreferrer">https://lab.civicrm.org/dev/core/issues/1393</a></p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-11-15T06:28:22.757Z
Answers.Text: So, it is a bug.
Answers.UserDisplayName: Pierre François
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-03-05T14:42:17.433Z
Answers.Text: Is there an update on this problem? I am trying to install CiviCRM 5.23.0 on Drupal 8.8.3 and I get the same error message
Answers.UserDisplayName: gebseng
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-03-05T15:12:49.177Z
Answers.Text: You can't install civi on drupal 8 from that screen anyway. Drupal 8 requires using composer.
Answers.UserDisplayName: Demerit
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-03-06T17:51:07.070Z
Answers.Text: sorry and thanks!
Answers.UserDisplayName: gebseng
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-03-06T18:36:07.110Z
Answers.Text: @gebseng - re progress: you can check by following the link above to the issue ticket.  So far, no progress has been recorded.
Answers.UserDisplayName: Aidan
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-09-15T17:54:11.043Z
Answers.Text: Will be fixed in 5.31.
Answers.UserDisplayName: Demerit
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-11-14T22:48:00.927Z
Answers.LastActivityDate: 2020-09-15T17:53:10.590Z
Answers.LastEditDate: 2020-09-15T17:53:10.590Z
Answers.UserDisplayName: Demerit
Body: <p>I installed Drupal 7 and when I try to add the civicrm (version 5.19.1) module into it, I get next error message on the web interface of Drupal:</p>
  
  <blockquote>
    <p>Unable to extract symbolic link
    {temporary://update-extraction-0a20b282/civicrm/vendor/pear/log/README.rst}</p>
  </blockquote>
  
  <p>and the module is not installed. I would like to know how to solve this.</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-11-14T13:30:48.137Z
Comments.Text: The tar.gz archive contains a broken symbolic link: `civicrm/vendor/pear/README.rst` pointing to an unexisting `docs/guide.txt` file.
Comments.UserDisplayName: Pierre François
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-11-14T20:59:29.793Z
Comments.Text: Are you following the instructions at https://docs.civicrm.org/sysadmin/en/latest/install/drupal7/ ?
Comments.UserDisplayName: Demerit
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-11-14T21:23:09.757Z
Comments.Text: Yes. Where I have the alternative, I choose: "As administrator in Drupal, go to Modules, click on Install New Module , and it will ask you to fill in the URL of the module. It will then fetch it and install it for you".
Comments.UserDisplayName: Pierre François
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-11-29T18:23:17.237Z
Comments.Text: I'm getting the same error in 5.19.3 upgrade install: `tar: civicrm/vendor/pear/log/README.rst: Cannot create symlink to 'docs/guide.txt': No such file or directory
  tar: Exiting with failure status due to previous errors` Is there a work around?
Comments.UserDisplayName: Larry Lowe
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-11-30T10:00:26.813Z
Comments.Text: Yes, the workaround is to upgrade from the command line interface and to extract the files from the `tar.gz` achive. If you don't have access to the hosting system with the shell, extract the `tar.gz` archive on your own desktop/laptop, remove the offending `civicrm/vendor/pear/log/README.rst` symbolic link and copy the remaining extracted files to the remote directory.
Comments.UserDisplayName: Pierre François
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-12-02T04:17:35.257Z
Comments.Text: This does not really answer the question. If you have a different question, you can ask it by clicking [Ask Question](https://civicrm.stackexchange.com/questions/ask). You can also [add a bounty](https://civicrm.stackexchange.com/help/privileges/set-bounties) to draw more attention to this question once you have enough [reputation](https://civicrm.stackexchange.com/help/whats-reputation). - [From Review](/review/low-quality-posts/10423)
Comments.UserDisplayName: Luke Stewart
Tags: <drupal>
Title: Get "Unable to extract symbolic link" error message when trying to install civicrm 5.19.1 module in Drupal
ThreadText: # Get "Unable to extract symbolic link" error message when trying to install civicrm 5.19.1 module in Drupal
  
  (Asked by: username_0 on 2019-11-14)
  
  I installed Drupal 7 and when I try to add the civicrm (version 5.19.1) module into it, I get next error message on the web interface of Drupal:
  
  > Unable to extract symbolic link
  > {temporary://update-extraction-0a20b282/civicrm/vendor/pear/log/README.rst}
  
  and the module is not installed. I would like to know how to solve this.
  
  **Tags:** drupal
  
  > **Comments:**
  > **username_0**: The tar.gz archive contains a broken symbolic link: `civicrm/vendor/pear/README.rst` pointing to an unexisting `docs/guide.txt` file.  
  > **username_1**: Are you following the instructions at https://docs.civicrm.org/sysadmin/en/latest/install/drupal7/ ?  
  > **username_0**: Yes. Where I have the alternative, I choose: "As administrator in Drupal, go to Modules, click on Install New Module , and it will ask you to fill in the URL of the module. It will then fetch it and install it for you".  
  > **username_2**: I'm getting the same error in 5.19.3 upgrade install: `tar: civicrm/vendor/pear/log/README.rst: Cannot create symlink to 'docs/guide.txt': No such file or directory tar: Exiting with failure status due to previous errors` Is there a work around?  
  > **username_0**: Yes, the workaround is to upgrade from the command line interface and to extract the files from the `tar.gz` achive. If you don't have access to the hosting system with the shell, extract the `tar.gz` archive on your own desktop/laptop, remove the offending `civicrm/vendor/pear/log/README.rst` symbolic link and copy the remaining extracted files to the remote directory.  
  > **username_3**: This does not really answer the question. If you have a different question, you can ask it by clicking [Ask Question](https://civicrm.stackexchange.com/questions/ask). You can also [add a bounty](https://civicrm.stackexchange.com/help/privileges/set-bounties) to draw more attention to this question once you have enough [reputation](https://civicrm.stackexchange.com/help/whats-reputation). - [From Review](/review/low-quality-posts/10423)  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2019-11-14. Score: 3 | Accepted answer
  
  UPDATE: This is now fixed in 5.31.
  
  ---
  
  I see what you're saying. Thanks for reporting. I've never used that alternative before. I believe it's coming from this line where it excludes the docs folder so the symlink is no longer valid.
  
  <https://github.com/civicrm/civicrm-core/blob/5.19.1/distmaker/dists/common.sh#L166>
  
  I've made a ticket at <https://lab.civicrm.org/dev/core/issues/1393>
  
  > **Comments:**
  > **username_0**: So, it is a bug.  
  > **username_4**: Is there an update on this problem? I am trying to install CiviCRM 5.23.0 on Drupal 8.8.3 and I get the same error message  
  > **username_1**: You can't install civi on drupal 8 from that screen anyway. Drupal 8 requires using composer.  
  > **username_4**: sorry and thanks!  
  > **username_5**: @username_4 - re progress: you can check by following the link above to the issue ticket.  So far, no progress has been recorded.  
  > **username_1**: Will be fixed in 5.31.  
  
  ---
  
  