| 3 May 2022 |
Rick (Mindavi) | What happens if you build it locally? Does it update the file? | 16:08:22 |
@anarres:catgirl.cloud | In reply to @rick:matrix.ciphernetics.nl It sounds like it mismatches with the flake.nix That was my first impulse as well. nix flake update doesn't give me any difference though. | 16:08:43 |
@anarres:catgirl.cloud | In reply to @rick:matrix.ciphernetics.nl What happens if you build it locally? Does it update the file? No, it doesn't change the lock file if run it locally | 16:09:10 |
Rick (Mindavi) | That's all I can think of. Maybe auth issues, but then the error message is bad :) | 16:10:43 |
@anarres:catgirl.cloud | If that's the case then it would in deed be a bad message :) I don't think so though. We're updating the server soon, so maybe it's just a fluke that will resolve itself. Thanks for you help | 16:11:47 |
@anarres:catgirl.cloud | * If that's the case then it would in deed be a bad message :) I don't think so though. We're updating the server soon, so maybe it's just a fluke that will resolve itself. Thanks for your help | 16:11:53 |
tilpner | anarres: desperate guess, but can you run nix flake lock? | 16:34:12 |
tilpner | for a while, the flake resolver needed (needs?) multiple iterations to arrive at a stable state if using lots of follows | 16:34:45 |
@anarres:catgirl.cloud | In reply to @tilpner:tx0.co anarres: desperate guess, but can you run nix flake lock? Unfortunately, I’ve tried this already. No change in behavior | 19:16:13 |
| 4 May 2022 |
| McSinyx joined the room. | 07:08:42 |
| @wybpip:matrix.org joined the room. | 15:01:53 |
| @wybpip:matrix.org left the room. | 15:01:54 |
| 5 May 2022 |
| Simon Adameit joined the room. | 08:23:12 |
| 7 May 2022 |
| nf changed their display name from nf to ncfavier. | 17:29:09 |
| 11 May 2022 |
hexa | for the firefox build on hydra it would be helpful if we could upload debug symbols to symbols.mozilla.org | 20:06:17 |
das_j | → #infra:nixos.org | 20:06:48 |
hexa | not sure, my ask is whether hydra can even do such a thing | 20:07:04 |
hexa | and how it would be specified | 20:07:20 |
das_j | ah. you can just use a RunCommand | 20:07:20 |
hexa | and that's not sandboxed I guess? | 20:07:34 |
das_j | it's ran under the hydra-notify daemon | 20:07:45 |
das_j | * it's run under the hydra-notify daemon | 20:07:48 |
hexa | and probably nothing that can be configured from within nixpkgs, right? | 20:08:08 |
das_j | well | 20:08:13 |
hexa | if nixpkgs would switch to a declarative setup cough | 20:08:23 |
das_j | https://github.com/NixOS/hydra/pull/1103 | 20:08:27 |
das_j | In reply to @hexa:lossy.network if nixpkgs would switch to a declarative setup cough let's do an RFC 🥳 | 20:08:52 |
hexa | oh wow, merged. means as soon as hydra is updated cough I can sign android | 20:10:53 |
hexa | * oh wow, merged. means as soon as hydra is updated cough I can make it sign my android builds … that I'm not yet using | 20:11:03 |
@linus:schreibt.jetzt | In reply to @hexa:lossy.network oh wow, merged. means as soon as hydra is updated cough I can make it sign my android builds … that I'm not yet using Rick (Mindavi) has picked up the work on getting hydra up-to-date in nixpkgs, and some PRs have been merged the past couple of days :) | 21:52:16 |