Sajith Sasidharan f89ad002f8 Use 2.7-buster Docker image for pypy ... Fix failing PyPy CI job. Fixes: ticket:3299		2020-04-14 16:14:07 -04:00
..
config.yml	Bump CentOS from 7 to 8 on CI	2020-04-13 10:09:25 -04:00
create-virtualenv.sh	Fix wording of comment	2020-01-13 20:12:43 -05:00
Dockerfile.centos	no more libyaml-devel, maybe it was merged into libyaml	2020-04-13 11:04:11 -04:00
Dockerfile.debian	Tell the rest of the platforms to keep using whatever "python2.7" is.	2019-06-25 19:07:00 -04:00
Dockerfile.fedora	Tell the rest of the platforms to keep using whatever "python2.7" is.	2019-06-25 19:07:00 -04:00
Dockerfile.pypy	Use 2.7-buster Docker image for pypy	2020-04-14 16:14:07 -04:00
Dockerfile.slackware	Tell the rest of the platforms to keep using whatever "python2.7" is.	2019-06-25 19:07:00 -04:00
Dockerfile.ubuntu	Tell the rest of the platforms to keep using whatever "python2.7" is.	2019-06-25 19:07:00 -04:00
fix-permissions.sh	Fix the permissions ... twice. Thanks, COPY.	2019-04-06 10:00:19 -04:00
populate-wheelhouse.sh	tor and i2p were already implied by test	2019-08-14 09:04:39 -04:00
prepare-image.sh	try telling the virtualenv to use pypy	2019-06-25 18:51:11 -04:00
run-build-locally.sh	Factor steps out for use by machine executer	2018-06-15 14:21:33 -04:00
run-tests.sh	Take a shot at really timing out the PyPy job.	2019-08-13 15:57:29 -04:00
secret-env-cipher	Re-generate with a new key because I leaked the old one	2019-04-03 14:18:19 -04:00
setup-virtualenv.sh	this was vaguely helpful sort of not really	2019-06-26 08:50:13 -04:00