lscolors 0.16.0 -> 0.17.0 https://github.com/sharkdp/lscolors/releases
attrpath: lscolors
Checking auto update branch...
No auto update branch exists
[version] 
[version] generic version rewriter does not support multiple hashes
[rustCrateVersion] 
[rustCrateVersion] Replacing cargoHash with sha256-1Cyg4WT4xYqc3s5AOXR9GfcS3qKOgscYujGXR9fzuCA=
[rustCrateVersion] Finished updating Crate version and replacing hashes
[golangModuleVersion] 
[golangModuleVersion] Not a buildGoModule package with vendorSha256 or vendorHash
[npmDepsVersion] 
[npmDepsVersion] No npmDepsHash
[updateScript] 
[updateScript] skipping because derivation has no updateScript
Diff after rewrites:
diff --git a/pkgs/applications/misc/lscolors/default.nix b/pkgs/applications/misc/lscolors/default.nix
index 99c330fa6804..d61499ed0737 100644
--- a/pkgs/applications/misc/lscolors/default.nix
+++ b/pkgs/applications/misc/lscolors/default.nix
@@ -2,14 +2,14 @@
 
 rustPlatform.buildRustPackage rec {
   pname = "lscolors";
-  version = "0.16.0";
+  version = "0.17.0";
 
   src = fetchCrate {
     inherit version pname;
-    hash = "sha256-gLtQIqdU6syTo+Z+P59kIpwEtiGCr/DOom9+jA8Uq98=";
+    hash = "sha256-efkSiwxL7sZIwFXJZunddAb4lTOfhj8oOEOUW3kyRXI=";
   };
 
-  cargoHash = "sha256-OA9iYGwKElvRaKoyelH9w5ZphoLKrbk8VXwZ2NyLLQY=";
+  cargoHash = "sha256-1Cyg4WT4xYqc3s5AOXR9GfcS3qKOgscYujGXR9fzuCA=";
 
   buildFeatures = [ "nu-ansi-term" ];
 

Successfully finished processing
cachix "/nix/store/hj686sxazs00jjqcbgsq3jb00ijb58nf-lscolors-0.17.0"
Waiting for OfBorg: https://events.ofborg.org/stats.php's evaluator.messages.waiting = 4
[check][nixpkgs-review]
Result of `nixpkgs-review` run on x86_64-linux [1](https://github.com/Mic92/nixpkgs-review)
<details>
  <summary>1 package built:</summary>
  <ul>
    <li>lscolors</li>
  </ul>
</details>

Automatic update generated by [nixpkgs-update](https://github.com/ryantm/nixpkgs-update) tools. This update was made based on information from https://github.com/sharkdp/lscolors/releases.


meta.description for lscolors is: Rust library and tool to colorize paths using LS_COLORS

meta.homepage for lscolors is: https://github.com/sharkdp/lscolors

meta.changelog for lscolors is: https://github.com/sharkdp/lscolors/releases/tag/v0.17.0


###### Updates performed
- Rust version update

###### To inspect upstream changes





###### Impact

<b>Checks done</b>

---

- built on NixOS
- The tests defined in `passthru.tests`, if any, passed
- found 0.17.0 in filename of file in /nix/store/hj686sxazs00jjqcbgsq3jb00ijb58nf-lscolors-0.17.0

---

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

```
1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
lscolors
```

</details>

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

---

Either **download from Cachix**:
```
nix-store -r /nix/store/hj686sxazs00jjqcbgsq3jb00ijb58nf-lscolors-0.17.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 lscolors https://github.com/r-ryantm/nixpkgs/archive/9b2f4b164b2cadc37cb588d8bc3da7715a06d61c.tar.gz
```
Or:
```
nix build github:r-ryantm/nixpkgs/9b2f4b164b2cadc37cb588d8bc3da7715a06d61c#lscolors
```

After you've downloaded or built it, look at the files and if there are any, run the binaries:
```
ls -la /nix/store/hj686sxazs00jjqcbgsq3jb00ijb58nf-lscolors-0.17.0
ls -la /nix/store/hj686sxazs00jjqcbgsq3jb00ijb58nf-lscolors-0.17.0/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.

Result of `nixpkgs-review` run on x86_64-linux [1](https://github.com/Mic92/nixpkgs-review)
<details>
  <summary>1 package built:</summary>
  <ul>
    <li>lscolors</li>
  </ul>
</details>

---

###### Maintainer pings

cc @SuperSandro2000 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/283754