nixpkgs-review build 746 packages and 4 failed to build: blsd, gitAndTools.grv, gitaly, python38Packages.aria2p with unrelated reasons.

blsd, grv and gitaly failed b/c of the wrong libgit2 version, I'm currently investigating the reason for it, here is the example output:

builder for '/nix/store/sib6dszinjv8ycsmfdjz4rinn7vyirgj-blsd-2017-07-27.drv' failed with exit code 1; last 10 log lines:
  configuring
  unpacking source archive /nix/store/558shbs6cs1738fj6b4q0721z7276pnq-git2go-14280de
  building
  runtime/cgo
  net
  github.com/libgit2/git2go
  # github.com/libgit2/git2go
  go/src/github.com/libgit2/git2go/git_dynamic.go:10:3: error: #error "Invalid libgit2 version; this git2go supports libgit2 v0.27
"
     10 | # error "Invalid libgit2 version; this git2go supports libgit2 v0.27"
        |   ^~~~~

@FRidh how can I determine when such change should go to the staging instead of the master? thank you

When there is more than 500 rebuilds, it should target staging.

When a PR is opened, you can have a look at the labels that ofborg placed. Offline you could do this with a tool such as nix-review.

@FRidh I don't see a reason to merge it to staging first. Go packages are generally quick and as resource-intensive as other languages. I've been merging Go prs to master directly.