kamp/fdroidserver
1
0
Fork 0
mirror of https://gitlab.com/fdroid/fdroidserver.git synced 2024-11-09 00:40:11 +01:00
Code Activity
33def096f5
fdroidserver/tests/metadata/dump/org.smssecure.smssecure.yaml

413 lines
8.2 KiB
YAML
Raw Normal View History

update: AllowedAPKSigningKeys metadata to enforce APK signers This field lets you specify which signing certificates should be trusted for APKs in a binary repo.
2021-07-20 22:31:27 +02:00
AllowedAPKSigningKeys: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
AntiFeatures: []
convert App to subclass of dict to support parsing/dumping libs Python is heavily based on its core data types, and dict is one of the more important ones. Even classes are basically a wrapper around a dict. This converts metadata.App to be a subclass of dict so it can behave like a dict when being dumped and loaded. This makes its drastically easier to use different data formats for build metadata and for sending data to the client. This approach will ultimately mean we no longer have to maintain custom parsing and dumping code. This also means then that the YAML/JSON field names will not have spaces in them, and they will match exactly what it used as the dict keys once the data is parsed, as well as matching exactly the instance attribute names: * CurrentVersion: 1.2.6 * app['CurrentVersion'] == '1.2.6' * app.CurrentVersion == '1.2.6' Inspired by: https://goodcode.io/articles/python-dict-object/
2016-11-23 17:25:59 +01:00
ArchivePolicy: null
AuthorEmail: null
AuthorName: null
support "Author Web Site" as metadata field Fastlane Supply, Triple-T Gradle Play Publisher, and many app stores include the possibility to specify a website for the author, as distinct from the website for the app. closes #204
2017-04-14 14:23:07 +02:00
AuthorWebSite: null
convert App to subclass of dict to support parsing/dumping libs Python is heavily based on its core data types, and dict is one of the more important ones. Even classes are basically a wrapper around a dict. This converts metadata.App to be a subclass of dict so it can behave like a dict when being dumped and loaded. This makes its drastically easier to use different data formats for build metadata and for sending data to the client. This approach will ultimately mean we no longer have to maintain custom parsing and dumping code. This also means then that the YAML/JSON field names will not have spaces in them, and they will match exactly what it used as the dict keys once the data is parsed, as well as matching exactly the instance attribute names: * CurrentVersion: 1.2.6 * app['CurrentVersion'] == '1.2.6' * app.CurrentVersion == '1.2.6' Inspired by: https://goodcode.io/articles/python-dict-object/
2016-11-23 17:25:59 +01:00
AutoName: SMSSecure
AutoUpdateMode: Version v%v
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
Binaries: null
Bitcoin: null
eliminate app.builds everywhere, it should be app['Builds'] The .txt format was the last place where the lowercase "builds" was used, this converts references everywhere to be "Builds". This makes it possible to load metadata YAML files with any YAML parser, then have it possible to use fdroidserver methods on that data, like metadata.write_metadata(). The test files in tests/metadata/dump/*.yaml were manually edited by cutting the builds: block and putting it the sort order for Builds: so the contents should be unchanged. ``` sed -i \ -e 's/app\.builds/app.get('Builds', \[\])/g' \ -e "s/app\.get(Builds, \[\]) =/app\['Builds'] =/g" \ -e "s/app\.get(Builds, \[\]) =/app\['Builds'] =/g" \ -e "s/app\.get(Builds, \[\])/app.get('Builds', \[\])/g" \ -e "s/app\.get('Builds', \[\])\.append/app\['Builds'\].append/g" \ -e "s/app\['builds'\]/app.get('Builds', [])/g" \ */*.* ```
2020-12-09 16:01:21 +01:00
Builds:
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
support manually adding per-build antiFeatures in metadata For cases like the OpenVPN vuln that was recently announced, it is useful for fdroiddata maintainers to be able to mark builds that have known vulnerabilities.
2017-06-27 23:55:38 +02:00
antifeatures: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
build: ''
buildjni: []
Test metadata files updated.
2017-06-21 08:26:52 +02:00
buildozer: false
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 66367479a4f57f347b5cbe8f6f8f632adaae7727
disable: builds, merge changes into upstream
encoding: null
extlibs: []
forcevercode: true
forceversion: false
gradle:
- 'yes'
gradleprops: []
init: ''
maven: false
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- touch signing.properties
- pushd $$GradleWitness$$
- gradle jar
- popd
- cp $$GradleWitness$$/build/libs/GradleWitness.jar libs/gradle-witness.jar
- sed -i -e '20,22d' build.gradle
- pushd $$PreferenceFragment$$
- gradle uploadArchives
- popd
- sed -i -e '/5470f5872514a6226fa1fc6f4e000991f38805691c534cf0bd2778911fc773ad/d'
build.gradle
- mkdir smil
- pushd smil
- wget -c http://www.w3.org/TR/smil-boston-dom/java-binding.zip
- unzip java-binding.zip
- popd
- cp -fR smil/java/org src/
- rm -fR smil
- sed -i -e '/org.w3c.smil/d' build.gradle
- cp -fR $$AospMms$$/src/org src/
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm:
- libs/*
scandelete: []
scanignore: []
srclibs:
- GradleWitness@10f1269c0aafdc1d478efc005ed48f3a47d44278
- PreferenceFragment@717a45433b927d2f0dfc5328f79e77c9682c37bc
- ShortcutBadger@3815ce2ec0c66acd7d7c0b4f2479df8fa70fed87
- AospMms@android-5.1.0_r3
subdir: null
submodules: false
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 5
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 0.3.3
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
support manually adding per-build antiFeatures in metadata For cases like the OpenVPN vuln that was recently announced, it is useful for fdroiddata maintainers to be able to mark builds that have known vulnerabilities.
2017-06-27 23:55:38 +02:00
antifeatures: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
build: ''
buildjni: []
Test metadata files updated.
2017-06-21 08:26:52 +02:00
buildozer: false
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: 9675ce5eecb929dcaddb43b3d9486fdb88b9ae1a
disable: builds, wait for upstream
encoding: null
extlibs: []
forcevercode: false
forceversion: false
gradle:
- 'yes'
gradleprops: []
init: ''
maven: false
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- touch signing.properties
- pushd $$GradleWitness$$
- gradle jar
- popd
- cp $$GradleWitness$$/build/libs/GradleWitness.jar libs/gradle-witness.jar
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm:
- libs/*.jar
scandelete: []
scanignore: []
srclibs:
- GradleWitness@10f1269c0aafdc1d478efc005ed48f3a47d44278
subdir: null
submodules: true
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 6
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 0.3.3
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
support manually adding per-build antiFeatures in metadata For cases like the OpenVPN vuln that was recently announced, it is useful for fdroiddata maintainers to be able to mark builds that have known vulnerabilities.
2017-06-27 23:55:38 +02:00
antifeatures: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
build: ''
buildjni: []
Test metadata files updated.
2017-06-21 08:26:52 +02:00
buildozer: false
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: v0.4.2
disable: builds locally, but not on BS
encoding: null
extlibs: []
forcevercode: false
forceversion: false
gradle:
- 'yes'
gradleprops: []
init: ''
maven: false
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- touch signing.properties
- ./build-witness.sh
- rm -rf libs/gradle-witness/build
- echo "org.gradle.jvmargs=-Xms512m -Xmx512m -XX:MaxPermSize=512m" >> gradle.properties
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm:
- libs/*.jar
scandelete: []
scanignore: []
srclibs: []
subdir: null
submodules: true
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 9
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 0.4.2
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
support manually adding per-build antiFeatures in metadata For cases like the OpenVPN vuln that was recently announced, it is useful for fdroiddata maintainers to be able to mark builds that have known vulnerabilities.
2017-06-27 23:55:38 +02:00
antifeatures: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
build: ''
buildjni: []
Test metadata files updated.
2017-06-21 08:26:52 +02:00
buildozer: false
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: v0.5.1
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: false
forceversion: false
gradle:
- 'yes'
gradleprops: []
init: ''
maven: false
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- touch signing.properties
- ./build-witness.sh
- rm -rf libs/gradle-witness/build
- echo "org.gradle.jvmargs=-Xms512m -Xmx512m -XX:MaxPermSize=512m" >> gradle.properties
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm:
- libs/*.jar
scandelete: []
scanignore: []
srclibs: []
subdir: null
submodules: true
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 11
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 0.5.1
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
support manually adding per-build antiFeatures in metadata For cases like the OpenVPN vuln that was recently announced, it is useful for fdroiddata maintainers to be able to mark builds that have known vulnerabilities.
2017-06-27 23:55:38 +02:00
antifeatures: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
build: ''
buildjni: []
Test metadata files updated.
2017-06-21 08:26:52 +02:00
buildozer: false
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: v0.5.2
disable: broken in upstream
encoding: null
extlibs: []
forcevercode: false
forceversion: false
gradle:
- 'yes'
gradleprops: []
init: ''
maven: false
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- touch signing.properties
- ./scripts/build-witness.sh
- rm -rf libs/gradle-witness/build
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm:
- libs/*.jar
scandelete: []
scanignore: []
srclibs: []
subdir: null
submodules: true
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 12
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 0.5.2
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
support manually adding per-build antiFeatures in metadata For cases like the OpenVPN vuln that was recently announced, it is useful for fdroiddata maintainers to be able to mark builds that have known vulnerabilities.
2017-06-27 23:55:38 +02:00
antifeatures: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
build: ''
buildjni: []
Test metadata files updated.
2017-06-21 08:26:52 +02:00
buildozer: false
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: v0.5.3
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: false
forceversion: false
gradle:
- 'yes'
gradleprops: []
init: ''
maven: false
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- touch signing.properties
- ./scripts/build-witness.sh
- rm -rf libs/gradle-witness/build
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm:
- libs/*.jar
scandelete: []
scanignore: []
srclibs: []
subdir: null
submodules: true
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 100
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 0.5.3
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
support manually adding per-build antiFeatures in metadata For cases like the OpenVPN vuln that was recently announced, it is useful for fdroiddata maintainers to be able to mark builds that have known vulnerabilities.
2017-06-27 23:55:38 +02:00
antifeatures: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
build: ''
buildjni: []
Test metadata files updated.
2017-06-21 08:26:52 +02:00
buildozer: false
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: v0.5.4
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: false
forceversion: false
gradle:
- 'yes'
gradleprops: []
init: ''
maven: false
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- touch signing.properties
- ./scripts/build-witness.sh
- rm -rf libs/gradle-witness/build
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm:
- libs/*.jar
scandelete: []
scanignore: []
srclibs: []
subdir: null
submodules: true
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 101
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 0.5.4
convert metadata.Build to a subclass of dict Like with the App class in the commit before, this makes it a lot easier to work with this data when converting between the internal formats and external formats like YAML, JSON, MsgPack, protobuf, etc. The one unfortunate thing here is Build.update. It becomes dict.update(), which is a method not an attribute. build.get('update') or build['update'] could be used, but that would be oddly inconsistent. So instead the field is renamed to 'androidupdate', except for in the .txt v0 metadata files. This better describes what field does anyway, since it runs `android update`. Build.update is only referenced in two places right next to each other for the ant builds, so this change still seems worthwhile.
2016-11-29 13:26:32 +01:00
- androidupdate: []
antcommands: []
support manually adding per-build antiFeatures in metadata For cases like the OpenVPN vuln that was recently announced, it is useful for fdroiddata maintainers to be able to mark builds that have known vulnerabilities.
2017-06-27 23:55:38 +02:00
antifeatures: []
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
build: ''
buildjni: []
Test metadata files updated.
2017-06-21 08:26:52 +02:00
buildozer: false
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
commit: v0.6.0
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
encoding: null
extlibs: []
forcevercode: false
forceversion: false
gradle:
- 'yes'
gradleprops: []
init: ''
maven: false
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
preassemble: []
Run shell scripts with -e (Closes: #1035) Make sudo, init prebuild, build and Prepare fields lists and only concatenate them with '; ' before execution. This allows arbitrary commands inside the fileds (even && and ';') as we don't need to split the commands again for rewritemeta.
2022-09-09 12:36:54 +02:00
prebuild:
- touch signing.properties
- ./scripts/build-witness.sh
- rm -rf libs/gradle-witness/build
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
rm:
- libs/*.jar
scandelete: []
scanignore: []
srclibs: []
subdir: null
submodules: true
support configing buildserver VM per-build with sudo= This adds the 'sudo' build field, which is just a script that is run as root. For more info, see the issue that this closes: refs #318 closes #317
2017-06-28 23:01:45 +02:00
sudo: ''
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
target: null
build: make per-build hard time limit customizable Add "timeout=n" metadata field that overrides build timeout (in seconds). The default is 7200, i.e. 2 hours.
2018-01-28 07:56:19 +01:00
timeout: null
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
versionCode: 102
rename Build fields: version -> versionName, vercode -> versionCode Since the YAML/JSON/etc. field names are now exactly the same as the field names used in the internal dict in the Build class, this is a global rename This keeps with the standard names used in Android: https://developer.android.com/guide/topics/manifest/manifest-element.html
2016-11-23 17:52:04 +01:00
versionName: 0.6.0
eliminate app.builds everywhere, it should be app['Builds'] The .txt format was the last place where the lowercase "builds" was used, this converts references everywhere to be "Builds". This makes it possible to load metadata YAML files with any YAML parser, then have it possible to use fdroidserver methods on that data, like metadata.write_metadata(). The test files in tests/metadata/dump/*.yaml were manually edited by cutting the builds: block and putting it the sort order for Builds: so the contents should be unchanged. ``` sed -i \ -e 's/app\.builds/app.get('Builds', \[\])/g' \ -e "s/app\.get(Builds, \[\]) =/app\['Builds'] =/g" \ -e "s/app\.get(Builds, \[\]) =/app\['Builds'] =/g" \ -e "s/app\.get(Builds, \[\])/app.get('Builds', \[\])/g" \ -e "s/app\.get('Builds', \[\])\.append/app\['Builds'\].append/g" \ -e "s/app\['builds'\]/app.get('Builds', [])/g" \ */*.* ```
2020-12-09 16:01:21 +01:00
Categories:
- Phone & SMS
Changelog: ''
CurrentVersion: 0.6.0
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
CurrentVersionCode: 102
eliminate app.builds everywhere, it should be app['Builds'] The .txt format was the last place where the lowercase "builds" was used, this converts references everywhere to be "Builds". This makes it possible to load metadata YAML files with any YAML parser, then have it possible to use fdroidserver methods on that data, like metadata.write_metadata(). The test files in tests/metadata/dump/*.yaml were manually edited by cutting the builds: block and putting it the sort order for Builds: so the contents should be unchanged. ``` sed -i \ -e 's/app\.builds/app.get('Builds', \[\])/g' \ -e "s/app\.get(Builds, \[\]) =/app\['Builds'] =/g" \ -e "s/app\.get(Builds, \[\]) =/app\['Builds'] =/g" \ -e "s/app\.get(Builds, \[\])/app.get('Builds', \[\])/g" \ -e "s/app\.get('Builds', \[\])\.append/app\['Builds'\].append/g" \ -e "s/app\['builds'\]/app.get('Builds', [])/g" \ */*.* ```
2020-12-09 16:01:21 +01:00
Description: 'SMSSecure is an SMS/MMS application that allows you to protect your
privacy while communicating with friends.
Using SMSSecure, you can send SMS messages and share media or attachments with complete
privacy.
* Easy. SMSSecure works like any other SMS application. There''s nothing to sign
up for and no new service your friends need to join.
* Reliable. SMSSecure communicates using encrypted SMS messages. No servers or internet
connection required.
* Private. SMSSecure uses the TextSecure encryption protocol to provide privacy
for every message, every time.
* Safe. All messages are encrypted locally, so if your phone is lost or stolen,
your messages are protected.
* Open Source. SMSSecure is Free and Open Source, enabling anyone to verify its
security by auditing the code.'
Disabled: null
Donate: null
FlattrID: null
IssueTracker: https://github.com/SMSSecure/SMSSecure/issues
Liberapay: null
License: GPL-3.0-only
Litecoin: null
MaintainerNotes: ''
Name: null
NoSourceSince: ''
OpenCollective: null
Provides: null
Repo: https://github.com/SMSSecure/SMSSecure
RepoType: git
RequiresRoot: false
SourceCode: https://github.com/SMSSecure/SMSSecure
Summary: Send encrypted text messages (SMS)
Translation: https://www.transifex.com/silence/silence
UpdateCheckData: null
UpdateCheckIgnore: null
UpdateCheckMode: Tags
UpdateCheckName: null
change VercodeOperation to TYPE_LIST
2022-10-27 13:11:37 +02:00
VercodeOperation: []
eliminate app.builds everywhere, it should be app['Builds'] The .txt format was the last place where the lowercase "builds" was used, this converts references everywhere to be "Builds". This makes it possible to load metadata YAML files with any YAML parser, then have it possible to use fdroidserver methods on that data, like metadata.write_metadata(). The test files in tests/metadata/dump/*.yaml were manually edited by cutting the builds: block and putting it the sort order for Builds: so the contents should be unchanged. ``` sed -i \ -e 's/app\.builds/app.get('Builds', \[\])/g' \ -e "s/app\.get(Builds, \[\]) =/app\['Builds'] =/g" \ -e "s/app\.get(Builds, \[\]) =/app\['Builds'] =/g" \ -e "s/app\.get(Builds, \[\])/app.get('Builds', \[\])/g" \ -e "s/app\.get('Builds', \[\])\.append/app\['Builds'\].append/g" \ -e "s/app\['builds'\]/app.get('Builds', [])/g" \ */*.* ```
2020-12-09 16:01:21 +01:00
WebSite: http://www.smssecure.org
added: null
convert metadata test dumps to YAML for easy comparison When making code changes related to the metadata parsing, it is useful to see how the internal format has changed by seeing the differences in the dump files. Those files are currently in the binary .pickle format. This just straight converts them to YAML, which is a text format, so that normal diff tools work to see changes. The dump files are named .yaml instead of .yml since .yml is used for hand- edited YAML files for fdroiddata/metadata, while these dump files here are a human readable form of a Python pickle.
2016-11-23 15:14:44 +01:00
comments: {}
id: org.smssecure.smssecure
rename lastupdated to lastUpdated to match fdroid client This lets index-v1 be parsed directly into class instances because the field/instance var names match exactly. The original index v0 element must retain the 'lastupdated' name for backwards compatibility.
2016-11-28 21:17:22 +01:00
lastUpdated: null
move all test metadata files to .yml format for f in metadata/*.txt; do ../fdroid rewritemeta --to yml $(basename $f | sed 's,\.txt,,'); done
2020-06-09 22:01:31 +02:00
metadatapath: metadata/org.smssecure.smssecure.yml
Copy Permalink