worldofpeace changed the topic of #nixos-dev to: NixOS Development (#nixos for questions) | NixOS 20.09 Nightingale ✨ https://discourse.nixos.org/t/nixos-20-09-release/9668 | https://hydra.nixos.org/jobset/nixos/trunk-combined https://channels.nix.gsc.io/graph.html | https://r13y.com | 20.09 RMs: worldofpeace, jonringer | https://logs.nix.samueldr.com/nixos-dev
supersandro2000 has quit [Disconnected by services]
supersandro2000 has joined #nixos-dev
b42 has joined #nixos-dev
{^_^} has joined #nixos-dev
justanotheruser has quit [Ping timeout: 268 seconds]
thibm_ has joined #nixos-dev
thibm has quit [Ping timeout: 240 seconds]
rajivr has joined #nixos-dev
mmlb22 has joined #nixos-dev
jonringer has quit [Remote host closed the connection]
gchristensen has joined #nixos-dev
evanjs has quit [Ping timeout: 256 seconds]
costrouc has quit [Quit: costrouc]
<pmy_> Hi. I cannot find how nixpkg's git branches are managed. What's the release frequency of nixos-unstable?
<pmy_> siraben: What's the typical interval between two nixos-unstable releases? I cannot find it on that page.
JJJollyjim has joined #nixos-dev
<JJJollyjim> i b
<JJJollyjim> **i believe an attempt is made once per day
<JJJollyjim> but if any of the builds in the "tested" job failm
<JJJollyjim> *fail
<JJJollyjim> , there is no release that day
<{^_^}> Invalid command syntax
<JJJollyjim> (sorry, enter key is easy to press...)
<JJJollyjim> you can view the attempts here https://hydra.nixos.org/job/nixos/trunk-combined/tested
<JJJollyjim> ( pmy_ )
<pmy_> OK. That makes sense.
<samueldr> it's a bit more nuanced than that
<pmy_> I have been waiting for the next nixos-unstable for a week.
<samueldr> when there are issues breaking channels, they generally are found on the status page https://status.nixos.org/
<samueldr> sometimes it's a sequence of different problems that stopped the channel advancing
<samueldr> so yeah, it's a bit more nuanced than "once a day", what happens once a day is a new evaluation with whatever is on top of master at tha moment in time
<samueldr> whenever the tested job succeeds _and_ all packages have been tried to be built for a given evaluation, the channel will advance to that revision
<samueldr> so it is believable that the channel could advance twice in a day
<samueldr> but for evals launched a one or two days before
<samueldr> (if it had to rebuild the whole world, which we try to avoid)
<samueldr> there is no manual way to trigger a channel advance either
<pmy_> Indeed. Your explanation makes more sense.
<pmy_> Nixos-unstable has been stalled for 8 days.
mkaito has quit [Quit: WeeChat 2.9]
justanotheruser has joined #nixos-dev
abathur has quit [Ping timeout: 264 seconds]
Emantor has quit [Quit: ZNC - http://znc.in]
Emantor has joined #nixos-dev
cole-h has quit [Ping timeout: 264 seconds]
orivej has quit [Ping timeout: 256 seconds]
hplar has quit [Ping timeout: 260 seconds]
hplar has joined #nixos-dev
__monty__ has joined #nixos-dev
thibm_ is now known as thibm
orivej has joined #nixos-dev
<lovesegfault> zimbatm: could I bother you to update nix-flakes-insaller to a newer nixUnstable?
orivej has quit [Ping timeout: 260 seconds]
hugolgst has joined #nixos-dev
<srhb> https://nixos.org front page is 404 apparently
<gchristensen> cc garbas
<garbas> gchristensen: one sec.
<garbas> gchristensen: fixed. i didn't noticed the build was triggered by netlify
<garbas> this is now disabled. since we deploy to netlify via github actions
<garbas> gchristensen: you maybe hace some time to look at the status.nixos.org PR?
mkaito has joined #nixos-dev
mkaito has joined #nixos-dev
jonringer has joined #nixos-dev
<hugolgst> netlify`s definitely the best service ever
kfound has joined #nixos-dev
<{^_^}> firing: RootPartitionLowDiskSpace: https://status.nixos.org/prometheus/alerts
<ajs124> hm. how exactly does the tarball job work and why can it break like this: https://nix-cache.s3.amazonaws.com/log/74kfh3pc10y5iin2r6crplabd0ky6vq4-nixpkgs-tarball-21.03pre258838.85298db412b.drv
<Mic92> rycee: niksnut please also have a read of this RFC: https://github.com/NixOS/rfcs/pull/42
<{^_^}> rfcs#42 (by Infinisil, 1 year ago, open): [RFC 0042] NixOS settings options
emilazy has quit [Read error: Connection reset by peer]
emilazy has joined #nixos-dev
m1cr0man has quit [Ping timeout: 272 seconds]
evanjs has joined #nixos-dev
kfound has quit [Remote host closed the connection]
abathur has joined #nixos-dev
__red__ has quit [Ping timeout: 256 seconds]
bridge[evilred] has quit [Ping timeout: 264 seconds]
bridge[evilred] has joined #nixos-dev
cole-h has joined #nixos-dev
m1cr0man has joined #nixos-dev
<{^_^}> resolved: RootPartitionLowDiskSpace: https://status.nixos.org/prometheus/alerts
m1cr0man has quit [Ping timeout: 264 seconds]
<abathur> I could use feedback (from anyone, but also gchristensen and infinisil :) on a change to the resholve Nix API to support using different settings to resolve different script(s) in a single package. I don't recall seeing a pattern for this so I've gotten *creative*. https://github.com/NixOS/nixpkgs/pull/85827#issuecomment-747831206
<abathur> ^ adisbladis also relevant to your ?
m1cr0man has joined #nixos-dev
rajivr has quit [Quit: Connection closed for inactivity]
m1cr0man has quit [Ping timeout: 260 seconds]
<{^_^}> firing: RootPartitionLowDiskSpace: https://status.nixos.org/prometheus/alerts
m1cr0man has joined #nixos-dev
orivej has joined #nixos-dev
m1cr0man has quit [Ping timeout: 264 seconds]
m1cr0man has joined #nixos-dev
<ekleog> Hmm… just noticed `nix-shell` ignores `lowPrio`/`hiPrio` and just takes the executables from the first buildInput that provides it. Do y'all think it's a bug or a feature, or a bug that must be considered as a feature because backwards-compatibility?
<regnat> ekleog: dunno if it should be called a “feature”, but afaik that's the intended behavior: the priority attribute is specific to buildend/nix-env and not something that the rest of the ecosystem cares about
<halfbit> removing -g when building gcc removes the debug symbols from libquadmath such that libquadmath no longer has references to musl-dev, but libgcc_s still does which is... interesting
<halfbit> is libgcc_s built with gcc builder.sh as part of gcc, I'd assume so?
<ekleog> regnat: hmm ok weird, that definitely tricked me until I got what was happening :)
Cale has quit [Remote host closed the connection]
cole-h has quit [Quit: Goodbye]
thibm has quit [Quit: WeeChat 2.6]
kfound has joined #nixos-dev
<{^_^}> firing: RootPartitionLowDiskSpace: https://status.nixos.org/prometheus/alerts
kfound has quit [Remote host closed the connection]
__monty__ has quit [Quit: leaving]
<{^_^}> resolved: RootPartitionLowDiskSpace: https://status.nixos.org/prometheus/alerts
Baughn has quit [Ping timeout: 246 seconds]
Baughn_ has joined #nixos-dev
Baughn_ is now known as Baughn