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
bbf17ee59c
fdroidserver/tests/metadata/dump/com.politedroid.yaml

199 lines
3.4 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: []
update test_read_metadata to use ruamel.yaml and YAML 1.2 I tried to get this to indent the .yaml files properly so yamllint defaults work with tests/metadata/dump/*.yaml, but it didn't take for some reason: yaml.indent(mapping=4, sequence=4, offset=2)
2023-05-02 10:59:53 +02:00
AntiFeatures:
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
NoSourceSince:
en-US: '1.5'
NonFreeNet: {}
metadata: Make ArchivePolicy an interger internally
2023-05-25 19:05:57 +02:00
ArchivePolicy: 4
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
AuthorEmail: null
AuthorName: null
AuthorWebSite: null
AutoName: Polite Droid
AutoUpdateMode: Version v%v
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:
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
- androidupdate: []
antcommands: []
antifeatures:
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
KnownVuln: {}
NonFreeAssets: {}
UpstreamNonFree: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
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
build: ''
buildjni: []
commit: 6a548e4b19
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
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
encoding: null
extlibs: []
forcevercode: false
forceversion: false
gradle: []
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
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
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
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
preassemble: []
prebuild: ''
rm: []
scandelete: []
scanignore: []
srclibs: []
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: ''
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
target: android-10
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: 3
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
versionName: '1.2'
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
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
build: ''
buildjni: []
commit: ad865b57bf3ac59580f38485608a9b1dda4fa7dc
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
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
encoding: null
extlibs: []
forcevercode: false
forceversion: false
gradle: []
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
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
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
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
preassemble: []
prebuild: ''
rm: []
scandelete: []
scanignore: []
srclibs: []
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: ''
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
target: android-15
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: 4
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
versionName: '1.3'
- androidupdate: []
antcommands: []
define "string map" type for new Anti-Features explanations closes #683
2023-04-21 10:00:40 +02:00
antifeatures: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
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
build: ''
buildjni: []
commit: 456bd615f3fbe6dff06433928cf7ea20073601fb
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
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
encoding: null
extlibs: []
forcevercode: false
forceversion: false
gradle: []
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
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
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
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
preassemble: []
prebuild: ''
rm: []
scandelete: []
scanignore: []
srclibs: []
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: ''
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
target: android-10
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
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
versionName: '1.4'
- androidupdate: []
antcommands: []
Add test for !1370 The bug fixed in !1370 was due to a reuse of the per app anti features dictionary in the per version one and adding the per version anti features into it. This was not caught by the test suite as the app versions are processed from newest to oldest and the test data had only anti features in the oldest version. This patch adds an anti feature to a newest version so only those in between should not have it.
2023-06-02 10:06:47 +02:00
antifeatures:
KnownVuln: {}
NonFreeAssets: {}
UpstreamNonFree: {}
Add build.binary
2023-02-04 13:26:24 +01:00
binary: null
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
build: ''
buildjni: []
commit: v1.5
fix fixtures in tests/metadata/dump
2018-08-07 00:02:07 +02:00
disable: ''
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
encoding: null
extlibs: []
forcevercode: false
forceversion: false
gradle:
update test_read_metadata to use ruamel.yaml and YAML 1.2 I tried to get this to indent the .yaml files properly so yamllint defaults work with tests/metadata/dump/*.yaml, but it didn't take for some reason: yaml.indent(mapping=4, sequence=4, offset=2)
2023-05-02 10:59:53 +02:00
- yes
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
gradleprops: []
init: ''
remove last `maven:` quirks and make it always a string It turns out that the maven: field was originally declared as a TYPE_STRING, given that it was not given a different type in metadata.py's flagtypes. The code was confused because it was given a default value of `False` rather than `None` as the rest of the TYPE_STRING fields have. This construct in build.py means maven: should always be a string: if '@' in build.maven: maven_dir = os.path.join(root_dir, build.maven.split('@', 1)[1]) else: maven_dir = root_dir
2023-04-20 10:09:11 +02:00
maven: null
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
ndk: null
novcheck: false
oldsdkloc: false
output: null
patch: []
Add postbuild
2023-02-16 13:11:26 +01:00
postbuild: ''
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
preassemble: []
prebuild: ''
rm: []
scandelete: []
scanignore: []
srclibs: []
subdir: null
submodules: false
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
sudo:
- echo 'this is just a test'
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
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
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
versionName: '1.5'
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:
category with no apps should be ignored, even if defined in config https://gitlab.com/fdroid/fdroidclient/-/issues/2619#note_1421280589 The test needed to change because the test index files contained category definitions that were not ever used in the "copy tests/repo, generate java/gpg keys, update, and gpgsign" test in tests/run-tests.
2023-06-07 15:57:58 +02:00
- Multimedia
- Security
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
- Time
Changelog: ''
CurrentVersion: '1.5'
make versionCode/build.timeout an integer Co-authored-by: Jochen Sprickerhof <git@jochen.sprickerhof.de>
2022-09-14 03:45:24 +02:00
CurrentVersionCode: 6
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: Activates silent mode during calendar events.
Disabled: null
Donate: null
FlattrID: null
IssueTracker: https://github.com/miguelvps/PoliteDroid/issues
Liberapay: null
License: GPL-3.0-only
Litecoin: null
MaintainerNotes: ''
Name: null
NoSourceSince: '1.5'
OpenCollective: null
Provides: null
Repo: https://github.com/miguelvps/PoliteDroid.git
RepoType: git
RequiresRoot: false
SourceCode: https://github.com/miguelvps/PoliteDroid
Summary: Calendar tool
Translation: ''
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: ''
added: null
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
id: com.politedroid
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/com.politedroid.yml
Copy Permalink