0e64736db4
security updates for added repos These commits fix a couple of security issues with adding repos, they should be included in the 0.65 release. Here is the bug report from Adam Pritchard, these issues should be fixed: 2. But wait, you say? Where's the "EF" at the start? F-Droid actually shows (and takes) a version of the fingerprint with the first byte (first two hex) dropped. Bwah? You can see this with Guardian's fingerprint here: https://guardianproject.info/2012/03/15/our-new-f-droid-app-repository/ len('050C8155DCA377F23D5A15B77D3713400CDBD8B42FBFBE0E3F38096E68CECE') / 2 * 8 == 248 ...But it should be 256. On purpose? 3. And it seems like there's a bug in F-Droid. If you enter the fingerprint when adding the repo, the repo gets flagged with "Unsigned", but if you add the repo without entering the fingerprint it doesn't. Reproduction: - Add https://guardianproject.info/repo/ and enter 050C8155DCA377F23D5A15B77D3713400CDBD8B42FBFBE0E3F38096E68CECE - Refresh - It's say "Unsigned" in red text under the repo name - Delete the repo - Add it again, but without the fingerprint - It won't have any red text This is surely unintended?
F-Droid Client
Client for F-Droid, the Free Software repository system for Android.
Building from source
The only required tools are the Android SDK and Apache Ant.
Once you have checked out the version you wish to build, run:
git submodule update --init
./ant-prepare.sh # This runs 'android update' on the libs and the main project
ant clean release
The project itself supports Gradle, but some of the libraries it uses don't. Hence it is currently not possible to build F-Droid with Gradle in a clean way without manual interaction.
Building as part of a ROM
Add the following lines to your repo manifest:
<remote name="fdroid" fetch="https://git.gitorious.org/f-droid" />
<remote name="github" fetch="https://github.com/" />
<project path="packages/apps/fdroidclient" name="fdroidclient.git" remote="fdroid" revision="0.62" />
<project path="packages/apps/fdroidclient/extern/UniversalImageLoader" name="nostra13/Android-Universal-Image-Loader" remote="github" revision="b1b49e51f2c43b119edca44691daf9ab6c751158" />
<project path="packages/apps/fdroidclient/extern/AndroidPinning" name="binaryparadox/AndroidPinning" remote="github" revision="ce84a19e753bbcc3304525f763edb7d7f3b62429" />
<project path="packages/apps/fdroidclient/extern/MemorizingTrustManager" name="ge0rg/MemorizingTrustManager" remote="github" revision="a705441ac53b9e1aba9f00f3f59aab81da6fbc9e" />
Adding F-Droid is then just a matter of adding F-Droid to your PRODUCT_PACKAGES.
Direct download
You can download the application directly from our site or browse it in the repo.
Contributing
You are welcome to submit Merge Requests via the Gitorious web interface. You can also follow our Issue tracker and our Forums.
Translating
The res/values-* dirs are kept up to date automatically via MediaWiki's
Translate Extension. See
our translation page if you
would like to contribute.
Running the test suite
FDroid client includes a embedded Android Test Project for running tests. It
is in the test/ subfolder. To run the tests from the command line, do:
git submodule update --init
./ant-prepare.sh # This runs 'android update' on the libs and the main project
ant clean emma debug install test
You can also run the tests in Eclipse. Here's how:
- Choose File -> Import -> Android -> Existing Android Code Into Workspace for the
fdroidclient/directory. - Choose File -> Import -> Android -> Existing Android Code Into Workspace for the
fdroidclient/test/directory - If fdroid-test has errors, right-click on it, select Properties, the Java Build Path, then click on the Projects tab.
- Click on the Add... button and select
fdroidclient/ - Right-click on the fdroid-test project, then Run As... -> Android JUnit Test
Troubleshooting
When building F-Droid, the following error may occur:
Invalid file: extern/UniversalImageLoader/library/build.xml
Check the output of the ./ant-prepare.sh command. This error is often accompanied by the following message:
Error: The project either has no target set or the target is invalid. Please provide a --target to the 'android update' command.
The most likely cause of this is that your installed Android SDK is missing the target version specified by one of the dependencies. For example, at the time of writing this, UniversalImageLoader uses the "android-16" target API, however the default install of the Android SDK will usually only install the latest version ("android-19" as of writing). So you will have to install the "android-16" target via the SDK manager.
NOTE: While it may be tempting to add "--target=android-19" to the ant-prepare.sh script, it is not the correct solution. Although it may work, it can cause strange bugs at runtime.
License
This program is Free Software: You can use, study share and improve it at your will. Specifically you can redistribute and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.