!VRULIdgoKmKPzJZzjj:nixos.org

Nix Hackers

899 Members
For people hacking on the Nix package manager itself188 Servers

Load older messages


SenderMessageTime
1 Jun 2021
@rgrunbla:matrix.orgReventlovRedacted or Malformed Event08:33:00
@rgrunbla:matrix.orgReventlovRedacted or Malformed Event08:33:31
@qyliss:fairydust.spaceAlyssa 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
@qyliss:fairydust.spaceAlyssa Rossin #exotic:nixos.org we're wondering what the way to go would be for somebody to build e.g. i486 packages19:26:43
@niksnut:matrix.orgniksnutDunno, it has been that way for a long time. Probably to avoid getting i786 or whatever.20:11:10
@niksnut:matrix.orgniksnut

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
@qyliss:fairydust.spaceAlyssa Rossah great, thanks20:19:29
@qyliss:fairydust.spaceAlyssa RossI 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
@jtojnar:matrix.orgJan 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
@jtojnar:matrix.orgJan 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
@qyliss:fairydust.spaceAlyssa Rossniksnut: while you're merging Nix PRs, any thoughts on https://github.com/NixOS/nix/pull/4773? :)11:35:55
@niksnut:matrix.orgniksnutDoes that work with lowdown?11:36:49
@sternenseemann:systemli.orgsterni niksnut: https://kristaps.bsd.lv/lowdown/lowdown.3.html#LOWDOWN_DEFLIST 11:37:32
@sternenseemann:systemli.orgsterni seems like you've already turned it on in libcmd/markdown.cc 11:38:24
@qyliss:fairydust.spaceAlyssa Rossoh, do they end up in a man page?11:39:32
@sternenseemann:systemli.orgsterni Alyssa Ross: :doc on the repl is rendered with lowdown's term rendering target 11:40:27
@qyliss:fairydust.spaceAlyssa Rossahh11:41:38
@qyliss:fairydust.spaceAlyssa Rosslet me test11:41:39
@sternenseemann:systemli.orgsterni 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
@sternenseemann:systemli.orgsternicmark is extensible, so lowdown is probably the constraining factor in the equation11:42:45
@qyliss:fairydust.spaceAlyssa Rossugh, I don't have the build cached any more11:43:00
@ryantm:matrix.orgryantmhttps://github.com/ryantm/mmdoc11:44:23
@ryantm:matrix.orgryantmhttps://github.com/NixOS/nixpkgs/pull/10806311:44:27
@qyliss:fairydust.spaceAlyssa Rosswow, nice11:45:03
@qyliss:fairydust.spaceAlyssa Rossniksnut: it doesn't make a difference to :doc, because that doesn't use any of the markup I changed11:55:01
@qyliss:fairydust.spaceAlyssa RossI think it just affects the mdbook manual11:57:16
@rgrunbla:matrix.orgReventlovRedacted or Malformed Event12:30:38
@rgrunbla:matrix.orgReventlovRedacted or Malformed Event12:31:17
@theophane:hufschmitt.netRegnat
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
@theophane:hufschmitt.netRegnat(But ignoring the references is actually unsound)12:35:14

Show newer messages


Back to Room ListRoom Version: 6