| 20 May 2026 |
dramforever | okay i read the actual man page and you can do the double userns dance with
unshare --map-root-user --pid --fork --load-interp ":py:E::py::$(which python3):" unshare --map-user "$(id -u)" --map-group "$(id -g)" bash | 15:38:02 |
dramforever | * okay i read the actual man page and you can do the double userns dance with something like
unshare --map-root-user --pid --fork --load-interp ":py:E::py::$(which python3):" unshare --map-user "$(id -u)" --map-group "$(id -g)" bash | 15:38:13 |
dramforever | make of that what you will | 15:41:57 |
| 21 May 2026 |
| rajudev joined the room. | 00:00:26 |
| inifynastic joined the room. | 03:48:01 |
| goatedxchef joined the room. | 19:38:00 |
| 22 May 2026 |
| DJ2BD joined the room. | 13:02:40 |
| Benedek joined the room. | 14:48:13 |
| Jon Hermansen changed their display name from jonhermansen to Jon Hermansen. | 19:18:39 |
| 23 May 2026 |
eveeifyeve | Has anyone considered a pr to flake registries to make them just an array of objects that contain owner repo and type? | 00:48:52 |
eveeifyeve | * Has anyone considered a pr to flake registries to make them just an array of objects that contain owner, repo and type instead of what we have currently? | 00:49:13 |
eveeifyeve | * Has anyone considered a pr to flake registries to make them just an array of objects that contain owner, repo and type instead of what we have currently, which IMO seems to deduplicate a lot of inputs? | 00:49:46 |
eveeifyeve | * Has anyone considered a pr to flake registries to make them just an array of objects that contain owner, repo and type instead of what we have currently? Which IMO seems to deduplicate a lot of inputs that doesn't be needed? | 00:50:06 |
eveeifyeve | * Has anyone considered a pr to flake registries to make them just an array of objects that contain owner, repo and type instead of what we have currently? Which IMO seems to deduplicate a lot of inputs that doesn't be needed. | 00:50:08 |
eveeifyeve | * Has anyone considered a pr to flake registries to make them just an array of objects that contain owner, repo and type instead of what we have currently? Which IMO seems to deduplicate a lot of inputs that doesn't be needed like the to and from. | 00:51:27 |
eveeifyeve | Like if there is no two and from, it should automatically assume that it is the to and from. | 00:53:47 |
| Yingchi Long changed their profile picture. | 11:24:21 |
| mtmn joined the room. | 15:21:13 |
| 26 May 2026 |
| phanirithvij changed their display name from loudgolem to phanirithvij. | 11:40:47 |
| Matt Sturgeon joined the room. | 16:33:14 |
Matt Sturgeon | Sorry to cross-post, and if this is off-topic.
I'm just wondering if anyone here is able to answer my question re unsafeDiscardStringContext vs unsafeDiscardOutputDependency (and the unsafeDiscardReferences attr) in the "nix language" room?
I'm unclear on the differences, when one might choose one over the other, whether they avoid building the (un)referenced derivation, etc.
https://matrix.to/#/!tDnwWRNkmmYtMXfaZl:nixos.org/$7ed1ckmSXBR3mQyk0RXYkXZM40_Thyd_4pVtBq1S4aw?via=nixos.org&via=matrix.org&via=tchncs.de
| 17:01:30 |
infinisil | (i gave an answer here: https://matrix.to/#/!tDnwWRNkmmYtMXfaZl:nixos.org/$KN92sh9o3hqm0lXJbwSKglFbi1PheX5brIZnKcGDf6s?via=matrix.org&via=tchncs.de&via=catgirl.cloud) | 21:15:09 |
| 27 May 2026 |
| @aangularframework:matrix.org left the room. | 03:35:32 |
| デニズさん joined the room. | 14:01:33 |
| arias 🏳️⚧️ joined the room. | 18:54:20 |
| isabel changed their profile picture. | 21:16:57 |
| 28 May 2026 |
| Akshay Sachdeva set a profile picture. | 05:30:27 |
| 29 May 2026 |
| lassulus changed their profile picture. | 07:06:29 |
| 31 May 2026 |
| Aliaksandr set a profile picture. | 00:30:59 |
| 1 Jun 2026 |
| Tanja (she/her) 📞 TNJA (8652) changed their display name from Tanja (she/her) to Tanja (she/her) 📞 TNJA (8652). | 15:31:39 |