<samueldr> the prefix? prefixed the nickname on the IRC message :)
<gchristensen> ah
<samueldr> The channel: Consider the channel http://hydra.earthtools.ca/jobset/arm/nixpkgs-arm-unstable/channel/latest as a binary cache.
<samueldr> (must be getting too many highlights otherwise, fixed it with this one clever trick)
tomberek has joined #nixos-aarch64
orivej has quit [Ping timeout: 240 seconds]
Acou_Bass has quit [Quit: byeeeeeeeeeeeeeee]
Acou_Bass has joined #nixos-aarch64
orivej has joined #nixos-aarch64
<gchristensen> doing a reboot to bring some ofborg updates, and it is going a bit sideways
<gchristensen> ok back up and running, sorry for the delay
orivej has quit [Ping timeout: 246 seconds]
s33se has joined #nixos-aarch64
s33se_ has quit [Ping timeout: 248 seconds]
<tomberek> what's the right channel to use for aarch64?
<samueldr> #nixos-aarch64
<samueldr> :)
<samueldr> ah, nixos channel duh
<samueldr> nixos-unstable then
<tomberek> ha, thx..... i'm finding myself rebuilding a lot
<samueldr> using nixos or another distro?
<samueldr> with another distro it would be nixpkgs-unstable, though nixos-unstable works too
<tomberek> looks like i'm on nixpkgs-unstable.....
<tomberek> I thought unstable had aarch64 builds, why am I rebuilding binutils, et. al?
<samueldr> I thought too
<samueldr> I'm never sure I'm looking at the right hydra jobsets
<samueldr> but it looks like last binutils build was 3 days ago https://hydra.nixos.org/job/nixpkgs/trunk/binutils.aarch64-linux/all
<samueldr> latest nixpkgs-unstable update was 1 hour ago
<samueldr> ah, jobset is linked in http://howoldis.herokuapp.com/
* samueldr is always confused by hydra's interface
<samueldr> okay, from the link to the *job* on howoldis, I get the page with tabs with a "Links" tab, https://hydra.nixos.org/job/nixpkgs/trunk/unstable#tabs-links
<samueldr> which in turn has two links, one "Latest successful build from a finished evaluation", which is dated 2018-01-17
<samueldr> so uh, channels advance since the job doesn't need aarch64 I guess
Dezgeg has quit [Ping timeout: 276 seconds]
<samueldr> eh, I'm still confused by the interface, it looks like it should still be good, don't know why binutils would be rebuilding
<tomberek> it would be nice to have an interface or a way to ascertain what has a cache. nix-build --dry-run -iA nixpkgs.hello is the best I've got so far
<samueldr> it's possible that once aarch64 support is "in a reasonable state" it won't happen much
<samueldr> (if from 18.03 aarch64 is supported, it maybe will block channels?)
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 248 seconds]
Dezgeg has joined #nixos-aarch64
Dezgeg has quit [Client Quit]
Dezgeg has joined #nixos-aarch64
<gchristensen> thats right samueldr
orivej has joined #nixos-aarch64
<tomberek> I'm trying to set up a nix-serve of the arm7l builds (the cs.helsinki cache came back online) on a non-arm machine? What part needs the gcroot added? the drv?
<tomberek> That does seem to prevent gc of the closure after nix-copy-closure
vcunat has joined #nixos-aarch64
<tomberek> At the moment I'm using the arm machine to get the closures via nix-build from the cs.helsinki cache, the copying them to the x86 store. Can that just be done directly?
<vcunat> you can nix-build on the x86 machine directly
<vcunat> substitutes work cross-arch
<vcunat> (I've already inspected some darwin paths from cache.nixos.org on my nixos machine.)
vcunat has quit [Quit: Leaving.]
Tasqa has quit [Ping timeout: 268 seconds]
<Dezgeg> now we have chromium theoretically building... let's see if hydra manages under the 10 hour limit
<samueldr> cool!
<gchristensen> nice :D
Tasqa has joined #nixos-aarch64
<gchristensen> https://hydra.nixos.org/build/67463991 only 12min left for it to finish :(