<disasm>
ma27[m]: are you creating a PR to remove nodejs 11?
<disasm>
I'm thinking since upstream hasn't fixed this yet we release without https://github.com/NixOS/nixpkgs/pull/68529 and can always cherry pick a patch in post-release when upstream is fixed.
<Taneb>
Or at least, the current user's profile *before* root's
<Taneb>
As it stands it doesn't seem like there's a way for a user to set their own channels on multi-user nix-on-other-Linux
__monty__ has joined #nixos-dev
FRidh has joined #nixos-dev
psyanticy has joined #nixos-dev
<worldofpeace>
When it comes to the 19.09 release, I'm still not very pleased with having issues like #65399 and #68314 all having to be solved case by case. And you can only tell there's an issue at runtime. This turns into this thing, for a lot of users, stuff just being broken in the latest release whereas before it worked and they relied on it. Frequently I see people doing the "wait and see it gets fixed" instead of opening
<aminechikhaoui>
there is a ton of changes since the last working commit
<gchristensen>
how about between last working and first failing?
<aminechikhaoui>
gchristensen not sure if we store the eval inputs if it fails
<gchristensen>
ah...
drakonis_ has quit [Ping timeout: 265 seconds]
<aminechikhaoui>
gchristensen I wonder if NIX_SHOW_STATS=1 would be useful to bisect, there is a gc.heapSize/totalBytes but I don't know if that's relevant
<Taneb>
I'd imagine there's useful info lurking in the hydra-evaluator logs
<Taneb>
gchristensen: did you see my notes about failing 19.09 builds from earlier?
<{^_^}>
#69365 (by arianvp, 1 week ago, open): update-users-groups.pl is broken when running NixOS tests interactively
<arianvp>
currently I cannot run any nixos tests on master interactively. They all fail
<arianvp>
and have been so for the last week or so.
<niksnut>
arianvp: maybe try deleting the VM state?
<arianvp>
aaaah
<arianvp>
there is state?
<arianvp>
where can I find that?
<niksnut>
sounds like you have a corrupt (zero-filled) state
<arianvp>
that sounds very plausible. where are those state files stored?
<niksnut>
i.e. /var/lib/nixos/declarative-* contains zeros
<niksnut>
iirc, /tmp/vm-state-<machine-name>
infinisil has quit [Quit: Configuring ZNC, sorry for the joins/quits!]
<niksnut>
there is a QCOW file in there containing the VM's filesystem
<arianvp>
aha
<arianvp>
thanks so much. that's probably it :)
<arianvp>
will try tomorrow
<drakonis_>
i have to ask it again, now that the flakes PR for nixpkgs is available, i can't figure out how to flip the unfree flag for building the system
<drakonis_>
seems like i'm out of my weight class here
infinisil has joined #nixos-dev
<niksnut>
drakonis_: you can't (at least not from the command line)
<drakonis_>
i'm trying to alter the flake to get it to work
<niksnut>
because you can't pass configuration to a flake to ensure hermetic evaluation
<niksnut>
you can however import it from another flake and pass config.allowUnfree or something like that
<drakonis_>
i'm trying to figure out how to achieve that
<niksnut>
something like this:
<niksnut>
packages.spotify = (import nixpkgs {
<niksnut>
}).spotify;
<niksnut>
config.allowUnfree = true;
<niksnut>
system = "x86_64-linux";
<drakonis_>
ah, interesting, okay, i'll try that out.
<drakonis_>
thank you very much.
<niksnut>
or in a nixos config, 'nixpkgs.config.allowUnfree = true;'
<drakonis_>
huh, well, i feel silly now.
<niksnut>
well, it's something of an unresolved UX problem
<niksnut>
how to do this on the command line
<drakonis_>
i think that could be resolved by adding a option that allows you to set "acceptable" licenses
<drakonis_>
default to including all free software, as is today, offer the ability to include nonfree software
<drakonis_>
and cherrypicked licenses
<infinisil>
There's also allowUnfreePredicate btw
<drakonis_>
never heard about that one
<drakonis_>
ah, is this for individual packages?
<delroth>
before I spam the PR list further, is there a better process for making a change to {master,19.09,19.03} than creating 3 individual PRs? I could rely on whoever merges it to properly do the backport, but I've had a few missed in the past and since these are one-off security changes I'd prefer to not have to babysit each of them too much.
<drakonis_>
so it is.
<infinisil>
drakonis_: Yeah, it's a function :: Derivation -> Bool
<samueldr>
delroth: in my experience this would be the way to go, if you don't want to rely on the merger to do it; cross-referencing them properly is a must though
<delroth>
ok, I've been doing that
<samueldr>
and thanks for the contributions :)
<delroth>
the 19.03/19.09 link to the master one (if any)
justanotheruser has quit [Ping timeout: 240 seconds]
<infinisil>
delroth: There's the @NixOS/backports team you can ping
<infinisil>
Not sure how well that works though
<delroth>
do I do that preemptively? or once merged?
<samueldr>
though as of right now it only pings 2 persons
<samueldr>
(feel free to add yourselves to the team)
<samueldr>
(those who can)
* infinisil
checks if he can
<samueldr>
delroth: I've seen it preemptively
<delroth>
(and I don't mind creating the extra PRs if it makes it easier to apply the backports, it's just a bit of a clutter in the PR list)
<samueldr>
what I like from the backports PRs is that ofborg will run
<samueldr>
the usual "just cherry pick and push" won't
<delroth>
that's a good point
<samueldr>
so it's easy to accidentally push something that won't
<samueldr>
won't build*
<infinisil>
"Membership requested. We’ll let you know once an administrator has reviewed your request."
<infinisil>
samueldr: I'm guilty of that
<samueldr>
weird, I thought this was freely joinable by people in the orga
* samueldr
is not used to github teams
<gchristensen>
we could probably add a "teams" list to the maintainer file
cjpbirkbeck has quit [Quit: Quitting now.]
justanotheruser has joined #nixos-dev
<worldofpeace>
I've also requested to be a part of the backports team, I already perform a lot of them.
<samueldr>
worldofpeace: approved
<samueldr>
github doesn't put that in the site-wide notifications though :/
<gchristensen>
yeah :/
<gchristensen>
https://twitter.com/grmpyprogrammer/status/1179495194997252103 is looking to switch to nixos tomorrow. firefox stable being available is a deal-breaker. maybe should let them know to wait until 19.09? looks like 19.03 doesn't have the latest ff yet
<emily>
you can also just use the mozilla overlay / mozilla's binaries
<gchristensen>
ah yeah
<gchristensen>
speaking of 19.09, how are we coming on that?
<worldofpeace>
TBH, don't think it would be ready this week
<gchristensen>
no worries
<worldofpeace>
right, just think there's regressions to fix, security leads, etc.
<infinisil>
gchristensen: firefox stable being s/available/unavailable I assume?
<gchristensen>
hm?
<infinisil>
gchristensen: You wrote "firefox stable being available is a deal-breaker"
<gchristensen>
ah right
drakonis_ has quit [Ping timeout: 240 seconds]
<worldofpeace>
we really need someone to review/integrate #70027. if fixes the ova test unblocking unstable