Download.blender.org MD5 checksum for blender releases #47571
Labels
No Label
legacy module
Rendering & Cycles
legacy module
User Interface
legacy project
Cycles
legacy project
Documentation
legacy project
Infrastructure: blender.org
legacy project
Infrastructure: Blender Web Assets
legacy project
Infrastructure: Websites
legacy project
User Interface
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Report
Type
To Do
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: infrastructure/blender-org#47571
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Multiple coders and general public might have had a need for an MD5 checksum added to the blender versions download pages.
Last year I committed code for game_engine_publishing.py The add-on automatically downloads blender archives for multiple OS types under the same blender version (e.g.: blender 2.76b for windows, mac and linux on ix86 and x86_64). This enables users to compile their game for multiple platforms with a single button click.
Reason
I found out that if there is a connection drop while downloading archives, we have no way of telling if it's corrupted or not.
This is why I think an MD5 checksum might be of great help.
Solution
Adding a new column called "MD5" or "MD5 checksum" to http://download.blender.org/release/BlenderX.XX/
Example
Changed status to: 'Open'
Added subscriber: @Genome36
Added subscriber: @Sergey
Changed status from 'Open' to: 'Archived'
That's more a feature request than a bug actually.
However, we'll indeed start doing md5 sums for the release starting with 2.77 release. For older releases you can simply compare file size you actually got and the one reported by server.
What if I take the step forward and create all the md5 checksums for all the files (for completion's sake) ?