-
-
Notifications
You must be signed in to change notification settings - Fork 10.7k
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
finding outdated casks with and without appcast #55268
Comments
2018-11-21 output up |
@core-code Thanks! Got the PRs up as well. The output is getting better and better. No problems today. |
awesome, thanks ;) 2018-11-22 output up |
@core-code Happy Thanksgiving! 🦃 Sorry I was a little late today. Here's the work for the day... data-dog - #54739 Everything else was updated. |
thanks ;) 2018-11-23 output up |
@core-code ...done.👍 ipsecuritas-This is a build number update. It's also not on their website. http://www.lobotomo.com/products/IPSecuritas/index.html
|
actually there was a problem 'mapping' the version number here, thanks for the heads-up, should be fixed now |
2018-11-24 output up |
@core-code Done. Some of them weren't merged but are now...👌 oni - Beta |
thanks ;) 2018-11-25 output up |
@core-code done. datadog-agent - #54739 |
this seems to be some sort of eternal quest ^^ 2018-11-26 output up - really tiny this time |
@core-code Done. datadog-agent - #54739 (The quest continues...) |
it seems they changed their download URLs, and are now hosting here: i've sent a PR |
@core-code Good work! 👌 |
2018-11-27 output up |
@core-code |
thanks ;) |
@core-code Done. appgate-sdp-client - No newer version available for download. |
thanks, adjusted the postprocessing 2018-11-29 output up |
@core-code |
2018-11-30 output up |
@core-code 🙌 done. alfred - No newer version available for download. |
2018-12-01 output up |
@core-code done - no problemos today 🎉 |
2018-12-02 output is online 🙂 |
@suschizu Thank you for the heads up! 🙏 datadog-agent - #54739 curl: (56) Unexpected EOF
Error: Download failed on Cask 'birdfont' with message: Download failed: https://birdfont.org/download/birdfont-3.17.0-free.dmg musescore - No newer version available for download. |
2018-12-03 output up probably a lot of things in there that already have open pull requests as things haven't been merged for a few days now. i want to include a check for open pull requests but didn't come around to it yet. also there is something new today: |
Should be fixed. |
Thanks @ran-dall! |
@suschizu Done ✊ | Thanks @core-code @vitorgalvao newversion_github-2020-12-10: 14 cask updates detected / 06 cask updates sent
newversion_sparkle-2020-12-10: 16 cask updates detected / 05 cask updates sent
database-processed-2020-12-10: 32 cask updates detected / 17 cask updates sent
containsversion-2020-12-10: 21 cask updates detected / 14 cask updates sent
UPDATED
|
Thanks @ran-dall! |
@suschizu Done ✊ newversion_github-2020-12-11: 16 cask updates detected / 08 cask updates sent
newversion_sparkle-2020-12-11: 26 cask updates detected / 09 cask updates sent
database-processed-2020-12-11: 26 cask updates detected / 12 cask updates sent
containsversion-2020-12-11: 20 cask updates detected / 09 cask updates sent
UPDATED
|
Thanks @ran-dall! |
@suschizu Done ✊ newversion_github-2020-12-12: 17 cask updates detected / 07 cask updates sent
newversion_sparkle-2020-12-12: 14 cask updates detected / 05 cask updates sent
database-processed-2020-12-12: 28 cask updates detected / 18 cask updates sent
containsversion-2020-12-12: 14 cask updates detected / 06 cask updates sent
UPDATED
|
Thanks @ran-dall! |
@suschizu Done ✊ newversion_github-2020-12-13: 19 cask updates detected / 11 cask updates sent
newversion_sparkle-2020-12-13: 06 cask updates detected / 02 cask updates sent
database-processed-2020-12-13: 06 cask updates detected / 02 cask updates sent
containsversion-2020-12-13: 09 cask updates detected / 03 cask updates sent
UPDATED |
Thanks @ran-dall! |
@suschizu Done ✊ newversion_github-2020-12-14: 17 cask updates detected / 13 cask updates sent
newversion_sparkle-2020-12-14: 09 cask updates detected / 05 cask updates sent
database-processed-2020-12-14: 02 cask updates detected / 02 cask updates sent containsversion-2020-12-14: 19 cask updates detected / 11 cask updates sent
UPDATED
|
@suschizu How we looking for today? |
hey @ran-dall - sorry for being so late - Christmas is coming closer :/ |
@suschizu Done ✊ newversion_github-2020-12-15: 17 cask updates detected / 09 cask updates sent
newversion_sparkle-2020-12-15: 30 cask updates detected / 15 cask updates sent
database-processed-2020-12-15: 03 cask updates detected / 03 cask updates sent containsversion-2020-12-15: 35 cask updates detected / 25 cask updates sent
UPDATED
|
Thanks @ran-dall! |
@suschizu Done ✊ newversion_github-2020-12-16: 12 cask updates detected / 10 cask updates sent
newversion_sparkle-2020-12-16: 09 cask updates detected / 08 cask updates sent
database-processed-2020-12-16: 03 cask updates detected / 01 cask updates sent
containsversion-2020-12-16: 13 cask updates detected / 10 cask updates sent
UPDATED
|
Thanks @ran-dall! |
@suschizu Done ✊ | @suschizu Can you post the output early tomorrow, please? newversion_github-2020-12-17: 15 cask updates detected / 09 cask updates sent
newversion_sparkle-2020-12-17: 15 cask updates detected / 09 cask updates sent
database-processed-2020-12-17: 03 cask updates detected / 02 cask updates sent
containsversion-2020-12-17: 32 cask updates detected / 23 cask updates sent
UPDATED
|
Thanks @ran-dall! |
@suschizu Done ✊ | Thank you! newversion_github-2020-12-18: 11 cask updates detected / 06 cask updates sent
newversion_sparkle-2020-12-18: 12 cask updates detected / 07 cask updates sent
database-processed-2020-12-18: 04 cask updates detected / 03 cask updates sent
containsversion-2020-12-18: 14 cask updates detected / 10 cask updates sent
UPDATED
|
Thanks @ran-dall! |
@suschizu Done ✊ newversion_github-2020-12-19: 17 cask updates detected / 10 cask updates sent
newversion_sparkle-2020-12-19: 14 cask updates detected / 04 cask updates sent
database-processed-2020-12-19: 02 cask updates detected / 02 cask updates sent containsversion-2020-12-19: 14 cask updates detected / 12 cask updates sent
UPDATED
|
Thanks @ran-dall! |
@suschizu Done ✊ newversion_github-2020-12-20: 11 cask updates detected / 07 cask updates sent
newversion_sparkle-2020-12-20: 09 cask updates detected / 04 cask updates sent
database-processed-2020-12-20: 05 cask updates detected / 04 cask updates sent
containsversion-2020-12-20: 03 cask updates detected / 01 cask updates sent
UPDATED
|
Thanks @ran-dall! |
@suschizu Done ✊ newversion_github-2020-12-21: 09 cask updates detected / 05 cask updates sent
newversion_sparkle-2020-12-21: 12 cask updates detected / 04 cask updates sent
database-processed-2020-12-21: 06 cask updates detected / 02 cask updates sent
containsversion-2020-12-21: 14 cask updates detected / 11 cask updates sent
UPDATED
|
@ran-dall i wanted to let you know that we are going to stop providing the daily data upload. there have been many issues over the past year where breaking changes were introduced without giving us any kind of advance notice. today the casks were modified to remove the appcasts and add some livecheck code which breaks our system. i only learned about this after the changes had already gone live. needless to say, we cannot continue to depend on a system that just makes breaking changes like this. i think its obvious that making changes like this without discussion or advance warning can only be called hostile and there seems to be zero consideration for our system that has sent more than 25.000 PRs from our combined efforts. thanks for your help over the years and for being part of our team to move this project forward. from our side this time has now concluded and we are going stop pouring more valuable time into this. |
@core-code It's the end of an era, that's for sure. That said, I do agree with your point of view, and FWIW I share similar feelings that our efforts are/were somewhat undervalued... NTM that in our time here our team has become some of the more notable contributors of this repo. So yes, I feel like we should have been looped in many of conversations relating to these situations. In fact, I think we've had a similar conversation a few months ago, when I decided to deprecate V1 and start working on V2. Regardless, I would like to maybe hear a little bit more from @vitorgalvao and @reitermarkus about what the reasoning really was. Also, I would like to get this "not looped in" situation taken care of, so that it doesn't keep happening in the future. Espcially for those of us, that will still be around. From where I'm standing, I already started working with All in all though, I'd like to think we had a good run. I also think we all became great friends in the process too. So, I don't like the idea of not seeing you around anymore. I (for one) still plan on contiuning to work on To end this on a positive note though, I'd like to thank everyone else that has helped in the last few years, it's been really great and an outstanding experience to work with all of you and getting to know you guys. I hope that all of you (including you @core-code (and @suschizu too) 😉) are still around when MLv2 effort picks up with the MLv1 left off. I'll probably start a thread in the coming days about the MLv2 to get people's feedback and what they would like to see in the new ML. Till then though, I wish everyone happy holidays and a very happy new year (after all 2020 was a bit of a dumpster fire). |
hello HBC community,
one of the 'problems' of Homebrew Cask is that it requires constant maintainance to keep working. any Cask with a version number needs to be updated every time a new version of this app is released.
for apps that have an sparkle/rss or github/atom feed from the vendor, keeping them up-to-date is relatively straightforward. @brianmorton has a great system implemented here. (his system incidentally also works for non-sparkle appcasts, but currently most of the Casks that have no sparkle, also have no appcast-stanza)
therefore i've been focusing my efforts on automatically finding outdated Casks on those without "sparkle appcast". every day i let a script run that compares the version of the Casks without appcast, to the database of app-versions that our company maintains. every day the script finds around 5 - 10 outdated Casks that should be updated e.g. using 'cask-repair'.
the design and implementation of the system is discussed here: #52837
and there was also a bit discussion about this here:
#54811
so, long story short, basically it would be great if the community could have a look at the
"cr-processed-DATE.txt"
files i place here:
http://macupdater.net/cask-repair/
each day and look through them to see which of those entries are real, official new releases of the apps and submit cask-repairs accordingly. i think this would also be a good task to get started with contributing to HBC.
for the time being, it would be best to note false positives (i.e. entries that are not real official releases of this app) here so i'll add them to the different filter-lists in the postprocessing script so that they won't appear in the next days output anymore.
UPDATE 11.dec.2018:
ok, the cask-repair system for apps without appcast has been working quite well over the past month, i guess around 80% success rate (i.e. percentage of entries in the txt files that are actually valid new releases). but, it seems like there are quite a lot of casks WITH appcast that are outdated despite the appcast. so i've implemented two new checks to try to improve the situation there:
crsparklefeed-DATE.txt
=> this checks each cask with an valid sparkle appcast each day and generates an output if the appcast has a new 'newest' entry since yesterday. since sparkle feeds should only contain valid releases, 100% of those should be valid updates to be done via 'cask-repair' (if someone else hasn't beaten you to it).
crgithub-DATE.txt
=> this checks each cask that has its releases on github (as denoted via the URL or APPCAST stanza) and checks github if a new release has been posted since yesterday. if available, it tries to query the 'Latest Release' as denoted on github by the developer, so that beta releases are not picked up. if no 'Latest Release' is marked, it falls back to just using the newest release and downgrades from error to warning.
The text was updated successfully, but these errors were encountered: