lopsided98 has quit [Remote host closed the connection]
lopsided98 has joined #nixos-aarch64
pbb has joined #nixos-aarch64
pbb has quit [Client Quit]
pbb has joined #nixos-aarch64
h0m1 has quit [Quit: WeeChat 2.7.1]
h0m1 has joined #nixos-aarch64
h0m1 has quit [Ping timeout: 272 seconds]
h0m1 has joined #nixos-aarch64
alex_giusi_tiri has quit [Quit: Leaving.]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 246 seconds]
lovesegfault has quit [Quit: WeeChat 2.7.1]
mvnetbiz_9 has joined #nixos-aarch64
mvnetbiz_ has quit [Ping timeout: 258 seconds]
mvnetbiz_9 is now known as mvnetbiz_
orivej has joined #nixos-aarch64
lovesegfault has joined #nixos-aarch64
orivej has quit [Ping timeout: 256 seconds]
zupo has joined #nixos-aarch64
<LinuxHackerman>
alex_giusi_tiri: if it's connected via both, it's probably replying to the wifi-incoming connection via ethernet, so the reply is coming from a different address than what the client is expecting, so the TCP handshake doesn't succeed.
<LinuxHackerman>
alex_giusi_tiri: does it work if you unplug the ethernet?
zupo has quit [Ping timeout: 264 seconds]
FRidh has joined #nixos-aarch64
lovesegfault has quit [Quit: WeeChat 2.7.1]
zupo has joined #nixos-aarch64
vika_nezrimaya has quit [Ping timeout: 256 seconds]
zupo_ has joined #nixos-aarch64
FRidh2 has joined #nixos-aarch64
FRidh has quit [Ping timeout: 256 seconds]
FRidh2 has quit [Client Quit]
FRidh2 has joined #nixos-aarch64
zupo has quit [Ping timeout: 246 seconds]
LinuxHackerman has left #nixos-aarch64 ["User left"]
zupo_ has quit [Ping timeout: 264 seconds]
zupo has joined #nixos-aarch64
lovesegfault has joined #nixos-aarch64
FRidh2 has quit [Ping timeout: 246 seconds]
FRidh2 has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zarel has quit [Ping timeout: 250 seconds]
vika_nezrimaya has joined #nixos-aarch64
zarel has joined #nixos-aarch64
zupo has joined #nixos-aarch64
vika_nezrimaya has quit [Ping timeout: 246 seconds]
zupo_ has joined #nixos-aarch64
zupo has quit [Ping timeout: 256 seconds]
zupo_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 250 seconds]
FRidh2 has quit [Ping timeout: 246 seconds]
FRidh has joined #nixos-aarch64
vika_nezrimaya has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
vika_nezrimaya has quit [Ping timeout: 264 seconds]
vika_nezrimaya has joined #nixos-aarch64
vika_nezrimaya has left #nixos-aarch64 ["ERC (IRC client for Emacs 26.3)"]
FRidh has quit [Ping timeout: 250 seconds]
FRidh2 has joined #nixos-aarch64
arianvp_ is now known as arianvp
lordcirth_ has joined #nixos-aarch64
orivej has joined #nixos-aarch64
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
cornu has joined #nixos-aarch64
<bennofs>
how does the binary channel for aarch64 work? I am surprised that I have to build nix-index, fd and mosh myself on nixos-20.03
<lordcirth_>
I don't think there's enough ARM build capacity to keep up
<bennofs>
how is the building of nixpkgs packages coupled the the nixos-20.03 jobset / channel updates / binary cache?
<srk>
git tag
<srk>
nixos-20.03 possibly, there might be declarative jobsets for hydra, not sure
<samueldr>
there is enough build capcity, the issue is that it was accidentally left off
<bennofs>
I'm still searching for the mechanism to wait for all paths to be completely built before the channel updates
<bennofs>
samueldr: what makes sure that when nixos/release-20.03/tested has finished, every package in the nixpkgs used by that job has been attempted to build (and either failed or finished)? I don't nixpkgs being a contituent of that jobset?
<samueldr>
hydra makes sure
<samueldr>
that's a hydra thing
<bennofs>
how does it know that? :O I understand that it waits for all constituents (like the tests) to finish. But how can it know that there is a different config, in pkgs/top-level/release.nix, that also has a list of jobs and that it needs to wait for that?
lordcirth__ has joined #nixos-aarch64
<bennofs>
argh wait I missed the "show all X thousand jobs" link
lordcirth_ has quit [Ping timeout: 246 seconds]
<bennofs>
I think I mixed up the jobset with the job. There is a tested "job" that aggregates the tests, but this "job" is part of a "jobset" that also contains "nixpkgs"
<samueldr>
it waits for all derivations of the eval
<samueldr>
an eval is part of the jobset
<bennofs>
yeah I missed the link how all of nixpkgs becomes part of the eval
<samueldr>
:)
<samueldr>
it can be confusing I fully know
<bennofs>
but it's in nixos/release-combined.nix, there's nixos, nixpkgs, and tested
<bennofs>
is there a reason for not mirroring the nixos-20.03-aarch64 jobset? storage costs? at least it's not part of channels.nix in nixos-org-configurations
<samueldr>
it's... complicated
<samueldr>
"mirroring" isn't what's in there
<samueldr>
all artifacts built by hydra are mirrored on the cache
<samueldr>
cache.nixos.org
<samueldr>
so currently we have mobile-nixos artifacts on cache.nixos.org
<samueldr>
what's missing though, is a discrete channel
<samueldr>
and the reason is part of the reason it wasn't evaluating until recently
<bennofs>
so we would want to have a separate channel for aarch64, as we don't want to block the main channel with aarch64 failures (didn't we have that setup as well for some short time in the past?)?
<bennofs>
ah wait, I basically just need my own little script to pick out the latest, finished eval from hydra
<bennofs>
since I'm using a git checkout anway, I only need to get the correct rev
<samueldr>
starting with the *next* release, we'll lobby hard against having split channels
<samueldr>
this current release will do as the last two-three releases
<bennofs>
we don't have split channels right now, do we? we only have a nixos-20.03 channel
<samueldr>
(though there may have been a channel accidentally left out)
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
radvendii has joined #nixos-aarch64
<radvendii>
Hi. I'm trying to install NixOS on a Raspberry Pi (3B), and I'm using the aarch64 image, and it's taking a very long time on the first nixos-rebuild
<radvendii>
i was told people here might have insight
<radvendii>
i was expecting it to download things from the binary cache, but it seems to be building them
<radvendii>
i see a bunch of lines like "CC kernel/time/time.o"
<lordcirth__>
Is it building anything other than the kernel?
<radvendii>
i also see " CC arch/arm64/kvm/hyp/debug-sr.o"
<radvendii>
so that's not in the kernel/ folder. not sure if it counts
<samueldr>
radvendii: which channel are you following?
<gchristensen>
I don't recognize any of those names
<radvendii>
should i use the 20.03 release? is that stable? i didn't remember it coming out
<gchristensen>
20.03 is stil lbeta
<gchristensen>
usually releases at the very end of the month
FRidh2 has quit [Quit: Konversation terminated!]
<radvendii>
i'm reading through old github issues to try to figure out how to point my nixos to use a specific nixpkgs commit (so that it can use the binary cache). can anyone point me to a solution?
<srk>
clone nixpkgs
<srk>
NIX_PATH=/home/me/git nix / nixos-rebuild
<srk>
pff
<tilpner>
You can also point NIX_PATH directly at a tarball of a specific commit
<srk>
or point NIX_PATH to the root of the dir where you cloned nixpkgs
<tilpner>
E.g. NIX_PATH=nixpkgs=https://github.com/NixOS/nixpkgs/archive/5241e5a193f009bc8b1235904a8bc15cbe0e2c00.tar.gz
<srk>
cool
<tilpner>
That's not necessarily a good idea, it will re-fetch that tarball every hour because you didn't add a hash
<radvendii>
hmmm i'm getting error: file 'nixos-config' was not found
<clever>
radvendii: use -I nixpkgs= instead of changing NIX_PATH
<clever>
radvendii: nixos-rebuild needs a nixos-config= in the path