F-Droid Monitor

log for com.bobek.compass:35

== Installed Android Tools ==2026-08-05 16:01:41,092 INFO: Creating log directory2026-08-05 16:01:41,092 INFO: Creating temporary directory2026-08-05 16:01:41,092 INFO: Creating output directory2026-08-05 16:01:41,094 DEBUG: Getting git vcs interface for https://github.com/Kr0oked/Compass.git2026-08-05 16:01:41,094 DEBUG: Checking com.bobek.compass:352026-08-05 16:01:41,094 INFO: Building com.bobek.compass:352026-08-05 16:01:41,095 DEBUG: Popen(['git', 'log', '-n', '1', '--pretty=%ct'], cwd=/home/vagrant/build/com.bobek.compass, stdin=None, shell=False, universal_newlines=False)2026-08-05 16:01:41,097 DEBUG: > sudo passwd --lock rootpasswd: password changed.2026-08-05 16:01:41,598 DEBUG: > sudo SUDO_FORCE_REMOVE=yes dpkg --purge sudo(Reading database ... 48131 files and directories currently installed.)Removing sudo (1.9.16p2-3+deb13u2) ...Purging configuration files for sudo (1.9.16p2-3+deb13u2) ...dpkg: warning: while removing sudo, directory '/etc/sudoers.d' not empty so not removedProcessing triggers for libc-bin (2.41-12+deb13u3) ...2026-08-05 16:01:44,803 INFO: Getting source for revision 086e3a93c429ac71e0934fc6cdbe358d4624a8792026-08-05 16:01:44,803 DEBUG: Directory: build/com.bobek.compass2026-08-05 16:01:44,803 DEBUG: > git rev-parse --show-toplevel2026-08-05 16:01:45,004 DEBUG: Directory: build/com.bobek.compass2026-08-05 16:01:45,004 DEBUG: > git submodule foreach --recursive git reset --hard2026-08-05 16:01:45,105 DEBUG: Directory: build/com.bobek.compass2026-08-05 16:01:45,105 DEBUG: > git reset --hard2026-08-05 16:01:45,406 DEBUG: Directory: build/com.bobek.compass2026-08-05 16:01:45,406 DEBUG: > git submodule foreach --recursive git clean -dffx2026-08-05 16:01:45,507 DEBUG: Directory: build/com.bobek.compass2026-08-05 16:01:45,507 DEBUG: > git clean -dffx2026-08-05 16:01:45,608 DEBUG: Directory: build/com.bobek.compass2026-08-05 16:01:45,608 DEBUG: > git -c core.askpass=/bin/true -c core.sshCommand=/bin/false -c url.https://.insteadOf=ssh:// -c url.https://u:p@bitbucket.org/.insteadOf=git@bitbucket.org: -c url.https://u:p@bitbucket.org.insteadOf=git://bitbucket.org -c url.https://u:p@bitbucket.org.insteadOf=https://bitbucket.org -c url.https://u:p@github.com/.insteadOf=git@github.com: -c url.https://u:p@github.com.insteadOf=git://github.com -c url.https://u:p@github.com.insteadOf=https://github.com -c url.https://u:p@gitlab.com/.insteadOf=git@gitlab.com: -c url.https://u:p@gitlab.com.insteadOf=git://gitlab.com -c url.https://u:p@gitlab.com.insteadOf=https://gitlab.com -c url.https://u:p@codeberg.org/.insteadOf=git@codeberg.org: -c url.https://u:p@codeberg.org.insteadOf=git://codeberg.org -c url.https://u:p@codeberg.org.insteadOf=https://codeberg.org fetch --prune --prune-tags --force origin2026-08-05 16:01:46,108 DEBUG: Directory: build/com.bobek.compass2026-08-05 16:01:46,109 DEBUG: > git -c core.askpass=/bin/true -c core.sshCommand=/bin/false -c url.https://.insteadOf=ssh:// -c url.https://u:p@bitbucket.org/.insteadOf=git@bitbucket.org: -c url.https://u:p@bitbucket.org.insteadOf=git://bitbucket.org -c url.https://u:p@bitbucket.org.insteadOf=https://bitbucket.org -c url.https://u:p@github.com/.insteadOf=git@github.com: -c url.https://u:p@github.com.insteadOf=git://github.com -c url.https://u:p@github.com.insteadOf=https://github.com -c url.https://u:p@gitlab.com/.insteadOf=git@gitlab.com: -c url.https://u:p@gitlab.com.insteadOf=git://gitlab.com -c url.https://u:p@gitlab.com.insteadOf=https://gitlab.com -c url.https://u:p@codeberg.org/.insteadOf=git@codeberg.org: -c url.https://u:p@codeberg.org.insteadOf=git://codeberg.org -c url.https://u:p@codeberg.org.insteadOf=https://codeberg.org fetch --prune --tags --force origin2026-08-05 16:01:46,610 DEBUG: Directory: build/com.bobek.compass2026-08-05 16:01:46,610 DEBUG: > git remote set-head origin --auto2026-08-05 16:01:47,211 DEBUG: Directory: build/com.bobek.compass2026-08-05 16:01:47,212 DEBUG: > git checkout -f 086e3a93c429ac71e0934fc6cdbe358d4624a8792026-08-05 16:01:47,513 DEBUG: Directory: build/com.bobek.compass2026-08-05 16:01:47,513 DEBUG: > git clean -dffx2026-08-05 16:01:47,614 INFO: commit: 086e3a93c429ac71e0934fc6cdbe358d4624a879 (SHA1: 086e3a93c429ac71e0934fc6cdbe358d4624a879)2026-08-05 16:01:47,614 DEBUG: Directory: build/com.bobek.compass2026-08-05 16:01:47,614 DEBUG: > git rev-parse --show-toplevel2026-08-05 16:01:47,815 DEBUG: Directory: build/com.bobek.compass2026-08-05 16:01:47,815 DEBUG: > git submodule deinit --all --force2026-08-05 16:01:47,916 INFO: Creating local.properties file at build/com.bobek.compass/local.properties2026-08-05 16:01:47,917 INFO: Creating local.properties file at build/com.bobek.compass/app/local.properties2026-08-05 16:01:47,920 INFO: Running 'prebuild' commands in build/com.bobek.compass/app2026-08-05 16:01:47,920 DEBUG: Directory: build/com.bobek.compass/app2026-08-05 16:01:47,920 DEBUG: > bash -e -u -o pipefail -x -c -- sed -i -e '/foojay/d' ../settings.gradle.kts; sed -i -e '/JavaLanguageVersion/s/11/21/' build.gradle.kts+ '[' -z '' ']'+ return+ case $- in+ return+ sed -i -e /foojay/d ../settings.gradle.kts+ sed -i -e /JavaLanguageVersion/s/11/21/ build.gradle.kts2026-08-05 16:01:48,125 INFO: Scanning source for common problems...2026-08-05 16:01:48,129 DEBUG: scanner is configured to use signature data from: 'suss'2026-08-05 16:01:48,129 DEBUG: downloading 'https://fdroid.gitlab.io/fdroid-suss/suss.json'2026-08-05 16:01:48,650 DEBUG: write 'suss.json' to cache2026-08-05 16:01:48,650 DEBUG: next suss.json cache update due in 23:59:59.9987622026-08-05 16:01:48,665 INFO: Removing gradle-daemon-jvm.properties at gradle/gradle-daemon-jvm.properties2026-08-05 16:01:48,665 INFO: Removing gradle-wrapper.jar at gradle/wrapper/gradle-wrapper.jar2026-08-05 16:01:48,673 INFO: Creating source tarball...2026-08-05 16:01:49,759 INFO: Building Gradle project...2026-08-05 16:01:49,760 DEBUG: Directory: build/com.bobek.compass/app2026-08-05 16:01:49,760 DEBUG: > /usr/local/bin/gradlew-fdroid assembleReleaseCACHEDIR set to /home/vagrant/.cache/gradlew-fdroidUpdate checksum from gradle-transparency-logFound 9.5.0 via distributionUrlDownloading missing gradle version 9.5.0Using cache directory /home/vagrant/.cache/gradlew-fdroidRunning /home/vagrant/.cache/gradlew-fdroid/versions/9.5.0/bin/gradle assembleReleaseWelcome to Gradle 9.5.0!Here are the highlights of this release:- Task provenance in reports and failure messages- Type-safe accessors for precompiled Kotlin Settings pluginsFor more details see https://docs.gradle.org/9.5.0/release-notes.htmlTo honour the JVM settings for this build a single-use Daemon process will be forked. For more on this, please refer to https://docs.gradle.org/9.5.0/userguide/gradle_daemon.html#sec:disabling_the_daemon in the Gradle documentation.Daemon will be stopped at the end of the buildFound corrupted package.xml at /opt/android-sdk/platforms/android-10/package.xmlException while marshalling /opt/android-sdk/platforms/android-10/package.xml. Probably the SDK is read-onlyFound corrupted package.xml at /opt/android-sdk/platforms/android-11/package.xmlException while marshalling /opt/android-sdk/platforms/android-11/package.xml. Probably the SDK is read-onlyFound corrupted package.xml at /opt/android-sdk/platforms/android-12/package.xmlException while marshalling /opt/android-sdk/platforms/android-12/package.xml. Probably the SDK is read-onlyFound corrupted package.xml at /opt/android-sdk/platforms/android-13/package.xmlException while marshalling /opt/android-sdk/platforms/android-13/package.xml. Probably the SDK is read-onlyFound corrupted package.xml at /opt/android-sdk/platforms/android-10/package.xmlException while marshalling /opt/android-sdk/platforms/android-10/package.xml. Probably the SDK is read-onlyFound corrupted package.xml at /opt/android-sdk/platforms/android-11/package.xmlException while marshalling /opt/android-sdk/platforms/android-11/package.xml. Probably the SDK is read-onlyFound corrupted package.xml at /opt/android-sdk/platforms/android-12/package.xmlException while marshalling /opt/android-sdk/platforms/android-12/package.xml. Probably the SDK is read-onlyFound corrupted package.xml at /opt/android-sdk/platforms/android-13/package.xmlException while marshalling /opt/android-sdk/platforms/android-13/package.xml. Probably the SDK is read-onlyChecking the license for package Android SDK Build-Tools 36 in /opt/android-sdk/licensesLicense for package Android SDK Build-Tools 36 accepted.Preparing "Install Android SDK Build-Tools 36 v.36.0.0"."Install Android SDK Build-Tools 36 v.36.0.0" ready.Installing Android SDK Build-Tools 36 in /opt/android-sdk/build-tools/36.0.0"Install Android SDK Build-Tools 36 v.36.0.0" complete."Install Android SDK Build-Tools 36 v.36.0.0" finished.Checking the license for package Android SDK Platform 37.0 in /opt/android-sdk/licensesLicense for package Android SDK Platform 37.0 accepted.Preparing "Install Android SDK Platform 37.0 (revision 2)"."Install Android SDK Platform 37.0 (revision 2)" ready.Installing Android SDK Platform 37.0 in /opt/android-sdk/platforms/android-37.0"Install Android SDK Platform 37.0 (revision 2)" complete."Install Android SDK Platform 37.0 (revision 2)" finished.Found corrupted package.xml at /opt/android-sdk/platforms/android-10/package.xmlException while marshalling /opt/android-sdk/platforms/android-10/package.xml. Probably the SDK is read-onlyFound corrupted package.xml at /opt/android-sdk/platforms/android-11/package.xmlException while marshalling /opt/android-sdk/platforms/android-11/package.xml. Probably the SDK is read-onlyFound corrupted package.xml at /opt/android-sdk/platforms/android-12/package.xmlException while marshalling /opt/android-sdk/platforms/android-12/package.xml. Probably the SDK is read-onlyFound corrupted package.xml at /opt/android-sdk/platforms/android-13/package.xmlException while marshalling /opt/android-sdk/platforms/android-13/package.xml. Probably the SDK is read-only[=========                              ] 25%                                   
> Task :app:preBuild UP-TO-DATE> Task :app:preReleaseBuild UP-TO-DATE> Task :app:mergeReleaseJniLibFolders> Task :app:mergeReleaseNativeLibs> Task :app:checkReleaseDuplicateClasses> Task :app:stripReleaseDebugSymbolsUnable to strip the following libraries, packaging them as they are: libandroidx.graphics.path.so, libdatastore_shared_counter.so. Run with --info option to learn more.> Task :app:mergeReleaseArtProfile> Task :app:extractReleaseNativeSymbolTables> Task :app:generateReleaseBuildConfig> Task :app:mergeReleaseNativeDebugMetadata NO-SOURCE> Task :app:collectReleaseDependencies> Task :app:releaseOssDependencyTask> Task :app:releaseOssLicensesTask> Task :app:extractReleaseSupportedLocales> Task :app:mapReleaseSourceSetPaths> Task :app:generateReleaseResources> Task :app:generateReleaseLocaleConfig> Task :app:processReleaseNavigationResources> Task :app:packageReleaseResources> Task :app:parseReleaseLocalResources> Task :app:javaPreCompileRelease> Task :app:generateReleaseRFile> Task :app:checkReleaseAarMetadata> Task :app:compileReleaseNavigationResources> Task :app:createReleaseCompatibleScreenManifests> Task :app:extractDeepLinksRelease> Task :app:processReleaseMainManifest> Task :app:processReleaseManifest> Task :app:extractProguardFiles> Task :app:mergeReleaseStartupProfile> Task :app:generateReleaseAssets UP-TO-DATE> Task :app:mergeReleaseResources> Task :app:mergeReleaseAssets> Task :app:compressReleaseAssets> Task :app:extractReleaseVersionControlInfo> Task :app:sdkReleaseDependencyDataVulnerable protobuf generated type in use: com.google.crypto.tink.proto.KeyDataAs of 2022/09/29 (release 21.7) makeExtensionsImmutable should not be called from protobuf gencode. If you are seeing this message, your gencode is vulnerable to a denial of service attack. You should regenerate your code using protobuf 25.6 or later. Use the latest version that meets your needs. However, if you understand the risks and wish to continue with vulnerable gencode, you can set the system property `-Dcom.google.protobuf.use_unsafe_pre22_gencode` on the command line to silence this warning. You also can set `-Dcom.google.protobuf.error_on_unsafe_pre22_gencode` to throw an error instead. See security vulnerability: https://github.com/protocolbuffers/protobuf/security/advisories/GHSA-h4h5-3hr4-j3g2Vulnerable protobuf generated type in use: com.google.crypto.tink.proto.Keyset$KeyAs of 2022/09/29 (release 21.7) makeExtensionsImmutable should not be called from protobuf gencode. If you are seeing this message, your gencode is vulnerable to a denial of service attack. You should regenerate your code using protobuf 25.6 or later. Use the latest version that meets your needs. However, if you understand the risks and wish to continue with vulnerable gencode, you can set the system property `-Dcom.google.protobuf.use_unsafe_pre22_gencode` on the command line to silence this warning. You also can set `-Dcom.google.protobuf.error_on_unsafe_pre22_gencode` to throw an error instead. See security vulnerability: https://github.com/protocolbuffers/protobuf/security/advisories/GHSA-h4h5-3hr4-j3g2Vulnerable protobuf generated type in use: com.google.crypto.tink.proto.KeysetAs of 2022/09/29 (release 21.7) makeExtensionsImmutable should not be called from protobuf gencode. If you are seeing this message, your gencode is vulnerable to a denial of service attack. You should regenerate your code using protobuf 25.6 or later. Use the latest version that meets your needs. However, if you understand the risks and wish to continue with vulnerable gencode, you can set the system property `-Dcom.google.protobuf.use_unsafe_pre22_gencode` on the command line to silence this warning. You also can set `-Dcom.google.protobuf.error_on_unsafe_pre22_gencode` to throw an error instead. See security vulnerability: https://github.com/protocolbuffers/protobuf/security/advisories/GHSA-h4h5-3hr4-j3g2Vulnerable protobuf generated type in use: com.google.crypto.tink.proto.EciesHkdfKemParamsAs of 2022/09/29 (release 21.7) makeExtensionsImmutable should not be called from protobuf gencode. If you are seeing this message, your gencode is vulnerable to a denial of service attack. You should regenerate your code using protobuf 25.6 or later. Use the latest version that meets your needs. However, if you understand the risks and wish to continue with vulnerable gencode, you can set the system property `-Dcom.google.protobuf.use_unsafe_pre22_gencode` on the command line to silence this warning. You also can set `-Dcom.google.protobuf.error_on_unsafe_pre22_gencode` to throw an error instead. See security vulnerability: https://github.com/protocolbuffers/protobuf/security/advisories/GHSA-h4h5-3hr4-j3g2Vulnerable protobuf generated type in use: com.google.crypto.tink.proto.KeyTemplateAs of 2022/09/29 (release 21.7) makeExtensionsImmutable should not be called from protobuf gencode. If you are seeing this message, your gencode is vulnerable to a denial of service attack. You should regenerate your code using protobuf 25.6 or later. Use the latest version that meets your needs. However, if you understand the risks and wish to continue with vulnerable gencode, you can set the system property `-Dcom.google.protobuf.use_unsafe_pre22_gencode` on the command line to silence this warning. You also can set `-Dcom.google.protobuf.error_on_unsafe_pre22_gencode` to throw an error instead. See security vulnerability: https://github.com/protocolbuffers/protobuf/security/advisories/GHSA-h4h5-3hr4-j3g2Vulnerable protobuf generated type in use: com.google.crypto.tink.proto.EciesAeadDemParamsAs of 2022/09/29 (release 21.7) makeExtensionsImmutable should not be called from protobuf gencode. If you are seeing this message, your gencode is vulnerable to a denial of service attack. You should regenerate your code using protobuf 25.6 or later. Use the latest version that meets your needs. However, if you understand the risks and wish to continue with vulnerable gencode, you can set the system property `-Dcom.google.protobuf.use_unsafe_pre22_gencode` on the command line to silence this warning. You also can set `-Dcom.google.protobuf.error_on_unsafe_pre22_gencode` to throw an error instead. See security vulnerability: https://github.com/protocolbuffers/protobuf/security/advisories/GHSA-h4h5-3hr4-j3g2Vulnerable protobuf generated type in use: com.google.crypto.tink.proto.EciesAeadHkdfParamsAs of 2022/09/29 (release 21.7) makeExtensionsImmutable should not be called from protobuf gencode. If you are seeing this message, your gencode is vulnerable to a denial of service attack. You should regenerate your code using protobuf 25.6 or later. Use the latest version that meets your needs. However, if you understand the risks and wish to continue with vulnerable gencode, you can set the system property `-Dcom.google.protobuf.use_unsafe_pre22_gencode` on the command line to silence this warning. You also can set `-Dcom.google.protobuf.error_on_unsafe_pre22_gencode` to throw an error instead. See security vulnerability: https://github.com/protocolbuffers/protobuf/security/advisories/GHSA-h4h5-3hr4-j3g2Vulnerable protobuf generated type in use: com.google.crypto.tink.proto.EciesAeadHkdfPublicKeyAs of 2022/09/29 (release 21.7) makeExtensionsImmutable should not be called from protobuf gencode. If you are seeing this message, your gencode is vulnerable to a denial of service attack. You should regenerate your code using protobuf 25.6 or later. Use the latest version that meets your needs. However, if you understand the risks and wish to continue with vulnerable gencode, you can set the system property `-Dcom.google.protobuf.use_unsafe_pre22_gencode` on the command line to silence this warning. You also can set `-Dcom.google.protobuf.error_on_unsafe_pre22_gencode` to throw an error instead. See security vulnerability: https://github.com/protocolbuffers/protobuf/security/advisories/GHSA-h4h5-3hr4-j3g2Vulnerable protobuf generated type in use: com.google.crypto.tink.proto.AesGcmKeyFormatAs of 2022/09/29 (release 21.7) makeExtensionsImmutable should not be called from protobuf gencode. If you are seeing this message, your gencode is vulnerable to a denial of service attack. You should regenerate your code using protobuf 25.6 or later. Use the latest version that meets your needs. However, if you understand the risks and wish to continue with vulnerable gencode, you can set the system property `-Dcom.google.protobuf.use_unsafe_pre22_gencode` on the command line to silence this warning. You also can set `-Dcom.google.protobuf.error_on_unsafe_pre22_gencode` to throw an error instead. See security vulnerability: https://github.com/protocolbuffers/protobuf/security/advisories/GHSA-h4h5-3hr4-j3g2> Task :app:writeReleaseAppMetadata> Task :app:writeReleaseSigningConfigVersions> Task :app:processReleaseManifestForPackage> Task :app:processReleaseResources> Task :app:kspReleaseKotlin> Task :app:compileReleaseKotlin> Task :app:compileReleaseJavaWithJavac> Task :app:hiltCollectClassesRelease> Task :app:processReleaseJavaRes> Task :app:hiltAggregateDepsRelease> Task :app:mergeReleaseJavaResource> Task :app:hiltJavaCompileRelease> Task :app:transformReleaseClassesWithAsm> Task :app:generateReleaseLintVitalReportModel> Task :app:mergeReleaseGeneratedProguardFiles> Task :app:expandReleaseArtProfileWildcards> Task :app:produceReleaseComposeMapping> Task :app:reportReleaseComposeMappingErrors> Task :app:minifyReleaseWithR8> Task :app:lintVitalAnalyzeRelease> Task :app:mergeReleaseComposeMapping> Task :app:lintVitalReportRelease> Task :app:lintVitalRelease> Task :app:compileReleaseArtProfile> Task :app:convertShrunkResourcesToBinaryRelease> Task :app:optimizeReleaseResources> Task :app:packageRelease> Task :app:createReleaseApkListingFileRedirect> Task :app:assembleReleaseBUILD SUCCESSFUL in 1m 44s59 actionable tasks: 59 executedConsider enabling configuration cache to speed up this build: https://docs.gradle.org/9.5.0/userguide/configuration_cache_enabling.html2026-08-05 16:03:36,884 DEBUG: Checking build/com.bobek.compass/app/build/outputs/apk/release/app-release-unsigned.apk2026-08-05 16:03:36,886 INFO: Successfully built com.bobek.compass:35 from 086e3a93c429ac71e0934fc6cdbe358d4624a8792026-08-05 16:03:36,887 INFO: success: com.bobek.compass2026-08-05 16:03:36,887 INFO: Finished2026-08-05 16:03:36,887 INFO: 1 build succeeded