com.matoski.adbm/lastbuild 28

From F-Droid
(Redirected from com.matoski.adbm/lastbuild)
Jump to: navigation, search

Build completed at 2016-01-18 21:25:08Z

'Build.py failed on server for com.matoski.adbm:1.3.1'

detail

INFO: Creating log directory
INFO: Creating temporary directory
INFO: Creating output directory
INFO: Building version 1.3.1 (28) of com.matoski.adbm
INFO: Getting source for revision 1.3.1
INFO: Creating local.properties file at build/com.matoski.adbm/local.properties
INFO: Creating local.properties file at build/com.matoski.adbm/app/local.properties
INFO: Cleaned build.gradle of keysigning configs at build/com.matoski.adbm/app/build.gradle
INFO: Cleaning Gradle project...
INFO: Scanning source for common problems...
INFO: Creating source tarball...
INFO: Building Gradle project...
ERROR: Could not build app com.matoski.adbm: Build failed for com.matoski.adbm:1.3.1
==== detail begin ====
Available gradle versions: 2.10 2.9 2.8 2.7 2.6 2.5 2.4 2.3 2.2.1 2.1 1.12 1.11 1.10 1.9 1.8 1.7 1.6 1.4
Found 2.2.1 via gradle plugin version 1.1
:app:preBuild UP-TO-DATE
:app:preReleaseBuild UP-TO-DATE
:app:checkReleaseManifest
:app:preDebugBuild UP-TO-DATE
:app:prepareComAndroidSupportSupportV42103Library
:app:prepareReleaseDependencies
:app:compileReleaseAidl
:app:compileReleaseRenderscript
:app:generateReleaseBuildConfig
:app:generateReleaseAssets UP-TO-DATE
:app:mergeReleaseAssets
:app:generateReleaseResValues
:app:generateReleaseResources
:app:mergeReleaseResources
AAPT warning(Job{title=Cruncher ic_action_refresh.png, latch=BooleanLatch{signaled=false}, result=false}): /home/vagrant/build/com.matoski.adbm/app/src/main/res/drawable-xhdpi/ic_action_refresh.png: libpng warning: iCCP: Not recognizing known sRGB profile that has been edited
AAPT warning(Job{title=Cruncher ic_action_refresh.png, latch=BooleanLatch{signaled=false}, result=false}): /home/vagrant/build/com.matoski.adbm/app/src/main/res/drawable-mdpi/ic_action_refresh.png: libpng warning: iCCP: Not recognizing known sRGB profile that has been edited
AAPT warning(Job{title=Cruncher ic_action_refresh.png, latch=BooleanLatch{signaled=false}, result=false}): /home/vagrant/build/com.matoski.adbm/app/src/main/res/drawable-hdpi/ic_action_refresh.png: libpng warning: iCCP: Not recognizing known sRGB profile that has been edited
:app:processReleaseManifest
:app:processReleaseResources
:app:generateReleaseSources
:app:compileReleaseJavaNote: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.

:app:lintVitalRelease/home/vagrant/build/com.matoski.adbm/app/src/main/res/values/strings.xml:120: Error: "quit" is not translated in "en" (English), "es" (Spanish), "ja" (Japanese), "mk" (Macedonian), "zh" (Chinese) [MissingTranslation]
  <string name="quit">Quit</string>
          ~~~~~~~~~~~

   Explanation for issues of type "MissingTranslation":
   If an application has more than one locale, then all the strings declared
   in one language should also be translated in all other languages.

   If the string should not be translated, you can add the attribute
   translatable="false" on the <string> element, or you can define all your
   non-translatable strings in a resource file called donottranslate.xml. Or,
   you can ignore the issue with a tools:ignore="MissingTranslation"
   attribute.

   By default this detector allows regions of a language to just provide a
   subset of the strings and fall back to the standard language strings. You
   can require all regions to provide a full translation by setting the
   environment variable ANDROID_LINT_COMPLETE_REGIONS.

   You can tell lint (and other tools) which language is the default language
   in your res/values/ folder by specifying tools:locale="languageCode" for
   the root <resources> element in your resource file. (The tools prefix
   refers to the namespace declaration http://schemas.android.com/tools.)

1 errors, 0 warnings
 FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:lintVitalRelease'.
> Lint found fatal errors while assembling a release target.
  
  To proceed, either fix the issues identified by lint, or modify your build script as follows:
  ...
  android {
      lintOptions {
          checkReleaseBuilds false
          // Or, if you prefer, you can continue to check for errors in release builds,
          // but continue the build even when errors are found:
          abortOnError false
      }
  }
  ...

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Total time: 37.827 secs
==== detail end ====