-
Notifications
You must be signed in to change notification settings - Fork 47
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
Calling bottle :unneeded is deprecated! #110
Comments
It isn't just elasticsearch, it is the beats too. (Or at least filebeat, heartbeat, metricbeat, and packetbeat) edit: looks like a fix from: 29faec9 |
Same issue also in:
|
Yep those are all addressed in the change I linked |
Was able to fix it on macOS Monterey using the above commands. Output:
NOTE: THIS WILL REMOVE AND REINSTALL ALL THE ELASTIC COMPONENTS ON YOUR MAC. TAKE NECESSARY BACKUPS BEFORE PROCEEDING |
Thanks, this worked for me 👍🏽 |
Hi all, I have opened a PR to document how to solve this problem. Thanks |
That PR does not solve the problem for me. Just to really be sure I issued the commands multiple times:
The commands returned successfully. But then using one of the commands that normally shows these error messages shows that the problem wasn'te resolved:
And then the suggested won't always be right, sometimes it would be /usr/local/ instead of /opt/ And doing
And then manually typing 'upgrade' for one of the impacted beats just says it is already up-to-date and doesn't force any kind of refresh / reset to the 'main' branch Double checking the update, not even restricting it:
Git doesn't even seem to be recognizing that there are other branch options other than master?
|
It is related to the default branch renaming, see https://github.com/elastic/homebrew-tap/pull/116/files#r759735461 |
On my local MacBook, after running |
That command worked on only 1 of 4 machines. They have all been brew doctored, brew updated, and brew upgraded many times recently. Three responded with:
The fourth responded with:
|
This issue is preventing |
I finally figured out how to fix this on my own since it was causing security issues. The original configuration of the branch via homebrew wasn't right, and that bad configuration was causing all other steps to fail. @a03nikki give these sequence of 3 commands a shot.... My homebrew install puts the taps in this location, if it is different for you of course you'll need to be in the right repo spot:
That resets a broken config, replacing hardcoded "master" filter with the "*" wildcard.
should then suddenly report that it discovered a bunch of new branches and changes beyond the #111 that was the last I could see previously.
to kick it in its pants.
should now show the 7.16.3 version of elasticsearch-full(etc) and should not show any of those "deprecated" errors. |
* [doc] Document the renaming from master to main The default branch is now `main` instead of `master`. The `master` branch is not updated anymore, and therefore can generate some warning messages. This commit adds instructions to explain how to update the local configuration to point to the new `main` branch. Relates #115 #110
A deprecation warning is coming with elastic-search
Somebody have a look :)
The text was updated successfully, but these errors were encountered: