Closed
Conversation
Member
Author
|
@Bot-wxt1221 Does the |
d4ff400 to
0aac48c
Compare
- Update to 1.3.49. - Add new `curl` buildInput as per upstream.
0aac48c to
90c6153
Compare
Member
Author
|
I'm going to close and open a new PR - it turns out Buildbox has a newer version available. |
Member
Author
|
@Bot-wxt1221 Can you review #487331 please? Thanks! |
This file contains hidden or 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.
Updating Buildbox derivation:
curlbuildInput as per upstream.We should have had the @r-ryantm bot make PRs automatically, but it didn't seem to. Buildbox releases regularly, so if anyone has clues as to why the bot didn't work, please LMK. I suspect its due to the new
curldependency.Things done
passthru.tests.nixpkgs-reviewon this PR. See nixpkgs-review usage../result/bin/.