FS#43882 - [mpv] Different md5sum for source package

Attached to Project: Community Packages
Opened by Mark E. Lee (bluerider) - Thursday, 19 February 2015, 04:31 GMT
Last edited by Christian Hesse (eworm) - Friday, 20 February 2015, 08:31 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Bartłomiej Piotrowski (Barthalion)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
When building from the PKGBUILD, I get an md5sum error since the md5sums don't match.

Additional info:
Reported md5sum : 7b8e910ffe6a36d1607330a5b8c2d82b
Calculated md5sum : b3d02a0db096e77ce38c3946dd631e58

Steps to reproduce:
Try to build mpv-0.8.0
This task depends upon

Closed by  Christian Hesse (eworm)
Friday, 20 February 2015, 08:31 GMT
Reason for closing:  Fixed
Additional comments about closing:  mpv 0.8.0-2 in [community]
Comment by Doug Newgard (Scimmia) - Thursday, 19 February 2015, 04:37 GMT
Calling this medium instead of low because there was an issue with the tag, so the current build is probably wrong. See  FS#43858 
Comment by Mark E. Lee (bluerider) - Thursday, 19 February 2015, 05:07 GMT
Aren't failed integrity checks for packages a critical issue? The PKGBUILD should be updated to contain the proper md5sums (or possibly switch to sha256sums).
Comment by Doug Newgard (Scimmia) - Thursday, 19 February 2015, 16:46 GMT
No, they are very definitely not "critical". See https://wiki.archlinux.org/index.php/Reporting_bug_guidelines#Severity

Loading...