| 19 May 2021 |
 jochensp | the fdroid update is run in the VM where the source code is prepared, not where the app is build | 12:14:51 |
|  djBRDF left the room. | 12:18:41 |
| djBRDF joined the room. | 12:21:04 |
 linsui | The update VM doesn't reset the source code? | 12:21:54 |
 FestplattenSchnitzel | _hc: Can you create a F-Droid "space" at Matrix? https://element.io/blog/spaces-the-next-frontier/
I'd also appreciate if we could've more rooms for specific topics like fdroidserver, fdroiddata, fdroidclient, … | 12:24:17 |
| jochensp | linsui: what do you mean by reset? | 12:25:52 |
| linsui | A checkout or something else. | 12:26:14 |
 cdesai | FestplattenSchnitzel: +1, that looks useful. | 12:26:17 |
| jochensp | linsui: a checkout is done for a new build, then rm: is done (and I think prebuild:), then the files are left in that state for fdroid update | 12:30:50 |
| linsui | Interesting! So the VM is setup when the build start and all prepare will be kept. Thanks! | 12:36:10 |
 proletarius101 | In reply to @festplattenschnitzel:matrix.org
_hc: Can you create a F-Droid "space" at Matrix? https://element.io/blog/spaces-the-next-frontier/
I'd also appreciate if we could've more rooms for specific topics like fdroidserver, fdroiddata, fdroidclient, … Grouping all fdroid groups into one space, and separating project updates into another channel in the group would be nice | 12:57:56 |
| proletarius101 | * Grouping all fdroid groups into one space, and separating project updates into another channel in the space would be nice | 12:58:30 |
| jochensp | seems like the freenode staff is now serious: https://blog.bofh.it/debian/id_461 | 12:59:42 |
| linsui | How about make an official Magisk module for Privileged Extension? The 3rd party one works well but the author refused to update.
> F-Droid does not seem interested in updating their installer extension, and I will of course update this module when F-Droid updates their extension. | 13:01:24 |
| cdesai | It's not that we're not interesting in updating, it just works | 13:04:31 |
| cdesai | the ota zip needs a maintainer however | 13:04:41 |
| cdesai | An official magisk module could be good as well, I don't see any reason not to do that | 13:05:08 |
| djBRDF left the room. | 13:08:09 |
| linsui | https://github.com/Magisk-Modules-Repo/Fdroid-Priv It's still 0.2.11. But it works well. | 13:10:13 |
| djBRDF joined the room. | 13:11:03 |
| cdesai | we could just build this similar to how the ota zip is currently built | 13:11:08 |
 _hc | jochensp: linsui builds are done in a VM which is thrown away. fdroid update maintains its own copy of the source code, but no operations are done on it except for git checkout basically | 13:13:24 |
| jochensp | _hc: are you sure rm: is not don there? I tried that on the build server | 13:14:11 |
| jochensp | *is not done on the fdroid update server | 13:14:35 |
| djBRDF left the room. | 13:23:43 |
| djBRDF joined the room. | 13:26:30 |
| _hc | jochensp: looks like rm: is run in common.prepare_source() which is only called in fdroid build and fdroid scanner | 13:28:55 |
| djBRDF left the room. | 13:32:12 |
| djBRDF joined the room. | 13:33:06 |
| jochensp | _hc: oups, you are right. thx :) | 13:58:02 |
