1 | | I can confirm this. The tar.bz2 file the Mozilla server delivers today is different from the one it delivered to us when we originally updated curl-ca-bundle to its current version in r135276 on April 21, 2015. Notably, the tar files inside the two tar.bz2 files are identical, as are the files inside the two identical tar files. I'm not sure why the Mozilla server would be doing different bzip2 compression of its tarballs today than it did in April. But the tarballs are automatically generated, so it's likely they don't keep the generated tarballs around indefinitely, and that since the last time the tarball was generated, they changed the version of their bzip2 software, or changed the options with which it is invoked, such that the compressed result differs. |
| 1 | I can confirm this. The tar.bz2 file the Mozilla server delivers today is different from the one it delivered to us when we originally updated curl-ca-bundle to its current version in r135276 on April 21, 2015. Notably, the tar files inside the two tar.bz2 files are identical, as are the files inside the two identical tar files. I'm not sure why the Mozilla server would be doing different bzip2 compression of its tarballs today than it did in April. But the tarballs are automatically generated, so it's likely they don't keep the generated tarballs around indefinitely, and it's possible that since the last time the tarball was generated, they changed the version of their bzip2 software, or changed the options with which it is invoked, such that the compressed result differs. |