ekleog 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 https://r13y.com | 18.09 release managers: vcunat and samueldr | https://logs.nix.samueldr.com/nixos-dev
aszlig_ is now known as aszlig
drakonis_ has joined #nixos-dev
drakonis has quit [Ping timeout: 264 seconds]
drakonis_ has quit [Quit: WeeChat 2.3]
drakonis has joined #nixos-dev
<gchristensen> https://twitter.com/lynxislazus/status/1100598304143036416 "I've released squashfskit which creates reproducible squashsfs images."
<gchristensen> wonder why they wouldn't just upstream the commits
<samueldr> :/ curious too, but at a glance, the squashfs project seems... lacking a bit in polish; their website states the latest release is 4.2 (2011), while the linked download page has a 4.3 release (2014)
<gchristensen> ..neat
pie__ has joined #nixos-dev
pie___ has quit [Ping timeout: 250 seconds]
drakonis has quit [Quit: WeeChat 2.3]
MoreTea has quit [Quit: WeeChat 1.9]
MoreTea has joined #nixos-dev
<ekleog_> well, the good thing is it's GPLv2, so at least in theory anyone can upstream those commits
<domenkozar> last hour for weekly content :)
johanot has joined #nixos-dev
<domenkozar> gchristensen: staging was merged, time to update r13y? :)
<Taneb> Is there a "things that need to be fixed up for 19.03" issue?
<srhb> domenkozar: lgtm
<srhb> Is the number (4) right though?
<srhb> Ah, looks like it.
<etu> domenkozar: looks good
<Profpatsch> qyliss: define -s fzf_opts "--reverse"
<Profpatsch> Ooooh, haha, I wanted to ask why there’s fzf *and* opts, because that doesn’t work with define.
<Profpatsch> But your diff underlined everything, so it hid the underscore.
<manveru> domenkozar: i'd say "Please take a look and give it a try"
<domenkozar> manveru: for static nix?
<manveru> for the printer
<manveru> it says "give it a test" atm, not sure if that's normal english?
<domenkozar> ah, yes.
<domenkozar> will fix
<manveru> otherwise it looks fine :D
<manveru> thanks for doing this
<manveru> really curious if i can get my printer to work with this now... it requires some hand-patched C code and netcatting it to port 911 of my printer atm :P
<domenkozar> yw :)
<domenkozar> I just don't print :D
<domenkozar> haven't needed it in last few years
<domenkozar> actually last time in itally
<domenkozar> for the ferry, they wanted a printed ticket, so I lost 1h finding a way to print it :)
<manveru> i sometimes print english/german/math exercises for my son
<manveru> my wife uses it more, since she's a designer, but she's on windows anyway :|
<domenkozar> ah school, yes
<Taneb> I ought to re-set up my printer
<Taneb> Didn't unpack it when I moved last March
<averell> also "With an one-liner shell..."
<domenkozar> too late :)
<domenkozar> and that was a real weekly!
asymmetric has quit [Ping timeout: 258 seconds]
init_6 has joined #nixos-dev
asymmetric has joined #nixos-dev
asymmetric has quit [Ping timeout: 264 seconds]
<arianvp> anybody experiening heighted levels of errors from nix cache?
<arianvp> getting 503s every once in a while
<arianvp> today
<Taneb> ...that's not idempotent, that's "has an attractor"
<Taneb> Wrong channel, sorry
<ivan> on master I think 81fa512bd82b5a856e0383c4930e8312bff644fb broke filezilla, can someone test
<ivan> checking for pugixml.hpp... no
<ivan> configure: error: pugixml.hpp not found. If you do not have pugixml installed as system library, you can use the copy of pugixml distributed with FileZilla by passing --with-pugixml=builtin as argument to configure.
<gchristensen> domenkozar: will do!
<gchristensen> had to fix up some libguestfs stuf :/
<domenkozar> exciting :D
asymmetric has joined #nixos-dev
johanot has quit [Quit: WeeChat 2.2]
scientist has joined #nixos-dev
<scientist> hello guys, I was wondering if you guys could help me with something
scientist has quit [Quit: WeeChat 2.2]
<gchristensen> huh, the minimal ISO expanded by 30 paths
<domenkozar> r13y?
<gchristensen> yea
<gchristensen> 1245 -> 1271
<domenkozar> 3% inflation
<domenkozar> seems legit
<simpson> Is that an overall improvement or backslide in terms of reproducibility, though?
<gchristensen> mmm neither
orivej has quit [Ping timeout: 250 seconds]
asymmetric has quit [Remote host closed the connection]
asymmetric has joined #nixos-dev
<aminechikhaoui> hm weird issue: NixOS 18.09 kernel 4.19.24 my enterprise corporate wifi works, with NixOS 19.03 4.19.25 doesn't connect to the wifi, downgrading to 4.19.24 also doesn't work
<aminechikhaoui> issue is the same as: https://bugzilla.kernel.org/show_bug.cgi?id=202521
<aminechikhaoui> but maybe I'm missing something in the downgrade
<aminechikhaoui> I just did http://ix.io/1C9Y
<samueldr> enter cynicism: another patch that got machine learned to a backport?
<aminechikhaoui> but this is the same kernel version working with 18.09 and not working on 19.03
<aminechikhaoui> so I'm probably missing something
<samueldr> if instead of downgrading you go to the generation that worked? (though I guess the generation is long gone?)
<aminechikhaoui> now I'm back to 18.09.2247.3276e04a39e which is the one that works
<aminechikhaoui> but the 19.03.* ones are the ones breaking the enterprise wifi connections so far on 4.20.x 4.19.25 and 4.19.24
<samueldr> 18.09 should also have received the upgrade, does it fail too?
<samueldr> (if it doesn't, then it maybe points towards something else than the kernel, that got upgraded)
<yorick> arianvp: yes, same
<aminechikhaoui> ah I think I didn't pull the latest for 18.09
<aminechikhaoui> lemme do that
init_6 has quit [Ping timeout: 250 seconds]
<aminechikhaoui> samueldr ok so 18.09 with 4.19.25 seems to work so likely not a kernel issue I guess
<samueldr> if you had 4.19.24 failing, too, on 19.03, it points to it not being the root cause
<samueldr> I don't have any more insight, other than "bisect it" which is... not always fun :/
init_6 has joined #nixos-dev
<aminechikhaoui> yeah :)
<domenkozar> network manager?
<aminechikhaoui> yeah I'm using network manager
<domenkozar> there were quite a few bumps there
<Profpatsch> Uh-oh, people started complaining about the cache on Twitter: https://twitter.com/pimiddy/status/1100718725119045633
<Profpatsch> Is that something about HTTP 50x errors which nix is not prepared to handle?
<samueldr> yeah, the other day I was asking about it because it felt like some background signal that *could* give the infra a bad look :/
<samueldr> other than failing, how should it handle 5xx errors?
<srhb> Does 50x get registered as a negative cache lookup?
<srhb> If so, people might be getting the 60 minute problem.
<samueldr> (though even worse are the 2xx with incomplete downloads)
<simpson> Can we make it more obvious how to compile without cache?
<samueldr> last time I had 5xx errors it cleared up in like one rebuild
<srhb> samueldr: Ok, no negative cache on it then, that's good.
<aminechikhaoui> I thought nix auto retries 5xx errors
<arianvp> It auto-retried
<LnL> yeah, s3 5xx should be retried with backoff but I thought that nix already did that
<LnL> unless it's only for the actual s3 implementation
orivej has joined #nixos-dev
<aminechikhaoui> I think it's at the libcurl downloader level, but those improvements are only in nix>=2.0 afaik
<averell> these 503 errors happen with the latest nix too, and manual retry makes them go away.
<gchristensen> I wish we could just go back to cloudfront
<Profpatsch> Oh, that’s Server overloaded
<Profpatsch> Yeah, figures, hydra doesn’t implement that.
<gchristensen> `nix` doesn't talk to hydra
<Profpatsch> But what should nix do in that case. Start building from scratch?
<Profpatsch> yeah, it’s coming from the cache provider
drakonis has joined #nixos-dev
init_6 has quit [Ping timeout: 258 seconds]
<LnL> gchristensen: hmm, it's fastly and not s3 that's returning the errors?
<gchristensen> yeah, think so
<LnL> oh, that's pretty bad :/
drakonis_ has joined #nixos-dev
drakonis has quit [Ping timeout: 250 seconds]
drakonis_ has quit [Read error: Connection reset by peer]
drakonis_ has joined #nixos-dev
drakonis_ has quit [Read error: Connection reset by peer]
drakonis_ has joined #nixos-dev
drakonis has joined #nixos-dev
drakonis_ has quit [Ping timeout: 258 seconds]
yl has joined #nixos-dev
janneke has quit [Quit: janneke quits Mes'sing]
janneke has joined #nixos-dev
ekleog_ is now known as ekleog
<arianvp> Should we file a ticket with fastly?
<gchristensen> I have anongoing thread with them, I'll mention it with them again
asymmetric has quit [Ping timeout: 268 seconds]
<manveru> for some reason this never happened to me, afaict
<LnL> yeah, same and a quick read seems to indicate requests are retried 5 times except for some special cases I assume are not relevant here
lopsided98_ is now known as lopsided98
<averell> fwiw i have that happen on hetzner, and the tweet guy above is german too
drakonis_ has joined #nixos-dev
drakonis has quit [Ping timeout: 259 seconds]
<aminechikhaoui> samueldr ok so I think 3f0a59314cf9f2ce2cb28be47b835854f6f459a9 probably introduced the issue with enterprise wifi connections
<aminechikhaoui> wpa_supplicant update from 2.6 ->2.7
<samueldr> a recent nixpkgs with it reverted to 2.6 works?
<aminechikhaoui> yeah I basically did `git checkout b5c1deca8ade2771851598b460a9c0e9fc0500fb pkgs/os-specific/linux/wpa_supplicant/` on a release-19.03 branch
<aminechikhaoui> and rebuild with it
<aminechikhaoui> that revision is the one prior to the update
drakonis has joined #nixos-dev
drakonis_ has quit [Ping timeout: 255 seconds]
orivej has quit [Ping timeout: 244 seconds]
<aminechikhaoui> samueldr reverting the patch seems to make work again
<aminechikhaoui> what's your opinion, should we report upstream or add a patch in such cases ?
<aminechikhaoui> or both :)
<samueldr> the former (reporting) will always be: yes!
<samueldr> also open and link a nixpkgs-side issue with links
<samueldr> as for a patch, eek, I can't tell without being familiar with the codebase :/
<andi-> wpa_supplicant is almost as bad as grub in releasing new versions. I think most people that use recent wpa_supplicant versions apply a bunch of newer patches from the original source tree..
<aminechikhaoui> yeah me neither, just seems to work with my experiments but might break other things
<samueldr> last time I agreed to a patch I subtly broke overlayfs in nixos unstable, so I won't judge here
yl has quit [Ping timeout: 244 seconds]