@stiV: there are two problems: 1) apt's version of sha256 when called in a certain way generated an improper sha256 (this is fixed in intrepid). However, since apt never uses the .gz/.bz2 files when doing hash checks, this isn't a realistic problem for any releases.
2) soyuz has been using apt's sha256 in the broken way to generate hashes. This is being worked around, and all broken hashes will be recalculated correctly for all releases as soon as the code is tested and rolled out. -- sha256 checksums in release files for all gzipped files broken https://bugs.launchpad.net/bugs/269014 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
