Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
C
Core
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 920
    • Issues 920
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • Development
  • Core
  • Issues
  • #1393

Closed
Open
Opened Nov 14, 2019 by DaveD@DaveDDeveloper

Tarball includes a symlink that goes nowhere, which causes alternate drupal install method to fail

In the docs (https://docs.civicrm.org/sysadmin/en/latest/install/drupal7/#directory) if you choose the first bullet point method of getting the tarball, it can fail because of a symlink that goes nowhere. See https://civicrm.stackexchange.com/questions/33708/get-unable-to-extract-symbolic-link-error-message-when-trying-to-install-civic

I believe it's because this line excludes the docs folder: https://github.com/civicrm/civicrm-core/blob/5.19.1/distmaker/dists/common.sh#L166

I don't think this is a recent thing.

One way to solve it might be to have that same line exclude README.rst.

Edited Nov 14, 2019 by DaveD
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
5.31.0
Milestone
5.31.0
Assign milestone
Time tracking
None
Due date
None
Reference: dev/core#1393