On 13.06.2018 15:40, Joris Meys wrote:
On Wed, Jun 13, 2018 at 3:16 PM, Uwe Ligges <
ligges at statistik.tu-dortmund.de <mailto:ligges at statistik.tu-dortmund.de>>
wrote:
When CRAN repacks and changes the DESCRIPTION file, the checksums
change, of course.
Best,
Uwe Ligges
Dear Uwe,
I understood that from the previous issue. In this case however, none of
the files -including the DESCRIPTION file- were changed. Am I right in
suspecting that a package is repacked when moved to the archive?
No, we do not repack generally then. Perhaps the package got orphaned?
Which package / tarball were you talking about? I can take a look why that
one was changed and inspect why the checksum changed.
Best,
Uwe Ligges
I
suspect that the tool used to repack the package is using gzip, and it is
possible to repack without adding a timestamp as explained here :
https://serverfault.com/questions/110208/different-md5sums-
for-same-tar-contents
I can explain the different checksums when some things are changed to our
HPC sysadmins, but they have -understandibly- difficulties with checksums
changing for released source tarballs. Is it possible to adapt the
archiving so that at least for identical tarballs the md5 sums remain the
same? Or if you have other suggestions to deal with this without having to
change hardcoded checksums in the easybuild repos, that would be very
welcome too.
Cheers
Joris
--
Joris Meys
Statistical consultant
Department of Data Analysis and Mathematical Modelling
Ghent University
Coupure Links 653, B-9000 Gent (Belgium)
<https://maps.google.com/?q=Coupure+links+653,%C2%A0B-9000+
Gent,%C2%A0Belgium&entry=gmail&source=g>
tel: +32 (0)9 264 61 79
-----------
Biowiskundedagen 2017-2018
http://www.biowiskundedagen.ugent.be/
-------------------------------
Disclaimer : http://helpdesk.ugent.be/e-maildisclaimer.php