| 24 Oct 2021 |
kranzes | but that's for me to figure out tomorrow | 21:15:58 |
kranzes | Good night! | 21:16:00 |
danielrf | before and after you could run: nix eval -f --arg configuration '{flavor="<flavor>";}' --raw config.buildNumber to use in the commit/tag | 21:17:08 |
danielrf | See also: https://github.com/danielfullmer/robotnix/blob/master/scripts/release-tag.sh | 21:17:20 |
danielrf | thanks, good night! | 21:17:23 |
kranzes | Could either use the add-and-commit workflow or just run it all through git commands | 21:27:13 |
kranzes | Latter is faster | 21:27:22 |
kranzes | Same end result | 21:27:28 |
kranzes | First option looks nicer usually | 21:27:39 |
kranzes | But with those scripts it's kinda simple | 21:27:58 |
danielrf | Btw, rbootnix tags are signed with a GPG key whose key material is on my personal yubikey. So unless there is a way to add signature to an existing tag, that'll still have to take place locally on my machine | 21:30:39 |
danielrf | * Btw, robotnix tags are signed with a GPG key whose key material is on my personal yubikey. So unless there is a way to add signature to an existing tag, that'll still have to take place locally on my machine | 21:30:44 |
kranzes | Hmm | 21:31:44 |
danielrf | but even just having a PR with the output from an auto-update script would be valuable | 21:32:08 |
kranzes | That won't be hard to do, yeah | 21:33:45 |
kranzes | Still need to manually, merge, tag, sign | 21:34:10 |
kranzes | Better than nothing though | 21:34:25 |
danielrf | I also test a build before tagging on each of those flavors | 21:34:50 |
danielrf | The eventual hope would be that we can just do the testing of minor updates automatically through cuttlefish too | 21:35:29 |
kranzes | In reply to @danielrf:matrix.org I also test a build before tagging on each of those flavors So it won't be completely automated either way | 21:36:30 |
kranzes | Unless we do the cuttlefish thing | 21:36:56 |
Yuka (she/her) | In reply to @yuka:yuka.dev GrapheneOS on bramble Everything seems to work fine | 23:04:56 |
Yuka (she/her) | Should microG work? I tested Graphene's sandboxed play services feature once more, but apparently there are still some missing shims for the play services location APIs. | 23:38:16 |
Yuka (she/her) | Also the GrapheneOS matrix channel is a mess | 23:41:20 |
danielrf | Not sure, I'm currently working on testing microg in vanilla and grapheneos now. | 23:42:27 |
Yuka (she/her) | In reply to @yuka:yuka.dev Also the GrapheneOS matrix channel is a mess Just mentioning microG in there will prompt a bunch of people to explain that microG is insecure and shouldn't be used.... lol | 23:42:55 |
Yuka (she/her) | hash mismatch in fixed-output derivation '/nix/store/qln9f0h1sicl6aldrsnn10qxz4w1y6kg-microg-12.patch':
wanted: sha256:0002i64dz4i0i5xv2cz51k08phlkhhg620b06n25bp2x88226m06
got: sha256:1i7vbqk9m3s0l0ilc4db8898kd162f0s1xssnd5vjh87smzq5b26
| 23:44:57 |
danielrf | I did a force push to that branch to fix that | 23:45:50 |
danielrf | Sry | 23:45:52 |
Yuka (she/her) | whoops | 23:45:55 |