APKUpdater: Remove non-validating builds
This commit is contained in:
parent
4edf566b78
commit
af68515a4b
|
@ -29,11 +29,13 @@ Build:1.3.2,2
|
||||||
gradle=yes
|
gradle=yes
|
||||||
|
|
||||||
Build:1.3.4,4
|
Build:1.3.4,4
|
||||||
|
disable=does not validate
|
||||||
commit=1.3.4
|
commit=1.3.4
|
||||||
subdir=app
|
subdir=app
|
||||||
gradle=yes
|
gradle=yes
|
||||||
|
|
||||||
Build:1.3.6,6
|
Build:1.3.6,6
|
||||||
|
disable=does not validate
|
||||||
commit=1.3.6
|
commit=1.3.6
|
||||||
subdir=app
|
subdir=app
|
||||||
gradle=yes
|
gradle=yes
|
||||||
|
@ -44,11 +46,7 @@ Build:1.3.7,7
|
||||||
gradle=yes
|
gradle=yes
|
||||||
|
|
||||||
Maintainer Notes:
|
Maintainer Notes:
|
||||||
Reproducible builds will most likely fail, since we have to
|
See https://github.com/rumboalla/apkupdater/issues/33 for reproducibility issues.
|
||||||
build from a non-tagged commit... but i wonder how upstream
|
|
||||||
should have managed to build without that. Lets try and try
|
|
||||||
again on failure with the next release. If this still does
|
|
||||||
not work: Talk to upstream about possible solutions.
|
|
||||||
.
|
.
|
||||||
|
|
||||||
Auto Update Mode:None
|
Auto Update Mode:None
|
||||||
|
|
Loading…
Reference in a new issue