!RROtHmAaQIkiJzJZZE:nixos.org

NixOS Infrastructure

386 Members
Next Infra call: 2024-07-11, 18:00 CEST (UTC+2) | Infra operational issues backlog: https://github.com/orgs/NixOS/projects/52 | See #infra-alerts:nixos.org for real time alerts from Prometheus.120 Servers

Load older messages


SenderMessageTime
24 Sep 2025
@wolfgangwalther:matrix.org@wolfgangwalther:matrix.org And freescout would access the account through the loginAccount given in infra, I guess. 18:26:40
@hexa:lossy.networkhexaalso, I'd suggest keeping it simple and go for nixpkgs@nixos.org maybe18:26:51
@hexa:lossy.networkhexa* also, I'd suggest keeping it simple and go for nixpkgs@nixos.org instead18:27:08
@wolfgangwalther:matrix.org@wolfgangwalther:matrix.org And, can we get notifications directly via freescout, too? Or do we essentially need to add all of us as forwarders as well? 18:27:34
@hexa:lossy.networkhexaNo idea.18:27:52
@winter:catgirl.cloudWinteryou can get notifs18:27:54
@winter:catgirl.cloudWinterno forwarding needed18:28:01
25 Sep 2025
@lt1379:matrix.orgLun Can someone please update #ROCm:nixos.org 's title to be NixOS ROCm to match #cuda:nixos.org ? 23:23:58
@hexa:lossy.networkhexanot ours, moderation managesthat23:35:18
@hexa:lossy.networkhexa* not ours, moderation manages that23:35:20
@hexa:lossy.networkhexa #matrix-suggestions:nixos.org 23:36:02
26 Sep 2025
@joerg:thalheim.ioMic92https://github.com/NixOS/nixos-wiki-infra/pull/310 Hacked some wikimedia extension together that should allow us to put the wiki behind fastly15:49:59
@dgrig:erethon.comdgrighttps://github.com/NixOS/nixpkgs/pull/446387 if anyone wants to review the package and module for https://github.com/NixOS/infra/issues/85316:08:26
@pyrox:pyrox.devdish [Fox/It/She]looks good to me, added to merge queue19:10:58
27 Sep 2025
@7c6f434c:nitro.chat7c6f434c joined the room.08:48:00
28 Sep 2025
@vuks:matrix.orgVuks joined the room.12:26:30
@hexa:lossy.networkhexa was talking with Lun yesterday about building rocm flavored packages on h.n.o 14:22:41
@hexa:lossy.networkhexaand the best idea we could come up with is a dedicated jobset release-rocm.nix with a list like release-cuda.nix, that is generated from comparing an eval with rocmSupport and one without it14:23:28
@hexa:lossy.networkhexathat list is too expensive to generate on every eval, but that is also not really required, it can gradually be adapted to what is needed14:24:02
@hexa:lossy.networkhexathe implication is that -rocm flavored package attributes can be removed in favor of config.rocmSupport or foobar.override { rocmSupport = true; }14:24:35
@hexa:lossy.networkhexa* the implication is that -rocm flavored package attributes can be removed in favor of just toggling config.rocmSupport or foobar.override { rocmSupport = true; }14:24:44
@hexa:lossy.networkhexa * the implication is that -rocm flavored package attributes can be removed in favor of just toggling config.rocmSupport or foobar.override { rocmSupport = true; } 14:24:53
@hexa:lossy.networkhexa so the idea is unstable-rocm, release-25.11-rocm 14:25:09
@vcunat:matrix.orgVladimír ČunátWhy will these be split away? Less build shares and/or frequency of evals?14:28:07
@hexa:lossy.networkhexawe can also integrate them in the main jobset 🤔14:46:37
@hexa:lossy.networkhexa* we can also integrate them in the main jobset 🤔 i was just not sure how to accomplish that14:46:45
@hexa:lossy.networkhexabecause we currently eval nixpkgs once with rocmSupport = false14:46:52
@hexa:lossy.networkhexaand they only have pkgsRocm and aliases with overrides that enable it14:47:25
@hexa:lossy.networkhexahttps://github.com/LunNova/nixpkgs/blob/push-kuknstozqsvo/pkgs/top-level/release-rocm.nix14:48:37
@vcunat:matrix.orgVladimír Čunát Plug in pkgsRocm attribute-subtree? Probably by adding the reference in our pkgs/top-level/release.nix 14:58:22

Show newer messages


Back to Room ListRoom Version: 6