diff options
| author | Jade Lovelace <jadel@mercury.com> | 2025-07-24 16:37:39 -0700 |
|---|---|---|
| committer | Jade Lovelace <jadel@mercury.com> | 2025-07-24 19:31:06 -0700 |
| commit | 4f93d9a2d14a0cf36c9e0c357f107959521d9658 (patch) | |
| tree | 991c595ba0258057dcb108afa49f6ba9a9e043c0 /pkgs/development/python-modules/rangehttpserver | |
| parent | 94aa5ea1369da344a11e85121ef51d14e305f5fd (diff) | |
mx-puppet-discord: remove
According to emilazy these were the only usages of sha1 in nixpkgs:
```
pkgs/servers/mx-puppet-discord/node-packages.nix
111: sha1 = "532e01241dbcb0f2769f1b9a7cde313d30101173";
120: sha1 = "68018cab4f59834b3fef2e59fbfd52938403e001";
129: sha1 = "52b0e8bb808a1202602899af67939b049dd42402";
138: sha1 = "0a37a3f9430ff7c29512d29882e25ae738a31283";
```
Anyone motivated to maintain it can feel free to restore this, it's just
not maintained at the moment, and the sha1 hashes need to go.
This was found after Ericson proposed implementing something like
https://github.com/NixOS/nix/issues/13544 in Lix, which led to the
question "who is using sha1 anyway?" and the realization we could just
*remove* support for it outside of .. the known chromium crimes.
Diffstat (limited to 'pkgs/development/python-modules/rangehttpserver')
0 files changed, 0 insertions, 0 deletions