nikivdev/code · error

You do not have write permission to {}

Error message

You do not have write permission to {}

What it means

In `check_write_permission` (src/upgrade.rs:~535), when the target path exists but its metadata reports `readonly()`, the function bails: the user lacks write permission to the existing binary, so a self-upgrade would fail. This is the pre-check before replacing the executable.

Source

Thrown at src/upgrade.rs:541

        let metadata = fs::metadata(path).or_else(|_| fs::metadata(parent))?;
        let uid = unsafe { libc::getuid() };

        if metadata.uid() == 0 && uid != 0 {
            bail!(
                "You don't have write permission to {} because it's owned by root.\n\
                 Consider updating flow through your package manager if installed from it.\n\
                 Otherwise run `f upgrade` as root.",
                path.display()
            );
        }
    }

    // Try to check if we can write
    if path.exists() {
        let metadata = fs::metadata(path)?;
        if metadata.permissions().readonly() {
            bail!("You do not have write permission to {}", path.display());
        }
    } else if !parent.exists() || fs::metadata(parent)?.permissions().readonly() {
        bail!("You do not have write permission to {}", parent.display());
    }

    Ok(())
}

/// Run the upgrade command.
pub fn run(opts: UpgradeOpts) -> Result<()> {
    let current = current_version();
    let current_exe = current_exe_path()?;

    println!("Current version: {}", current);

    // Check write permissions early
    let output_path = opts
        .output

View on GitHub (pinned to a747e741ae)

Solutions

1. Run the upgrade with elevated privileges (`sudo f upgrade`) if the location is system-owned.
2. Use the package manager that installed the binary to update it.
3. Check permissions with `ls -l $(which f)` and add write access: `chmod u+w <path>` (if appropriate).
4. Reinstall into a user-writable prefix such as ~/.local/bin.

BIN="$(command -v f)"
[ -w "$BIN" ] || { echo "$BIN not writable; use sudo or package manager"; exit 1; }

When it happens

Trigger: `path.exists()` is true and `fs::metadata(path)?.permissions().readonly()` is true — i.e. the binary file is read-only for the current user (mode without user-write, e.g. 0555/0444, or read-only mount).

Common situations: Binaries installed system-wide (0555) via package manager; read-only /usr mounted from a container image or NFS; file managed by nix/immutable store.

Related errors

• You don't have write permission to {} because it's owned by
• jj git export retry loop should always return
• fzf not found on PATH – install it to use fuzzy selection.
• moon build output directory missing: {}
• Refusing to overwrite {}

AI-assisted analysis of nikivdev/code@a747e741ae (2026-09-01). Data as JSON: /api/errors/ce62edc46450ff8b. Report an issue: GitHub.