| 2 Jun 2021 |
 Jan Tojnar | Did something change regarding the cycle detection? Now I am getting “error: cycle detected in build of … in the references of output 'lib' from output 'jack'” and the output paths for the cyclic outputs are not in the store, not even with --keep-failed | 01:38:50 |
| Jan Tojnar | with stable Nix, the output paths are listed in the error message (so I do not have to fish for them in the build log) and they exist even without --keep-failed | 01:40:46 |
 Alyssa Ross | niksnut: while you're merging Nix PRs, any thoughts on https://github.com/NixOS/nix/pull/4773? :) | 11:35:55 |
 niksnut | Does that work with lowdown? | 11:36:49 |
 sterni (he/him) | niksnut: https://kristaps.bsd.lv/lowdown/lowdown.3.html#LOWDOWN_DEFLIST | 11:37:32 |
| sterni (he/him) | seems like you've already turned it on in libcmd/markdown.cc | 11:38:24 |
| Alyssa Ross | oh, do they end up in a man page? | 11:39:32 |
| sterni (he/him) | Alyssa Ross: :doc on the repl is rendered with lowdown's term rendering target | 11:40:27 |
| Alyssa Ross | ahh | 11:41:38 |
| Alyssa Ross | let me test | 11:41:39 |
| sterni (he/him) | we are in a bit of an unfortunate situation where we render the manuals with pandoc atm, ryantm is implementing the potential next manual renderer using cmark and nix is using lowdown for rendering markdown on the terminal | 11:41:52 |
| sterni (he/him) | cmark is extensible, so lowdown is probably the constraining factor in the equation | 11:42:45 |
| Alyssa Ross | ugh, I don't have the build cached any more | 11:43:00 |
 ryantm | https://github.com/ryantm/mmdoc | 11:44:23 |
| ryantm | https://github.com/NixOS/nixpkgs/pull/108063 | 11:44:27 |
| Alyssa Ross | wow, nice | 11:45:03 |
| Alyssa Ross | niksnut: it doesn't make a difference to :doc, because that doesn't use any of the markup I changed | 11:55:01 |
| Alyssa Ross | I think it just affects the mdbook manual | 11:57:16 |
 Reventlov | Redacted or Malformed Event | 12:30:38 |
| Reventlov | Redacted or Malformed Event | 12:31:17 |
 Regnat | In reply to @rgrunbla:matrix.org
hey Regnat , about https://github.com/NixOS/nix/issues/4859#issuecomment-852980341, how come it was working at some point ? Was that before content addressed nix ? I think that references in CA paths were just ignored before https://github.com/NixOS/nix/commit/0abb3ad53795aa3a4792d30e5721a337f0eddfb7 , so things were kinda-working | 12:34:59 |
| Regnat | (But ignoring the references is actually unsound) | 12:35:14 |
| 4 Jun 2021 |
| Regnat | Eelco Dolstra John Ericson I think I forgot to mention, but I’ll be off on monday, so I won’t join the Nix-CAS weekly | 11:02:42 |
|  rycee joined the room. | 21:44:44 |
| rycee | Howdy. I'm a bit curious, does anybody know if there has been any work done on supporting suid executables natively in Nix? Specifically, how one would do it securely (if at all possible) while still allowing user profiles? | 21:59:00 |
| 6 Jun 2021 |
 Mic92 | In reply to @rycee:rycee.net
Howdy. I'm a bit curious, does anybody know if there has been any work done on supporting suid executables natively in Nix? Specifically, how one would do it securely (if at all possible) while still allowing user profiles? I guess it would require a separate user set of users that are allowed to install setuid binaries and a nix-daemon for sure. To allow creating setuid binaries while building one could employ usernamespaces. After the build the nix-daemon would need to shift uids back. One issue still is that the nix store only knows one uid (0), which does not cover all use cases of setuid. | 07:06:59 |
| Mic92 | To be honest I think the current approach of not having this in nix but external sounds cleaner to me. | 07:07:29 |
| 7 Jun 2021 |
 manveru | is anyone working on a fix for https://github.com/NixOS/nix/issues/4893 ? | 14:33:17 |
 John Ericson | In reply to @joerg:bethselamin.de
To be honest I think the current approach of not having this in nix but external sounds cleaner to me. yeah the design of setuid binaries is pretty ugly to begin with | 14:53:20 |
| Mic92 | For NUR users there is now: #nur:bethselamin.de | 21:29:34 |
