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. https://github.com/easybuilders/easybuild-easyconfigs/pull/6446 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.
Best, Uwe Ligges
Cheers Joris
______________________________________________ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
