<immae>
So having a privilegeEscalationCommand will require making a correct "parsing" of arguments and transform them depending on the case
<siraben>
haven't been testing cross because of lack of cache
<immae>
(and it doesn’t solve the issue for binaries or programs that "explicitly" cal sudo)
tomberek has quit [Ping timeout: 240 seconds]
vcunat has quit [Ping timeout: 272 seconds]
TV is now known as tv
vcunat has joined #nixos-dev
<andi->
Was/Is the binary cache having troubles? Just had a 502 followed by 503s
TAZJIN is now known as tazjin
<siraben>
How would I do a graph query on nixpkgs like, "give me all x ∈ nixpkgs whose dependencies all compile on darwin but x itself does not have darwin in meta.platforms"?
vcunat has quit [Ping timeout: 258 seconds]
<andi->
I don't think we have that ability just yet. You could always look at hydra and try to wrangle that data into whatever you need.
<STERNI>
I think parsing derivations is your best bet maybe?
<STERNI>
oh, but then you don't have meta.platforms
<siraben>
So found the packages that with `buildInputs = []` but no darwin in the meta.platforms
<siraben>
I've thought of making some fancy graph viewer that would show the frontier of darwin-buildable packages and let you click the nodes (package expressions) to edit and fix
<siraben>
dunno but I feel like doing graph queries in nix lang ATM the most natural fit
<siraben>
s/ATM/ATM is
orivej has joined #nixos-dev
tilpner has joined #nixos-dev
iyefrat has joined #nixos-dev
<iyefrat>
how do i find out what is holding up the nixpkgs build so i can track the issue?
orivej_ has joined #nixos-dev
orivej has quit [Ping timeout: 245 seconds]
vcunat has quit [Ping timeout: 272 seconds]
orivej_ has quit [Read error: Connection reset by peer]
orivej has joined #nixos-dev
iyefrat has quit [Remote host closed the connection]
EDEF is now known as edef
vcunat has joined #nixos-dev
vcunat has quit [Client Quit]
PROFPATSCH is now known as Profpatsch
aminechikhaoui8 is now known as aminechikhaoui
<maralorn>
iyefrat: You go to status.nixos.org click on the "Hydra job for tests" of the channel you care about. Choose the latest failed build and look into the logs.
<sterni>
> WARNING: POSSIBLE DNS SPOOFING DETECTED!
<94KAAA9XC>
error: syntax error, unexpected '!', expecting ')', at (string):489:40
<sterni>
when will hydra support ANSI escape sequences (or filter them out) :p
<sterni>
(the answer is: when I send a PR)
<gchristensen>
siraben: unfortunately for the binary cache we can't accept contributions like that
orivej has quit [Ping timeout: 256 seconds]
orivej_ has joined #nixos-dev
<siraben>
gchristensen: I see. Are the darwin builders up?
<gchristensen>
siraben: at the top of https://hydra.nixos.org/ in the blue box is a link to grafana and a json dump called quue runner stats, poke around there and see if you can find the answers you're looking for?
<siraben>
gchristensen: Thanks
orivej_ has quit [Ping timeout: 256 seconds]
<sterni>
wait hydra does handle escape sequences for the eval errors log now?
<supersandro2000>
Can someone rename the bot? The new name is problematic
94KAAA9XC has quit [Remote host closed the connection]
{^_^} has joined #nixos-dev
<gchristensen>
,botsnack
<{^_^}>
Oh thanks, have a cookie yourself
srk has quit [Remote host closed the connection]
srk has joined #nixos-dev
<sterni>
{^_^} (~graham@NixOS/user/gchristensen)
<sterni>
graham of borg indeed
<gchristensen>
nrn
orivej has joined #nixos-dev
mkaito has joined #nixos-dev
jonringer has joined #nixos-dev
pmy has quit [Ping timeout: 264 seconds]
pmy has joined #nixos-dev
mkaito has quit [Quit: WeeChat 3.0.1]
tomberek has joined #nixos-dev
mkaito has joined #nixos-dev
orivej has quit [Ping timeout: 246 seconds]
<gchristensen>
what if there was a way to instruct nix to skip output scanning and assume it has no dependencies? it is a bit annoying to have ISOs / AMIs / etc. depend on the entire closure despite being a self-contained artifact
<gchristensen>
in some cases I've done very annoying things to "fix" this in nix: let ami = ...; encoded = runCommand "encoded" {} "base64 ${ami} > $out"; in runCommand "decoded" {} "base64 -d ${encoded} > $out"
<gchristensen>
this gets close but isn't a total fix: you still have references to stdenv
arcnmx has quit [Quit: Idle for 30+ days]
<ehmry>
this nix depenency on mdbook is nasty
<ehmry>
i'm trying to deploy some containers but I can't because they have to build some dipshit rust markdown parser
<sterni>
:|
<sterni>
ehmry: nix stable shouldn't depend on that right?!
<samueldr>
boolean inputs are not the only way to customize things
<sterni>
adisbladis: yeah, but you want some context what it does plus what kind of value it expects
<adisbladis>
Yeah, not saying this is remotely good enough
<samueldr>
especially given some derivations will change their behaviour on a missing dependency, so `.override({ zlib = null; })` could be customizing the build, rather than breaking it!
<sterni>
adisbladis: often you can guess by which functionArgs have a default value as per functionArgs
<sterni>
but it doesn't always work well
<sterni>
samueldr: yeah there is overall not a consistent style established for these kinds of things
<sterni>
which I guess could be a second step, but much harder because it breaks user's configurations
<samueldr>
I think the actual "solution" here is something that's been proposed
<samueldr>
a "callPackage2" where it works in two steps, one for dependency injection, one for configuraiton
<sterni>
yeah that would be pretty nice, since we could use functionArgs as a fallback then
tomberek has quit [Quit: Connection closed]
tomberek has joined #nixos-dev
<sterni>
what's the plan for the docbook we have in option descriptions btw?
<samueldr>
I don't know that there is a plan or not yet, but I assume it'll be changed at the same time the nixos docs will be
<samueldr>
which is not right now because of tooling issues as it requires a slim closure size since it is rebuilt on every generation for every user
<samueldr>
(but being worked on AFAIK)
ris has joined #nixos-dev
orivej has joined #nixos-dev
clever has quit [Ping timeout: 240 seconds]
clever has joined #nixos-dev
<ekleog>
unrelated to that, IMO the major thing missing “from the nix language” is ability to doc-comment functions
<ekleog>
even without changing callPackage2 it'd already allow us to document the derivation parameters
<sterni>
when I look at nixUnstable I doubt it's comming tbh
<sterni>
:doc is implemented in a way which really only works for builtins
<sterni>
but at least something like https://github.com/tazjin/nixdoc being established as the default™ and actively used would be great
<tazjin>
sterni: the manual uses that
<tazjin>
so it's sort of established, but it'd probably be great if someone else takes over the project and puts it in nix-community or something (unless that already happened and I missed it)
<sterni>
yeah, I just noticed
<sterni>
that's actually nice
<sterni>
doesn't seem like it yet
xwvvvvwx has quit [K-Lined]
orivej has quit [K-Lined]
<supersandro2000>
overriding with null should be just removed tbh
<supersandro2000>
along with ? null and assert not null
<sterni>
documenting overrides and removing such things could be done in a joint effort feasibly I think
<sterni>
? null is especially funny because it isn't even necessary in 90% of cases
<sterni>
because nix is lazy
<adisbladis>
tazjin: You wanna transfer it?
terrorjack has joined #nixos-dev
<samueldr>
sterni: why do you say `? null` isn't necessary?
<samueldr>
> callPackage ({ foobarbaz }: 1) { }
<{^_^}>
anonymous function at (string):489:14 called without required argument 'foobarbaz', at /var/lib/nixbot/nixpkgs/master/repo/lib/customisation.nix:69:16
<sterni>
samueldr: often you have patterns like { ...., foolib ? null, withFoolib ? false }:
<sterni>
samueldr: in which case you don't need foolib ? null because if you only conditionally add it to buildInputs it isn't evaluated anyways
<samueldr>
unless it's not part of the package set
<samueldr>
e.g. was removed in an overlay
<samueldr>
then it would fail as it's called without a required argument
<sterni>
how would you remove a package in an overlay?
<sterni>
self: super: builtins.removeAttrs [ … ] super ?!