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

neofetch: 3.0.1 -> 3.2.0 #27608

Closed
wants to merge 1 commit into from
Closed

neofetch: 3.0.1 -> 3.2.0 #27608

wants to merge 1 commit into from

Conversation

konimex
Copy link
Contributor

@konimex konimex commented Jul 24, 2017

Motivation for this change

The patch is needed to address dylanaraps/neofetch#752. The patches are in upstream, but not in 3.2.0. The patch won't be needed in any subsequent releases.

Things done

Please check what applies. Note that these are not hard requirements but mereley serve as information for reviewers.

  • Tested using sandboxing
    (nix.useSandbox on NixOS,
    or option build-use-sandbox in nix.conf
    on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • Linux
  • 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/)
  • Fits CONTRIBUTING.md.

cc: @alibabzo

@mention-bot
Copy link

@konimex, thanks for your PR! By analyzing the history of the files in this pull request, we identified @alibabzo to be a potential reviewer.

@jfrankenau
Copy link
Member

I'd suggest to add the comment regarding the patch to the default.nix.

# configuration file, w3m directory (for fetching images) and ASCII
# directory properly. It won't be needed in subsequent releases.
patches = [
./config.patch
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this patch available over http? Generally we prefer to use fetchpatch over embedding the patch in the repo.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just uploaded it to the release, so yeah it's available over HTTP.

@romildo
Copy link
Contributor

romildo commented Aug 10, 2017

The sha256 for the patch is wrong. It should be:

0c6vsa74bxq6qlgbv3rrkhzkpvnq4304s6y2r1bl0sachyakaljy

@konimex
Copy link
Contributor Author

konimex commented Aug 10, 2017

Oops. My bad. Anyway, I'm closing this one since for some reason I lost the branch (even after fetching all remotes I cannot fetch the branch). Will open a new PR later.

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