Zen

Translation

English type: Plain text
When making automated binary repositories with `fdroid update`, it is generally easy to find out the expected signing key for the APKs that are gathered. `AllowedAPKSigningKeys` lets the repo operator set the expected signing keys, then `fdroid update` will check that the APKs are signed by one of those keys. If not, the mismatched APKs will not be included in the repo. If `fdroid update --delete-unknown` is specified, the mismatched APKs will be deleted. Then an automated process can be used to download newer APKs to the repo, and they will only be included if they have a known good signature. The value is a lowercase hex value of the SHA-256 fingerprint of the signing certificate. This can be fetched using:
0/7240 · 724

Sign in to save the translation.

English Spanish Actions
`novcheck: true`<a name="build_novcheck"></a>
 
: Don't check that the version name and code in the resulting APK are
correct by looking at the build output - assume the metadata
is correct. This takes away a useful level of sanity checking, and
should only be used if the values can't be extracted.
 
`antifeatures: <antifeature1>[,<antifeature2>,...]`<a name="build_antifeatures"></a>
 
: List of Anti-Features for this specific build. They are described
in [_AntiFeatures_](#AntiFeatures).
 
_AllowedAPKSigningKeys_<a name="AllowedAPKSigningKeys"></a>
 
When making automated binary repositories with `fdroid update`, it is generally easy to find out the expected signing key for the APKs that are gathered. `AllowedAPKSigningKeys` lets the repo operator set the expected signing keys, then `fdroid update` will check that the APKs are signed by one of those keys. If not, the mismatched APKs will not be included in the repo. If `fdroid update --delete-unknown` is specified, the mismatched APKs will be deleted. Then an automated process can be used to download newer APKs to the repo, and they will only be included if they have a known good signature. The value is a lowercase hex value of the SHA-256 fingerprint of the signing certificate. This can be fetched using:
 
apksigner verify --print-certs example.apk | grep SHA-256
 
_AntiFeatures_<a name="AntiFeatures"></a>
Binarios<a name="Binaries"></a>
This is optional - if present, it contains a comma-separated list of any of the following values, describing an anti-feature the application has. It is a good idea to mention the reasons for the anti-feature(s) in the description:
Esto es opcional - si está presente, contiene una lista separada por comas de cualquiera de los siguientes valores, describiendo una anti-característica que la aplicación tenga. Es una buena idea mencionar las razones de la(s) anti-característica(s) en la descripción:
'Ads' - the application contains advertising.
'Anuncios' - la aplicación contiene anuncios.
'Tracking' - user or activity data is tracked or leaks, by default. True if the app or a feature can not be used without collecting and sharing such data, or doing requests to a data collecting network service (regard- less if the service is based on free software, or not). For example, activity-based down-loading of weather data, maps, avatars etc. (data hosting and delivery services), or uploading of crash logs etc.
'Tracking' - el usuario o la actividad se rastrea o filtra, por defecto. Verdadero si la aplicación o una característica no se puede utilizar y recolectar esos datos, o hacer peticiones a un red de recogida de datos (independientemente de si el servicio se basa en software libre o no). Por ejemplo, descarga de datos meteorológicos basados en la actividad, mapas, avatares, etc. (servicios de alojamiento y envío de datos), o subida de registros de errores etc.

Loading…

User avatar delthia

Translation changed

  1. F-Droid
  2. Website Docs
  3. Spanish
When making automated binary repositories with `fdroid update`, it is generally easy to find out the expected signing key for the APKs that are gathered. `AllowedAPKSigningKeys` lets the repo operator set the expected signing keys, then `fdroid update` will check that the APKs are signed by one of those keys. If not, the mismatched APKs will not be included in the repo. If `fdroid update --delete-unknown` is specified, the mismatched APKs will be deleted. Then an automated process can be used to download newer APKs to the repo, and they will only be included if they have a known good signature. The value is a lowercase hex value of the SHA-256 fingerprint of the signing certificate. This can be fetched using:
Cuando se hacen repositorios de binarios automatizados con `fdroid update`, generalm
a year ago
User avatar delthia

Translation added

  1. F-Droid
  2. Website Docs
  3. Spanish
When making automated binary repositories with `fdroid update`, it is generally easy to find out the expected signing key for the APKs that are gathered. `AllowedAPKSigningKeys` lets the repo operator set the expected signing keys, then `fdroid update` will check that the APKs are signed by one of those keys. If not, the mismatched APKs will not be included in the repo. If `fdroid update --delete-unknown` is specified, the mismatched APKs will be deleted. Then an automated process can be used to download newer APKs to the repo, and they will only be included if they have a known good signature. The value is a lowercase hex value of the SHA-256 fingerprint of the signing certificate. This can be fetched using:
Cuando se hacen repositorios de binarios automatizados con `fdroid update`, generalm
a year ago
Browse all string changes

Things to check

Has been translated

Previous translation was "Cuando se hacen repositorios de binarios automatizados con `fdroid update`, generalm".

Fix string

Reset

Glossary

English Spanish
download descarga F-Droid Glossary
Repo Repositorio F-Droid Glossary
Repo Repositorio F-Droid Glossary

Lietotņu glabātava.
Update Actualizar F-Droid Glossary

String information

Source string description
type: Plain text
Flags
md-text
Source string location
_docs/Build_Metadata_Reference.md
String age
2 years ago
Last updated
11 months ago
Source string age
2 years ago
Translation file
po/_docs.es.po, string 557