From 65257b79f9409c1d171ae8ccb430cd2be176427e Mon Sep 17 00:00:00 2001 From: Ciaran Gultnieks Date: Sat, 10 May 2014 18:08:24 +0100 Subject: [PATCH] Don't update DiskUsage to 3.4.3 (3043) --- metadata/com.google.android.diskusage.txt | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/metadata/com.google.android.diskusage.txt b/metadata/com.google.android.diskusage.txt index 552d605e8d..0681019eeb 100644 --- a/metadata/com.google.android.diskusage.txt +++ b/metadata/com.google.android.diskusage.txt @@ -58,9 +58,25 @@ Build:3.4.2,3042 cp extra/system.jar libs/ buildjni=yes +Build:3.4.3,3043 + disable=Build system issue, see maintainer notes + commit=9a06fa318639 + rm=jni/scan,assets/scan + patch=ndk-out.patch + prebuild=mkdir libs && \ + cp extra/system.jar libs/ + buildjni=yes + Maintainer Notes: The system.jar is from AOSP - see extra/system.jar.README and [https://code.google.com/p/diskusage/issues/detail?id=19] + +The build system complains that native code should have been built but none +was packaged. This is partially correct - it's 'packaged' in the assets +directory, for some reason. This does highlight a problem, because it means +that the app will only work on ARM, but Android and the F-Droid client don't +know that. Really it should be packaged properly. But should we allow the +build to go through anyway? . Auto Update Mode:None