The thing is I didn't have the permission to upload the files, so another core developer did it for me (Jerome Glisse). It's probably just a different version of gcc between his machine and mine that caused this issue. The files should be okay and the announcement is wrong. Sorry about that.
Marek
On Sun, Aug 12, 2012 at 10:09 AM, Andreas Radke a.radke@arcor.de wrote:
Am Sat, 11 Aug 2012 21:25:04 +0200 schrieb Marek Olšák maraeo@gmail.com:
git tag: libdrm-2.4.38
http://dri.freedesktop.org/www/libdrm/libdrm-2.4.38.tar.bz2 MD5: 8018e0bce5059cee05d855503d262cce libdrm-2.4.38.tar.bz2 SHA1: 21718ddb8be71bc74845a33c2b4fbda1de942e16 libdrm-2.4.38.tar.bz2 SHA256: a7caec55c945f7f8dec55fea9200391a168298bcdc4cb9a93c976e748193171a libdrm-2.4.38.tar.bz2
This is what I get here:
[andyrtr@workstation64 trunk]$ sha256sum libdrm-2.4.38.tar.bz2 && md5sum libdrm-2.4.38.tar.bz2 3e5a2f318edaf1eef41e7e6c85aa9596d6f9f8b083ec4d7d6710ffbb8921e7e9 libdrm-2.4.38.tar.bz2 a910d1305adcaa6561a7450899949105 libdrm-2.4.38.tar.bz2
Can you confirm this?
-Andy ArchLinux