| 13 Nov 2023 |
 raitobezarius | as long as we cover a significant amount of issues, I think we did what we could | 14:11:25 |
| raitobezarius | I also unfortunately don't have much time myself as I have too much on my plate in general | 14:11:43 |
| raitobezarius | So my priority is:
(1) ensuring nixpkgs is in a good state
(2) not mindlessly breaking out of tree users
(3) cleaning up this mess post branch off | 14:12:14 |
| raitobezarius | How much we make (2) awesome is function of anyone's contributions here and in the PostgreSQL NixOS community | 14:12:33 |
 bendlas | yeah, maybe best course is to just be as explicit as possible in docu, about the various problems with any of the approaches .. I'll have a look at postgres.md | 14:16:17 |
| raitobezarius | I double checked and currently master didn't introduce new usage of ensurePermissions | 14:17:26 |
| raitobezarius | So I will write release notes | 14:17:29 |
| raitobezarius | And I will run testing in parallel | 14:17:45 |
| raitobezarius | I wish nixpkgs-review could do that | 14:20:34 |
| raitobezarius | well, it breaks on mastodon anyway | 14:25:15 |
| raitobezarius | ok
matrix-sliding-sync
mautrix-facebook
zabbix-(proxy|server)
onlyoffice
tt-rs
hydron
| 14:33:49 |
| raitobezarius | this stuff doesn't possess any test in nixpkgs | 14:33:55 |
| raitobezarius | otherwise everything else should be covered by tests (which uncovered already issues in the PR) | 14:34:12 |
| raitobezarius | I want to cry, people made stupid defaults | 14:43:21 |
| raitobezarius | Mobilizon has a default database of mobilizon_prod, I switch it back to user as a default, this will make all existing deployments explode | 14:43:40 |
| raitobezarius | * Mobilizon has a default database of mobilizon_prod, if I switch it back to user as a default, this will make all existing deployments explode | 14:45:09 |
| bendlas | oof ... so add ensureDatabaseOwners = {}; instead, or switch to mobilizon database name, pending stateVersion == 23.11? | 14:49:59 |
| raitobezarius | I'm trying to evaluate the blast radius | 14:52:35 |
| raitobezarius | And we can think of potential solutions | 14:52:40 |
| raitobezarius | So far, Mobilizon is like this, SourceHut possessā¦ multiple databases | 14:52:54 |
| raitobezarius | (metasrht, buildsrht, gitsrht, etc, etc.) | 14:53:00 |
| raitobezarius | But I think they are operated under the same user | 14:53:06 |
| raitobezarius | OK, that's it in terms of evaluation errors | 14:53:27 |
| raitobezarius | Mobilizon and SourceHut | 14:53:32 |
| raitobezarius | 
Download image.png | 14:53:43 |
| raitobezarius | gro BRRR EPYC | 14:53:44 |
| bendlas | I mean, the cleanest solution would be services.postgresql.ensureDatabases.*.owner, but unfortunately that has also been taken from us, no thanks to ensureDatabases being a list of strings š„² | 14:54:26 |
| raitobezarius | Yep, I think I agree with that | 14:54:41 |
| raitobezarius | This is for 24.05 | 14:54:48 |
| raitobezarius | My only objective here is to minimize the amount of breakages we will have to fix during ZHF | 14:55:03 |
