Closed tiiiecherle closed 4 years ago
Error: It seems there already exists a Binary at '/usr/local/bin/nextcloudcmd'; not overwriting.
@reitermarkus What do you think? Should --force
override this?
Error: It seems there already exists a Binary at '/usr/local/bin/nextcloudcmd'; not overwriting.
@reitermarkus What do you think? Should
--force
override this?
I have made it so --force
overrides the error, and instead prints a warning as it does when installing .app
's with --force
.
I think for binaries we should only override:
Caskroom
path of the same caskAgreed with @reitermarkus. Even with --force
we shouldn’t take the risk of irreversibly deleting a user script or breaking other tools that depend on it.
Thanks for looking into this.
I don't know much about the background code but for the user using --force
in my opinion should really force an override.
I don't know if @reitermarkus's suggestion would solve the following problem, if yes, it is ok for me.
I'm using --force
in my own update script and therefore --force
should lead to always having all app related files in the latest version and making the install/update succeed. This worked for the last years without problems.
I checked for the nextcloud and chromium cask that are currently failing to update with --force
for me. The error files (/usr/local/bin/nextcloudcmd
and /usr/local/bin/chromium
) are both symlinks. I don't know if there are other casks with other issue possibilities regarding this.
Thanks in advance for working on the fix.
Can someone please explain why "not overwriting" is preferred if the conflicting name/path is a file.
--force
.--force
for an update should be all files updated to the latest version.Thanks
Can someone please explain why "not overwriting" is preferred if the conflicting name/path is a file.
https://github.com/Homebrew/homebrew-cask/issues/88401#issuecomment-683410923
@vitorgalvao Thanks, I already read that but I don't know exactly what that means. Do you mean it could possibly overwrite a file that doesn't even belong to the referring cask?
Is it not the way it has ever been until a few days ago to overwrite the conflicting files using --force
?
Do you mean it could possibly overwrite a file that doesn't even belong to the referring cask?
Yes.
Is it not the way it has ever been until a few days ago to overwrite the conflicting files using
--force
?
I no longer recall.
General troubleshooting steps
--force
.brew update-reset && brew update
and retried my command.brew doctor
, fixed as many issues as possible and retried my command.Description of issue
Some casks do not get installed correctly when using
--force
if app is already installed, e.g. nextcloud, github...Command that failed
nextcloud is just an example, fails on multiple casks if cask is already installed.
Output of command with
--force --verbose --debug
Output of
brew cask doctor
Output of
brew tap