kamp/fdroidserver
1
0
Fork 0
mirror of https://gitlab.com/fdroid/fdroidserver.git synced 2024-11-04 14:30:11 +01:00
Code Activity
14127bf418
fdroidserver/tests/repo/index.xml

319 lines
18 KiB
XML
Raw Normal View History

test for original "v0" index XML compatibility The original index.xml format needs to stay around for backwards compatibility, but we shouldn't touch it anymore once the new format is in place. This is a test to make sure `fdroid update` can still generate the correct XML. install_list and uninstall_list should be tuples or lists in order to ensure that the order is preserved. These tests also check that the added and lastupdated dates are working correct, based on the dates in tests/stats/known_apks.txt. I could see no useful way to test the timestamp, it is just hardcoded using a regexp search-and-replace. Running these tests manually might require deleting tmp/apkcache.
2017-02-23 21:23:45 +01:00
<?xml version="1.0" encoding="utf-8"?>
<fdroid>
add signer to index v1
2017-09-19 15:34:29 +02:00
<repo icon="fdroid-icon.png" name="My First F-Droid Repo Demo" pubkey="308204e1308202c9a003020102020434597643300d06092a864886f70d01010b050030213110300e060355040b1307462d44726f6964310d300b06035504031304736f7661301e170d3136303931333230313930395a170d3434303133303230313930395a30213110300e060355040b1307462d44726f6964310d300b06035504031304736f766130820222300d06092a864886f70d01010105000382020f003082020a028202010086ef94b5aacf2ba4f38c875f4194b44f5644392e3715575d7c92828577e692c352b567172823851c8c72347fbc9d99684cd7ca3e1db3e4cca126382c53f2a5869fb4c19bdec989b2930501af3e758ff40588915fe96b10076ce3346a193a0277d79e83e30fd8657c20e35260dd085aa32eac7c4b85786ffefbf1555cafe2bc928443430cdbba48cfbe701e12ae86e676477932730d4fc7c00af820aef85038a5b4df084cf6470d110dc4c49ea1b749b80b34709d199b3db516b223625c5de4501e861f7d261b3838f8f616aa78831d618d41d25872dc810c9b2087b5a9e146ca95be740316dcdbcb77314e23ab87d4487913b800b1113c0603ea2294188b71d3e49875df097b56f9151211fc6832f9790c5c83d17481f14ad37915fd164f4fd713f6732a15f4245714b84cd665bdbd085660ea33ad7d7095dcc414f09e3903604a40facc2314a115c0045bb50e9df38efb57e1b8e7cc105f340a26eeb46aba0fa6672953eee7f1f92dcb408e561909bbd4bdf4a4948c4d57c467d21aa238c34ba43be050398be963191fa2b49828bc1e4eeed224b40dbe9dc3e570890a71a974a2f4527edb1b07105071755105edcb2af2f269facfb89180903a572a99b46456e80d4a01685a80b233278805f2c876678e731f4ec4f52075aeef6b2b023efbb8a3637ef507c4c37c27e428152ec1817fcba640ad601cb09f72f0fbe2d274a2410203010001a321301f301d0603551d0e04160414c28bf33dd5a9a17338e5b1d1a6edd8c7d141ed0b300d06092a864886f70d01010b0500038202010084e20458b2aafd7fc27146b0986f9324f4260f244920417a77c9bf15e2e2d22d2725bdd8093ec261c3779c3ca03312516506f9410075b90595b41345956d8eb2786fb5994f195611382c2b99dba13381b0100a30bc9e6e47248bf4325e2f6eec9d789216dc7536e753bf1f4be603d9fa2e6f5e192b4eb988b8cdb0bb1e8668a9225426f7d4636479f73ed24ad1d2657c31e63c93d9679b9080171b3bd1bf10a3b92b80bd790fbf62d3644900cd08eae8b9bf9c2567be98dc8cdd2ae19a8d57a3e3e2de899f81f1279f578989e6af906f80c8c2b67651730ee7e568c1af5bcb845b6d685dc55332a9984aeceaea3b7e883447edf1c76b155d95253e39b9710eaa22efa6c81468829702b5dce7126538f3ca70c2f0ad9a5795435fdb1f715f20d60359ef9a9926c7050116e802df651727447848827815f70bd82af3cedd08783156102d2d8ce995c4c43b8e47e91a3e6927f3505a5d395e6bebb84542c570903eeab4382a1c2151f1471c7a06a34dc4d268d8fa72e93bdcd2dccc4302ecac47b9e7e3d8bc9b46d21cd097874a24d529548018dc190ff568c6aa428f0a5eedff1a347730931c74f19277538e49647a4ad7254f4c1ec7d4da12cce9e1fad9607534e66ab40a56b473d9d7e3d563fd03cad2052bad365c5a29f8ae54f09b60dbca3ea768d7767cbe1c133ca08ce725c1c1370f4aab8e5b6e286f52dc0be8d0982b5a" timestamp="1480431575" url="https://MyFirstFDroidRepo.org/fdroid/repo" version="19">
test for original "v0" index XML compatibility The original index.xml format needs to stay around for backwards compatibility, but we shouldn't touch it anymore once the new format is in place. This is a test to make sure `fdroid update` can still generate the correct XML. install_list and uninstall_list should be tuples or lists in order to ensure that the order is preserved. These tests also check that the added and lastupdated dates are working correct, based on the dates in tests/stats/known_apks.txt. I could see no useful way to test the timestamp, it is just hardcoded using a regexp search-and-replace. Running these tests manually might require deleting tmp/apkcache.
2017-02-23 21:23:45 +01:00
<description>This is a repository of apps to be used with F-Droid. Applications in this repository are either official binaries built by the original application developers, or are binaries built from source by the admin of f-droid.org using the tools on https://gitlab.com/u/fdroid. </description>
<mirror>http://foobarfoobarfoobar.onion/fdroid/repo</mirror>
<mirror>https://foo.bar/fdroid/repo</mirror>
</repo>
<install packageName="org.adaway"/>
<uninstall packageName="com.android.vending"/>
<uninstall packageName="com.facebook.orca"/>
handle bad SDK Version values in APKs Even though it is invalid to have *SdkVersion in AndroidManifest.xml set as anything but an integer, sometimes people manage to get something in there. `fdroid update` needs to be able to handle all that. * https://developer.android.com/guide/topics/manifest/uses-sdk-element#min * https://gitlab.com/souch/SMSbypass/blob/v0.9/app/src/main/AndroidManifest.xml#L29 * https://gitlab.com/souch/SMSbypass/blob/v0.9/app/src/main/res/values/strings.xml#L27 admin#65
2018-04-26 13:17:25 +02:00
<application id="souch.smsbypass">
<id>souch.smsbypass</id>
<added>2018-04-26</added>
<lastupdated>2018-04-26</lastupdated>
<name>Battery level</name>
<summary>Filter SMS and show them in a fake app</summary>
<icon>souch.smsbypass.9.png</icon>
<desc>&lt;p&gt;In order to keep away curious eyes, SMS-bypass filters incoming SMS messages before they reach your inbox. Based on bughunter2.smsfilter.&lt;/p&gt;&lt;p&gt;Features:&lt;/p&gt;&lt;ul&gt;&lt;li&gt; Discrete fake app &quot;Battery level&quot;: Long tap on Battery percentage will show SMS.&lt;/li&gt;&lt;li&gt; Filter incoming SMS specified address: redirect the SMS to SMS-bypass messages list; remove SMS arrival sound or vibration; show a discreet notification icon (battery level); vibrate if checked in settings&lt;/li&gt;&lt;li&gt; Add contact from contact list&lt;/li&gt;&lt;li&gt; Export messages to a text file&lt;/li&gt;&lt;/ul&gt;</desc>
tests: adapt to spdx v4.0.0
2018-05-16 22:49:57 +02:00
<license>GPL-3.0-only</license>
handle bad SDK Version values in APKs Even though it is invalid to have *SdkVersion in AndroidManifest.xml set as anything but an integer, sometimes people manage to get something in there. `fdroid update` needs to be able to handle all that. * https://developer.android.com/guide/topics/manifest/uses-sdk-element#min * https://gitlab.com/souch/SMSbypass/blob/v0.9/app/src/main/AndroidManifest.xml#L29 * https://gitlab.com/souch/SMSbypass/blob/v0.9/app/src/main/res/values/strings.xml#L27 admin#65
2018-04-26 13:17:25 +02:00
<categories>Phone &amp; SMS</categories>
<category>Phone &amp; SMS</category>
<web>https://gitlab.com/souch/SMSbypass</web>
<source>https://gitlab.com/souch/SMSbypass/tree/HEAD</source>
<tracker>https://gitlab.com/souch/SMSbypass/issues</tracker>
<donate>http://rodolphe.souchaud.free.fr/donate</donate>
<flattr>cad90e036b975ed129a3ce80a0750466</flattr>
<marketversion>0.9</marketversion>
<marketvercode>9</marketvercode>
<package>
<version>0.9</version>
<versioncode>9</versioncode>
<apkname>souch.smsbypass_9.apk</apkname>
<hash type="sha256">80b0ae68a1189baa3ee6717092e3dbf1a4210165f7f7e5f2f9616bd63a2ec01d</hash>
<size>81295</size>
<sdkver>8</sdkver>
<targetSdkVersion>18</targetSdkVersion>
<added>2018-04-26</added>
<sig>e50c99753cd45e2736d52cb49be07581</sig>
<permissions>READ_CONTACTS,READ_EXTERNAL_STORAGE,RECEIVE_SMS,SEND_SMS,VIBRATE,WRITE_EXTERNAL_STORAGE</permissions>
</package>
</application>
aapt 26.0.0 is required to properly parse permissions and label #236 closes #395 aapt 26.0.0 outputs the permissions correctly closes #306 aapt 26.0.0 now outputs: application-label:'K-9 Mail'
2017-12-22 17:28:25 +01:00
<application id="duplicate.permisssions">
<id>duplicate.permisssions</id>
<added>2017-12-22</added>
<lastupdated>2017-12-22</lastupdated>
<name>Duplicate Permisssions</name>
<summary>Test app for all possible &lt;uses-permissions&gt;</summary>
<icon>duplicate.permisssions.9999999.png</icon>
<desc>&lt;p&gt;No description available&lt;/p&gt;</desc>
<license>Unknown</license>
<categories>tests</categories>
<category>tests</category>
<web></web>
<source></source>
<tracker></tracker>
<marketversion></marketversion>
<marketvercode>9999999</marketvercode>
<package>
<versioncode>9999999</versioncode>
<apkname>duplicate.permisssions_9999999.apk</apkname>
update: handle APKs with a blank versionName Instead of just crashing, first try to use the versionName as written in the build metadata, otherwise just let it be blank. A blank versionName will cause fdroidclient < 1.3 to crash. Blank versionNames are not allowed in the .txt metadata format, only .yml. closes #477 closes #478 closes fdroidclient#1416 closes fdroidclient#1417 closes fdroidclient#1418 fdroiddata!3061
2018-04-17 12:15:51 +02:00
<hash type="sha256">8367857fe75f85321ce2c344b34804d0bc193707f6ba03710d025d9030803434</hash>
<size>27446</size>
aapt 26.0.0 is required to properly parse permissions and label #236 closes #395 aapt 26.0.0 outputs the permissions correctly closes #306 aapt 26.0.0 now outputs: application-label:'K-9 Mail'
2017-12-22 17:28:25 +01:00
<sdkver>18</sdkver>
<targetSdkVersion>27</targetSdkVersion>
<added>2017-12-22</added>
update index metadata tests for 673a3517d337e9e9de736459c13b0126883b8fba
2018-04-16 11:47:48 +02:00
<sig>056c9f1554c40ba59a2103009c82b420</sig>
aapt 26.0.0 is required to properly parse permissions and label #236 closes #395 aapt 26.0.0 outputs the permissions correctly closes #306 aapt 26.0.0 now outputs: application-label:'K-9 Mail'
2017-12-22 17:28:25 +01:00
<permissions>ACCESS_NETWORK_STATE,ACCESS_WIFI_STATE,CHANGE_WIFI_MULTICAST_STATE,INTERNET,READ_EXTERNAL_STORAGE,WRITE_EXTERNAL_STORAGE</permissions>
<uses-permission maxSdkVersion="18" name="android.permission.READ_EXTERNAL_STORAGE"/>
<uses-permission maxSdkVersion="18" name="android.permission.WRITE_EXTERNAL_STORAGE"/>
<uses-permission-sdk-23 maxSdkVersion="27" name="android.permission.REQUEST_IGNORE_BATTERY_OPTIMIZATIONS"/>
</package>
</application>
include non-APKs that match metadata and fdroid-generated filenames Since it is now possible to build and include arbitrary files, like OTA update ZIP files, the update procedure needs to look for non-APK files that match the packageName_versionCode pattern of fdroid-generated files. !193 admin#14 privileged-extension#9
2017-03-10 18:28:22 +01:00
<application id="fake.ota.update">
<id>fake.ota.update</id>
<added>2016-03-10</added>
<lastupdated>2016-03-10</lastupdated>
strip file extension from generated name for non-APKs With a generic file, the file name is the only guaranteed name metadata field. So if the name is not specified in the metadata, then the name is set to the filename. This changes that so that the file extension is stripped from that generated name.
2017-06-01 10:29:30 +02:00
<name>fake.ota.update_1234</name>
include non-APKs that match metadata and fdroid-generated filenames Since it is now possible to build and include arbitrary files, like OTA update ZIP files, the update procedure needs to look for non-APK files that match the packageName_versionCode pattern of fdroid-generated files. !193 admin#14 privileged-extension#9
2017-03-10 18:28:22 +01:00
<summary>Tests whether OTA ZIP files are being include</summary>
<desc>&lt;p&gt;F-Droid can make use of system privileges or permissions to install, update and remove applications on its own. The only way to obtain those privileges is to become a system app.&lt;/p&gt;&lt;p&gt;This is where the Privileged Extension comes in - being a separate app and much smaller, it can be installed as a system app and communicate with the main app via AIDL IPC.&lt;/p&gt;&lt;p&gt;This has several advantages:&lt;/p&gt;&lt;ul&gt;&lt;li&gt; Reduced disk usage in the system partition&lt;/li&gt;&lt;li&gt; System updates don't remove F-Droid&lt;/li&gt;&lt;li&gt; The process of installing into system via root is safer&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;This is packaged as an OTA (Over-The-Air) update ZIP file. It must be installed using TWRP or other Android recovery that can flash updates to the system from the /data/data/org.fdroid.fdroid folder on the /data partition. The standalone APK is called F-Droid Privileged Extension.&lt;/p&gt;</desc>
<license>Apache-2.0</license>
<categories>System</categories>
<category>System</category>
<web>https://f-droid.org</web>
<source>https://gitlab.com/fdroid/privileged-extension</source>
<tracker>https://gitlab.com/fdroid/privileged-extension/issues</tracker>
<donate>https://f-droid.org/about</donate>
<marketversion>0.2.1</marketversion>
<marketvercode>2000</marketvercode>
<package>
update: use only 7 chars of SHA256 for non-APK version name #460
2018-04-16 23:36:12 +02:00
<version>897a92a</version>
include non-APKs that match metadata and fdroid-generated filenames Since it is now possible to build and include arbitrary files, like OTA update ZIP files, the update procedure needs to look for non-APK files that match the packageName_versionCode pattern of fdroid-generated files. !193 admin#14 privileged-extension#9
2017-03-10 18:28:22 +01:00
<versioncode>1234</versioncode>
<apkname>fake.ota.update_1234.zip</apkname>
<hash type="sha256">897a92a4ccff4f415f6ba275b2af16d4ecaee60a983b215bddcb9f8964e7a24c</hash>
<size>233</size>
<added>2016-03-10</added>
</package>
</application>
test for original "v0" index XML compatibility The original index.xml format needs to stay around for backwards compatibility, but we shouldn't touch it anymore once the new format is in place. This is a test to make sure `fdroid update` can still generate the correct XML. install_list and uninstall_list should be tuples or lists in order to ensure that the order is preserved. These tests also check that the added and lastupdated dates are working correct, based on the dates in tests/stats/known_apks.txt. I could see no useful way to test the timestamp, it is just hardcoded using a regexp search-and-replace. Running these tests manually might require deleting tmp/apkcache.
2017-02-23 21:23:45 +01:00
<application id="obb.main.oldversion">
<id>obb.main.oldversion</id>
<added>2013-12-31</added>
<lastupdated>2013-12-31</lastupdated>
<name>OBB Main Old Version</name>
<summary></summary>
<icon>obb.main.oldversion.1444412523.png</icon>
<desc>&lt;p&gt;No description available&lt;/p&gt;</desc>
tests: adapt to spdx v4.0.0
2018-05-16 22:49:57 +02:00
<license>GPL-3.0-only</license>
test for original "v0" index XML compatibility The original index.xml format needs to stay around for backwards compatibility, but we shouldn't touch it anymore once the new format is in place. This is a test to make sure `fdroid update` can still generate the correct XML. install_list and uninstall_list should be tuples or lists in order to ensure that the order is preserved. These tests also check that the added and lastupdated dates are working correct, based on the dates in tests/stats/known_apks.txt. I could see no useful way to test the timestamp, it is just hardcoded using a regexp search-and-replace. Running these tests manually might require deleting tmp/apkcache.
2017-02-23 21:23:45 +01:00
<categories>Development</categories>
<category>Development</category>
<web></web>
<source>https://github.com/eighthave/urzip</source>
<tracker></tracker>
<bitcoin>1Fi5xUHiAPRKxHvyUGVFGt9extBe8Srdbk</bitcoin>
<marketversion></marketversion>
<marketvercode>99999999</marketvercode>
<package>
<version>0.1</version>
<versioncode>1444412523</versioncode>
<apkname>obb.main.oldversion_1444412523.apk</apkname>
fix mistake: lists use .append() not .add() This was a mistake in 5ad3486741cee7d76d251cc27a49e1b4fa7310b9
2017-04-10 20:02:54 +02:00
<hash type="sha256">c5f149e526f89c05c62923bdb7bb1e2be5673c46ec85143f41e514340631449c</hash>
<size>14323</size>
test for original "v0" index XML compatibility The original index.xml format needs to stay around for backwards compatibility, but we shouldn't touch it anymore once the new format is in place. This is a test to make sure `fdroid update` can still generate the correct XML. install_list and uninstall_list should be tuples or lists in order to ensure that the order is preserved. These tests also check that the added and lastupdated dates are working correct, based on the dates in tests/stats/known_apks.txt. I could see no useful way to test the timestamp, it is just hardcoded using a regexp search-and-replace. Running these tests manually might require deleting tmp/apkcache.
2017-02-23 21:23:45 +01:00
<sdkver>4</sdkver>
<targetSdkVersion>18</targetSdkVersion>
<obbMainFile>main.1434483388.obb.main.oldversion.obb</obbMainFile>
<obbMainFileSha256>d3eb539a556352f3f47881d71fb0e5777b2f3e9a4251d283c18c67ce996774b7</obbMainFileSha256>
<added>2013-12-31</added>
fix mistake: lists use .append() not .add() This was a mistake in 5ad3486741cee7d76d251cc27a49e1b4fa7310b9
2017-04-10 20:02:54 +02:00
<sig>eb41d4d6082bb3e81c3d58dbf7fc7332</sig>
<permissions>ACCESS_NETWORK_STATE,ACCESS_WIFI_STATE,BLUETOOTH,BLUETOOTH_ADMIN,CHANGE_NETWORK_STATE,CHANGE_WIFI_MULTICAST_STATE,CHANGE_WIFI_STATE,INTERNET,NFC,RECEIVE_BOOT_COMPLETED</permissions>
<uses-permission maxSdkVersion="22" name="android.permission.ACCESS_NETWORK_STATE"/>
<uses-permission maxSdkVersion="18" name="android.permission.BLUETOOTH_ADMIN"/>
<uses-permission-sdk-23 maxSdkVersion="25" name="android.permission.WRITE_SETTINGS"/>
test for original "v0" index XML compatibility The original index.xml format needs to stay around for backwards compatibility, but we shouldn't touch it anymore once the new format is in place. This is a test to make sure `fdroid update` can still generate the correct XML. install_list and uninstall_list should be tuples or lists in order to ensure that the order is preserved. These tests also check that the added and lastupdated dates are working correct, based on the dates in tests/stats/known_apks.txt. I could see no useful way to test the timestamp, it is just hardcoded using a regexp search-and-replace. Running these tests manually might require deleting tmp/apkcache.
2017-02-23 21:23:45 +01:00
</package>
</application>
<application id="obb.main.twoversions">
<id>obb.main.twoversions</id>
<added>2015-10-12</added>
<lastupdated>2016-06-20</lastupdated>
<name>OBB Main Two Versions</name>
<summary></summary>
<icon>obb.main.twoversions.1101617.png</icon>
<desc>&lt;p&gt;No description available&lt;/p&gt;</desc>
tests: adapt to spdx v4.0.0
2018-05-16 22:49:57 +02:00
<license>GPL-3.0-only</license>
test for original "v0" index XML compatibility The original index.xml format needs to stay around for backwards compatibility, but we shouldn't touch it anymore once the new format is in place. This is a test to make sure `fdroid update` can still generate the correct XML. install_list and uninstall_list should be tuples or lists in order to ensure that the order is preserved. These tests also check that the added and lastupdated dates are working correct, based on the dates in tests/stats/known_apks.txt. I could see no useful way to test the timestamp, it is just hardcoded using a regexp search-and-replace. Running these tests manually might require deleting tmp/apkcache.
2017-02-23 21:23:45 +01:00
<categories>Development</categories>
<category>Development</category>
<web></web>
<source>https://github.com/eighthave/urzip</source>
<tracker></tracker>
<bitcoin>1Fi5xUHiAPRKxHvyUGVFGt9extBe8Srdbk</bitcoin>
<marketversion></marketversion>
<marketvercode>99999999</marketvercode>
<package>
<version>0.1</version>
<versioncode>1101617</versioncode>
<apkname>obb.main.twoversions_1101617.apk</apkname>
<srcname>obb.main.twoversions_1101617_src.tar.gz</srcname>
<hash type="sha256">9bc74566f089ef030ac33e7fbd99d92f1a38f363fb499fed138d9e7b774e821c</hash>
<size>11481</size>
<sdkver>4</sdkver>
<targetSdkVersion>18</targetSdkVersion>
<obbMainFile>main.1101615.obb.main.twoversions.obb</obbMainFile>
<obbMainFileSha256>d3eb539a556352f3f47881d71fb0e5777b2f3e9a4251d283c18c67ce996774b7</obbMainFileSha256>
<added>2016-06-20</added>
<sig>b4964fd759edaa54e65bb476d0276880</sig>
</package>
<package>
<version>0.1</version>
<versioncode>1101615</versioncode>
<apkname>obb.main.twoversions_1101615.apk</apkname>
<hash type="sha256">7b0b7b9ba248e15751a16e3a0e01e1e24cbb673686c38422030cb75d5c33f0bb</hash>
<size>11480</size>
<sdkver>4</sdkver>
<targetSdkVersion>18</targetSdkVersion>
<obbMainFile>main.1101615.obb.main.twoversions.obb</obbMainFile>
<obbMainFileSha256>d3eb539a556352f3f47881d71fb0e5777b2f3e9a4251d283c18c67ce996774b7</obbMainFileSha256>
<added>2016-01-01</added>
<sig>b4964fd759edaa54e65bb476d0276880</sig>
</package>
<package>
<version>0.1</version>
<versioncode>1101613</versioncode>
<apkname>obb.main.twoversions_1101613.apk</apkname>
<hash type="sha256">cce97a52ff18d843185be7f22ecb1a557c36b7a9f8ba07a8be94e328e00b35dc</hash>
<size>11477</size>
<sdkver>4</sdkver>
<targetSdkVersion>18</targetSdkVersion>
<obbMainFile>main.1101613.obb.main.twoversions.obb</obbMainFile>
<obbMainFileSha256>d3eb539a556352f3f47881d71fb0e5777b2f3e9a4251d283c18c67ce996774b7</obbMainFileSha256>
<added>2015-10-12</added>
<sig>b4964fd759edaa54e65bb476d0276880</sig>
</package>
</application>
<application id="obb.mainpatch.current">
<id>obb.mainpatch.current</id>
<added>2016-04-23</added>
allow APKs with same packageName/versionCode but different signer There are many APKs out in the wild that claim to be the same app and version and each other, but they are signed by different keys. fdroid should be able to index these, and work with them. This supports having the developer's signature via reproducible builds, random collections of APKs like repomaker, etc.
2017-05-30 14:52:33 +02:00
<lastupdated>2017-06-01</lastupdated>
test for original "v0" index XML compatibility The original index.xml format needs to stay around for backwards compatibility, but we shouldn't touch it anymore once the new format is in place. This is a test to make sure `fdroid update` can still generate the correct XML. install_list and uninstall_list should be tuples or lists in order to ensure that the order is preserved. These tests also check that the added and lastupdated dates are working correct, based on the dates in tests/stats/known_apks.txt. I could see no useful way to test the timestamp, it is just hardcoded using a regexp search-and-replace. Running these tests manually might require deleting tmp/apkcache.
2017-02-23 21:23:45 +01:00
<name>OBB Main/Patch Current</name>
<summary></summary>
<icon>obb.mainpatch.current.1619.png</icon>
<desc>&lt;p&gt;No description available&lt;/p&gt;</desc>
tests: adapt to spdx v4.0.0
2018-05-16 22:49:57 +02:00
<license>GPL-3.0-only</license>
test for original "v0" index XML compatibility The original index.xml format needs to stay around for backwards compatibility, but we shouldn't touch it anymore once the new format is in place. This is a test to make sure `fdroid update` can still generate the correct XML. install_list and uninstall_list should be tuples or lists in order to ensure that the order is preserved. These tests also check that the added and lastupdated dates are working correct, based on the dates in tests/stats/known_apks.txt. I could see no useful way to test the timestamp, it is just hardcoded using a regexp search-and-replace. Running these tests manually might require deleting tmp/apkcache.
2017-02-23 21:23:45 +01:00
<categories>Development</categories>
<category>Development</category>
<web></web>
<source>https://github.com/eighthave/urzip</source>
<tracker></tracker>
<bitcoin>1Fi5xUHiAPRKxHvyUGVFGt9extBe8Srdbk</bitcoin>
<marketversion></marketversion>
<marketvercode>99999999</marketvercode>
<package>
<version>0.1</version>
<versioncode>1619</versioncode>
<apkname>obb.mainpatch.current_1619.apk</apkname>
<hash type="sha256">eda5fc3ecfdac3252717e36bdbc9820865baeef162264af9ba5db7364f0e7a0c</hash>
<size>11479</size>
<sdkver>4</sdkver>
<targetSdkVersion>18</targetSdkVersion>
<obbMainFile>main.1619.obb.mainpatch.current.obb</obbMainFile>
<obbMainFileSha256>d3eb539a556352f3f47881d71fb0e5777b2f3e9a4251d283c18c67ce996774b7</obbMainFileSha256>
<obbPatchFile>patch.1619.obb.mainpatch.current.obb</obbPatchFile>
<obbPatchFileSha256>d3eb539a556352f3f47881d71fb0e5777b2f3e9a4251d283c18c67ce996774b7</obbPatchFileSha256>
<added>2016-04-23</added>
<sig>b4964fd759edaa54e65bb476d0276880</sig>
</package>
</application>
tests: test moving files to and from the archive #166
2017-06-27 23:33:24 +02:00
<application id="com.politedroid">
<id>com.politedroid</id>
<added>2017-06-23</added>
<lastupdated>2017-06-23</lastupdated>
<name>Polite Droid</name>
<summary>Calendar tool</summary>
<icon>com.politedroid.6.png</icon>
<desc>&lt;p&gt;Activates silent mode during calendar events.&lt;/p&gt;</desc>
tests: adapt to spdx v4.0.0
2018-05-16 22:49:57 +02:00
<license>GPL-3.0-only</license>
tests: test moving files to and from the archive #166
2017-06-27 23:33:24 +02:00
<categories>Time</categories>
<category>Time</category>
<web></web>
<source>https://github.com/miguelvps/PoliteDroid</source>
<tracker>https://github.com/miguelvps/PoliteDroid/issues</tracker>
<marketversion>1.5</marketversion>
<marketvercode>6</marketvercode>
<package>
<version>1.5</version>
<versioncode>6</versioncode>
<apkname>com.politedroid_6.apk</apkname>
<hash type="sha256">70c2f776a2bac38a58a7d521f96ee0414c6f0fb1de973c3ca8b10862a009247d</hash>
<size>16578</size>
<sdkver>14</sdkver>
<targetSdkVersion>21</targetSdkVersion>
<added>2017-06-23</added>
<sig>b4964fd759edaa54e65bb476d0276880</sig>
<permissions>READ_CALENDAR,RECEIVE_BOOT_COMPLETED</permissions>
</package>
<package>
<version>1.4</version>
<versioncode>5</versioncode>
<apkname>com.politedroid_5.apk</apkname>
<hash type="sha256">5bdbfa071cca4b8d05ced41d6b28763595d6e8096cca5bbf0f9253c9a2622e5d</hash>
<size>18817</size>
<sdkver>3</sdkver>
<targetSdkVersion>10</targetSdkVersion>
<added>2017-06-23</added>
<sig>b4964fd759edaa54e65bb476d0276880</sig>
<permissions>READ_CALENDAR,RECEIVE_BOOT_COMPLETED</permissions>
</package>
<package>
<version>1.3</version>
<versioncode>4</versioncode>
<apkname>com.politedroid_4.apk</apkname>
<hash type="sha256">c809bdff83715fbf919f3840ee09869b038e209378b906e135ee40d3f0e1f075</hash>
<size>18489</size>
<sdkver>3</sdkver>
<targetSdkVersion>3</targetSdkVersion>
<added>2017-06-23</added>
<sig>b4964fd759edaa54e65bb476d0276880</sig>
<permissions>READ_CALENDAR,READ_EXTERNAL_STORAGE,READ_PHONE_STATE,RECEIVE_BOOT_COMPLETED,WRITE_EXTERNAL_STORAGE</permissions>
</package>
<package>
<version>1.2</version>
<versioncode>3</versioncode>
<apkname>com.politedroid_3.apk</apkname>
<hash type="sha256">665d03d61ebc642289fda697f71a59305b0202b16cafc5ffdae91cbe91f0b25d</hash>
<size>17552</size>
<sdkver>3</sdkver>
<targetSdkVersion>3</targetSdkVersion>
<added>2017-06-23</added>
<sig>b4964fd759edaa54e65bb476d0276880</sig>
<permissions>READ_CALENDAR,READ_EXTERNAL_STORAGE,READ_PHONE_STATE,RECEIVE_BOOT_COMPLETED,WRITE_EXTERNAL_STORAGE</permissions>
</package>
</application>
test for original "v0" index XML compatibility The original index.xml format needs to stay around for backwards compatibility, but we shouldn't touch it anymore once the new format is in place. This is a test to make sure `fdroid update` can still generate the correct XML. install_list and uninstall_list should be tuples or lists in order to ensure that the order is preserved. These tests also check that the added and lastupdated dates are working correct, based on the dates in tests/stats/known_apks.txt. I could see no useful way to test the timestamp, it is just hardcoded using a regexp search-and-replace. Running these tests manually might require deleting tmp/apkcache.
2017-02-23 21:23:45 +01:00
<application id="info.guardianproject.urzip">
<id>info.guardianproject.urzip</id>
<added>2016-06-23</added>
<lastupdated>2016-06-23</lastupdated>
<name>urzip-πÇÇπÇÇ现代汉语通用字-български-عربي1234</name>
<summary>一个实用工具，获取已安装在您的设备上的应用的有关信息</summary>
<icon>info.guardianproject.urzip.100.png</icon>
<desc>&lt;p&gt;It’s Urzip 是一个获得已安装 APK 相关信息的实用工具。它从您的设备上已安装的所有应用开始，一键触摸即可显示 APK 的指纹，并且提供到达 virustotal.com 和 androidobservatory.org 的快捷链接，让您方便地了解特定 APK 的档案。它还可以让您导出签名证书和生成 ApkSignaturePin Pin 文件供 TrustedIntents 库使用。&lt;/p&gt;&lt;p&gt;★ Urzip 支持下列语言： Deutsch, English, español, suomi, 日本語, 한국어, Norsk, português (Portugal), Русский, Slovenščina, Türkçe 没看到您的语言？帮忙翻译本应用吧： https://www.transifex.com/projects/p/urzip&lt;/p&gt;&lt;p&gt;★ 致用户：我们还缺少你喜欢的功能？发现了一个 bug？请告诉我们！我们乐于听取您的意见。请发送电子邮件至: support@guardianproject.info 或者加入我们的聊天室 https://guardianproject.info/contact&lt;/p&gt;</desc>
tests: adapt to spdx v4.0.0
2018-05-16 22:49:57 +02:00
<license>GPL-3.0-only</license>
ensure that app.Categories is always a list of strings This just makes it easier for people writing build recipes. Rewriting will output a list of strings as well. The test index.xml and categories.txt are updated to include the new number categories, and the changed CurrentVersionCode to 2147483647 (MAX_VALUE)
2016-12-06 16:11:25 +01:00
<categories>Development,GuardianProject,1,2.0</categories>
test for original "v0" index XML compatibility The original index.xml format needs to stay around for backwards compatibility, but we shouldn't touch it anymore once the new format is in place. This is a test to make sure `fdroid update` can still generate the correct XML. install_list and uninstall_list should be tuples or lists in order to ensure that the order is preserved. These tests also check that the added and lastupdated dates are working correct, based on the dates in tests/stats/known_apks.txt. I could see no useful way to test the timestamp, it is just hardcoded using a regexp search-and-replace. Running these tests manually might require deleting tmp/apkcache.
2017-02-23 21:23:45 +01:00
<category>Development</category>
<web>https://dev.guardianproject.info/projects/urzip</web>
<source>https://github.com/guardianproject/urzip</source>
<tracker>https://dev.guardianproject.info/projects/urzip/issues</tracker>
<bitcoin>1Fi5xUHiAPRKxHvyUGVFGt9extBe8Srdbk</bitcoin>
<marketversion></marketversion>
ensure that app.Categories is always a list of strings This just makes it easier for people writing build recipes. Rewriting will output a list of strings as well. The test index.xml and categories.txt are updated to include the new number categories, and the changed CurrentVersionCode to 2147483647 (MAX_VALUE)
2016-12-06 16:11:25 +01:00
<marketvercode>2147483647</marketvercode>
test for original "v0" index XML compatibility The original index.xml format needs to stay around for backwards compatibility, but we shouldn't touch it anymore once the new format is in place. This is a test to make sure `fdroid update` can still generate the correct XML. install_list and uninstall_list should be tuples or lists in order to ensure that the order is preserved. These tests also check that the added and lastupdated dates are working correct, based on the dates in tests/stats/known_apks.txt. I could see no useful way to test the timestamp, it is just hardcoded using a regexp search-and-replace. Running these tests manually might require deleting tmp/apkcache.
2017-02-23 21:23:45 +01:00
<package>
<version>0.1</version>
<versioncode>100</versioncode>
rename test files to work round filename length limits It seems a lot of things like tar, Windows, some filesystems, etc. do not handle long filenames. #416
2017-11-27 16:35:58 +01:00
<apkname>urzip-; Рахма́нинов, [rɐxˈmanʲɪnəf] سيرجي_رخمانينوف 谢尔盖·.apk</apkname>
test for original "v0" index XML compatibility The original index.xml format needs to stay around for backwards compatibility, but we shouldn't touch it anymore once the new format is in place. This is a test to make sure `fdroid update` can still generate the correct XML. install_list and uninstall_list should be tuples or lists in order to ensure that the order is preserved. These tests also check that the added and lastupdated dates are working correct, based on the dates in tests/stats/known_apks.txt. I could see no useful way to test the timestamp, it is just hardcoded using a regexp search-and-replace. Running these tests manually might require deleting tmp/apkcache.
2017-02-23 21:23:45 +01:00
<hash type="sha256">15c0ec72c74a3791f42cdb43c57df0fb11a4dbb656851bbb8cf05b26a8372789</hash>
<size>11471</size>
<sdkver>4</sdkver>
<targetSdkVersion>18</targetSdkVersion>
<added>2016-06-23</added>
<sig>b4964fd759edaa54e65bb476d0276880</sig>
</package>
</application>
</fdroid>
Copy Permalink