<danderson>
is there a timeline on the next release these days? After doing a nix training on the current stable, I'm enthusiastic about not having to do that again, because the old tools are... well.
<michaelpj>
danderson: I think the next release will be 21.05, i.e. in May
<qyliss>
I think danderson was asking about Nix, given the previous conversation, not NixOS
<michaelpj>
oh right
<michaelpj>
that makes more sense!
<niksnut>
hopefully real soon
zarel has joined #nixos-dev
Jackneill has joined #nixos-dev
Jackneilll has quit [Read error: Connection reset by peer]
srk has quit [Remote host closed the connection]
srk has joined #nixos-dev
<lukegb>
bah! BAH! this build's dependency fetching process produces nondeterministic zip files
<gchristensen>
from where? iirc that is why we have fetchzip, to make it deterministic?
<lukegb>
it's inside buildBazelPackage, and it's a Python wheel that ends up being fetched
* gchristensen
feels sick
<lukegb>
wait, did I say "fetched" I meant "just sort of built while bazel is discovering its dependencies because it just runs pip"
<lukegb>
there's a better set of rules for doing that that aren't this chaotic but this project isn't using them yet :(
<__monty__>
Thanks. Had considered it for video conferencing with people who couldn't be expected to get software to work recently. Yet another reason to stay away.
<gchristensen>
zoom has essentially mastered that
<ekleog>
does zoom web video on firefox work nowadays? last I checked I could figure out the right sequence of clicks only with chromium, it never suggested them for firefox
leungbk has quit [Quit: ERC (IRC client for Emacs 28.0.50)]
<elvishjerricco>
I'm trying to figure out how to get systemd-cryptsetup to link against the main systemd derivation instead of its own copy of libsystemd-shared, so that it takes less space in my initrd. But if I just ln -s the original lib into the build directory, it still rebuilds it.
<elvishjerricco>
supersandro2000: Well the way systemd-cryptsetup-generator works is by using `pkgs.systemd.overrideAttrs` to build only the systemd-cryptsetup-generator targets of the systemd package (which are not built in the regular systemd derivation).
<elvishjerricco>
So I've tried just using ln -s to put the regular derivation's lib in the build directory of the overriding derivation. But it didn't work
<elvishjerricco>
Meanwhile, do we even use/support lvm2_activation_generator_systemd_red_hat? Because that's the only reason there would be a cyclic dependency between cryptsetup and systemd
<supersandro2000>
overwrite the overwrite to just use regular systemd?
<elvishjerricco>
supersandro2000: That's basically what I'm doing
<supersandro2000>
I didn't find it in the repo. Can you send a link?
<elvishjerricco>
supersandro2000: Oh. It's gone. I'm working on 20.09. I guess it's been removed since then
<elvishjerricco>
Er, oh I'm on 20.03. That's worse than I thought lol
<supersandro2000>
😂
<supersandro2000>
yeah than I can't really help you
<supersandro2000>
I am always on unstable
<elvishjerricco>
Ok so I'm going to head to unstable for this lol
<ajs124>
elvishjerricco: the lvm2 and a lot of systemd stuff changed quite a bit from 20.03. I can link you some relevant PRs, if you're interested, but basically, the systemd derivation ich much more modular now.