binderhub image: refreeze requirements.txt

[jupyterhub-bot]

The binderhub image's requirements.txt has been refrozen based on requirements.in.

[manics]

This causes the tests to fail pycurl/pycurl#834

[minrk]

If I've understood the issue, adding --no-binary=pycurl ought to fix it

[consideRatio]

I failed to get it working in z2jh @minrk, but we have build stages etc and its a bit complicated.

jupyterhub/zero-to-jupyterhub-k8s#3365

I tried to do --no-binary=pycurl etc, but we have multistage builds etc making things a bit complicated, and I didn't got it working.

Practically, I tried adding the --no-binary=pycurl to the pip wheel command in our build stage.

[minrk]

I saw that. I believe jupyterhub/zero-to-jupyterhub-k8s#3371 is the missing piece there.

The approach taken here (pip install --no-deps *.whl) already avoids the problem solved by --no-index there, because it doesn't try to recalculate what to install from a requirements file, instead saying "install all these wheel files, don't look anywhere else or think too much about it."

[minrk]

Looks like it didn't work! Will investigate further.

[consideRatio]

Argh, I messed up - i re-run the watch dependencies script and the commits in this PR were removed.

@minrk do you have them locally to re-push?

[minrk]

No worries! FWIW, a pushed commit is never really lost on GitHub even if it's not in a current branch. Commits can be fetched by their sha and re-pushed, e.g.

commit=49577647498b24344d86bbec0c8c6e5403ace3dc
git fetch origin $commit # download the commit if you haven't fetched it before
git reset $commit --hard
git push origin update-image-requirements -f

[consideRatio]

Ah, thanks @minrk!!