| 28 Sep 2025 |
 hexa | and recursing into pkgsRocm was a non-starter | 17:14:39 |
| hexa | but importing it into the existing jobset is absolutely fine with me | 17:15:21 |
 Lun | Is there a point in still having a separate release-rocm.nix then? I could put the generated list of different-for-rocm packages somewhere in rocm-modules and have release.nix's pull those in under packageJobs without needing a new top level release- file | 18:00:15 |
| Lun | * Is there a point in still having a separate release-rocm.nix then? I could put the generated list of different-for-rocm packages somewhere in rocm-modules and have release.nix pull those in under packageJobs without needing a new top level release- file | 18:00:49 |
 Vladimír Čunát | Whatever the way, I assume that we want to filter the jobs for x86_64-linux only, so the approach should support that somehow. (Because other platforms are rarely combined with HW where rocm makes sense?) | 18:17:27 |
 K900 | Technically you can have an AMD GPU in an ARM server | 18:20:53 |
