Closed WizoneDE closed 1 year ago
bevanjkay
commented
1 year ago It is possible that the install of some of your casks have incomplete metadata, there were some minor issues when the API was first introduced.
Can you try brew reinstall <token> for one or some of the affected casks and see if a newer version is installed?
WizoneDE
commented
1 year ago I did a few of them first with reinstall instead of upgrade cask
example output from one of them via reinstall:
brew reinstall --cask datagrip
==> Downloading https://download.jetbrains.com/datagrip/datagrip-2023.1.dmg
==> Downloading from https://download-cdn.jetbrains.com/datagrip/datagrip-2023.1.dmg
######################################################################## 100.0%
==> Uninstalling Cask datagrip
==> Backing App 'DataGrip.app' up to '/usr/local/Caskroom/datagrip/2022.1.5,221.5787.39/DataGrip.app'
==> Removing App '/Applications/DataGrip.app'
==> Purging files for version 2022.1.5,221.5787.39 of Cask datagrip
==> Installing Cask datagrip
==> Moving App 'DataGrip.app' to '/Applications/DataGrip.app'
🍺 datagrip was successfully installed!So you received the updated version of datagrip there. If the cask metadata was corrupted prior to the reinstall hopefully you would now receive any subsequent updates as expected.
WizoneDE
commented
1 year ago brew reinstall --cask datagrip and brew upgrade --cask datagrip
both are installing the newest version but just using brew upgrade or brew outdated wasn't listen them.
Did now force a complete reinstallation of all casks via
brew list --cask | xargs brew reinstallwill See what will happen within the next two weeks with new casks updates if they are showing up in brew outdated and will installed via brew upgraded.
razvanazamfirei
commented
1 year ago Hi @WizoneDE, based on a cursory look, the apps you are referencing are marked as being able to auto-update. See here for more information.
You can try running brew upgrade --greedy or setting HOMEBREW_UPGRADE_GREEDY to force an update. If that does not fix the problem, please let us know.
bevanjkay
commented
1 year ago @razvanazamfirei Calling a cask directly with brew upgrade <token> does not check for auto_updates do the greedy flags are unrelated here.
WizoneDE
commented
1 year ago @razvanazamfirei thanks for the linked information, makes it more clear now for me.
My idea of using brew is to have an overview over all installed apps and mostly get them automatic up to date. Even if the apps you are marked with auto_updates and offering an self update service, most of the time this is not working or helpful since not every app is offering a background update service to check in recurring intervals. some of the listed apps are only installed to have them ready if needed and not often open. but they are only searching for an update after an app start. And some of them only if you explicit force search for an update in the options menu. many of the "auto_update" flagged apps were outdated on my Mac since I only opened them a few month ago.
any chance to get an --greedy option for outdated too? get them still listed as "update available" in the outdated list would be a big benefit. I could decide to run the update via app or just force an upgrade/reinstall via brew.
And to have my brew list mostly synced with my manual update installations it would be cool to have another parameter for update like --silent or --caskonly to just update the cask to the newest version brew is offering without downloading and (re)installing the app.
razvanazamfirei
commented
1 year ago Hi @WizoneDE, thanks for the suggestions. I agree that it would make sense to have a greedy option for brew outdated. We just recently implemented HOMEBREW_UPGRADE_GREEDY so it's something we could consider implementing in the future. In the meantime, you might find https://github.com/buo/homebrew-cask-upgrade to be a neat tool that may gives similar functionality. I personally have an alias to brew cu -af which gives similar information to brew outdated --greedy.
I think the solution to your last suggestions would take quite a bit of work, but if it's something you're interested in, we're very welcoming to any PRs down in https://github.com/Homebrew/brew. 😄 Let us know how else we can help!
bevanjkay
commented
1 year ago The brew outdated command can receive either of the three greedy flags, --greedy, --greedy-latest or --greedy-auto-updates.
Verification
--force.brew update-reset && brew updateand retried my command.brew doctor, fixed as many issues as possible and retried my command.Description of issue
brew upgrade doesn't upgrade desktop apps now for a longer time. the apps are not listed under brew outdated too.
but if you start to search manually for an upgrade for a cask there are minor and major updates which will be installed....
brew list --cask | xargs brew upgrade
on my system after starting to update a few of them manually first:
example from another system: Brew upgrade and outdated doesn't show anything
Command that failed
Brew upgrade
Output of command with
--verbose --debugOutput of
brew doctorandbrew configOutput of
brew tap