fix: make updates work from zoom.yml setup #13
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Zoom seems to have changed the setup of their repositories and seems to be working towards proper Linux repositories for automatic updates. I only got the relevant info via a support request, but was then handed a very nice Markdown document with valid instructions of how to configure the Zoom RPM repo. I have implemented these recommendations with this new setup and tested it by uninstalling Zoom (and repo and key) on my Framework laptop and rerunning the playbook. So this should be working (until Zoom decides on a different architecture)...