Re-add openSUSE Tumbleweed to CI and packages. #16869
Draft
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
|
Rebased to pick up latest changes in master. |
|
One reason that the build fails is that the gcc compiler of package builder (Tumbleweed) does not provide the Edited: w8 I am not 100% sure about this commend |
|
Rebased to pick up latest changes. |
|
Rebased again to pick up latest changes. |
|
Rebased to pick up the latest changes in master (in particular, the protobuf changes). |
|
Rebased to pick up the latest changes (including a fix for Protobuf/Abseil handling that should make this finally work). |
github-actions
bot
added
the
area/packaging
This seems to be required to get openSUSE Tumbleweed to handle them properly when installed from a local directory.
This is needed to make the install work properly on openSUSE.
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.
Summary
Due to issues in the upstream handling of certain packages (namely, certain packages can’t actually be upgraded in openSUSE Docker containers because they blindly assume certain constraints that are not met there), we previously had to remove Tumbleweed from CI.
This PR re-adds Tumbleweed, with the following caveats:
Test Plan
CI passes on this PR.
The mitigations for the package testing code cannot be fully tested without the problematic situation occurring in the first place and it’s not really possible to predict when it will come up, so there’s not a good way to test them.