| 3 Dec 2025 |
 Qyriad | Yeah and imho a long term goal is to entirely yeet the installer and replace it with a single statically linked lix binary, and lix will just be capable of bootstrapping itself | 20:03:23 |
 aloisw | firebird-static-x86_64-unknown-linux-musl> checking for /proc/self/maps... configure: error: cannot check for file existence when cross compiling
Not that Firebird gets a lot further… | 20:03:54 |
 raitobezarius | i dreamed of shipping pg but i think it's unrealistic yeah | 20:14:09 |
 Jassuko | There is beauty in storing package manager data in flat files. I’ve needed to touch APT ”database” quite some times when things have gone bad.
SQLite would be still within a scope of somewhat fixable in weird situations, but depending on psql or some full server suite software… uhhh -_- | 20:22:26 |
| Jassuko | Idea of using psql burns down as soon as you need to ever bump the major version forward. The migration hell and backwards incompatibility will bite instantly on package manager -like use case. | 20:24:42 |
| Jassuko | Current SQLite on the other hand can probably read 20 years old DB files just fine. | 20:25:36 |
| Jassuko | Oh. Actually read and write.. and up to 21 years old files. :D
Newer versions of SQLite can always read and/or write database files created by older versions of SQLite, back to version 3.0.0 (2004-06-18).
| 20:28:38 |
| raitobezarius | yeah that's good except that the lifetime of my SQLite DB is usually <1y before it corrupts itself: D | 21:00:31 |
 piegames | How does Lix Buildkite work? What Buildkite plan are we using? | 21:05:04 |
| piegames | Also, can buildkite be used from Forgejo actions directly? | 21:05:23 |
| raitobezarius | Lix Buildkite works via git hooks that are set on Gerrit, on a global level | 21:16:27 |
| raitobezarius | Once a patchset is created or a patchset is merged, a Go program is called who will POST to Buildkite to start a build on a certain ref | 21:16:41 |
| raitobezarius | We have the "special" open source plan | 21:16:53 |
| raitobezarius | The pipeline for the job is a simple nix run lix#ci-config which calls a calculate-buildkite-steps.py script which emits dynamic JSON that expands the graph of builds as we n-e-j them | 21:17:38 |
| raitobezarius | Theoretically yes, there was an AFNix infra task to get this working, but I didn't have to finish it for lanzaboote in the end | 21:18:19 |
| raitobezarius | 
Download clipboard.png | 21:18:38 |
| raitobezarius | that's the exact Lix plan | 21:18:41 |
| raitobezarius | ah Forgejo actions you said | 21:19:09 |
| raitobezarius | that's a pretty weird thing to do to call Buildkite from there, but I don't see any reason why not | 21:19:25 |
| piegames | Then what is the business model of Buildkite? Because gerrit users probably don't abound | 21:32:04 |
| raitobezarius | the business model of buildkite is selling you hosted CI minutes and various features surrounding the control plane | 21:32:29 |
| raitobezarius | what is your fundamental question? | 21:32:57 |
| piegames | I'm just curious | 21:35:03 |
| raitobezarius | I see | 21:35:13 |
| raitobezarius | TLDR Buildkite is the most advanced public CI system that exist and is probably earning a shit ton of money via enterprise contracts with very large monorepos out there IMHO | 21:35:33 |
| Qyriad | it's a shame to not use our own infra but man does it work a hell of a lot better than buildbot ever did | 22:36:50 |
 just1602 | Yeah, buildbot looks nice in theory, but in practice it looked rough | 23:27:25 |
| 4 Dec 2025 |
| raitobezarius | this is being fixed | 01:32:51 |
| raitobezarius | but slowly :D | 01:33:04 |
| aloisw | In reply to @raitobezarius:matrix.org
yeah that's good except that the lifetime of my SQLite DB is usually <1y before it corrupts itself: D Is it because of SQLite bugs, or because you're doing something weird to it? | 05:49:14 |
