Idea shamelessly stolen from 4e60b0efae.
I realized that I don't really know anymore where I'm listed as maintainer and what
I'm actually (co)-maintaining which means that I can't proactively take
care of packages I officially maintain.
As I don't have the time, energy and motivation to take care of stuff I
was interested in 1 or 2 years ago (or packaged for someone else in the
past), I decided that I make this explicit by removing myself from several
packages and adding myself in some other stuff I'm now interested in.
I've seen it several times now that people remove themselves from a
package without removing the package if it's unmaintained after that
which is why I figured that it's fine in my case as the affected pkgs
are rather low-prio and were pretty easy to maintain.
`git-annex` version 6.20180719 enhances the output of `git-annex info`
with a description and UUID of the repository which broke the testcase
`test_process_annex_info_batch` which parses the output of the info
command.
The testcase has been fixed accordingly and the patch was filed upstream
here: https://github.com/alpernebbi/git-annex-adapter/pull/6
I rechecked the functionality in a simple python environment with the
following expression:
```
with import ./. {};
python3.withPackages (ps: with ps; [ git-annex-adapter ])
```
Furthermore I tested the main functionality in a Python REPL within the environment.
The Darwin patch fixes tests that rely on `rev`, a binary which is
distributed in the `utillinux` package and not available on Nix with
Darwin.
To make the purpose of the patches for future contributors clear I
documented the purpose for each patch.
The exception message is broken becuase of some uppercase vs. lowercase
issues that have been patched accordingly.
Additionally use `fetchpatch` rather than `fetchurl` to apply patches
into the build.
