Upgrading Firefox cask to v113 somehow corrupted the cask binary #4498
-
Output of
|
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 12 replies
-
As someone else noted, this is likely related to changes in the upgrade mechanism of casks (to prevent them being quarantined/removed from the dock). I had a similar problem with the most recent upgrade of chrome and chrome canary. |
Beta Was this translation helpful? Give feedback.
-
Adding similar behavior from ==> Upgrading google-chrome to 113.0.5672.92
==> Downloading https://dl.google.com/chrome/mac/universal/stable/GGRO/googlechrome.dmg
######################################################################################################################################################################################################################################################### 100.0%
Warning: No checksum defined for cask 'google-chrome', skipping verification.
==> Uninstalling Cask google-chrome
==> Backing App 'Google Chrome.app' up to '/opt/homebrew/Caskroom/google-chrome/113.0.5672.63/Google Chrome.app'
==> Removing App '/Applications/Google Chrome.app'
==> Purging files for version 113.0.5672.63 of Cask google-chrome
==> Installing Cask google-chrome
==> Moving App 'Google Chrome.app' to '/Applications/Google Chrome.app'
cp: /opt/homebrew/Caskroom/google-chrome/113.0.5672.92/Google Chrome.app/*: No such file or directory
cp: /opt/homebrew/Caskroom/google-chrome/113.0.5672.92/Google Chrome.app/.*: No such file or directory
==> Purging files for version 113.0.5672.92 of Cask google-chrome
Error: Failure while executing; `/usr/bin/sudo -E -- /bin/cp -pR /opt/homebrew/Caskroom/google-chrome/113.0.5672.92/Google\ Chrome.app/\* /opt/homebrew/Caskroom/google-chrome/113.0.5672.92/Google\ Chrome.app/.\* /Applications/Google\ Chrome.app/` exited with 1. Here's the output:
cp: /opt/homebrew/Caskroom/google-chrome/113.0.5672.92/Google Chrome.app/*: No such file or directory
cp: /opt/homebrew/Caskroom/google-chrome/113.0.5672.92/Google Chrome.app/.*: No such file or directory
==> Upgrading google-chrome-canary to 115.0.5759.0
==> Downloading https://dl.google.com/chrome/mac/universal/canary/googlechromecanary.dmg
######################################################################################################################################################################################################################################################### 100.0%
Warning: No checksum defined for cask 'google-chrome-canary', skipping verification.
==> Uninstalling Cask google-chrome-canary
==> Backing App 'Google Chrome Canary.app' up to '/opt/homebrew/Caskroom/google-chrome-canary/115.0.5751.0/Google Chrome Canary.app'
==> Removing App '/Applications/Google Chrome Canary.app'
==> Purging files for version 115.0.5751.0 of Cask google-chrome-canary
==> Installing Cask google-chrome-canary
==> Moving App 'Google Chrome Canary.app' to '/Applications/Google Chrome Canary.app'
cp: /opt/homebrew/Caskroom/google-chrome-canary/115.0.5759.0/Google Chrome Canary.app/*: No such file or directory
cp: /opt/homebrew/Caskroom/google-chrome-canary/115.0.5759.0/Google Chrome Canary.app/.*: No such file or directory
==> Purging files for version 115.0.5759.0 of Cask google-chrome-canary
Error: Failure while executing; `/usr/bin/sudo -E -- /bin/cp -pR /opt/homebrew/Caskroom/google-chrome-canary/115.0.5759.0/Google\ Chrome\ Canary.app/\* /opt/homebrew/Caskroom/google-chrome-canary/115.0.5759.0/Google\ Chrome\ Canary.app/.\* /Applications/Google\ Chrome\ Canary.app/` exited with 1. Here's the output:
cp: /opt/homebrew/Caskroom/google-chrome-canary/115.0.5759.0/Google Chrome Canary.app/*: No such file or directory
cp: /opt/homebrew/Caskroom/google-chrome-canary/115.0.5759.0/Google Chrome Canary.app/.*: No such file or directory |
Beta Was this translation helpful? Give feedback.
-
I'm able to consistently reproduce this using |
Beta Was this translation helpful? Give feedback.
-
Someone else is reporting the same "undefined method: artifacts" error in Homebrew/brew#15406. I'm still not sure how to reproduce that specific error, so if you have some consistent steps to do that please let me know. |
Beta Was this translation helpful? Give feedback.
-
What I find strange is that I ran the exact same thing today (with the minor release of Firefox 113.0.1) and this time it went through without problems: fabian@MacBook ~ % brew upgrade --greedy Any idea why this time it worked as expected? AFAIK nothing was changed on Brew side or was committed since I reported the issue. I am curious if it was just me this time or if this issue still persists when upgrading other casks (such as Chrome, as mentioned by @timfallmk). |
Beta Was this translation helpful? Give feedback.
Forcing a reinstall of the affected casks got me back on the road with no loss of settings.