Apparently these rcs are quite stable and upstream is not going to release versions without rc soon.

@orivej i chose the rc because in the latest "stable" release the tests broke ...

meta didn't evaluate this way; fixed in 623df97.

@vcunat Thank you! I'm working on automating such basic sanity checks of the PRs that is lighter weight than nox-review.

For a quick test I'm using

nix-env -f . -qaP --meta --json --drv-path --show-trace >/dev/null

It might be also nice to run something like

./maintainers/scripts/rebuild-amount.sh $(git merge-base HEAD master)

could we add this to travis-ci instead of it trying to build the whole thing from master? 👍
in the meantime i will add the quick check to my workflow

(well, hijacking this thread :-/) My vision would be to attempt to rebuild the changes only if there are a few of them. Another thing is that to most people it's not obvious at all whether a change is a mass rebuild (and thus whether it should go to staging instead).

@vcunat how about having multiple build steps for all these things, like:

• sanity check (packages evaluate)
• meta check (meta evaluates)
• mass rebuild check (will build more than 100 packages)

When we see which test fails it would actually help the maintainers getting a quick overview about the state of the PR.