Skip to content
Snippets Groups Projects
Commit 4d3e48fb authored by Armin Rigo's avatar Armin Rigo
Browse files

Fix the links for source. Fix the md5/sha1. As usual it's done by

downloading the file and dumping the md5/sha1 that I got, which means
it's bogus as a security measure, but people insist anyway. I'll try
this time to leave out the .zip...
parent 4673a6bd
No related branches found
No related tags found
No related merge requests found
......@@ -140,8 +140,8 @@
* `pypy-2.0b2-src.tar.bz2`__ (sources, Unix line endings)
* `pypy-2.0b2-src.zip`__ (sources, Unix line endings too, sorry)
.. __: https://bitbucket.org/pypy/pypy/get/release-2.0-beta-2.tar.bz2
.. __: https://bitbucket.org/pypy/pypy/get/release-2.0-beta-2.zip
.. __: https://bitbucket.org/pypy/pypy/get/release-2.0-beta2.tar.bz2
.. __: https://bitbucket.org/pypy/pypy/get/release-2.0-beta2.zip
Or you can checkout the current trunk using Mercurial_ (the trunk
usually works and is of course more up-to-date)::
......@@ -226,8 +226,7 @@
e7655066baed3c7bbbca7df617817dd5 pypy-1.9-win32.zip
2c9f0054f3b93a6473f10be35277825a pypy-1.8-sandbox-linux64.tar.bz2
009c970b5fa75754ae4c32a5d108a8d4 pypy-1.8-sandbox-linux.tar.bz2
4a346df59983e4a5c50e8ee211f80619 release-2.0-beta-1.tar.bz2 (source)
60270f1b919e75f818028da52ab8c3d3 release-2.0-beta-1.zip (source)
c6afb6dd3fcc57ba2c4144780a42412f release-2.0-beta2.tar.bz2 (source)
699fe12476a1783d6f91de59f48adc01c93c39df pypy-2.0-beta2-linux64-libc2.15.tar.bz2
591e661b091ed4849fdf5aab7e73393dea64016b pypy-2.0-beta2-linux.tar.bz2
......@@ -239,5 +238,4 @@
4f060f4fab0f07bbc7de0ac8f95275eb08d726a3 pypy-1.9-win32.zip
895aaf7bba5787dd30adda5cc0e0e7fc297c0ca7 pypy-1.8-sandbox-linux64.tar.bz2
be94460bed8b2682880495435c309b6611ae2c31 pypy-1.8-sandbox-linux.tar.bz2
281439ca2fb56edfe26fc65f99ab6eb238097425 release-2.0-beta-1.tar.bz2 (source)
a2fc9b8031b5817ccd4389d97e3d8c480b48eb78 release-2.0-beta-1.zip (source)
66d77a7ef98b9bff33a6ac19834c3a598bb9fa97 release-2.0-beta2.tar.bz2 (source)
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment