gchristensen changed the topic of #nixos-dev to: NixOS Development (#nixos for questions) | https://hydra.nixos.org/jobset/nixos/trunk-combined https://channels.nix.gsc.io/graph.html | 18.09 release managers: vcunat and samueldr | https://logs.nix.samueldr.com/nixos-dev
<pie__> hi we are trying to build nix on freebsd, the configure file that gets generated by autoconf (afaict) uses /bin/sh, but this line https://github.com/NixOS/nix/blame/master/configure.ac#L217
<pie__> uses bash syntax
<pie__> that seems incorrect. can someone corroborate my line of thought?
<pie__> i mean, that should be fixed to not use bash syntax?
<clever> pie__: what is line 1 of the generated configure script?
<pie__> #! /bin/sh
<samueldr> this indeed looks bash-y
<clever> pie__: how does it behave if you change it to #!/bin/bash ?
<pie__> it works when we do that
<pie__> err
<pie__> the path is different, but it still works when we use bash
<samueldr> I guess /usr/bin/bash since that's AFAIK where freebsd put it in the past
<pie__> yeah basically something like that
<samueldr> the "right" shebang to use would be /usr/bin/env bash if it can be done for aucotonf
<pie__> well basically my question is nix expected to be build with sh or bash. if its sh, this should be fixed?
<samueldr> not knowing for sure, I feel like this is a bug
<samueldr> something that needs to be fixed
Synthetica has quit [Quit: Connection closed for inactivity]
<pie__> im not really set up to do that myself right now...can you maybe open an issue or something just so there is some record of this?
<pie__> or actually
<pie__> i think we can open a github issue
<samueldr> probably way better than me opening an issue when I only have heard of it through you :)
<pie__> i mean thats perfectly reasonable :P
<{^_^}> nix#2604 (by 0mp, 39 seconds ago, open): configure.ac contains Bash-specific syntax
jtojnar has quit [Quit: jtojnar]
<pie__> ummm there may actually be additional bashisms in there
<samueldr> I bet it's probably if that one snuck in
<samueldr> probable*
<pie__> apparently that may have worked so far because /bin/sh is symlinked to bash or something on some systems? idk
<samueldr> most likely
<samueldr> or to a bashy enough shell
<samueldr> e.g. debian/ubuntu with dash
{`-`}_ has joined #nixos-dev
{`-`}_ has joined #nixos-dev
<ivan> cd nixpkgs && rg '^\t' **/*.nix
{`-`} has quit [Remote host closed the connection]
{`-`}_ is now known as {`-`}
<ivan> https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/filesystems/relfs/default.nix http://relfs.sourceforge.net/ this looks like a good candidate for removal - can't imagine anyone still uses it
pie__ has quit [Ping timeout: 244 seconds]
sir_guy_carleton has joined #nixos-dev
lassulus_ has joined #nixos-dev
lassulus has quit [Ping timeout: 268 seconds]
lassulus_ is now known as lassulus
orivej has quit [Ping timeout: 245 seconds]
hedning has quit [Quit: hedning]
sir_guy_carleton has quit [Quit: WeeChat 2.2]
Synthetica has joined #nixos-dev
niksnut has quit [Ping timeout: 250 seconds]
niksnut has joined #nixos-dev
orivej has joined #nixos-dev
init_6 has joined #nixos-dev
orivej has quit [Ping timeout: 272 seconds]
olejorgenb[m] has joined #nixos-dev
<timokau[m]> I still don't understand what blocks a channel and what doesn't. Why was there a nixos-unstable-small eval one day ago with 3 failing tests which suceeded, while the current eval with just one of those tests failing fails?
jtojnar has joined #nixos-dev
<domenkozar> timokau[m]: did you read http://howoldis.herokuapp.com
<timokau[m]> domenkozar: I did now (visited that website countless times but never actually read the explanation text)
<timokau[m]> But that doesn't really explain why https://hydra.nixos.org/build/86418620 with 3 failures is considered "succeeded" while https://hydra.nixos.org/build/86520641 with only a subset of the failures is "failed"
<domenkozar> O_O it should fail if any of jobs fail
<domenkozar> maybe there was some russian roulette feature added meanwhile
orivej has joined #nixos-dev
delroth has quit [Quit: WeeChat 2.3]
delroth has joined #nixos-dev
<timokau[m]> The nixpkgs-unstable channel is currently blocked by ghc timing out on darwin
<timokau[m]> Is that expected to take insanely long?
<domenkozar> nope, probably transient
niksnut has quit [Remote host closed the connection]
pie__ has joined #nixos-dev
pie__ has quit [Remote host closed the connection]
pie__ has joined #nixos-dev
pie__ has quit [Ping timeout: 245 seconds]
zukaboo has joined #nixos-dev
niksnut has joined #nixos-dev
JosW has joined #nixos-dev
pie__ has joined #nixos-dev
orivej has quit [Ping timeout: 272 seconds]
pie__ is now known as [redacted]
[redacted] is now known as pie__
pie__ has quit [Ping timeout: 252 seconds]
pie_ has joined #nixos-dev
zukaboo has quit [Quit: KVIrc 5.0.0 Aria http://www.kvirc.net/]
init_6 has quit []
emily has quit [Quit: leaving]
pie__ has joined #nixos-dev
pie_ has quit [Ping timeout: 252 seconds]
<pie__> samueldr, re: yesterday: apparently its documented that configure needs bash https://nixos.org/nix/manual/#ch-installing-source "Bash Shell. The ./configure script relies on bashisms, so Bash is required."
<pie__> however autotools does not support using anything except sh for portability reasons
<samueldr> I think there's a workaround possible when calling
<samueldr> I saw it at some places when looking quickly yesterday
<samueldr> try: CONFIG_SHELL=/usr/bin/bash ./configure
<samueldr> I have no idea if it should work
JosW has quit [Quit: KVIrc 4.2.0 Equilibrium http://www.kvirc.net/]
nDuff has joined #nixos-dev
<pie__> samueldr, we tried that, doesnt work
<pie__> or at least we couldnt get it to work
<samueldr> good to know it doesn't, I guess
orivej has joined #nixos-dev
sir_guy_carleton has joined #nixos-dev