-
-
Notifications
You must be signed in to change notification settings - Fork 10.9k
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
Can't upgrade (or install) twine
#176995
Comments
What is the output of |
And using the Finder to open .dmg files (and then eject them) works as expected. |
I wonder if it is getting stuck on the command after the eject command. |
I updated Homebrew:
Unfortunately, my problem persists. |
Unhelpful probably, but couldn't replicate in a clean VM environment using either v4.3.3 or v4.3.6 of Homebrew. Almost sounds like a resource being held open preventing eject, but can't think what it would be. Agree that it's probably not a Immediately stupid question - have you tried rebooting? Wondering if somehow you are out of space in |
I've rebooted several times in the last 24 hours. I'm afraid it hasn't seemed to make a difference. I don't know how to check the specific capacity of Just now I tried (re)installing three casks: Here's an ominous twist: after the failed Chatterino installation, I tried to run ![]() Rebooting did not make either |
BLUF: At this stage with the new information, I don't think this is specifically a Homebrew issue, but do think you should be wary of your disk. More - I wouldn't think It's possible you have bad sectors on your disk, and you've hit a point where installing or mounting something is trying to use that disk portion in I/O ops, either read or write. Having issues enumerating volumes could point to a broader issue, but that's not exactly a definitive diagnosis, but I'd at least say disk issues can't be ruled out. Are you having any other issues outside of Homebrew with reading or writing data, running programs, etc? I am not trying to strike fear here, but (as I am 100% sure you know) you should have backups and be aware that if your disk is actually failing it can cause very wonky behavior. Personal story: I was trying to file copy a 2013 MBP spinning HDD that was ticking and starting failure in target disk mode to a external disk attached to another MBP. File copy hung partway through and froze, and corrupted the APFS volume of the disk I was transferring files to - the good SSD - when I |
None whatsoever that I've noticed. And about 11 years ago I had HDD issues that slowly progressed to catastrophic failure (which corrupted my backups too, ugh) so I'm familiar with at least some of the symptoms. And so far the only problems I'm seeing are these, and w/r/t Homebrew Cask specifically; formula-based
I appreciate the warning, and fortunately I have multiple verified backups of my data, if it comes to that. |
Yeah, and I'm being transparent - I could be completely wrong and it is a Homebrew Cask issue, but I don't know what it would immediately be. One of the other maintainers may have a better idea, and I'll continue to give it some thought. The fact it persists after reboots is the concerning part, since if you had situations with locked or open resources those would be cleared on restart. The worst problems are "sometime" problems. Have you gotten any of |
Right? That was concerning me too. And I really was quite sure I hadn't noticed any other signs of data corruption—at least, not on my main drive. But out of an abundance of caution, I tried rebooting again, except I unplugged all my external drives first... and would you believe it, suddenly everything was working. It turns out that one of my external drives has some kind of filesystem fsck-up (inode/flag mismatches, whatever those are) which Disk Utility can identify but apparently can't repair. Since everything (Homebrew, Cask, and Disk Utility) is working as expected without that drive plugged in, I have to assume its filesystem problems were somehow causing And so, a little sheepishly, I'm closing this issue. I really appreciate everyone's time, especially @krehel for putting me onto the idea of a dodgy disk. Thanks! ❤️ |
Happy to help @zgracem - unfortunate circumstance but glad we got it potentially identified. What you mentioned makes sense - and Best of luck in resolution of your issue. |
Verification
--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
So I tried upgrading the Twine cask this morning and the operation stalled indefinitely: I had to
^C
it after 15 minutes. I tried uninstalling the cask, which seemed to work. But then I tried reinstalling it, which also resulted in Homebrew hanging until I hit^C
about 10 minutes later.brew install --cask twine --force
didn't help.brew update-reset && brew update
ran OK but didn't fix the problem.brew install --cask twine --appdir=/Applications
(my default is--appdir=~/Applications
) didn't help.rm -rf /usr/local/Caskroom/twine
per this comment didn't help.rm -f ~/Library/Caches/Homebrew/downloads/*--Twine-*.dmg
) didn't help.ls -dl "$(brew --caskroom)"
reveals that I am the owner of the Caskroom directory.brew install --cask twine --verbose --debug
(see below) seems to suggest a problem unmounting the installation disk image, but I don't know enough about macOS to troubleshoot any further.Finally, for whatever it's worth, I had the same problem upgrading/reinstalling Obsidian last week, when I didn't have time to save the command output or open an issue. But that leads me to suspect this isn't a problem with Twine per se.
Command that failed
brew upgrade --cask twine; brew install --cask twine
Output of command with
--verbose --debug
Output of
brew doctor
andbrew config
Output of
brew tap
The text was updated successfully, but these errors were encountered: