It used to be the case (ref missing) that cargo did treat
`src/$libName.rs` as an alternative to `src/lib.rs` when the latter
wasn't present. Recently I failed to reproduce that with vanilla cargo
and it started to cause pain with some crates of the form:

some_crate/
 `- src
   `- main.rs
   `- some_crate.rs

We would build `src/some_crate.rs` and thing it is a library while that
might not be the actual case. This crate is a valid `bin` crate not a
`lib` crate as far as I can tell from the samples I took.

I removed support for the previously required heuristic and commented
out the test cases in case we will need them again. We could crawl in
the Git history but chances are that the next person looking into this
doesn't know about the history.

Previously I did use `runCommand` to do the same. Using
releaseTools.aggregate seems a lot saner and we might get nicer hydra
output of the tests that are failing.

Django-2.1 support ended on December 2, 2019, so drop it in nixpkgs as
well.

 zsh-bd:init at 2018-07-04

pythonPackages.django_2_1: drop

Renamed maintainer lucas8 -> dwarfmaster

fanficfare: 3.13.0 -> 3.15.0

…-path

buildRustCrate: remove custom lib path heuristic

fplll: 5.3.1 -> 5.3.2

https://github.com/github/hub/releases/tag/v2.14.1
https://github.com/github/hub/releases/tag/v2.14.0

gitAndTools.hub: 2.13.0 -> 2.14.1