<gchristensen>
andi-: this is a new and exciting deadlock :)
<gchristensen>
oh, no, Ike didn't get the new nix. looking.
Ericson2314 has joined #nixos-dev
orivej has quit [Ping timeout: 252 seconds]
sir_guy_carleton has quit [Quit: WeeChat 2.0]
FRidh has joined #nixos-dev
Ericson2314 has quit [Ping timeout: 252 seconds]
sphalerite has quit [Quit: WeeChat 2.0]
sphalerite has joined #nixos-dev
sphalerite has quit [Quit: WeeChat 2.0]
sphalerite has joined #nixos-dev
sphalerite has quit [Quit: WeeChat 2.0]
sphalerite has joined #nixos-dev
init_6 has joined #nixos-dev
<manveru>
time to rename it to 行けない...
orivej has joined #nixos-dev
FRidh has quit [Quit: Konversation terminated!]
init_6 has quit []
goibhniu has joined #nixos-dev
<gchristensen>
train wifi isn't the best place to debug broken builders... but it is a fine place to start doing deploys -- the atomic update is perfect.
sir_guy_carleton has joined #nixos-dev
<ekleog>
manveru: that pun was… :D
<manveru>
was just celebrating that i finally switched from ibus+anthy to fcitx+mozc :)
<ekleog>
mozc ftw
<ekleog>
(though I'm ibus+mozc currently)
<gchristensen>
what did that message say?
<ekleog>
time to rename it to « it doesn't work » (which is pronounced « ikenai » in japanese)
<gchristensen>
haha
phreedom has quit [Quit: No Ping reply in 180 seconds.]
phreedom has joined #nixos-dev
obadz has quit [Ping timeout: 252 seconds]
<gchristensen>
it would be interested to see Nix's evaluator be able to run multiple builtin fetches at once
<andi->
more locking issues? ;-)
<gchristensen>
I'm doing an eval with about 23 builins.fetchTarball's and it is ... a bit slow
<gchristensen>
error: Nix daemon out of memory oops
<samueldr>
#47901 has 5612 changed paths according to ofborg, but **only** aarch64; since they're on separate jobsets on hydra is it fine to merge without going through staging?
<samueldr>
mic92: how do you want to proceed for an update to alacritty? I see it's using your fork
<samueldr>
confirming that by using the upstream 0.2.1 release my (only?) issue with alacritty has been fixed
<andi->
wasn't there talks about moving away from the fork?
edef has quit [Remote host closed the connection]
edef has joined #nixos-dev
<samueldr>
there was talk recently about alacritty here, don't really remember what it was all about so I'm asking
<gchristensen>
go for it, samueldr
<samueldr>
good, was wondering if there was yet something I wouldn't foresee
<samueldr>
dhess: think you can track the status of this in the coming hydra evals?
<samueldr>
(I'll try to remember to check too)
<andi->
I am a bit confused about https://nixos.org/channels/nixos-18.03/git-revision, it shows as d16a7ab which is from 20th of september, the nixpkgs-channels repo points to the commits the IRC bot announces.. When I update the channel locally I also end up on the commit from the 20th september.
<andi->
same is visible on 18.09, nixpkgs-channels branch points to a commit from 3 days ago while the channel is from the 3rd october
* samueldr
wonders if his fix for updates going back from the future actually worked
<andi->
two days ago the 18.03 channel on this machine was on a newer machine.. :/
<andi->
s/machine\./revision./
<samueldr>
:)
<andi->
How does that process actually work? can an old evaluation cause a "new" channel bump with an old revision?
<Mic92>
samueldr: ah right, the fork-less version was in staging
<Mic92>
because it required a fix in buildRustPackage
<samueldr>
I mainly don't want to step on toes
<Mic92>
0.2.1 can be backported as well
<Mic92>
it fixes a security issue
<samueldr>
if you meant to 18.09, even without security issues, it would have been; "patch" level update with bug fixes are important
<samueldr>
so uhm, I'm still unclear on how to proceed due to the other change being in staging; do we wait until staging is merged back into master? otherwise whatever your fork fixes will be lost for a small while
<gchristensen>
hydra does definitely, when jobs are restarted. the script should protect itself flom that though, and has code to do that
<andi->
ok
<gchristensen>
ie, if a job for the latest finished jobset is restarted, it is no longer finished:)
<andi->
I just wasn't sure wether hydra pushes some hook or if there is a regular job interval on nixos.org that pulls. It seems like it pulls regulary on such a url for each release?