| 25 Jul 2020 |
|  avril left the room. | 03:19:18 |
|  wb9688 left the room. | 03:19:18 |
|  guerby left the room. | 03:19:19 |
| wb9688 joined the room. | 06:45:53 |
| wb9688 | kitsunyan: Oh, I didn't see that, but why is it doing that? | 06:45:53 |
|  cdesai joined the room. | 08:58:48 |
| cdesai | It is unfortunately a long standing issue and AFAIK we don't exactly know why | 08:58:49 |
| wb9688 | It seems to have built some apps in the current build cycle, but after 10:46 it started failing for all apps (including NewPipe) :/ | 14:37:57 |
 kitsunyan | 2 weeks ago there were cases when packages were actually built, but only ~50% of them are deployed. | 15:17:30 |
| kitsunyan | And next build cycle they were re-built again, but failed with "could not bring up vm" error :D | 15:18:02 |
| kitsunyan | So I have to wait about 10 days or so. | 15:18:34 |
| kitsunyan |
It is unfortunately a long standing issue and AFAIK we don't exactly know why
Is it possible to add some logging of these incidents? It happens too often.
| 15:21:21 |
 fynngodau | Bubu: Remember when I was wondering how to find accounts that were registered with a device via adb? My demo implementation of enabling privextension as a device admin (via adb locally) then froze
all apps that are capable of providing any account and thus [didn't] require "contact" permission
I now know this is possible with adb shell dumpsys account! Data in there looks very much like that returned by the AccountManager API
| 21:48:24 |
| 26 Jul 2020 |
|  Tobiwan joined the room. | 12:34:45 |
| Tobiwan | Hi, I'm the maintainer of FFUpdater https://f-droid.org/en/packages/de.marmaro.krt.ffupdater/ and I've got trouble to deploy my updated application to F-Droid. | 12:34:45 |
| Tobiwan | The "Build Log" (https://f-droid.org/wiki/page/de.marmaro.krt.ffupdater/lastbuild_47) says "could not bring up vm 'builder_default'" for quite a time. Is there anything I can do to fix this error? | 12:34:45 |
| wb9688 | Tobiwan: Nope, that's a F-Droid bug that sometimes happens for random apps | 12:37:16 |
| Tobiwan | ok | 12:38:24 |
| Tobiwan | thanks for the fast answer :) | 12:38:29 |
 Bubu | In reply to @fynngodau:disroot.org
Bubu: Remember when I was wondering how to find accounts that were registered with a device via adb? My demo implementation of enabling privextension as a device admin (via adb locally) then froze
all apps that are capable of providing any account and thus [didn't] require "contact" permission
I now know this is possible with adb shell dumpsys account! Data in there looks very much like that returned by the AccountManager API
Oh, interesting. | 16:28:26 |
|  vancz joined the room. | 19:55:47 |
| vancz | Hi folks, is there a dashboard for current build status or something? | 19:55:47 |
| vancz | or otherwise a list of infrastructure? | 19:56:18 |
| wb9688 | https://f-droid.org/wiki/index.php?title=Special:RecentChanges&days=30&from=&hidebots=0&limit=500, but that'll be gone soon and there's some JSON API that I don't remember the URL of | 19:57:00 |
| wb9688 | Or is that not what you meant with 'current build status'? | 19:57:22 |
| vancz | err yeah i wasnt really clear, like if I want to see how close an app update is to getting in | 19:57:54 |
| vancz | oh wow a wiki heh, kind of a weird way to do that but sure why not | 19:58:47 |
| wb9688 | vancz: That's for the build status and at https://gitlab.com/fdroid/fdroiddata/-/commits/master/ you could see if an update has been picked up | 20:00:34 |
| wb9688 | Or at the specific app's file e.g. https://gitlab.com/fdroid/fdroiddata/-/blob/master/metadata/org.schabi.newpipe.yml | 20:01:27 |
| vancz | hm, ok cool so its in https://gitlab.com/fdroid/fdroiddata/-/commit/d8fbd5063118bc8fa469d4a868304661b4cd14cf | 20:02:23 |
