diff options
| author | Alyssa Ross <hi@alyssa.is> | 2023-12-14 00:49:36 +0100 |
|---|---|---|
| committer | Alyssa Ross <hi@alyssa.is> | 2024-02-27 15:01:14 +0100 |
| commit | 4c77fa6a1aa3e6e438b438c4cf5b423a4271264b (patch) | |
| tree | 812f3df56278e1a50461e9dccc1c3347f5af4c4b | |
| parent | git-remote-hg.meta.maintainers: drop myself (diff) | |
| download | nixpkgs-4c77fa6a1aa3e6e438b438c4cf5b423a4271264b.tar.gz | |
libtiff: drop maintainership
When I added myself as a maintainer here, I thought it would be way
less work than it turns out to be, because I didn't realise how
vulnerability-prone libtiff is. I basically haven't been maintaining
it at all, so let's reflect reality.
(cherry picked from commit 411fd474e120d9d6f7640c1f3894cfd665866320)
| -rw-r--r-- | pkgs/development/libraries/libtiff/default.nix | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/pkgs/development/libraries/libtiff/default.nix b/pkgs/development/libraries/libtiff/default.nix index 22b0f8af2043..8e735369e076 100644 --- a/pkgs/development/libraries/libtiff/default.nix +++ b/pkgs/development/libraries/libtiff/default.nix @@ -85,7 +85,6 @@ stdenv.mkDerivation rec { description = "Library and utilities for working with the TIFF image file format"; homepage = "https://libtiff.gitlab.io/libtiff"; changelog = "https://libtiff.gitlab.io/libtiff/v${version}.html"; - maintainers = with maintainers; [ qyliss ]; license = licenses.libtiff; platforms = platforms.unix; }; |
