A new version add the check of SHA512 sums instead of SHA1. 0.2.1 version is pushed.
CC: (none) => geiger.david68210Assignee: bugsquad => geiger.david68210
Assigning to QA, Advisory: ============================= mageiasync needs to deal with SHA512 checksums, so this new release adds the check of SHA512 sums instead of SHA1. More info: Now mageiasync replaces python-mageiasync, this is the same package, we have just changed the name. Packages in 5/core/updates_testing: ======================== mageiasync-0.2.1-1.mga5.noarch.rpm Source RPM: ======================== mageiasync-0.2.1-1.mga5.src.rpm
Assignee: geiger.david68210 => qa-bugs
Tested this on a 64-bit system. Ran it on the Classic 64-bit DVD iso, which took a good two hours. md5 and sha512 checksums returned OK. Any need to run this on 32-bit seeing as it is a noarch package? I do not have the infrastructure for i586.
CC: (none) => tarazed25
Whiteboard: (none) => MGA5-64-OK
Thanks Len for testing, I'm not in QA team, but I confirm that my modifications are only in Python code. What can be different between arch are modules such hashlib. It was already used, but not the sha512 function.
Thanks papoteur; so it is a marginal case. I shall not validate this then, to give someone else the chance to test it on i586.
Keywords: (none) => validated_updateWhiteboard: MGA5-64-OK => MGA5-64-OK MGA5-32-OK advisoryCC: (none) => davidwhodgins, sysadmin-bugs
Tested this on a 32-bit system, with the 4.4.6 kernel update candidate installed. Synced both Classical Mageia 6 DVD isos. md5 and sha512 checksums reported as OK.
CC: (none) => andrewsfarm
An update for this issue has been pushed to the Mageia Updates repository. http://advisories.mageia.org/MGAA-2016-0047.html
Status: NEW => RESOLVEDResolution: (none) => FIXED