--- On Sat, 6/8/11, René Scharfe <rene.scharfe@xxxxxxxxxxxxxx> wrote: > That doesn't sound good. Looking at the R source, > however, I can see > that they use a two different algorithms to compute the > checksum than > the one specified by POSIX (even though I don't fully > understand what it > actually is their doing, since I don't know R). So > worry too much about > the warning; as long e.g. "tar tf <file>" doesn't > complain your archive > should be intact. I filed the bug, https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=14654 and they have fixed it bug has a few comments to make: --------------- Fixed in R-devel and patched (your checksum field has more than 6 digits which is highly unusual [since it can't be larger than 6 digits] but technically allowable). I should add that the original tar format mandated that checksums are terminated by NUL SPACE, so in that sense your tar file is invalid (there can't be more than 6 digits since the checksum field consists of 8 bytes). untar2 will now be more forgiving, but whatever program created that tar file should be fixed. ----------------- Please feel free to respond directly at the R bug tracking system, or I can cut-and-paste bits of e-mails also... -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html