Commit 9fcb44f8 authored by Allison Karlitskaya's avatar Allison Karlitskaya

core-3.4: switch bluez to using tar.xz

kernel.org's standard operating procedures sometimes involve compressed
tarballs being regenerated from the uncompressed form.  gzip, by
default, stores a timestamp of when this happened.  This can cause the
checksum of the .tar.gz file to spuriously change (as just happened with
bluez-4.87).

xz doesn't share this behaviour, so switch to using the .tar.xz file
instead.

https://bugzilla.gnome.org/show_bug.cgi?id=670698
parent 48ed4e4b
......@@ -902,9 +902,9 @@
-->
<autotools id="bluez" autogenargs="--enable-udevrules=no">
<pkg-config>bluez.pc</pkg-config>
<branch repo="kernel.org" module="pub/linux/bluetooth/bluez-4.87.tar.gz" version="4.87"
hash="sha256:86afb988935e5385fb22ea0893f269f870d6f78b18aaccea6d4d0e253e2f241b"
md5sum="8e615a4e3a05e3b44259e8c51881d48d" size="1114526"/>
<branch repo="kernel.org" module="pub/linux/bluetooth/bluez-4.87.tar.xz" version="4.87"
hash="sha256:165e4025e86ecbf2ade2c2f96d3f0de8d98e90fe3ce54d26c4f7e135f46bd61a"
size="760456"/>
<dependencies>
</dependencies>
</autotools>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment