Package: fdroidserver / 0.2.1-4

Metadata

Package Version Patches format
fdroidserver 0.2.1-4 3.0 (quilt)

Patch series

view the series file
Patch File delta Description
fix getsig install path.patch | (download)

setup.py | 3 2 + 1 - 0 !
1 file changed, 2 insertions(+), 1 deletion(-)

---
hard code path to openjdk 7.patch | (download)

fdroidserver/common.py | 2 2 + 0 - 0 !
fdroidserver/init.py | 4 2 + 2 - 0 !
fdroidserver/publish.py | 6 3 + 3 - 0 !
fdroidserver/update.py | 4 2 + 2 - 0 !
4 files changed, 9 insertions(+), 7 deletions(-)

 Normally fdroid looks in the PATH to find Java's keytool and jarsigner,
 but if the user changes the default JDK to something other than Java 1.7,
 then fdroid will break.  So this package uses the hard-coded path to
 the Java 1.7 version of the tools.
fix local sync perms.patch | (download)

fdroidserver/server.py | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 `rsync --chmod` does nothing without the --perms flag
do not include timestamps in .gz files of docs.patch | (download)

docs/gendocs.sh | 24 13 + 11 - 0 !
1 file changed, 13 insertions(+), 11 deletions(-)

 [patch 1/1] do not include timestamps in .gz files of docs

The timestamps in the .gz files are not used for anything, and they break
the reproducibility of the build.  Giving --no-name means gzip will not
save the filename and timestamp in the gz file itself.  When gunziping, the
current file name will be used, minus the .gz suffix.

remove redundant test_sdk_exists call its called by .patch | (download)

fdroidserver/common.py | 3 0 + 3 - 0 !
1 file changed, 3 deletions(-)

 [patch 2/7] remove redundant test_sdk_exists() call, its called by
 test_build_tools_exists()

No need to call test_sdk_exists() before test_build_tools_exists() since
test_build_tools_exists() calls test_sdk_exists() as the first thing it
does.

switched last aapt call to use central config aapt.patch | (download)

fdroidserver/common.py | 3 1 + 2 - 0 !
1 file changed, 1 insertion(+), 2 deletions(-)

 [patch 3/7] switched last aapt call to use central config['aapt']


find cmds from SDK build tools in a more flexible wa.patch | (download)

fdroidserver/build.py | 4 2 + 2 - 0 !
fdroidserver/common.py | 56 47 + 9 - 0 !
fdroidserver/init.py | 47 25 + 22 - 0 !
fdroidserver/update.py | 4 2 + 2 - 0 !
4 files changed, 76 insertions(+), 35 deletions(-)

 [patch 5/7] find cmds from sdk build-tools in a more flexible way, on
 the fly

This is a more flexible approach than testing for the complete SDK and
build-tools up front.  This will only test for the commands that are
actually being run, so that if you only have `aapt` installed, you can do
`fdroid update` without errors, but other commands will still give
appropriate errors.

This also makes the build_tools item in config.py optional, it is only
needed if you want to force a specific version of the build-tools.

run all SDK tools commands using SdkToolsPopen.patch | (download)

fdroidserver/common.py | 32 3 + 29 - 0 !
fdroidserver/install.py | 6 3 + 3 - 0 !
fdroidserver/publish.py | 6 3 + 3 - 0 !
3 files changed, 9 insertions(+), 35 deletions(-)

 [patch 6/7] run all sdk tools commands using sdktoolspopen


do not set sdk_path in config.py if using system pro.patch | (download)

examples/config.py | 2 1 + 1 - 0 !
fdroidserver/common.py | 8 6 + 2 - 0 !
fdroidserver/init.py | 49 28 + 21 - 0 !
3 files changed, 35 insertions(+), 24 deletions(-)

 [patch 7/7] do not set sdk_path in config.py if using system-provided
 aapt

By not setting sdk_path when /usr/bin/aapt is found, sdk_path then defaults
to $ANDROID_HOME when its used.  Since in this case, aapt will be used from
the system path, using aapt entirely ignores sdk_path.  If the user runs
`fdroid build` in this setup, sdk_path will be $ANDROID_HOME, so it should
check the env vars for it, but maybe that doesn't actually work like that
yet.