00:58
<selfsymmetric-mu>
I have two files called `mermaid.css` and `mermaid.json`. I want to wrap up `mmdc` and pass those two files as arguments. But I need to get them into the nix store first. How do I get them there? https://hastebin.com/raw/hexelokaye

01:21
<c00w>
The simple answer is that their go.mod file isn't fully correct - right now the best way to fix this is to clone the repo, run `go mod tidy` then `go mod install -mod=vendor` (to confirm it works), and then git diff --patch and check the patch into nixpkgs and in the derivation.

01:41
<bhipple>
I mean across all of Nixpkgs: I'm building with a bunch of air-gapped builders that can hit Artifactory, but not the standard gopkgs endpoints; Artifactory has those mirrored, but I'd like to tell the builders to talk to Artifactory instead of golang.org et all

01:43
<bhipple>
Right, that's what I've done, but we turn it off in NixPkgs -- so when I do it, it blows the hashes on everything. Altho maybe I need to just look at it more closely, because we should be building FODs ...

01:43
<c00w>
I think you can just do something like overrideModAttrs = ( _: {

01:45
<bhipple>
That'd make my overlay a little less invasive, because I could just add my mirror to mirrors.nix without hacking up the golang builder

01:46
<quinn>
so i'm using pulseaudio with sway, and though my DBUS_SESSION_ADDRESS is set inside of sway, it's not accessible to my pulseaudio service (/proc/$pulse_pid/environ). any thoughts on why that is/how i might go about fixing it

02:50
<quinn>
selfsymmetric-mu: sorry, i'm only looking at the end of this. if you're fetchUrling your <head> and you have the sha256 of the old head, nix will just used the cached fetchUrl with the old sha256

02:50
<quinn>
without reading through that quirk may be relevant, sorry if it isn't

02:50
<quinn>
c00w: that's fine. i was really excited when you mentioned extraConfig though (:

03:08
<energizer>
> After a number of rounds of review the discussion should settle and a general consensus should emerge. This bit is left intentionally vague and should be refined in the future. We don't have a technical commitee so controversial changes will be rejected by default.

08:06
<DamienCassou>
We are 2 users of NixOS on 2 recent Lenovo Thinkpad laptops. In both cases, our battery performance as decreased massively in NixOS. My own laptop is 3 weeks old and the battery lasts 2h instead of 6h.

08:38
<tom39291>
Hey, this'll sound ridiculous, but I've been a happy NixOS user for 5+ machines for 2+ years, and I have no idea how to evaluate/build/instantiate a nix expression/derivation if it's not part of nixops or nix-shell. I'm ~ok with Nix the language, but unfamiliar with conventions around importing lib/pkgs/nixpkgs and attrPaths. Can anyone suggest a resource for understanding these?

10:02
<fendor__>
Hi! Installed nixos, booted into the usb via nomodeset since the gfx is not supported by default, installed nixos and then installed the graphics drivers via videoDrivers = ["nvidia"];

10:03
<fendor__>
but I get random freezes in KDE and the terminal, until keyboard and mouse become unresponsive altogether

10:03
<fendor__>
how can I debug that? I can boot with the initial boot config and nomodeset just fine and there are not freezes there

13:22
<evils>
infinisil: well, i was a bit hesitant to do a staging PR in the first place because i've never done that, and nix-review took less than an hour, but with the second PR, wouldn't using staging save a bunch of rebuilding?

13:24
<infinisil>
I'm not too involved with the staging process, but from what I understand, it's a pain to merge it into master. There can be conflicts, build problems, etc. And the more commits went to staging, the more difficult it gets to track down how to solve it

13:25
<evils>
ah, i thought it was close to master but built less often

13:27
<infinisil>
The reason for staging (again from what I understand) is to not cause stdenv rebuilds on master (meaning on master most things should be cached), and to bunch together changes that cause mass rebuilds (so multiple mass rebuild changes only cause one)

13:28
<evils>
well, bunch together mass rebuilds is the reason i thought it'd be a good idea to do the two asciidoctor PRs to staging, but apparently "the biggest rebuild i've done" doesn't count as a mass rebuild xD

13:28
<infinisil>
Considering there are like 20k-30k packages in nixpkgs, with a couple PR's that change 100s of packages, the overlap between them is probably rather slim, meaning no rebuilds would be saved

13:31
<evils>
bqv: but my PR is a small fix, and the other one increases the asciidoctor closure size by 40M; one's very likely to be merged, the other needs some review i think

13:31
<turion>
How do I start a nix repl in a nixpkgs tree such that I get all the packages in scope?

13:31
<infinisil>
I've had this idea before: We could have multiple levels of staging branches, and each level gets a different amount of rebuilds. E.g. 10k+ rebuilds go to the first level, 1k+ to the second one, 100+ to the third one

13:57
<supermarin>
Hi there, a somewhat noob question: yesterday I wanted to build neovim from source. Instead of installing all the deps on my main OS (macOS), I wanted to make a shell.nix file and include everything needed to build neovim in there, then use nix-shell --pure. I think using --pure is what I want, since I don't want any macOS-provided stuff involved

13:57
<supermarin>
in the build. Now the problem: I was expecting that a simple package override would work (use the same formula as nixpkgs uses, and override sources). I've also tried with stdenv.lib.overrideDerivation. My question is: Am I doing something horribly wrong, or neovim's formula is just written in a non-standard way so the standard nix practices

14:02
<supermarin>
iclanzan eventually i was able to build it without --pure, but when I launch it there's a bunch of lua errors (some lua deps are missing). but definitely not satisfied with how much i was ductaping.

14:02
<supermarin>
the problem with --pure i didn't know how to solve is, some of the lua makefiles are using `sw_vers` which is a macOS binary

14:03
<supermarin>
and doesn't have a nix package you could include as a buildInput

14:03
<chris_>
Is it possible to mount a direct partition / drive to qemu using the `vm` module (I assume)? It seems qemu needs a `-hda` parameter passed to it, but I don't see it mentioned anywhere in the nix file.

14:21
<turion>
I just wanted to write to the Agda mailing list that packaging Agda has just become easier because there is now good Agda support in nixpkgs. But I can't even find a good oneliner to simply install agda together with a standard library

14:22
<turion>
I mean, a oneliner so that people won't think I'm making a bad joke when I write "Installing Agda and some libraries has just become simpler!"

14:29
<turion>
Agda is a fantastic programming language from a theoretical perspective, but unfortunately all the boring software engineering aspects like package management weren't the focus when the language was developed. Afaikt, there is no real package manager, and you have to do that by hand usually. I was hoping that the agda infrastructure in nixpkgs could step in to serve as the same role that stackage plays in the Haskell ecosystem.

14:29
<turion>
So if there is an ergonomic oneliner how people can install agda with some libraries using nix, that's an advancement.

14:46
<turion>
Agda libraries were hard before because it required people to keep a text file with paths of downloaded repos up to date. Now we're doing a bit better in nixpkgs by automating the downloaded repo part.

15:25
<turion>
I guess I haven't given https://github.com/agda/agda-pkg enough credit in the whole Agda package management rant. So maybe nixpkgs should first interoperate with that before announcing the solution to all problems

15:41
<gordon>
i’m building a derivation for a qt app, it builds, it runs in the nix-shell, but outside, in my standard environment, it fails with `qt.qpa.plugin: Could not find the Qt platform plugin "xcb" in ""`

15:42
<gordon>
but my QT_PLUGIN_PATH is the same in both environments :|

15:51
<colemickens>
Firefox 74 ships new MOZ_DBUS_REMOTE env variable and it forces Firefox on X11 to use D-Bus remote protocol as well as Wayland version does. So when X11 Firefox is launched after Wayland one with the same profile, already running Wayland instance is reused to open the link instead of the “Close Firefox” greetings.

15:52
<colemickens>
That sounds like something else is still wrong then.

17:37
<Baughn>
gchristensen: I think you said you were using Sway... mind if I pick your brain for a second? Firefox is lagging out, and I wonder if that's a *known* problem. It does seem to be sway-specific, but I can't find references.

17:38
<T0pH4t>
is it possible to modify the packages passed to a module in a container? For example I might have containers.foo = { config = {config, pkgs, ...}: services.foo = {...} }. foo is a standard custom module, is it possible to modify the pkgs it uses to include some of my own?

18:14
<evils>
colemickens: no offense taken, i was under the impression i tried setting the env var (by way of `env ... firefox`) (i'm not very familiar with setting stuff like this) which is why i'm trying to make sure by messing with the wrapper

18:15
<emily>
wonder what a better term would be. "build-in-(instantiation|evaluation)"?

18:24
<srhb>
emily: Though I think v2 is the only one with proper completions for non --option style

18:24
<Fare>
Hi. I have an "interesting" problem with #!-interpreted #!-interpreters -- this works on Linux, but not on macOS. Using env as a shim works on macOS but fails on Linux in Docker because of a 128-char #!-line limitation. Using /usr/bin/env generally works, but apparently not if the binary is used during the nix build. Sigh.

18:25
<srhb>
Fare: Did you hear about that time Linux broke all of NixOS? :-)

18:25
<Fare>
Is it possible to for /usr/bin/env to exist while building? After all, it's a standard path defined in POSIX that even NixOS provides.

18:25
<emily>
srhb: v2 as in nix(1) or the nix- commands in 2.something?

18:37
<ajs124>
bdju: you can use `nix why-depends` or some tool like that

18:38
<lunik1>
and I don't know if libarchive is used as the default tar in any other BSD than Free, so maybe not those either

18:39
<bdju>
ajs124: how do I find out how to use this? `nix why-depends p7zip` doesn't work, doing pkgs.p7zip didn't work either. Says more arguments are required, but can't think of what else I'd add.

18:39
<ajs124>
you need to pass it two... drvs? I think. someone here probably knows how to use it, but I'll go see if I can find some documentation.

18:41
<bdju>
also, I don't know what two to pass it, I just want p7zip removed, I *think* mulitbootusb needs it, but commenting out both doesn't get me anywhere, so then I don't know how I would then go on to see if anything else needed it if I need two files listed

18:41
<ajs124>
ah, so wait. you have p7zip in you system or home-manager or where?

18:42
<bdju>
ajs124: p7zip is in my home.nix for home-manager, I can't update because of it, but removing it from my file also isn't working.

18:42
<bdju>
I do everything declaratively so it should just look at the list, see it's gone, and move on... not so simple, I guess.

18:42
<Fare>
Aha, Docker inherits the kernel from outside, so on my machine I have the NixOS kernel and everything's fine, but on Gitlab, they use one of these kernels with tighter #!-line limitations and I can't #!/...coreutils...env /full/path/to/nix/stuff

18:43
<ajs124>
bdju: then you can probably do nix-store -q --tree $HOME/.nix-profile

18:43
<lucksus>
Hey folks, I'm trying to cross-compile my Rust project to Android using a nix-shell (on Ubuntu host) with `crossSystem`, and I'm running into the exact same problem described and patched here: https://github.com/NixOS/nixpkgs/issues/56156. I tried to apply the same patch using an overly but no matter what I do, it seems the overlay doesn't apply to

18:43
<lucksus>
the LLVM pulled in by crossSystem. And I can't find comprehensive documentation for crossSystem, like how to set the LLVM version used etc. Any help or link to docs would be very appreciated!

19:26
<bqv>
Weird question, do you guys think it'd be possible to make a docker quine? :D I.e. A docker image that when spun up, starts another docker daemon inside and spins itself up as an image on it

19:48
<simpson>
balsoft: Due to *interpretative overhead*, I would be surprised if you can get 256 layers deep. Empirically, we know that each time we nest an interpreter, we get a multiplicative factor of a slowdown, and that factor is roughly constant, so that the overall slowdown is exponential.

19:48
<lassulus>
how do I get python2Packages.matplotlib and python2Packages.wxPython into the same env? if I run: nix-shell -p '(python2.withPackages (pp: [ pp.wxPython pp.matplotlib ]))' I get: collision between `/nix/store/riixmkhlx39af12libb31154p19h4f81-python2.7-backports.ssl_match_hostname-3.7.0.1/lib/python2.7/site-packages/backports/__init__.py' and

19:54
<simpson>
And, to be on-topic, this is why IFD is so practically useful compared to recursive Nix: The latter is *way* harder to get right, because of the arbitrary nesting of calling Nix while calling Nix.

20:49
<aswanson>
I just switched my nix-channel over to 20.03, and now when I try to `nixos-rebuild` I'm getting errors about the perl interpreter missing a `perl530` attribute and the python default.nix not knowing what `callPackage` is

21:36
<bqv>
both are problematic (the former could be replaced by writeShellScriptBin and the latter is layers of superfluous stuff)

21:36
<aswanson>
cole-h: I've tried disabling my install of inetutils since a grep of nixpkgs showed that it had a depency on help2man, and the wireguard kernel module I had enabled, but no dice so far

21:48
<aswanson>
cole-h: I don't think I have any overlays on this system, but I also have half a dozen abandoned projects or tweaks lying around so who knows. Thanks for the assist, but I'll revisit this another day

23:44
<palo>
I'm updating to 20.03 (from 19.09) and I get a messagt that my cargoSha is not correct (for some of my packages) but when I try to build (nix-build) I always get the same sha, also when I set it to 1111.. and run nixos-rebuild switch I get the same sha as 'got: sha256'