Closed Tealk closed 3 years ago
The same issue is on 10.5 when using the command brew autoupdate --start --upgrade --enable-notification
.
The command is running fine with the --enable-notification
.
Oh right, the error occurs only when you chain commands together.
So should all the commands be run seperntly? I haven't been able to get this to work (with notifications) in the last two weeks.
So if you want all the "flags" on run all fo these commands?
brew autoupdate --start 43200
brew autoupdate --upgrade
brew autoupdate --cleanup
brew autoupdate --enable-notification
I feel like on my old OS i was able to run.
brew autoupdate --start 43200 --upgrade --cleanup --enable-notification
I've manage to chain all commands except --enable-notification. So just do brew autoupdate --start 43200 --upgrade --cleanup first and then brew autoupdate --enable-notification
Excellent trying that now
Hey I tried running the commands in the order you mentioned but haven't gotten a notification that its running on one of my machines running OS X Catalina (It is working on a different machine same commands, so def a homebrew issue on my end)
I tried uninstalling Brew and reinstalling but still haven't gotten the notification in the time frame or on restart.
brew autoupdate --status Autoupdate is installed and running
Anything I can try with the logs or commands to give it a kick
So should all the commands be run seperntly? I haven't been able to get this to work (with notifications) in the last two weeks.
So if you want all the "flags" on run all fo these commands?
brew autoupdate --start 43200
brew autoupdate --upgrade
brew autoupdate --cleanup
brew autoupdate --enable-notification
I feel like on my old OS i was able to run.
brew autoupdate --start 43200 --upgrade --cleanup --enable-notification
This does not work, it will not affect the generated updater
script in ~/Library/Application Support/com.github.domt4.homebrew-autoupdate
.
You need to --delete
if you want to --start
with different parameters, else the updater
script is not updated.
Sorry I'm lost here.
I have run the brew autoupdate --delete command before setting new peramaters, but after doing that should I run all of those commands one at a time
brew autoupdate --start 43200 brew autoupdate --upgrade
ect..
I tried running them all together without notification and running brew autoupdate --enable-notification by itself afterwards but I am still not getting notifications.
From what I can gather, right now you can't run it with notifications. Either you run the script and don't get notifications or you just don't run it and wait for a fix
But in case you want to run it, it works. I have noticed my packages getting updated
https://github.com/DomT4/homebrew-autoupdate/pull/32#issuecomment-709678688
Some explanation there on the wait time. Does anyone still have issues after doing brew update
and running the autoupdate
script with --enable-notification
enabled?
Works for me, thanks!
Hello, I am using MacOS 11 and get the following error message when executing the script: