Problem description: It is _not_ possible to find the checksums of the daily builds. The checksums such as md5, sha1 and sha512 checksums are useful for checking the integrity of files. Since the files are large, there can be accidental transmission errors. Users could be allowed to check if the files downloaded are complete and are not corrupt files when the checksums are given.
Steps to reproduce:
2. _No_ checksums are found.
Current behavior: _No_ checksums of daily builds are found.
Expected behavior: Add checksums of daily builds. For example,
(Using Bug Submission Assistant, I am not sure if the correct _sub-component_ was selected.)
Operating System: All
Version: 184.108.40.206 release
For Daily Builds, I didn't find them either, so changing to -> NEW
However, for convenient end user builds, there are at least GPG signatures, see
Having checksums of our daily builds seems like a good candidate for an EasyHack. I assume it would be a little extra code added to the tinbuild system...
Confirm the same issue:
(In reply to comment #2)
> Having checksums of our daily builds seems like a good candidate for an
> EasyHack. I assume it would be a little extra code added to the tinbuild
Cloph - Could please you verify if this is an EasyHack?
It is an easy hack, although just fixing in the build bot repo isn't enough - you also need to ping tinderbox administrators to update their scripts.
Tinderbox build scripts are in contrib/buildbot repository (there are three variants)
In order to limit the confusion between ProposedEasyHack and EasyHack and to make queries much easier we are changing ProposedEasyHack to NeedsDevEval.
Thank you and apologies for the noise
as confirmed by cloph, this is an easyhack
Ticket moved to Redmine, see https://redmine.documentfoundation.org/issues/1555
Migrating Whiteboard tags to Keywords: (EasyHack)