!RROtHmAaQIkiJzJZZE:nixos.org

NixOS Infrastructure

424 Members
Next Infra call: 2024-07-11, 18:00 CEST (UTC+2) | Infra operational issues backlog: https://github.com/orgs/NixOS/projects/52 | See #infra-alerts:nixos.org for real time alerts from Prometheus.133 Servers

Load older messages


SenderMessageTime
14 Oct 2021
@k900:0upti.meK900 All the examples I've seen just use github:nixos/nixpkgs 12:17:32
@k900:0upti.meK900Which is how I ended up here12:17:42
@lukegb:zxcvbnm.ninjalukegb (he/him)The branch is, iirc, updated by the same infrastructure that updates the channel definitions anyway12:17:59
@toonn:matrix.orgtoonn Ah, there's no release-unstable? I know the branch naming isn't intuitive with the stable branches. 12:18:04
@k900:0upti.meK900nixpkgs-unstable the branch seems to follow the nixpkgs-unstable Hydra job at least12:18:29
@lukegb:zxcvbnm.ninjalukegb (he/him)You say that you're missing rustc from nixpkgs-unstable though?12:19:31
@k900:0upti.meK900Yes12:20:25
@k900:0upti.meK900Oh god wait I might be an idiot12:26:29
@k900:0upti.meK900OK no I'm not12:27:08
@k900:0upti.meK900It is building the right branch12:27:14
@toonn:matrix.orgtoonn I guess rustc may not be in the set of things that need to be fully evaluated before the channel advances. 12:28:28
@toonn:matrix.orgtoonn Which is a bit unfortunate since sphinx has started depending on it and tons of stuff depends on that for documentation. 12:28:52
@lukegb:zxcvbnm.ninjalukegb (he/him)https://p.lukegb.com/MildlyDaringHoneybee.txt looks fine to me12:28:58
@lukegb:zxcvbnm.ninjalukegb (he/him)what attrpath are you trying to build?12:30:22
@k900:0upti.meK900Same one here12:30:57
@k900:0upti.meK900...that is weird12:31:02
@k900:0upti.meK900Is the CDN being weird again?12:31:11
@lukegb:zxcvbnm.ninjalukegb (he/him)You sure you don't have a magic extra nixpkgs input that's tracking master somehow? :P12:32:10
@k900:0upti.meK900I definitely don't12:32:21
@lukegb:zxcvbnm.ninjalukegb (he/him) What does e.g. curl -v https://cache.nixos.org/2zbj4ag44472w1g94k2fvzgp9i7jwwb9.narinfo get you? 12:34:07
@lukegb:zxcvbnm.ninjalukegb (he/him)Other dumb things: you haven't accidentally removed the cache.nixos.org binary cache?12:34:28
@k900:0upti.meK900Nope12:35:33
@k900:0upti.meK900It did fetch some things too12:35:39
@k900:0upti.meK900Just not all of them for some reason12:35:44
@moritz.hedtke:matrix.orgmoritz.hedtke
In reply to @lukegb:zxcvbnm.ninja
At that point you have a human doing the Hydra scheduler's job, and the time would be better spent fixing the scheduler, imo
I thought hydra would use the nix distributed builders feature and do something like nix-build something/release.nix -A something --dont-abort-on-failed-builds or would that not work?
12:41:57
@lukegb:zxcvbnm.ninjalukegb (he/him)Alas, it's not quite that simple12:48:44
@linus.heckemann:matrix.mayflower.deLinux Hackerman K900: the "advance-blocking set" for nixpkgs-unstable is pretty small, maybe try nixos-unstable instead? 12:49:16
@lukegb:zxcvbnm.ninjalukegb (he/him) Linux Hackerman: nixos-unstable won't block on Darwin at all, so that's probably not good advice for someone on Darwin 12:49:45
@linus.heckemann:matrix.mayflower.deLinux HackermanOh right never mind me, missed that bit of context, sorry12:50:03
@k900:0upti.meK900Yeah, I'm using nixos-unstable for my own boxes12:50:31

Show newer messages


Back to Room ListRoom Version: 6