Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

exa: 0.8.0 -> 2019-01-26 #54702

Closed
wants to merge 1 commit into from
Closed

Conversation

Nadrieril
Copy link
Contributor

Motivation for this change

exa has not had a release in more than a year, but the master branch seems stable. A new release has been requested (ogham/exa#441) but still not here.
This updates exa to the latest master version.
Ping maintainer @ehegnes if you think this is legitimate.

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Assured whether relevant documentation is up to date
  • Fits CONTRIBUTING.md.

@Mic92
Copy link
Member

Mic92 commented Jan 27, 2019

Do you know if there is a particular reason a new release has not happened yet?

@Nadrieril
Copy link
Contributor Author

I don't. The owner is active on the repo and knows a release is due (ogham/exa#441 (comment)), but gives no reason for why it's not there yet.

@killercup
Copy link
Member

superseded by #64773

@dywedir dywedir closed this Jul 15, 2019
@Nadrieril Nadrieril deleted the update-exa branch May 5, 2020 14:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants