@GrahamcOfBorg build cordless

After applying the requested changes I am getting this:

hash mismatch in fixed-output derivation '/nix/store/7lzy5cjv73rf7prk7y112hcym5625lj8-source':
  wanted: sha256:0rh58mynxka119g5g5mmz19ffisvj0y7ivc168kaaxbw3fr4v77g
  got:    sha256:1l2ajzqiw2pg2fn37wc4w7x0bswzig2xs9f0xmxxil57m7waf3wg

However, none of those hashsums appears in my file. What am I doing wrong herre?

Here is what I got so far:

{ stdenv, buildGoModule, fetchFromGitHub }:

buildGoModule rec {
  pname = "cordless";
  version = "2019-06-13";

  src = fetchFromGitHub {
    owner = "Bios-Marcel";
    repo = pname;
    rev = version;
    sha256 = "ef9c4db21b7c75a5263281ed783c905b47e752f8b596575e0a41cd6e7d450566";
  };

  doCheck = true;

  modSha256 = "08a1dg4d7fjdy8w3sbri3ik8k7c1snpa0rzwinal6inzmdyancys";

  subPackages = [ "." ];

  meta = with stdenv.lib; {
    description = "A third party Discord client";
    longDescription = ''
      Cordless is a third party Discord client that runs on the
      commandline and aims to have a low memory footprint and
      bandwidth consumption.
    '';
    homepage = https://www.github.com/Bios-Marcel/cordless;
    license = licenses.bsd3;
    maintainers = [ maintainers.biosmarcel ];
    platforms = platforms.linux;
  };
}

I just tried building this. After changing modSha256 to 1mxjbqddb6w3hjdscm2fkxq9z4w9vi08lgwyrg7i1x558lr914b3, it installed for me.

Weird

ping (triage)

Anything blocking this other than the fetchFromGitHub thing?

Well, this is quite outdated either way. Should I just make a new PR?

I don't see the problem with updating this one. FWIW, it still works fine (though I updated the version, and changed it to fetchFromGitHub)

Thank you for your contributions.

This has been automatically marked as stale because it has had no activity for 180 days.

If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity.

Here are suggestions that might help resolve this more quickly:

1. Search for maintainers and people that previously touched the related code and @ mention them in a comment.
2. Ask on the NixOS Discourse.
3. Ask on the #nixos channel on irc.freenode.net.