| 19 Nov 2024 |
 emily | we would really ideally automatically check the contents of those FODs against the previous vendor directory before merging something this risky… a treewide replacement of opaque FOD hashes is one of the most dangerous changes you can make given FOD injection vulnerabilities | 12:23:21 |
| emily | also, formatting in the same commits of a PR this huge is not acceptable | 12:24:01 |
 Ainz Ooal Gown | oof I thought I asked them not to do that | 12:24:56 |
| 21 Nov 2024 |
 zowoq | We've enabled the auto-allocate-uids and use-cgroups features for the linux CI builders, if you encounter any problems with your builds please let me know. | 01:24:16 |
 Mic92 | Nice. This enables systemd-nspawn tests | 10:42:58 |
| 22 Nov 2024 |
|  artemist joined the room. | 07:06:06 |
| 23 Nov 2024 |
|  6t8k removed their profile picture. | 12:17:53 |
| 6t8k set a profile picture. | 12:31:27 |
| 24 Nov 2024 |
|  danjujan joined the room. | 10:32:26 |
| 25 Nov 2024 |
|  @nullcube:matrix.org joined the room. | 10:04:21 |
| 26 Nov 2024 |
|  musicmatze left the room. | 09:15:28 |
|  Emmanuel Genga joined the room. | 19:58:25 |
| Emmanuel Genga | RyanTm upgrade a package I maintain and the ofborg eval fails due to a hash mismatch, how can I update the hash ?
https://logs.ofborg.org/?key=nixos/nixpkgs.359031&attempt_id=23a3f086-e929-4ac2-bc07-66ad2e480f76 | 20:01:07 |
 dish [Fox/It/She] | you would need to update the package yourself and submit a PR to nixpkgs for the update. | 22:26:06 |
| 27 Nov 2024 |
|  Drewry Pope joined the room. | 02:17:35 |
|  Noa joined the room. | 07:29:26 |
| Mic92 | if it works with nix-update, you can maybe define a passthru.updateScript | 18:05:07 |
| Mic92 | there is a nix-update helper function for that. | 18:05:19 |
| emily | I think in this case the tag just got rewritten (so it'd be good if we could diffoscope the two, but I don't know how you get r-ryantm's FODs) | 18:13:48 |
| 18 Dec 2024 |
|  @steeringwheelrules:tchncs.de left the room. | 13:54:02 |
| 27 Nov 2024 |
|  soiledit left the room. | 18:15:04 |
|  jopejoe1 (4094@39c3) changed their display name from jopejoe1 to jopejoe1 [4094]. | 18:18:23 |
 lewo | Hello!
It looks like there is an issue with Hydra declarative jobsets.
The job .jobset/jobset successfully got the JSON from GitLab but the jobset corresponding to the MR has not been created.
Do you know if there are something on Hydra that could explain this behavior? | 20:58:03 |
| lewo | It was still working 2 weeks ago (because the jobset for the MR 346 has been created) | 21:02:36 |
| lewo | We didn't merge anything since 2 months in master so the declarative jobset configuration has not been updated from the repository side. | 21:04:13 |
| lewo | And the Hydra project configuration looks ok. | 21:04:30 |
| lewo | * And the Hydra project configuration looks good. | 21:04:38 |
| lewo | Maybe there is something relevant in the Hydra logs 🤔 | 21:05:17 |
|  Tami joined the room. | 23:40:09 |
| 28 Nov 2024 |
| zowoq | Jobset is working now. I disabled a hydra component that I thought wasn't needed, that caused new MRs from SNM to be ignored. Sorry about that. | 01:21:26 |
