Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

goose update fails with 'Can't replace existing directory' error #1745

Closed
pwgseml opened this issue Mar 18, 2025 · 1 comment · Fixed by #1838
Closed

goose update fails with 'Can't replace existing directory' error #1745

pwgseml opened this issue Mar 18, 2025 · 1 comment · Fixed by #1838
Assignees
Labels
bug Something isn't working

Comments

@pwgseml
Copy link

pwgseml commented Mar 18, 2025

When I run goose update at the command line, I get the following error:

❯ goose update
Downloading stable release: goose-aarch64-apple-darwin.tar.bz2...
Extracting goose-aarch64-apple-darwin.tar.bz2...
goose: Can't replace existing directory with non-directory
tar: Error exit delayed from previous errors.

Steps to Reproduce

  1. Have Goose already installed on macOS (Apple Silicon)
  2. Run goose update from the terminal
  3. Observe the error during the extraction phase

System Information

  • Operating System: macOS
  • Architecture: ARM64 (Apple Silicon)
  • Goose Installation Method: I followed the instructions at go/getgoose
    curl -fsSL https://github.com/block/goose/releases/download/stable/download_cli.sh \| GOOSE_PROVIDER=databricks GOOSE_MODEL=goose DATABRICKS_HOST=https://block-lakehouse-production.cloud.databricks.com/ bash

Additional Context

The error seems to occur during the extraction of the update package, suggesting there might be a file system permission issue or a conflict between directory and file types during the update process.

Additional Notes

  • This was my first time running goose update
  • ❯ goose --version 1.0.13
  • To the best of my knowledge, I have not made any manual modifications to the Goose installation directory
@meenalc meenalc added the bug Something isn't working label Mar 20, 2025
@kalvinnchau
Copy link
Collaborator

I believe this occurs because when we extract the binary out of the tar https://github.com/block/goose/blob/main/download_cli.sh#L82, it creates a binary named goose, so if there's a directory already named goose from where you're running goose update it will fail.

If you run this from another directory it should work, can you confirm that @pwgseml ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants