Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • S slapos.recipe.build
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • nexedi
  • slapos.recipe.build
  • Merge requests
  • !10

Merged
Created Feb 18, 2020 by Jérome Perrin@jeromeOwner

make_read_only_recursively: don't touch symlink targets

  • Overview 3
  • Commits 1
  • Pipelines 1
  • Changes 2

This fixes a problem visible when installing openssl 1.1.1d from component/openssl. At the end of install step, some symlinks are created inside openssl install directory for all certificates from ca-certificates part, then the "make read only" step occurs, which recursively chmod on files and folder in openssl installed parts, but since this was following symlinks, it was also trying to make readonly in ca-certificates parts, which in my case was belonging to another unix user, because it was a shared part folder from outer level slapos.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: fix/make_read_only_symlinks
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7