[jhbuild] core-3.4: switch bluez to using tar.xz



commit 9fcb44f8270a6b61bd23616f45bc4597de550fae
Author: Ryan Lortie <desrt desrt ca>
Date:   Fri Feb 24 11:14:18 2012 -0500

    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

 modulesets/gnome-suites-core-3.4.modules |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)
---
diff --git a/modulesets/gnome-suites-core-3.4.modules b/modulesets/gnome-suites-core-3.4.modules
index 6d4c7bb..64bb67e 100644
--- a/modulesets/gnome-suites-core-3.4.modules
+++ b/modulesets/gnome-suites-core-3.4.modules
@@ -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>



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]