[R-pkg-devel] Checksums changed on CRAN without any visible modifications to files.
ligge@ @ending from @t@ti@tik@tu-dortmund@de
Wed Jun 13 15:16:46 CEST 2018
On 13.06.2018 12:45, Joris Meys wrote:
> Dear all,
> I have another report of checksums for CRAN packages that changed without
> any visible change to the package itself.
> At the time of the release of R3.5, pkgmaker was at version 0.22. A bit
> after the release, this version was archived and replaced by the new one
> (0.27). Somewhere in that process the checksum for the tarball of version
> 0.22 changed.
> The only explanation I can come up with, is that either because of the
> release of R3.5 or because of the archiving the tarball was recreated and
> has a different timestamp. That's the only way I know a MD5 checksum of a
> tarball can change without any change to the files in there.
> Anyone knows what is going on here, and how this can be circumvented at the
> client side?
When CRAN repacks and changes the DESCRIPTION file, the checksums
change, of course.
More information about the R-package-devel