Dockerfile: fail fast if mbuffer is not compatible/fetchable [#589] #635
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
This was referenced Feb 7, 2024
oetiker
previously approved these changes
Mar 11, 2024
oetiker
approved these changes
Mar 13, 2024
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.
Another old branch found in the attic, addresses issue #589 to fail fast if the
mbufferpackage can not be installed from the side repo (only take time to install standard packages if we could use that addition).Related to issue #629 in a way that until its PRs #630/#632 the local
mbufferon theznapzend'ing system was actually irrelevant, it seems. And #622 and #624 as a recent example of OS version bump involved.