[Rd] Wrongly checked MD5 checksums in R 3.2.0's windows binary

Duncan Murdoch murdoch.duncan at gmail.com
Mon May 11 11:06:45 CEST 2015

On 11/05/2015 4:31 AM, peter dalgaard wrote:
> On 11 May 2015, at 09:53 , Martin Maechler <maechler at lynne.stat.math.ethz.ch> wrote:
>>>>>>> Tal Galili <tal.galili at gmail.com>
>>>>>>>    on Sun, 10 May 2015 23:13:09 +0300 writes:
>>> Dear R-devel members, Several R user recently reported
>>> <https://github.com/talgalili/installr/issues/30> (while
>>> using the installr
>>> <http://cran.r-project.org/web/packages/installr>package)
>>> that when running MD5 checksums on a recent R installation
>>> (R 3.2.0), they get that the files ‘bin/R.exe’,
>>> ‘bin/Rscript.exe’ have the wrong MD5 checksums on Windows.
>>> I intend to remove the test for these files in the next
>>> version of installr, but I thought this might interest
>>> people to know.
>> Well, one could argue that this is a bug in your package.
> ...especially since this seems to be about executable files _after_ install, not the installer binaries. I don't think we provide the md5sums for those, do we?

Yes, they're in the MD5 file in the top level directory after installing.

The issue with files in the bin directory is that they depend on whether
it's a 32 bit or 64 bit install, but the MD5 sums are computed only for
the 32 bit files.  Those two files should be identical to each other,
and to one of i386/Rfe.exe or x64/Rfe.exe.  They need to be special-cased.

Duncan Murdoch

More information about the R-devel mailing list