My snapshot downloading script just complained that there is a difference between i386/SHA256 and the result of running
cat index.txt | grep -Fv SHA256 | xargs cksum -a sha256 in the i386 directory. The difference is exactly this: 16a17 > SHA256 (install47.iso) = > 7105afbd45e11072347ce43bcae92d2343022500ab5e397bb16480940bb96b62 20d20 < SHA256 (install47.iso) = 7105afbd45e11072347ce43bcae92d2343022500ab5e397bb16480940bb96b62 That is, the same line is the 20th line in SHA256, but ends up being the 17th line when computing the cksums (because install47.iso is the 17th, alphabetically); the checkum itself is the same, though Looking at SHA256, it seems that install47.iso is out of order, alphabetically. Once edited into the 'correct' place, there is no difference. Is it intentional that index.txt is sorted but SHA256 is not?
