Hi everyone. Tracing back what occurred on the botched release I
realized that generating the announce ended up regenerating the tarballs
(it ran make dist again, and I didn't notice).
I've uploaded the tarballs matching the original announce (which is
below). Please check back on the freedesktop.
On Sat, Oct 12, 2013 at 12:32:59PM -0700, Ben Widawsky wrote:
> Regarding the checksums...
>
> The release script in xorg/util/modular failed for me during the
> release. As a result, I had to munge the script to generate the announce
> without rerunning the script (which the script advises when i
Regarding the checksums...
The release script in xorg/util/modular failed for me during the
release. As a result, I had to munge the script to generate the announce
without rerunning the script (which the script advises when it fails).
Apparently my munging was flawed, and I honestly have no clue
Are you sure about those checksums?
sha256sum -b libdrm-2.4.47.tar.gz
7980f80ed634b1489ef3276b7aa267c46172c160 *libdrm-2.4.47.tar.gz
md5sum -b libdrm-2.4.47.tar.gz
f1deddfa214dae295d20d041cadc1e79 *libdrm-2.4.47.tar.gz
sha256sum -b libdrm-2.4.47.tar.gz
a8756a55b131893320dc2193d18ca6013ec6e11bbe2
Alex Deucher (2):
radeon: add berlin pci ids
radeon: pad CS to 8 DW
Ben Widawsky (1):
libdrm: bump to 2.4.47
Chia-I Wu (1):
intel: silence valgrind warnings for unsynchronized maps
Damien Lespiau (3):
drm: Synchronize the stereo 3D mode flags from the kernel headers
Am Fri, 11 Oct 2013 23:04:02 -0700 (PDT)
schrieb Laurent Carlier :
> Am i alone ?
> c2dac2250adbcea23efb18fa8cf484c0f43c8ffbf5064ec82678bc410084f8e7
> libdrm-2.4.47.tar.bz2
>
The same here.
-Andy
ArchLinux
signature.asc
Description: PGP signature
___
Le vendredi 11 octobre 2013 10:11:18 Ben Widawsky a écrit :
>
> http://dri.freedesktop.org/libdrm/libdrm-2.4.47.tar.bz2
> MD5: e043d6d59328887b9e434f4d27aacc09 libdrm-2.4.47.tar.bz2
> SHA1: d9775b71c681c67a53794a72785a45846a17578c libdrm-2.4.47.tar.bz2
> SHA256: a98809a55ede4dac17416cac41f1f017
