eza: 0.18.10 -> 0.18.11

[r-ryantm]

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/eza-community/eza/releases.

meta.description for eza is: A modern, maintained replacement for ls

meta.homepage for eza is: https://github.com/eza-community/eza

meta.changelog for eza is: https://github.com/eza-community/eza/releases/tag/v0.18.11

Updates performed

• Rust version update

To inspect upstream changes

• Release on GitHub

• Compare changes on GitHub

Impact

Checks done

---

• built on NixOS
• The tests defined in passthru.tests, if any, passed
• found 0.18.11 with grep in /nix/store/yi8sjbxhy8gm2krgpg5yh38x5k34qb42-eza-0.18.11
• found 0.18.11 in filename of file in /nix/store/yi8sjbxhy8gm2krgpg5yh38x5k34qb42-eza-0.18.11

---

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
eza

Instructions to test this update (click to expand)

---

Either download from Cachix:

nix-store -r /nix/store/yi8sjbxhy8gm2krgpg5yh38x5k34qb42-eza-0.18.11 \
  --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 eza https://github.com/r-ryantm/nixpkgs/archive/fad5531d02141c33462d57fd4b7a789934721cd3.tar.gz

Or:

nix build github:r-ryantm/nixpkgs/fad5531d02141c33462d57fd4b7a789934721cd3#eza

After you've downloaded or built it, look at the files and if there are any, run the binaries:

ls -la /nix/store/yi8sjbxhy8gm2krgpg5yh38x5k34qb42-eza-0.18.11
ls -la /nix/store/yi8sjbxhy8gm2krgpg5yh38x5k34qb42-eza-0.18.11/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 --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

2 packages built:

• eza
• eza.man

---

Maintainer pings

cc @cafkafk @9glenda for testing.

[cafkafk]

I've already submitted a PR for this

[AndersonTorres]

I've already submitted a PR for this

Nope.

https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+eza+is%3Aclosed

The most recent is 0.18.10

And 0.18.11 was released 10 minutes ago.

[cafkafk]

I've already submitted a PR for this

Nope.

https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+eza+is%3Aclosed

The most recent is 0.18.10

And 0.18.11 was released 10 minutes ago.

Seems I failed to click enter when I released it this morning, this seems identical to what I had which I tested so lgtm

[cafkafk]

And 0.18.11 was released 10 minutes ago.

This is off by about 15 hours https://github.com/eza-community/eza/releases/tag/v0.18.11

[uncenter]

I've already submitted a PR for this

Nope.
https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+eza+is%3Aclosed
The most recent is 0.18.10
And 0.18.11 was released 10 minutes ago.

Seems I failed to click enter when I released it this morning, this seems identical to what I had which I tested so lgtm

Why "lgtm" and then open #305421 with the exact same changes?

[AndersonTorres]

Result of nixpkgs-review pr 305314 run on x86_64-linux 1

2 packages built:

• eza
• eza.man

[AndersonTorres]

@NixOS/nixpkgs-merge-bot merge

[nixpkgs-merge-bot]

@AndersonTorres merge not permitted (#305350):
github id: 5954806 is not in maintainers, valid maintainers are: cafkafk, 9glenda

[cafkafk]

@NixOS/nixpkgs-merge-bot merge

[nixpkgs-merge-bot]

Merge completed