27 Apr 2021 |
_hc | I agree that's something we need to improve on, but I don't have a clear idea of the issues and possible pitfalls. maybe that's something we could discuss at the meeting? I know uniq has thought about that area of the processs more than I | 11:48:50 |
_hc | he implemented the build log support, for example | 11:48:59 |
_hc | that would change the conception of how the repo files are managed | 11:49:31 |
_hc | since the beginning, disabled: removed all the files for that entry | 11:49:52 |
_hc | AFAIK | 11:50:01 |
_hc | its also been used as a way to remove everything related to a release | 11:50:40 |
_hc | honestly, that seems like something better solved by moving to buildbot, it would give us that for free | 11:51:14 |
_hc | and more | 11:51:34 |
proletarius101 | I see at least one VM that I *think* is assigned to fdroid. Can I ask you to check in and confirm there is not any disconnect on your side? It's also possible I guess that we've had requests from more than one project of the same name but I don't see any pending application for fdroid. After submitting an application the ticketing system should have sent an email including the ticket # for the hosting application. That would be very | 11:52:34 |
proletarius101 | _hc: | 11:52:44 |
proletarius101 | I think we missed something (with FOSSHost)? | 11:53:00 |
_hc | jochensp: The buildbot prototype I set up on verification proved to me that it is possible to move to buildbot incrementally, so I'm much rather see us moving in that direction than adding hacks to core logic. | 11:53:54 |
jochensp | _hc: agreed | 11:55:21 |
_hc | proletarius101: you should join #freenode_#fosshost-special-project:matrix.org if you're planning on tracking the fosshost stuff. Its a room just for getting fdroid setup there | 11:55:54 |
_hc | very low traffice | 11:56:04 |
proletarius101 | Well, the above message is from @mplsCorwin, who I think is a member of fosshost? | 11:57:32 |
proletarius101 | Or maybe it's in a different procedure? | 11:58:14 |
_hc | when I first requested hosting from them, they setup that IRC room and that's the only place so far where the CDN stuff has been discussed | 12:02:51 |
_hc | proletarius101: did you still want to set up the docker-based buildserver? That would be great to have for verification.f-droid.org and for local developer builds | 12:12:41 |
_hc | I can hand over a fosshost VM to dedicate to that | 12:13:04 |
proletarius101 | In reply to @eighthave:matrix.org proletarius101: did you still want to set up the docker-based buildserver? That would be great to have for verification.f-droid.org and for local developer builds Yes | 12:26:27 |
proletarius101 | You mean containerize them too? | 12:26:39 |
proletarius101 | The build server itself is already in a container? | 12:27:15 |
_hc | yeah, like getting vagrant to build docker containers just like the buildserver VM, then making it possible to run builds in it using fdroid build | 12:27:25 |
_hc | you could either use vagrant's docker support, or just make a Dockerfile that calls the provisioning scripts in fdroidsrver/buildserver/ | 12:28:08 |
proletarius101 | Sure. Containerization is definitely what I'm looking forward to and capable of doing | 12:28:14 |
proletarius101 | In reply to @eighthave:matrix.org you could either use vagrant's docker support, or just make a Dockerfile that calls the provisioning scripts in fdroidsrver/buildserver/ Probably a dockerfile which is more standard | 12:28:35 |
_hc | vagrant is more standard for fdroid, FWIW | 12:30:12 |
_hc | but I'm fine with either approach | 12:30:24 |
| * jochensp always thinks Debian packages should be standard (and are, kind of) | 12:30:42 |