ceres-solver 2.1.0 -> 2.2.0 https://repology.org/project/ceres-solver/versions
attrpath: ceres-solver
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/ceres-solver/default.nix b/pkgs/development/libraries/ceres-solver/default.nix
index 7052c98d8ef8..9aa56ede07c5 100644
--- a/pkgs/development/libraries/ceres-solver/default.nix
+++ b/pkgs/development/libraries/ceres-solver/default.nix
@@ -19,11 +19,11 @@ assert runTests -> gflags != null;
stdenv.mkDerivation rec {
pname = "ceres-solver";
- version = "2.1.0";
+ version = "2.2.0";
src = fetchurl {
url = "http://ceres-solver.org/ceres-solver-${version}.tar.gz";
- sha256 = "sha256-99dO7N4K7XW/xR7EjJHQH+Fqa/FrzhmHpwcyhnAeL8Y=";
+ sha256 = "sha256-SLIwKnmG7OFyiYR3w7zW3rj7XPGbMye8SZaarUzt6C0=";
};
outputs = [ "out" "dev" ];
Successfully finished processing
cachix "/nix/store/ffyvarj1mgh7gza8n43linkb9sgplpcd-ceres-solver-2.2.0"
[check][nixpkgs-review]
Result of `nixpkgs-review` run on x86_64-linux [1](https://github.com/Mic92/nixpkgs-review)
9 packages failed to build:
- colmap
- colmapWithCuda
- natron
- openmvg
- openturns
- python310Packages.opensfm
- python310Packages.openturns
- python311Packages.opensfm
- python311Packages.openturns
4 packages built:
- ceres-solver
- openmvs
- rtabmap
- xfitter
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/ceres-solver/versions.
meta.description for ceres-solver is: C++ library for modeling and solving large, complicated optimization problems
meta.homepage for ceres-solver is: http://ceres-solver.org
###### Updates performed
- Version update
###### To inspect upstream changes
###### Impact
Checks done (click to expand)
---
- built on NixOS
- The tests defined in `passthru.tests`, if any, passed
- found 2.2.0 with grep in /nix/store/ffyvarj1mgh7gza8n43linkb9sgplpcd-ceres-solver-2.2.0
- found 2.2.0 in filename of file in /nix/store/ffyvarj1mgh7gza8n43linkb9sgplpcd-ceres-solver-2.2.0
---
Rebuild report (if merged into master) (click to expand)
```
13 total rebuild path(s)
13 package rebuild(s)
First fifty rebuilds by attrpath
ceres-solver
colmap
colmapWithCuda
natron
openmvg
openmvs
openturns
python310Packages.opensfm
python310Packages.openturns
python311Packages.opensfm
python311Packages.openturns
rtabmap
xfitter
```
Instructions to test this update (click to expand)
---
Either **download from Cachix**:
```
nix-store -r /nix/store/ffyvarj1mgh7gza8n43linkb9sgplpcd-ceres-solver-2.2.0 \
--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 ceres-solver https://github.com/r-ryantm/nixpkgs/archive/fe2b78eb0e6b0c5cd94c4525afd877112113cc01.tar.gz
```
Or:
```
nix build github:r-ryantm/nixpkgs/fe2b78eb0e6b0c5cd94c4525afd877112113cc01#ceres-solver
```
After you've downloaded or built it, look at the files and if there are any, run the binaries:
```
ls -la /nix/store/ffyvarj1mgh7gza8n43linkb9sgplpcd-ceres-solver-2.2.0
ls -la /nix/store/ffyvarj1mgh7gza8n43linkb9sgplpcd-ceres-solver-2.2.0/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)
9 packages failed to build:
- colmap
- colmapWithCuda
- natron
- openmvg
- openturns
- python310Packages.opensfm
- python310Packages.openturns
- python311Packages.opensfm
- python311Packages.openturns
4 packages built:
- ceres-solver
- openmvs
- rtabmap
- xfitter
---
###### Maintainer pings
cc @giogadi 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/261033