<edef>
gchristensen: any particular reason for that?
<domenkozar>
I've opted just to substitute via ssh
<edef>
gchristensen: i just noticed it when looking at the result of a check
<domenkozar>
but now I get warnings for untrusted store
<domenkozar>
untrusted signatures*
<domenkozar>
I probably need to sign them first
<domenkozar>
oh man this is why I wrote cachix, I forget sometimes :)
<gchristensen>
edef I want result_to_check to be a pure function and haven't done the work to have builders report the completion date, and I guess didn't consider passing the date in to result_to_check :P
<gchristensen>
edef: want to send a PR doing that second option?
<edef>
yeah
<gchristensen>
great!
<gchristensen>
also #nixos-borg
pie___ has joined #nixos-dev
pie__ has quit [Remote host closed the connection]
<{^_^}>
nixos-weekly#72 (by domenkozar, 5 days ago, open): Call for Content: 2018/14
<domenkozar>
weekly reminder that it's time to publish those blog posts :)
<gchristensen>
<3 domenkozar for doing the good work
<qyliss^work>
domenkozar++
<{^_^}>
domenkozar's karma got increased to 13
<ekleog>
zimbatm: given niksnut gave his +1 on IRC I guess the FCP has technically started and should be announced in weekly… or maybe we should wait for an official comment on the PR so that the fact the RFC process has been followed is explicit and shown as example?
<domenkozar>
:)
<domenkozar>
I wonder how to improve call for content
<domenkozar>
right now I make sure there's a PR always open
<domenkozar>
and do a weekly ping
<zimbatm>
ekleog: +1 for adding it to nixos-weekly
<vdemeester>
Mic92: ok, I'll take a look a bit later, thanks :)
<Mic92>
vdemeester: but looking at this again. Are you sure the build break because of cross-compiling?
<vdemeester>
Mic92: I just know that my git bisect told me this commit is the one making that package fail.. not yet sure why (the error I'm getting it `cgo.a: permission denied`)
<Mic92>
vdemeester: do you try to build without cgo?
<Mic92>
i.e. static binaries?
<Mic92>
*fully static
<vdemeester>
Mic92: nop, pretty sure it's required for that package (gpgme, …), I don't think there is a possibility to build it static
<gchristensen>
ce=mac8-guest&var-instance=mac8-host&var-instance=mac9-guest&var-instance=mac9-host&var-machine=All mac1 is migrated too, but can't boot macos for some reason, and mac9 seems to have some broken hardware.
<globin>
gchristensen++
<{^_^}>
gchristensen's karma got increased to 55
<LnL>
!m gchristensen
<LnL>
this is great :D
alp has quit [Ping timeout: 245 seconds]
alp has joined #nixos-dev
<gchristensen>
it would be very nice if I could have an instance drop-down option for "mac.-guest" and "mac.-host" so you don't have to tick a zillion boxes -- is there a way to do anything like this, LnL?
<LnL>
I think so, do they have labels?
<gchristensen>
what kind of labels would you like? (I don't know)
<LnL>
mac-host and mac-guest
<gchristensen>
no, they don't have that sort of label. I imagine I could do that at the importer? or can node-exporter do it?
<gchristensen>
it isn't real nice because all the queries had to be edited, and thinking now it'd be nice to be able to add more, like architecture ... but also wouldn't relish going back to edit all the queries again
<LnL>
oh, I see what you did now
<gchristensen>
what did I do? :P
<LnL>
was the instance= there before?
<gchristensen>
yeah
<gchristensen>
is there a nicer way?
<LnL>
I thought you could filter stuff in the variables section, but it didn't entirely work as I expected
<gchristensen>
oh looks like I could edit the JSON directly, much more quickly than via the gui
<LnL>
with a query like label_values(node_boot_time_seconds{role=~"$role"}, instance) for instance instead of label_values(instance)
<gchristensen>
oh cool
<gchristensen>
it is kinda weird grafana doesn't support "global" filters
<gchristensen>
but I suppose that makes sense with more complicated queries
<LnL>
yeah, also dashboards can show different metrics in which case a bunch of the filters wouldn't make sense anyway
<gchristensen>
nix2grafana
<LnL>
hehe
<simpson>
I had had some Grafana config in Nix, but it did not work reliably and I gave up on that.
orivej has joined #nixos-dev
drakonis_ has joined #nixos-dev
drakonis has quit [Ping timeout: 252 seconds]
<gchristensen>
seems a bit annoying, anyway
<LnL>
being able to edit interactively is also really important for this IMHO
<simpson>
Yeah, but I wish that it could all be saved to portable JSON always.
<gchristensen>
it can
<simpson>
I guess one could manually import and export everything. That *is* an option.
<LnL>
it uses the s3 client directly instead of the store api
<Ericson2314>
Mic92: don't see why not
<LnL>
isn't AR already set?
<Mic92>
LnL: right, I have seen many buildsystems using AR, while they actually want AR_FOR_TARGET.
<Ericson2314>
Mic92: you mean they use AR_FOR_BUILD when they want AR
<Ericson2314>
because they hard-code `ar`
<Ericson2314>
because in most situations using the wrong AR is fine
<Ericson2314>
(but not all situations!)
<Ericson2314>
Mic92: the first advantages of getting the compiler from the previous stage is then build<->build, host<->host, target<->target always
<Ericson2314>
you don't have to think about the mapping
<Mic92>
Ericson2314: Ok. The problem is actually different. $AR == ar, which does not exists
<Ericson2314>
2nd advantage is one can cross compile the cross compiler for free
<Mic92>
Ericson2314: I am not sure how this would look like for rust though.
<Ericson2314>
Mic92: for rustc?
<Ericson2314>
which derivation?
<Mic92>
Ericson2314: no the AR problem is in openldap
<Ericson2314>
oh
<Ericson2314>
this is just a library
<Ericson2314>
there should be no mention of target anywhere
<Mic92>
Ericson2314: regarding taking the compiler from the previous stage, whould the pre-compiled rustc binary just end up in stdenv.
<Ericson2314>
for cross compilation, AR != "ar"
<Ericson2314>
what do you mean? probably would need to bind a rustcBootstrap
<Ericson2314>
so that rustBoostrap can depend on buildPackages.rustcBootstrap
<Ericson2314>
and rust depend on buildPackages.rustc
<Ericson2314>
my line notes were too deep in the weeds and me reading things wrong, my comment at the bottom of the PR thread on the big picture is better
<LnL>
niksnut: oh my bad, substituters goes through the daemon so I didn't have credentials configured