| 31 May 2021 |
 Regnat | (Well, if you use NIX_REMOTE the symlinks will be broken because Nix will run in a different mount namespace) | 10:34:16 |
 Reventlov | Redacted or Malformed Event | 10:34:19 |
| Regnat | I have to go for lunch, let me know once it’s done | 10:35:00 |
| Reventlov | Redacted or Malformed Event | 12:00:20 |
| Reventlov | Redacted or Malformed Event | 13:01:49 |
| Reventlov | Redacted or Malformed Event | 13:02:14 |
| Reventlov | Redacted or Malformed Event | 13:08:40 |
 infinisil | I've got a Nix PR that I think is ready to be merged: https://github.com/NixOS/nix/pull/4790 | 17:12:26 |
| 1 Jun 2021 |
|  [0x4A6F] changed their display name from 0x4A6F to [0x4A6F]. | 06:36:27 |
| Reventlov | Redacted or Malformed Event | 07:23:31 |
| Reventlov | Redacted or Malformed Event | 07:23:48 |
| Regnat | In reply to @rgrunbla:matrix.org
hey Regnat , the CA experimental features actually fix the compilation, but it does not really work when you use it as the input for another flakes, e.g https://0x0.st/-2Ic.txt Yes, as I said, this isn’t really supposed to work 🙃 | 07:24:53 |
| Reventlov | Redacted or Malformed Event | 07:25:02 |
| Regnat | I’m not sure why you need hello to be a fixed-output derivation tbh | 07:25:31 |
| Reventlov | Redacted or Malformed Event | 07:25:59 |
| Reventlov | Redacted or Malformed Event | 07:26:47 |
| Regnat | Ugh that’s ugly ☹️ | 08:27:20 |
| Regnat | If all you want is to have all the submodules fetched, maybe you can remove the build artifacts that have a self-ref in the postBuild | 08:28:02 |
| Reventlov | Redacted or Malformed Event | 08:32:17 |
| Reventlov | Redacted or Malformed Event | 08:32:35 |
| Reventlov | Redacted or Malformed Event | 08:33:00 |
| Reventlov | Redacted or Malformed Event | 08:33:31 |
 Alyssa Ross | @eelco:nixos.org do you know why i*86 platforms are forced to i686 for the Nix system in configure.ac? | 19:26:04 |
| Alyssa Ross | in #exotic:nixos.org we're wondering what the way to go would be for somebody to build e.g. i486 packages | 19:26:43 |
 niksnut | Dunno, it has been that way for a long time. Probably to avoid getting i786 or whatever. | 20:11:10 |
| niksnut | Oh, here is the explanation:
commit 966bd9d19fb43b6a6022572eb7d80c1e03bfaf3e
Author: Eelco Dolstra <e.dolstra@tudelft.nl>
Date: Fri Aug 13 09:57:51 2004 +0000
* WTF? More canonical system name problems ("athlon-linux" instead of
"i686-linux").
| 20:12:38 |
| Alyssa Ross | ah great, thanks | 20:19:29 |
| Alyssa Ross | I only managed to find the commit from Ludo in 2011 that just said "it's always been this way" | 20:19:42 |
| 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 |
