Skip to content

fix: Add $SUDO to uv installation commands for proper permissions#15877

Open
rdtr wants to merge 1 commit intofacebookincubator:mainfrom
rdtr:fix-uv-install-permissions
Open

fix: Add $SUDO to uv installation commands for proper permissions#15877
rdtr wants to merge 1 commit intofacebookincubator:mainfrom
rdtr:fix-uv-install-permissions

Conversation

@rdtr
Copy link

@rdtr rdtr commented Dec 31, 2025

The install_uv and uv_install functions install binaries to $INSTALL_PREFIX/bin (defaults to /usr/local/bin), which requires elevated permissions on non-root systems.

This change adds $SUDO to both functions, consistent with how apt commands are already handled in the setup scripts.
These lines were initially introduced for Docker-based development, where containers run as root and no permission issues occur. This fix addresses the case when running setup-ubuntu.sh directly on a Ubuntu host machine as a non-root user.

The change is consistent with the existing pattern used for apt commands throughout the setup scripts.

Test plan

  • Tested ./scripts/setup-ubuntu.sh install_build_prerequisites on Ubuntu 22.04 as non-root user
  • Verified uv and cmake installations complete successfully with the fix

The install_uv and uv_install functions install binaries to
\$INSTALL_PREFIX/bin (defaults to /usr/local/bin), which requires
elevated permissions on non-root systems.

This change adds \$SUDO to both functions, consistent with how
apt commands are already handled in the setup scripts.
@netlify
Copy link

netlify bot commented Dec 31, 2025

Deploy Preview for meta-velox canceled.

Name Link
🔨 Latest commit 02ee7a9
🔍 Latest deploy log https://app.netlify.com/projects/meta-velox/deploys/6955018331ea680008b894d6

@meta-cla
Copy link

meta-cla bot commented Dec 31, 2025

Hi @rdtr!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

@meta-cla
Copy link

meta-cla bot commented Dec 31, 2025

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

@meta-cla meta-cla bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Dec 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant