-
Notifications
You must be signed in to change notification settings - Fork 58
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
doesn't seem to be updating? #149
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
If I understand you correctly, you're 100% right. Everyone with your configuration is experiencing exactly the same behavior regarding the "skipped" runs due to the device being asleep. To "improve" your situation, I would recommend you the add the Please refer to the following issue and linked solution: Issue: #59 Solution: #119 It happens to be that I created the solution a while back and it worked well for months. I'll update the fork and you're welcome to test the feature by manually installing the linked branch (onece updated). |
|
I am having the same issue. Brew autoupdate does not seem to be working. Are there some logs I could check to see if it is even running?
indicates it is installed and running but I have been waiting for a couple of apps to be updated and they are not. I have the --immediate switch on and it doesn't autoupdate even after a restart. |
Yes, the path to the logfile can be found in the
Do these apps update when you run |
This new scheduler syntax is not yet support in the main release. I'll create a guide on how to test the feature tomorrow. |
Thank you, @swissbuechi , the logs helped me find the error with some apps that were not updating. |
Hi just started using. Sorry if these questions have been answered elsewhere. I did search but can't seem to find answers to what i'm looking for.
Two different macs. Both have Sequoia 15.1. I used the following command to setup the auto updater:
brew autoupdate start 604800 --upgrade --cleanup --sudo
so it should be running every week.
I did receive a notification that it would be running in the background after i first run the command. Its been longer than a week & just periodically checking
brew outdated
it doesn't look like the update has ever worked on either machine.1st how does this work if it misses an update because the machine was off? I have 1 mac that stay on all the time. The other one is on periodically. Does it run as soon as you turn it on or does it just skip it if its not on at the time is supposed to run.
Is there any mechanism i can use to see if its tried to run & if it failed or if it at least tried to run?
The text was updated successfully, but these errors were encountered: