monero 0.17.1.3 -> 0.17.1.5 #106010
Merged
monero 0.17.1.3 -> 0.17.1.5 #106010
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
|
Result of 1 package marked as broken and skipped:
1 package built:
|
|
Result of 2 packages built:
|
|
Any reason why we aren't bumping up to v0.17.1.5 for both? |
Am I missing something? Isn't it what this PR is doing? |
|
Result of 2 packages built:
|
|
@rnhmjoj Total brain fart on my end, apologies - thought one of them was going from 0.17.1.3 -> 0.17.1.4. LGTM |
RaghavSood
approved these changes
Dec 6, 2020
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.
Motivation for this change
Version bump
Things done
./result/bin/)nix path-info -Sbefore and after)Notes: my client stopped synchronising to the remote node, maybe it's unrelated but it would be good if someone could confirm.