this is a mass rebuild, please target staging-20.09

git rebase --onto=origin/staging-20.09 HEAD^
git push .. .. --force

then change target branch

git rebase --onto=origin/staging-20.09 HEAD^

[root@evil:/home/red/projects/nixpkgs]# git rebase --onto=origin/staging-20.09 HEAD^
fatal: Does not point to a valid commit 'origin/staging-20.09'

Sorry - I'm git impaired :/

please do git remote -v, you probably just have upstream named differently from me

please do git remote -v, you probably just have upstream named differently from me

[root@evil:/home/red/projects/nixpkgs]# git remote -v
origin  git@github.com:redvers/nixpkgs (fetch)
origin  git@github.com:redvers/nixpkgs (push)
upstream        https://github.com/nixos/nixpkgs.git (fetch)
upstream        https://github.com/nixos/nixpkgs.git (push)

ah, you cloned from your fork:

git rebase --onto=upstream/staging-20.09 HEAD^
git push .. .. --force

should work

ah, you cloned from your fork:

git rebase --onto=upstream/staging-20.09 HEAD^
git push .. .. --force

should work

Okay - I think we're good now?

Thanks for your due diligence.

git history looks good now

@andir

This likely wont get merged until the current staging-20.09 gets merged

@GrahamcOfBorg eval

shouldn't have "package new"

@jonringer Hydra is not picking up on the new build timeout for GHC, blocking staging-20.09. A mass rebuild may be exactly what we need, so we get a new hash, therefore a new "Build" and possibly an increased timeout.

See also NixOS/hydra#830
and https://hydra.nixos.org/build/129420286