duckdb: 0.1.8 -> 0.2.1 #97113
Merged
duckdb: 0.1.8 -> 0.2.1 #97113
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
replace with `false` as its use here is pointless anyway.
risicle
approved these changes
Sep 4, 2020
|
@ofborg build duckdb python37Packages.duckdb |
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.
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/cwida/duckdb/releases.
meta.description for duckdb is: "DuckDB is an embeddable SQL OLAP Database Management System"
meta.homepage for duckdb is: "https://github.com/cwida/duckdb"
meta.changelog for duckdb is: ""
Updates performed
To inspect upstream changes
Release on GitHub
Compare changes on GitHub
Impact
Checks done (click to expand)
built on NixOS
The tests defined in
passthru.tests, if any, passed0 of 0 passed binary check by having a zero exit code.
0 of 0 passed binary check by having the new version present in output.
found 0.2.1 with grep in /nix/store/93b754b73mgyqd1734q6hc3fw67nxgw9-duckdb-0.2.1
directory tree listing: https://gist.github.com/ca878526a5f74336c1e51d11605a0db3
du listing: https://gist.github.com/2c28c335bcd7533683595ffc120dc6d8
Rebuild report (if merged into master) (click to expand)
Instructions to test this update (click to expand)
Either download from Cachix:
(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the
trusted-userslist or you can usesudosince root is effectively trusted.Or, build yourself:
After you've downloaded or built it, look at the files and if there are any, run the binaries:
Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of
nixpkgs-review12 packages failed to build:
1 package built:
Maintainer pings
cc @costrouc for testing.