Upgrading icalendar to 4.0.3 broke the pinned dateutil version.
Luckily khal 0.9.10 now works with dateutil 2.7, so we no longer need to
override it. However now one test in khal fails (the string output
changed from icalendar 4.0.2 to 4.0.3)...
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/khal/versions.
These checks were done:
- built on NixOS
- Warning: no invocation of /nix/store/wkssgwwqyffwnf7c8p1zi180xjm256il-khal-0.9.9/bin/.ikhal-wrapped had a zero exit code or showed the expected version
- Warning: no invocation of /nix/store/wkssgwwqyffwnf7c8p1zi180xjm256il-khal-0.9.9/bin/ikhal had a zero exit code or showed the expected version
- Warning: no invocation of /nix/store/wkssgwwqyffwnf7c8p1zi180xjm256il-khal-0.9.9/bin/.khal-wrapped had a zero exit code or showed the expected version
- Warning: no invocation of /nix/store/wkssgwwqyffwnf7c8p1zi180xjm256il-khal-0.9.9/bin/khal had a zero exit code or showed the expected version
- 0 of 4 passed binary check by having a zero exit code.
- 0 of 4 passed binary check by having the new version present in output.
- found 0.9.9 with grep in /nix/store/wkssgwwqyffwnf7c8p1zi180xjm256il-khal-0.9.9
- directory tree listing: https://gist.github.com/a146a88f248f45c280a17c50a0d46b79
- du listing: https://gist.github.com/72d0555178317dce9c07ab814f13f512
With this patch I remove myself as a maintainer for all packages I
currently maintain.
This is due the fact that I will be basically off the grid from May 2018
until early 2019, as I will be on a trip through north america.
I will revert this patch as soon as I'm back, as I plan to continue
contributing to nixpkgs then.
But as I cannot maintain anything during that time, I'd like to get this
patch merged.
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>