samueldr changed the topic of #nixos-dev to: #nixos-dev NixOS Development (#nixos for questions) | NixOS 19.09 is released! https://discourse.nixos.org/t/nixos-19-09-release/4306 | https://hydra.nixos.org/jobset/nixos/trunk-combined https://channels.nix.gsc.io/graph.html | https://r13y.com | 19.09 RMs: disasm, sphalerite | https://logs.nix.samueldr.com/nixos-dev
ixxie has quit [Ping timeout: 240 seconds]
justanotheruser has quit [Ping timeout: 240 seconds]
justanotheruser has joined #nixos-dev
<clever> samueldr: ahh nice, but who hosts it and how big is the disk and such?
<samueldr> hm?
<clever> samueldr: for gitub actions
<samueldr> I presume "a" cloud provider, and it's ephemeral
<clever> ah
<samueldr> the difference is the first implementation of workflows for github couldn't run multiple steps in the same context
<samueldr> so you couldn't have one step for building, then another to send to cachix
<samueldr> the /nix/store would be lost
<clever> yeah
<samueldr> while the "new" way, multiple steps share the same VM
<samueldr> but if you're using a docker container, you're using an ephemeral /nix/store!
<samueldr> so that's an advantage of using the install nix action
<vaibhavsagar> wait, so the `/nix/store` persists across different invocations?
<vaibhavsagar> that's a huge improvement if so
<samueldr> no, still ephemeral
<samueldr> but the initial workflows, different *steps* were not running in a common environment, only a golden "workspace" directory was shared
<samueldr> while now multiple steps can run in the same environment
<samueldr> unless I misunderstand something
<vaibhavsagar> ah, I see
<vaibhavsagar> IMO GitHub Actions don't seem that much better than Travis CI
<samueldr> since everything was ephemeral, is you simply used nixos/nix docker, did nix-build
<samueldr> the next step would receive a broken symlink
<samueldr> never used travis ci
<vaibhavsagar> oh, I use it pretty heavily for all my stuff, it's very nice in combination with Cachix to handle caching
cptchaos83 has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
cptchaos83 has joined #nixos-dev
Scriptkiddi has quit [Remote host closed the connection]
das_j has quit [Remote host closed the connection]
das_j has joined #nixos-dev
Scriptkiddi has joined #nixos-dev
ajs124 has quit [Quit: Gateway shutdown]
greizgh has quit [Quit: greizgh]
greizgh has joined #nixos-dev
andi- has quit [Remote host closed the connection]
andi- has joined #nixos-dev
justanotheruser has quit [Ping timeout: 265 seconds]
justanotheruser has joined #nixos-dev
ixxie has joined #nixos-dev
ixxie has quit [Ping timeout: 276 seconds]
FRidh has joined #nixos-dev
MichaelRaskin has joined #nixos-dev
<worldofpeace> ,tell Thra11 I was reverted to have been merged to staging, in hindsight it would have been fine for master https://github.com/NixOS/nixpkgs/pull/73952#issuecomment-557761747, but I believe it's already in staging-next.
<{^_^}> worldofpeace: I'll pass that on to Thra11
<worldofpeace> ah darn, that was meant or #nixos :D
<clever> building '/nix/store/m86wy24y3w1g7hw4q47lgl2aw2hw428y--vc4-elf-stage-staticgcc-debug-6.5.0.drv' on 'ssh://builder@192.168.2.32'...
<clever> Ericson2314: why is there a -- at the start?
<clever> /nix/store/rcjmiq80kph7az6qxyb97j4z2f494k07-vc4-elf--vc4-elf-stage-finalgcc-debug-wrapper-6.5.0.drv
<clever> Ericson2314: it feels like the "vc4-elf" string somehow gained a stray - ?
globin has quit [Quit: o/]
globin has joined #nixos-dev
ckauhaus has joined #nixos-dev
globin has joined #nixos-dev
globin has quit [Changing host]
globin has joined #nixos-dev
globin has quit [Changing host]
globin has joined #nixos-dev
ckauhaus has quit [Quit: WeeChat 2.6]
ckauhaus has joined #nixos-dev
<FRidh> globin: could you explain why env. is used on the structured attributes branch?
<clever> Ericson2314: i can confirm that the vc4 PR still works on real hardware
<globin> FRidh: currently writing a blog post (pre-RFCish) explaining a few things
<FRidh> okay
<FRidh> looks like it's much bigger than I anticipated
<FRidh> *expected
<globin> FRidh: in short declare -a/-A doesn't allow exporting, so to keep it consistent, all parameters to mkDrv are local bash vars and then it's easier to make it explicit with env to ensure which vars are exported
<globin> and that also only allows values to be scalar types
__monty__ has joined #nixos-dev
genesis has quit [Quit: Leaving]
FRidh has quit [Quit: Konversation terminated!]
mmlb has quit [Ping timeout: 252 seconds]
ris has joined #nixos-dev
<ris> discovery: fetchpatch is broken inside glibc/common.nix
<gchristensen> yea
<ris> evaluating the hash works, so if your store already has the fetchpatch result, you're fine
Ox4A6F has joined #nixos-dev
<gchristensen> hm I wouldn't have expected evaluation to work
<ris> so should patches to glibc use fetchurl instead?
<gchristensen> at some point in the bootstrapping phase we needto either use fetchurl, or just put patches in the repo
<clever> there is a bootstrap fetchurl, that will use a curl from the bootstrap tools
<clever> it may be possible to make a bootstrap fetchpatch?
<ris> ok - i guess correct-pwent-parsing-issue-and-resulting-build.patch needs to be fixed at some point because it currently isn't bootstrappable if you don't have a binary cache
<ris> it's only applied on musl cross compiles though
<ris> oh - musl _or_ cross compiles
<clever> it could use the host fetchpatch implementation?
<clever> to not depend on itself
<ris> dunno, i generally fear to tread too deep into the realm of bootstrapping
_0mp has joined #nixos-dev
ris has quit [Ping timeout: 250 seconds]
drakonis_ has joined #nixos-dev
drakonis_ has quit [Read error: Connection reset by peer]
drakonis_ has joined #nixos-dev
drakonis_ has quit [Read error: Connection reset by peer]
drakonis_ has joined #nixos-dev
drakonis has quit [Ping timeout: 245 seconds]
drakonis has joined #nixos-dev
justanotheruser has quit [Quit: WeeChat 2.6]
drakonis_ has quit [Ping timeout: 252 seconds]
justanotheruser has joined #nixos-dev
ris has joined #nixos-dev
drakonis_ has joined #nixos-dev
drakonis has quit [Ping timeout: 265 seconds]
drakonis has joined #nixos-dev
drakonis_ has quit [Ping timeout: 276 seconds]
drakonis_ has joined #nixos-dev
drakonis1 has joined #nixos-dev
drakonis has quit [Ping timeout: 246 seconds]
drakonis_ has quit [Ping timeout: 276 seconds]
eraserhd has joined #nixos-dev
ixxie has joined #nixos-dev
<Ericson2314> clever: yes Imessed up the dashses but then I fixed
<_0mp> FYI, we are trying to finish adding Nix (the package manager) to the FreeBSD ports. Join us in #freebsd-nix on Freenode if you are insterested.
<simpson> Ooh, the first step in assimilation. Sounds fun.
<_0mp> yes!
<samueldr> :/
<samueldr> I thought linux_testing was built on hydra, so issues could be caught earlier
<samueldr> waiting on a fresh build, but there might be something going on with the build
<samueldr> (on aarch64)
<samueldr> hmmm, though linux_testing_hardened is?
<samueldr> yep, issue on hydra too
lopsided98 has quit [Ping timeout: 245 seconds]
lopsided98 has joined #nixos-dev
<samueldr> though, this might be something that's solved with compiler/assembler options
<thefloweringash> Looks like another case of #64916
<{^_^}> https://github.com/NixOS/nixpkgs/issues/64916 (by thefloweringash, 18 weeks ago, open): Linux kernel versions 4.4 and 4.10 don't build on nixos-unstable Aarch64
<samueldr> possibly, that's why I was speaking up :)
{`-`} has joined #nixos-dev
drakonis has joined #nixos-dev
justanotheruser has quit [Ping timeout: 240 seconds]
justanotheruser has joined #nixos-dev
MichaelRaskin has quit [Quit: MichaelRaskin]
phreedom has quit [Remote host closed the connection]
phreedom has joined #nixos-dev
phreedom has quit [Remote host closed the connection]
phreedom has joined #nixos-dev
ajs124 has joined #nixos-dev
__monty__ has quit [Quit: rebootying]
_0mp has left #nixos-dev [#nixos-dev]
<clever> Ericson2314: ah
<Ericson2314> clever: yeah?
<clever> about the dashes
ixxie has quit [Ping timeout: 240 seconds]
justanotheruser has quit [Ping timeout: 265 seconds]