Article about RPM upgrades #1683
Merged
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
nwt
approved these changes
May 26, 2021
Co-authored-by: Noah Treuhaft <[email protected]>
Co-authored-by: Noah Treuhaft <[email protected]>
Co-authored-by: Noah Treuhaft <[email protected]>
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.
As described in #1565, testing has revealed a minor incompatibility in the Linux RPM packaging between our old and new installers, such that these Linux users will need to manually uninstall the old release before the new one can install successfully. This is a bummer, but thankfully RPM Linux happens to be the least popular of our OS platform permutations, and it's only a one-time procedure to get over this transition, so it's hopefully not an excessive burden.
In addition to adding the article to the wiki, when we announce the
v0.25.0release, my intent is to also put a link to the article in a prominent red-lettered notice at https://www.brimsecurity.com/download/ near the links to the Linux artifacts in hopes of calling the appropriate users' attention to the article before they download the RPM and see the installation fail. I'll also plan to emphasize it in the Release Notes. I've made notes-to-self regarding both of these details in my checklist for when we're doing final assembly of the next release.Closes #1565