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
<Mic92> Ericson2314: some stuff maybe could be in nix, but not all of it. However a userspace program might be suitable: I once did something similar for interactive usage: https://github.com/Mic92/x86_64-linux-cheatsheats#introspect-libc
<gchristensen> oh very cool Mic92
<Mic92> quiet useful for people using: https://github.com/iovisor/bcc
<Ericson2314> oh, nice!
<Mic92> that is the cooler variant though: https://github.com/inspector-repl/inspector
<Mic92> but nobody likes to compile clang from source.
<gchristensen> speaking of clang, could I nerd-snipe you in to trying to make rust's bindgen's middling C++ support work with Nix? :P
<Mic92> gchristensen: it does not?
<gchristensen> I haven't successfully done it, but that doesn't mean very much
<Mic92> bloody w3m.
<Mic92> it wants a host generator too.
asymmetric has quit [Ping timeout: 250 seconds]
<Mic92> even worse then w3m is nginx
<gchristensen> :
<gchristensen> o
<Mic92> and nginx compiles
pie__ has joined #nixos-dev
pie___ has quit [Remote host closed the connection]
sir_guy_carleton has joined #nixos-dev
<ekleog> zimbatm: done :) (for the nixos weekly entry for RFC36)
<samueldr> would a sparse file of 304MB, but apparent size of 4.1GB be over hydra's limit of 2GB?
<gchristensen> shouldn't..?
<gchristensen> Ithoughti t looked at actual bytes
<samueldr> nix path-info -S prints the apparent size
<samueldr> (I'm now looking at build-remote.cc)
<gchristensen> ...huh ....
<samueldr> one example derivation is libguestfs-appliance
<samueldr> (and I'm thinking it does use the apparent size since it's disabled for hydra builds)
pie___ has joined #nixos-dev
aszlig has quit [Ping timeout: 244 seconds]
<samueldr> so yeah, looks like it's apparent size
pie__ has quit [Ping timeout: 268 seconds]
aszlig has joined #nixos-dev
sir_guy_carleton has quit [Quit: WeeChat 2.2]
lassulus_ has joined #nixos-dev
lassulus has quit [Ping timeout: 245 seconds]
lassulus_ is now known as lassulus
Lisanna has joined #nixos-dev
jtojnar has quit [Quit: jtojnar]
Lisanna has quit [Ping timeout: 250 seconds]
Lisanna has joined #nixos-dev
Lisanna_ has joined #nixos-dev
Lisanna has quit [Ping timeout: 245 seconds]
garbas has quit [Ping timeout: 250 seconds]
Lisanna_ has quit [Remote host closed the connection]
Lisanna has joined #nixos-dev
NKataDelYoda has joined #nixos-dev
garbas has joined #nixos-dev
NKataDelYoda has quit [Ping timeout: 256 seconds]
Jackneill has quit [Read error: Connection reset by peer]
Jackneill has joined #nixos-dev
__Sander__ has joined #nixos-dev
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-dev
<tilpner> I just accidentally requested code reviews and closed my PR just by trying to fix my git branch
<tilpner> I didn't interact with the GH UI at all :/
<tilpner> Someone please merge #51300 before I mess it up again? :c
<{^_^}> https://github.com/NixOS/nixpkgs/pull/51300 (by tilpner, 1 week ago, open): minio/minio-client: update
<tilpner> srhb++
<{^_^}> srhb's karma got increased to 28
<srhb> tilpner: :) Spooky git action at a distance is annoying :D
<tilpner> More so when it affects other people and is broadcasted to #nixos c.c
<srhb> I've done worse. :-P
<gchristensen> there have been much worse :)
<gchristensen> approx. a year ago someone pushed 50-100 branches to nixos/nixpkgs instead of their fork, and then deleted them...
<gchristensen> which is fine. it didn't cause anything but a bit of stress about what was going on. user error happens (though this particular error can be prevented :))
pie___ has quit [Remote host closed the connection]
pie__ has joined #nixos-dev
<aminechikhaoui> aszlig wanna have a look at https://github.com/NixOS/nixops/pull/1061
<aminechikhaoui> imo we can make that config an option and set the default to accept-new, then it's up to the user to set something different with possible security issues
<{^_^}> nixops#1061 (by amemni, 2 days ago, open): StrictHostKeyChecking option "accept-new" only works for newer OpenSSH versions thus brakes ssh-tunneling for NixOs 17.09
<aminechikhaoui> let me now if it's fine to push a change that adds an option :)
<gchristensen> yikes, 17.09...
<gchristensen> 'eyy aminechikhaoui what do you think about this one https://github.com/NixOS/nixops/pull/1024 ? it isn't 100% done, but its basically done. the only remaining bit is figuring out how to fix the remaining wait_for_tcp_port usage.
<{^_^}> nixops#1024 (by grahamc, 7 weeks ago, open): Allow specifying arbitrary SSH configuration for nodes
<gchristensen> I've been using it to deploy to foundation's macs for >7 weeks now
<aminechikhaoui> gchristensen sounds ok to me
<gchristensen> neat
<aminechikhaoui> requesting a review from aszlig as well as he touched some parts of that config :)
<gchristensen> well ... now that it has a chance of merging, let me finish it up
<gchristensen> maybe un-request from aszlig for now?
<aminechikhaoui> sure
<aminechikhaoui> done
jtojnar has joined #nixos-dev
<nbp> niksnut: zimbatm: FYI, I am in a meeting until 18:00, if you want to meet tonight, otherwise let's meet on Thursday.
worldofpeace has joined #nixos-dev
asymmetric has joined #nixos-dev
<niksnut> there's an organized dinner tonight, so let's do thursday
__Sander__ has quit [Quit: Konversation terminated!]
worldofpeace has quit [Ping timeout: 268 seconds]
worldofpeace has joined #nixos-dev
pie___ has joined #nixos-dev
pie__ has quit [Remote host closed the connection]
scott has joined #nixos-dev
catern has joined #nixos-dev
<Mic92> If you are reviewing projects that are built with go, make sure they are build with buildGoPackage. It should be also chosen if the project uses a makefile. In this case overwrite the buildPhase.
Synthetica has joined #nixos-dev
jtojnar has quit [Read error: Connection reset by peer]
jtojnar has joined #nixos-dev
asymmetric has quit [Ping timeout: 260 seconds]
<qyliss> Hmm, new Bundix is causing me problems
<qyliss> Or more specifically, it’s surfacing issues with Ruby in nixpkgs because of the new support for groups
<qyliss> If you have a “production” group of dependencies, that by default won’t be included in the derivation if the gemset was generated with new Bundix.
<qyliss> I’ll see where I get with a PR, but mentioning here for visibility
<qyliss> cc zimbatm
<simpson> Who knows how to update kubenix's API definitions? Newer k8s clusters aren't happy with kubenix's old output and I'm having to sed a few API version.
<simpson> Hm. Okay, so I can't do 1.12 yet, but 1.11 is fine for now. Still, I'd really like to know how to generate commits like https://github.com/xtruder/kubenix/commit/c01b2fdab29a5abc0992ddd0d9aaa71720689499
<simpson> ...Nope, 1.11 kubenix with 1.11 k8s still needs the sed. Guess I should open an issue. Sorry for the noise.
asymmetric has joined #nixos-dev
worldofpeace has quit [Ping timeout: 268 seconds]
worldofpeace has joined #nixos-dev
worldofpeace has quit [Remote host closed the connection]
pie__ has joined #nixos-dev
drakonis_ has joined #nixos-dev
pie___ has quit [Ping timeout: 260 seconds]
<gchristensen> anyone have info on the next staging-next merge? (cc Mic92)
<Mic92> gchristensen: sorry, no. This is more fridh's territory.
orivej has quit [Ping timeout: 252 seconds]
orivej has joined #nixos-dev
apaul1729 has joined #nixos-dev
<simpson> manveru: Hm, that might be it. And then just pick the right release version? That could work.
<manveru> sounds like a plan :)
pxc has joined #nixos-dev
pxc has quit [Quit: WeeChat 2.3]
pxc has joined #nixos-dev
pxc has quit [Quit: WeeChat 2.3]
worldofpeace has joined #nixos-dev
asymmetric has quit [Ping timeout: 245 seconds]
pie__ has quit [Read error: Connection reset by peer]
pie__ has joined #nixos-dev