cryptominisat 5.11.14 -> 5.11.15 https://repology.org/project/cryptominisat/versions
attrpath: cryptominisat
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/applications/science/logic/cryptominisat/default.nix b/pkgs/applications/science/logic/cryptominisat/default.nix
index 0645fd29522f..a028803db139 100644
--- a/pkgs/applications/science/logic/cryptominisat/default.nix
+++ b/pkgs/applications/science/logic/cryptominisat/default.nix
@@ -8,13 +8,13 @@
 
 stdenv.mkDerivation rec {
   pname = "cryptominisat";
-  version = "5.11.14";
+  version = "5.11.15";
 
   src = fetchFromGitHub {
     owner = "msoos";
     repo = "cryptominisat";
     rev = version;
-    hash = "sha256-p/sVinjEh078PGtJ6JBRA8EmrJVcchBs9L3bRZvCHuo=";
+    hash = "sha256-OenuIPo5U0+egWMpxfaKWPLbO5YRQJSXLYptih+ZQQ0=";
   };
 
   buildInputs = [ python3 boost ];

Successfully finished processing
cachix "/nix/store/jz59ja5jvchl1ngagb75q3j9aig1sn5a-cryptominisat-5.11.15"
[check][nixpkgs-review]
[check][nixpkgs-review] took longer than 45m and timed out
nixpkgs-review took longer than 45m and timed out
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/cryptominisat/versions.


meta.description for cryptominisat is: An advanced SAT Solver

meta.homepage for cryptominisat is: https://github.com/msoos/cryptominisat




###### Updates performed
- Version update

###### To inspect upstream changes

- [Release on GitHub](https://github.com/msoos/cryptominisat/releases/tag/5.11.15)

- [Compare changes on GitHub](https://github.com/msoos/cryptominisat/compare/5.11.14...5.11.15)

###### Impact

<details>
<summary>
<b>Checks done</b> (click to expand)
</summary>

---

- built on NixOS
- The tests defined in `passthru.tests`, if any, passed
- found 5.11.15 with grep in /nix/store/jz59ja5jvchl1ngagb75q3j9aig1sn5a-cryptominisat-5.11.15
- found 5.11.15 in filename of file in /nix/store/jz59ja5jvchl1ngagb75q3j9aig1sn5a-cryptominisat-5.11.15

---

</details>
<details>
<summary>
<b>Rebuild report</b> (if merged into master) (click to expand)
</summary>

```
4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath
bitwuzla
cryptominisat
klee
stp
```

</details>

<details>
<summary>
<b>Instructions to test this update</b> (click to expand)
</summary>

---

Either **download from Cachix**:
```
nix-store -r /nix/store/jz59ja5jvchl1ngagb75q3j9aig1sn5a-cryptominisat-5.11.15 \
  --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 cryptominisat https://github.com/r-ryantm/nixpkgs/archive/1d182037be34c894dded0565e64da762a72c8759.tar.gz
```
Or:
```
nix build github:r-ryantm/nixpkgs/1d182037be34c894dded0565e64da762a72c8759#cryptominisat
```

After you've downloaded or built it, look at the files and if there are any, run the binaries:
```
ls -la /nix/store/jz59ja5jvchl1ngagb75q3j9aig1sn5a-cryptominisat-5.11.15
ls -la /nix/store/jz59ja5jvchl1ngagb75q3j9aig1sn5a-cryptominisat-5.11.15/bin
```

---

</details>
<br/>



### 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.

nixpkgs-review took longer than 45m and timed out

---

###### Maintainer pings

cc @Mic92 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/263288