| 19 May 2021 |
|  djBRDF joined the room. | 08:58:59 |
| djBRDF left the room. | 10:02:24 |
| djBRDF joined the room. | 10:03:27 |
 uniq | _hc: is the verification server okay? It didn't publish any build results for a couple of weeks and I can't login via ssh. | 10:46:43 |
 _hc | uniq: I can ssh to it, so its up. I don't know why it isn't running, probably because it is running in a hacked together buildbot setup ;-). I'm happy to hand over mainteneance to anyone who wants to run it. | 10:52:04 |
| _hc | it could be a plain buildserver setup | 10:54:20 |
 proletarius101 | In reply to @debeule:gnugen.ch
first betas are just UI changes anyway, right? It's May. So the beta is released, which means the feature set is nearly locked | 11:17:05 |
 linsui | Is it possible to move the fastlane when building? E.g. move the fastlane from a flavor to top directory? | 11:34:06 |
|  jochensp joined the room. | 11:38:51 |
| jochensp | linsui: why would that be needed? afair F-Droid doesn't care if it is in a subdir | 11:38:51 |
 FestplattenSchnitzel | jochensp: do you know where this is located in fdroidserver? I could take a look … | 11:42:59 |
| djBRDF left the room. | 11:42:59 |
| jochensp | FestplattenSchnitzel: what exactly? | 11:43:17 |
| djBRDF joined the room. | 11:43:57 |
| FestplattenSchnitzel | Processing fastlane. Or isn't it in fdroidserver? | 11:43:58 |
| jochensp | that's here: https://gitlab.com/fdroid/fdroidserver/-/blob/master/fdroidserver/update.py#L1139 | 11:45:48 |
| linsui | I'm wondering what the process is. The fdroidserver will look for the metadata after building without clean? | 11:46:42 |
| linsui | Then we can also use the fastlane for Jami. | 11:47:17 |
| jochensp | it is in the froid update step, which updates the repo. The sources will be there but not the build data as that is in a separate VM | 11:48:49 |
| linsui | The modified source code will be there until the next update? | 11:52:24 |
| jochensp | what do you mean by "modified source code"? | 11:52:48 |
| linsui | The source code in which the addon directory is removed. | 11:54:10 |
| jochensp | yes | 11:54:38 |
| jochensp | I think build/ is never cleaned up | 11:54:58 |
| linsui | Interesting! So all artifacts are kept there until the next build. | 11:59:07 |
| jochensp | not sure again I understand what you mean by artifacts and next build, the builds are happening in fresh VMs and only the sources transferred to the build VM stays | 12:02:15 |
| linsui | How does the VM filter the source code so that only the modified code will stay there? | 12:06:41 |
| jochensp | what? where? | 12:10:05 |
| jochensp | linsui: what should be filtered and why? | 12:11:30 |
| linsui | Ah, I guess I got what you mean. The source code will be reset in a fresh VM but the update happened in the modified dirty build directory. Am I right? | 12:13:27 |
