gchristensen changed the topic of #nixos-dev to: NixOS Development (#nixos for questions) | https://hydra.nixos.org/jobset/nixos/trunk-combined https://channels.nix.gsc.io/graph.html | 18.09 release managers: vcunat and samueldr | https://logs.nix.samueldr.com/nixos-dev
orivej has joined #nixos-dev
<aszlig> samueldr: i'd say, we won't have the hasbang-regression when 5.0 is released, so you can probably tick that off your kernel regression list :-)
<samueldr> aszlig: :) progress?
<aszlig> err, that comment doesn't make sense
* samueldr waits for the edit
<samueldr> I think I understand what's wrong in the comment
orivej has quit [Ping timeout: 240 seconds]
<aszlig> updated
<aszlig> the first sentence was a bit "truncated" ;-)
<samueldr> yeah, that's because the change, AFAIUI, isn't "don't truncate the hashbang" but more "stop executing if it exceeds" right?
<aszlig> given that there are a bunchload of perl scripts out there, someone outside of nix(os) _will_ notice ;-)
<aszlig> yep
<aszlig> it has always truncated the hashbang
worldofpeace has quit [Remote host closed the connection]
<samueldr> we do have a longer initial segment to our hashbangs though
<samueldr> at least a bug report has been opened
<aszlig> which is why perl re-parses its own hashbang to allow multiple args and get around the length limitation
<aszlig> samueldr: yah, i also added a comment on that: https://bugzilla.kernel.org/show_bug.cgi?id=202497#c1
<samueldr> (yes)
<samueldr> though I'm somehow thinking it will make it to 5.0, since it's been there since -rc1 :/
<aszlig> samueldr: well, then it will be fixed in 5.0.1 :-D
<samueldr> :) that bug in particular wasn't bugging (heh) me, it's the whole new-lts-breaks-stuff that bugs me the most
<aszlig> at least compared to the overlayfs bug i'm pretty optimistic about a timely fix :-D
<aszlig> yep, dito
<aszlig> i mean, we could just revert the whole overlayfs refactor for 4.19
<samueldr> this sounds like a recipe for subtle bugs
<aszlig> but that's also "meh" and could also introduce new bugs
<aszlig> yep
* samueldr is thinking about our own subtle bug previously introduced
<aszlig> yeah
<aszlig> hm... i do have an idea though
<aszlig> we could use that revert *only* for nixos vm tests
<samueldr> I had that in mind, but I was dismissing the idea as "wrong", since it wouldn't test the real kernel
<samueldr> (though it might be less wrong than the half fixing)
<aszlig> like adding boot.kernelPatches to qemu-vm.nix
<aszlig> or just properly debug the issue
<aszlig> which would be the best fix
<aszlig> but i already spent 3 days debugging the issue and currently have a deadline on an entirely different project X-/
<samueldr> sure, you're doing great work already, and now that the message is out, it's less of an issue imho
<aszlig> samueldr: yeah, maybe we have a working patch by monday, who knows :-)
<aszlig> for our release we still have a month to go, so i'm also optimistic that the bug will be solved by then :-)
<gchristensen> fingers crossed
init_6 has joined #nixos-dev
init_6 has quit []
drakonis has joined #nixos-dev
q6AA4FD has quit [Read error: Connection reset by peer]
q6AA4FD has joined #nixos-dev
lassulus_ has joined #nixos-dev
lassulus has quit [Ping timeout: 272 seconds]
lassulus_ is now known as lassulus
pie__ has joined #nixos-dev
pie___ has quit [Ping timeout: 272 seconds]
init_6 has joined #nixos-dev
drakonis has quit [Quit: WeeChat 2.3]
init_6 has quit [Ping timeout: 245 seconds]
orivej has joined #nixos-dev
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-dev
orivej has quit [Ping timeout: 244 seconds]
init_6 has joined #nixos-dev
init_6 has quit [Ping timeout: 245 seconds]
flokli has quit [Quit: WeeChat 2.2]
flokli has joined #nixos-dev
init_6 has joined #nixos-dev
init_6 has quit []
init_6 has joined #nixos-dev
init_6 has quit []
__Sander__ has joined #nixos-dev
__Sander__ has quit [Quit: Konversation terminated!]
orivej has joined #nixos-dev
orivej has quit [Ping timeout: 250 seconds]
orivej has joined #nixos-dev
drakonis has joined #nixos-dev
orivej has quit [Ping timeout: 246 seconds]
orivej has joined #nixos-dev
copumpkin has joined #nixos-dev
orivej has quit [Ping timeout: 272 seconds]
aszlig has quit [Quit: Kerneling down for reboot NOW.]
aszlig has joined #nixos-dev
JosW has joined #nixos-dev
jtojnar has quit [Read error: Connection reset by peer]
jtojnar has joined #nixos-dev
<infinisil> What does #nixos-dev think of this? https://github.com/NixOS/nixpkgs/pull/51319#discussion_r253316734
<infinisil> dwm-status has by default some support flags enabled, resulting in a 100MB build, but this user seems to go for low closure size (can't blame them)
<gchristensen> I'm not real sure about the value of making a service for programs like dwm
<infinisil> Turning the flags off means Only 65MB, but the build isn't cached
<gchristensen> -status
<MichaelRaskin> Isn't dwm build pretty fast anyway?
<infinisil> MichaelRaskin: Yeah it's actually not too bad, but still, rust compiler, all dependencies need to be fetched and then compiled
<infinisil> gchristensen: Can be said about a lot of modules that get adde
<infinisil> d
<gchristensen> and I think it is worth sying :)
<infinisil> gchristensen: Feel free to comment. I figured if it's one user that wants it (and it's not something too odd), then probably more users want it too, and that's enough of a reason to be okay with adding it
<infinisil> for me to be okay*
<tilpner> Building dwm-status fetches 447MiB and takes 800% CPU for a while
JosW has quit [Quit: KVIrc 4.2.0 Equilibrium http://www.kvirc.net/]
orivej has joined #nixos-dev
drakonis has quit [Quit: WeeChat 2.3]
orivej has quit [Ping timeout: 246 seconds]
Synthetica has joined #nixos-dev
MichaelRaskin has quit [Quit: MichaelRaskin]