ZERO Hydra Failures 20.03

Jobsets:

• https://hydra.nixos.org/jobset/nixos/release-20.03
• https://hydra.nixos.org/jobset/nixos/release-20.03-aarch64
• https://hydra.nixos.org/jobset/nixpkgs/nixpkgs-20.03-darwin
• https://hydra.nixos.org/jobset/nixpkgs/staging-20.03

Mission

Every time we branch off a release we stabilize the release branch.
Our goal here is to get as little as possible jobs failing on the release-20.03 jobset.
I'd like to heighten, while it's great to focus on zero as our goal, it's essentially to
have all deliverables that worked in the previous release work here also.

How many failing jobs are there?

At the opening of this issue we have the main jobset at 1204 failing jobs, x86_64-darwin at 1384, and aarch64-linux at 7482.

The first evaluation of 19.09 had 1654 failing jobs.
So we're actually starting off with slightly less failing jobs compared to the last release.

How to help

1. Select an evaluation of the release-20.03 jobset by #id
   

2. Find a failed job ❌️
   

3. Work out why it's failing and fix it

4. Pull Request the fix

Generally the job fails on master also, you can verify that on Hydra - example URL: https://hydra.nixos.org/job/nixpkgs/trunk/bash.x86_64-linux.
That means most PR's should be targeted on master or staging for mass rebuilding changes.

Always reference this issue in the body of your PR:

ZHF: #80379

5. Backport it to release-20.03 or staging-20.03.

Details on that are in CONTRIBUTING.
Please ping @NixOS/nixos-release-managers on the PR.

Packages that don't get fixed

The remaining packages will be marked as broken before the release (on the failing platforms).
You can do this like:

meta = {
  # ref to issue/explanation
  # `true` is for everything
  broken = stdenv.isDarwin 
};

These are the utility flags used to test the type of platform.

Closing

This is a great way to help NixOS, and it was some of my earliest contributions.
Let's go ✌️

✨️ worldofpeace

cc @NixOS/nixpkgs-committers @NixOS/nixpkgs-maintainers