duckdb 0.9.1 -> 0.9.2 https://repology.org/project/duckdb/versions attrpath: duckdb Checking auto update branch... No auto update branch exists [version] [version] updated version and sha256 [rustCrateVersion] [rustCrateVersion] No cargoSha256 or cargoHash found [golangModuleVersion] [golangModuleVersion] Not a buildGoModule package with vendorSha256 or vendorHash [npmDepsVersion] [npmDepsVersion] No npmDepsHash [updateScript] [updateScript] skipping because derivation has no updateScript [quotedUrls] [quotedUrls] nothing found to replace Diff after rewrites: diff --git a/pkgs/development/libraries/duckdb/default.nix b/pkgs/development/libraries/duckdb/default.nix index c9f6711780b0..801ad7979aee 100644 --- a/pkgs/development/libraries/duckdb/default.nix +++ b/pkgs/development/libraries/duckdb/default.nix @@ -15,13 +15,13 @@ let in stdenv.mkDerivation rec { pname = "duckdb"; - version = "0.9.1"; + version = "0.9.2"; src = fetchFromGitHub { owner = pname; repo = pname; rev = "v${version}"; - hash = "sha256-UG/vV/6WxVLq9mdze8pSDFJIekOgGsg93dzMq6eP6Dg="; + hash = "sha256-QFK8mEMcqQwALFNvAdD8yWixwMYHSbeo6xqx86PvejU="; }; patches = [ ./version.patch ]; Successfully finished processing cachix "/nix/store/fqk1yrpm8kgwscc8wdskj307m6s6dyx0-duckdb-0.9.2" [check][nixpkgs-review] Result of `nixpkgs-review` run on x86_64-linux [1](https://github.com/Mic92/nixpkgs-review)
2 packages failed to build:
9 packages built:
Automatic update generated by [nixpkgs-update](https://github.com/ryantm/nixpkgs-update) tools. This update was made based on information from https://repology.org/project/duckdb/versions. meta.description for duckdb is: Embeddable SQL OLAP Database Management System meta.homepage for duckdb is: https://duckdb.org/ meta.changelog for duckdb is: https://github.com/duckdb/duckdb/releases/tag/v0.9.2 ###### Updates performed - Version update ###### To inspect upstream changes - [Release on GitHub](https://github.com/duckdb/duckdb/releases/tag/v0.9.2) - [Compare changes on GitHub](https://github.com/duckdb/duckdb/compare/v0.9.1...v0.9.2) ###### Impact
Checks done (click to expand) --- - built on NixOS - The tests defined in `passthru.tests`, if any, passed - found 0.9.2 with grep in /nix/store/fqk1yrpm8kgwscc8wdskj307m6s6dyx0-duckdb-0.9.2 - found 0.9.2 in filename of file in /nix/store/fqk1yrpm8kgwscc8wdskj307m6s6dyx0-duckdb-0.9.2 ---
Rebuild report (if merged into master) (click to expand) ``` 11 total rebuild path(s) 11 package rebuild(s) First fifty rebuilds by attrpath duckdb mycli python310Packages.duckdb python310Packages.duckdb-engine python310Packages.ibis-framework python310Packages.sqlglot python311Packages.duckdb python311Packages.duckdb-engine python311Packages.ibis-framework python311Packages.sqlglot sbclPackages.duckdb ```
Instructions to test this update (click to expand) --- Either **download from Cachix**: ``` nix-store -r /nix/store/fqk1yrpm8kgwscc8wdskj307m6s6dyx0-duckdb-0.9.2 \ --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \ --option trusted-public-keys ' nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs= cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY= ' ``` (The Cachix cache is only trusted for this store-path realization.) For the Cachix download to work, your user must be in the `trusted-users` list or you can use `sudo` since root is effectively trusted. Or, **build yourself**: ``` nix-build -A duckdb https://github.com/r-ryantm/nixpkgs/archive/eb641e6b6da5662f405f2d1661334822f3b41d1d.tar.gz ``` Or: ``` nix build github:r-ryantm/nixpkgs/eb641e6b6da5662f405f2d1661334822f3b41d1d#duckdb ``` After you've downloaded or built it, look at the files and if there are any, run the binaries: ``` ls -la /nix/store/fqk1yrpm8kgwscc8wdskj307m6s6dyx0-duckdb-0.9.2 ls -la /nix/store/fqk1yrpm8kgwscc8wdskj307m6s6dyx0-duckdb-0.9.2/bin ``` ---

### 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-review` run on x86_64-linux [1](https://github.com/Mic92/nixpkgs-review)
2 packages failed to build:
9 packages built:
--- ###### Maintainer pings cc @costrouc @cpcloud for [testing](https://github.com/ryantm/nixpkgs-update/blob/master/doc/nixpkgs-maintainer-faq.md#r-ryantm-opened-a-pr-for-my-package-what-do-i-do). https://api.github.com/repos/NixOS/nixpkgs/pulls/267732