Fixed
Status Update
Comments
ha...@at.or.at <ha...@at.or.at> #2
Looks like cbba6f8fcf025e1b533326746763aa1d6e2cf4001b1b441602bb44d253bc49ac was put back as platform-27_r01.zip, but no platform-27_r02.zip yet.
am...@google.com <am...@google.com> #3
Thank you for reporting this issue. We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
ha...@guardianproject.info <ha...@guardianproject.info> #4
It seems the original one has been put back now, this is what I'm seeing now:
$ sha256sum platform-27_r01.zip
cbba6f8fcf025e1b533326746763aa1d6e2cf4001b1b441602bb44d253bc49ac platform-27_r01.zip
$ sha1sum platform-27_r01.zip
dfda0862550768ed04a4fb0e03c322230aff9fdc platform-27_r01.zip
$ sha256sum platform-27_r01.zip
cbba6f8fcf025e1b533326746763aa1d6e2cf4001b1b441602bb44d253bc49ac platform-27_r01.zip
$ sha1sum platform-27_r01.zip
dfda0862550768ed04a4fb0e03c322230aff9fdc platform-27_r01.zip
ha...@guardianproject.info <ha...@guardianproject.info> #5
It seems to be flipping back and forth, back and forth between the two. There is this wonderful property to have in software binary release systems known as "binary transparency". I would love to see Google practice this https://www.eff.org/deeplinks/2014/02/open-letter-to-tech-companies . Using version numbers when releases change would also be handy.
ha...@guardianproject.info <ha...@guardianproject.info> #6
I stuck both binaries here, you can verify them by the familiar SHA-256 sums ;-)
https://verification.f-droid.org/build-metadata/
dn...@google.com <dn...@google.com> #7
The development team has fixed the issue that you have reported.
Description
This totally breaks reproducible builds since it is not even possible to redownload the original platform-27_r01.zip. We're tracking this issue here: