<exarkun1>
does a consumer need to do anything special to deal with multiple output derivations? eg libsodium has out w/ the libs and dev w/ the headers. Another package w/ libsodium in its buildInputs is failing to link against libsodium (can't find it). is that to do w/ multiple outputs or something else?
<exarkun1>
seems like pkgconfig in the dev output points at the right lib path so maybe this other thing's build script is just busted somehow...
jperras has quit [Ping timeout: 244 seconds]
<clever>
> libsodium.outputs
<{^_^}>
[ "out" "dev" "debug" ]
<clever>
exarkun1: "${libsodium}" would be the 1st output (out in this case), but when you put libsodium into the buildInputs, the stdenv will i think refer to .dev automatically
<exarkun1>
yes, that's true.
jperras has joined #nixos
<exarkun1>
(re first comment)
<exarkun1>
show-derivation tells me that /nix/store/kjqz6x25gai4r3fs8bzkjcifkis81zza-libsodium-1.0.16-dev is a buildInput
<clever>
any files in `ls -l /nix/store/kjqz6x25gai4r3fs8bzkjcifkis81zza-libsodium-1.0.16-dev/nix-support/` ?
<exarkun1>
The code compiles so it finds the headers, I suppose. Then fails to link, so doesn't find the libraries. It is not adding the correct -L to find the library in the "out" output though.
<clever>
rust likely doesnt obey the search path stuff in cc-wrapper
<exarkun1>
well, sort of rust, -ish.
<gchristensen>
exarkun1: do you work for LA?
<exarkun1>
pkgs.altcoins.zcash is C++ but it has some Rust dependencies
<exarkun1>
and libsodium is C
<exarkun1>
gchristensen: I do
<clever>
exarkun1: if you use .override, you can replace inputs far more easily
<clever>
.override lets you change the inputs when callPackage is loading something, so you dont have to map over the buildInputs like that
<exarkun1>
clever: good to know!
<gchristensen>
exarkun1: very cool :) it is very exciting to see Nix around places
<exarkun1>
gchristensen: :)
<exarkun1>
clever: would you use both `override` and `overrideAttrs`, then? One to replace librustzcash and the other to change the other package attrs? I don't see how you override things like version w/ `override`
<clever>
exarkun1: yeah
<clever>
exarkun1: and note, that changing version with overrideAttrs rarely has the effect you intend
<clever>
you need to instead change name and src
<exarkun1>
I've noticed weirdness there, it's on my list of things to understand better
<clever>
which i see you are changing
tzemanovic has joined #nixos
<Purple-mx>
sphalerite (IRC): re: precompiled nix tree; Id like to get it implemented. its quite wasteful to parse nixpkgs every tie
<clever>
Purple-mx: i can also see that being useful to save the result of thunks after the first run, to speed things up, and also to do more type-checking
Myrl-saki has joined #nixos
<exarkun1>
clever: uh oh, how does scoping of the set passed to override work? surely I can't just say `{ foo = bar }` and any attribute named `foo` anywhere is replaced with `bar`?
<exarkun1>
is it `pkgs` attributes?
<exarkun1>
if so, `librustzcash` is not a `pkgs` attribute :/
<Purple-mx>
clever: exactly, I bet some quick evaluations might go 50-100x faster
fragamus has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<clever>
Purple-mx: one random thought, what if you have a database, where you store bytecode for every single lambda, and you have the entire AST as rows in the db
<clever>
Purple-mx: and when you eval a thunk, you fill in another field of its result
<clever>
and you have an index of filehash -> Value row#
<clever>
hmmm, but it also depends on the files it imports
<clever>
for example, <nixpkgs/default.nix> will inspect the contents of ~/.nixpkgs, ~/.config/nixpkgs, and an env var, and import a config.nix
<clever>
so you would need to store the pre-forced AST in the cache, and keep the import statements intact
<clever>
and maybe track what paths are pure, and can cache the result of thunks
<clever>
Purple-mx: what do you think of the above?
sbdchd has joined #nixos
<CMCDragonkai>
clever: A programmable database?
<clever>
CMCDragonkai: more about caching the entire AST in a db, and caching the result of pure functions between executions
<CMCDragonkai>
Could you reuse the nix-store to do that?
<clever>
maybe? but it would make the performance of `ls /nix/store` much much worse
sbdchd has quit [Ping timeout: 252 seconds]
<CMCDragonkai>
ls never finishes for me already lol
<CMCDragonkai>
what if it was stuck in a subdirectory
<CMCDragonkai>
clever: That's a great idea! I've been working on something like that, but in a more distributed setting.
slack1256 has joined #nixos
carlosdagos has joined #nixos
<{^_^}>
[nixpkgs] @samueldr pushed 10 commits to release-18.09: https://git.io/fA6LX
mizu_no_oto has joined #nixos
<CMCDragonkai>
clever: Although the speed improvement would heavily depend on whether `/nix/expr` is cached in memory.
Kelppo has quit []
<clever>
yeah
jonreeve has quit [Quit: WeeChat 2.1]
fragamus has joined #nixos
<fragamus>
Hi I forgot how to find the configuration files installed with a package. It keeps them in a place unique to the package, not in /etc right?
<fragamus>
Oh right nixos is mostly a Euro-OS and you guys are sleeping right now
<fragamus>
Let me take this opportunity to say you guys built a great OS
thc202 has quit [Ping timeout: 272 seconds]
fragamus has quit [Client Quit]
jtojnar has quit [Quit: jtojnar]
jtojnar has joined #nixos
adetokunbo has quit [Quit: This computer has gone to sleep]
johnw has joined #nixos
johnw has quit [Changing host]
johnw has joined #nixos
<johnw>
Should foo.bar or baz 1 be intepreted as (foo.bar or baz) 1 or foo.bar or (baz 1)? The precedence rules seems to suggest the former.
lektrik has joined #nixos
mizu_no_oto has quit [Quit: Computer has gone to sleep.]
<infinisil>
> { bar = lib.id; }.bar or null 1
<{^_^}>
1
<infinisil>
johnw: I mean, it is the former indeed
<johnw>
ah, ok, I'm not going insane: 608730af4404f40586ba1e764fbc8576451ec513
<johnw>
i had assumed nixpkgs was correct on this
<johnw>
I apparently it wasn't
<infinisil>
Ah heh yeah, it is a debatable precedence imo
<ldlework>
i feel like nix is very "left leaning"
JonReed has quit [Ping timeout: 252 seconds]
<johnw>
it wants to offer all of us health care?
<ldlework>
hehe
kiloreux has quit [Ping timeout: 245 seconds]
jperras has quit [Ping timeout: 246 seconds]
<johnw>
hmm.. if I run this: nix-instantiate --eval -E 'with (import <nixpkgs> {}); buildEnv { name = "foo"; paths = [libxml2];}' -I nix=$PWD/data/nix/corepkgs --strict
<johnw>
each time I run it I get one of 3 errors, each in a different file
<johnw>
all because on darwin, at that point stdenv.cc = "/dev/null", rather than a set
<kandinski>
is there any python user here? I'm trying to figure how to install the formatting tool black as a command line executable, but in nixpkgs I can only find a module, which I understand is for libraries not executables. Any tip?
<Purple-mx>
its one part of a big project, to redefing the entire OS basically, to only use structured trees, no more shell, no more editing 'code as text' - only an AST editing/browsing interface and everything is an IPC
<Purple-mx>
keep everything stored binary, with a consensus/index to map them
<Purple-mx>
just basically ending a few years of research
jtojnar has quit [Read error: Connection reset by peer]
adetokunbo has joined #nixos
jtojnar has joined #nixos
<Purple-mx>
nix already treats everything as structured, so it doesnt need to be serializing/deserializing. but that means using an RPC interface for nix daemon control
<Purple-mx>
but at least I could start by feeding a precompiled tree as a file
<Purple-mx>
I wont be working on nix first
adetokunbo has quit [Client Quit]
adetokunbo has joined #nixos
adetokunbo has quit [Remote host closed the connection]
<ryantm>
I am trying to use nix-env -qa but I'd like to set a nixpkgs config option. Like the ones in `import <nixpkgs> {configGoesHere}`. Is there a way to do that from the nix-env cmd line?
<{^_^}>
[nixpkgs] @dingxiangfei2009 opened pull request #46592 → dockerTools: use closureInfo to load hashes and closure sizes into the Nix DB → https://git.io/fA63z
mayhewluke has quit [Ping timeout: 244 seconds]
mayhewluke has joined #nixos
<ekleog>
ryantm: --arg
<ryantm>
ekleog: Thanks. I'm trying to set config.allowAliases to false, but `--arg config.allowAliases false` doesn't work
<ryantm>
Well, there are not too many. Looks like vim-plugins should get something like top-level/aliases.nix to stop people from using aliases within that file.
<xok>
can anyone help me add a writeable directory to it?..
slyfox has quit [Ping timeout: 245 seconds]
<MichaelRaskin>
Why does it need to be writeable (and by whom?). Normally we try to patch the program to take the writeable path out of an environment variable. Or make a symlink to /var/programname/ if it fits the purpose of the program…
slyfox has joined #nixos
nD5Xjz has quit [Ping timeout: 244 seconds]
reinzelmann has quit [Quit: Leaving]
<xok>
MichaelRaskin: I want to add an "uploads/" directory where user uploaded files will go...
ma27_ has joined #nixos
ma27_ has quit [Client Quit]
hyper_ch2 has joined #nixos
<MichaelRaskin>
That sounds like a service on top of the package, and it sounds like you want to pass the upload directory as a parameter to the program (either command-line or config)
semilattice has quit [Ping timeout: 245 seconds]
<xok>
MichaelRaskin: isn't it possible to add a symlink with the correct name ( uploads/ ) inside the derviation?..
<MichaelRaskin>
Symlink is possible, but likely to be suboptimal…
Ariakenom has joined #nixos
ma27 has quit [Remote host closed the connection]
<xok>
MichaelRaskin: can you help with a symlink?... I will try if it works for me...
fragamus has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<MichaelRaskin>
Creating a symlink doesn't verify that the target exists
endformationage has quit [Quit: WeeChat 1.9.1]
<xok>
where should I put the writeable directory and create a link to it?..
<xok>
I dont' want to put it in the /tmp/
<MichaelRaskin>
You cannot create it during the package build anyway (you can create the symlink, but not a writeable directory)
nD5Xjz has joined #nixos
<xok>
I am not building a package, I just copy the directory to the newly deployed machine via nixops...
<xok>
I now want to have a single writeable directory ( or a symlink to it )...
disasm_ is now known as disasm
jackdk has joined #nixos
philippD has joined #nixos
brejoc has joined #nixos
tzemanovic has quit []
<elvishjerricco>
xok: It's not a good idea to have symlinks to writable directories in the nix store. The correct thing is to provision such directories outside the nix store by other means, like systemd
flokli has quit [Quit: WeeChat 2.0.1]
<xok>
elvishjerricco: I see the wordpress package does the same:
tzemanovic has quit [Remote host closed the connection]
drewr has quit [Ping timeout: 252 seconds]
<pyvpx>
when I do a nix-env -qa python, for example, I get five identical listings
jasongrossman has joined #nixos
<pyvpx>
how are these different? why are there five? is nix-env -qa not the canonical way to search for a package *name* to install?
<goibhniu>
pyvpx: if you add "P" you'll get more details
<goibhniu>
P includes the "attribute path"
<srhb>
pyvpx: In general there's no canonical way to search for a package _name_ to install, and you shouldn't install packages by name at all.
<emily>
pyvpx: if you're using nix 2, "nix search" is quite a bit nicer.
mayhewluke has quit [Ping timeout: 244 seconds]
Myrl-saki has quit [Ping timeout: 240 seconds]
hamishmack has joined #nixos
mayhewluke has joined #nixos
<cement>
you're saying that the recommended way to install packages is to use the nix expressions?!?
thc202 has quit [Ping timeout: 252 seconds]
<cement>
like literally copy-paste that shit into a big ole .nix file, and run whatever over that?
<cement>
I call shenanigans.
Myrl-saki has joined #nixos
tzemanovic has joined #nixos
Myrl-saki is now known as Guest30516
<goibhniu>
cement: you have many options, but you're better off using the attribute path rather than the name if you install into a user profile
fendor has joined #nixos
<cement>
bleh.
<srhb>
cement: I'm just saying "not names" -- attrs is the right way yeah :)
<goibhniu>
as you suggest, you can also keep a set of packages in a file and install that into your user profile
<cement>
attr paths might as well be names to mortals anyways
<emily>
cement: what, no, nix-env can take an attribute path?
<srhb>
cement: Sure.
<pyvpx>
srhb: okay. if not by name then...? I want to install python 3 or the latest dpdk...I'm not sure I fully appreciate the proper way to accomplish that
<cement>
I learned that the encantation was "nix-env -iA nixpkgs.<name of package>"
<cement>
incantation*
<srhb>
pyvpx: Do the search goibhniu suggested, then install the attr by using nix-env -iA <attrpath>
<srhb>
pyvpx: That is, the leftmost column
<pyvpx>
ahh. I see
thc202 has joined #nixos
<srhb>
Names aren't unique across nixpkgs, so installing by names is at best confusing, and mostly just wrong. attrpaths are unique.
<goibhniu>
to make matters worse, when you list your installed packages, you can only see the names rather than attr paths :D
<cement>
unless you do what I was calling shenanigans on and only install through a .nix file that lists everything
hamishmack has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Guest30516 has quit [Ping timeout: 240 seconds]
<srhb>
goibhniu: And you can also only uninstall them by name :-P
Neo-- has joined #nixos
<srhb>
(or path...)
<pyvpx>
yes that all seems less than ideal
<pyvpx>
but I get it
<pyvpx>
less than ideal as far as UX
<cement>
very much so
<pyvpx>
I see I've installed the wrong dpdk, since I did it by name, and it helpfully picked "the first" one
<Taneb>
Is there some library function to go from an attrset to a list of key-value pairs?
<cement>
either you're pushing the boundaries of mortality, or you can barely use nix
<srhb>
Taneb: I think it's called toList or something.. It's either in the attrs lib or the list lib
<teto>
nox feels clunky but overall is nice to install software
<sphalerite>
cement: Apparently I'm pushign the boundaries of mortality!
<cement>
by my standards, yes
<Taneb>
srhb: there's toList in the list lib but that just puts things in a list
<srhb>
Taneb: mapAttrsToList id at least :P
<cement>
I'm not saying that it's hard, but there is a *bunch* of BG info needed to be useful
<srhb>
Oh, no, it takes both name and value
Guest30516 has joined #nixos
<srhb>
I swear there's a lib function for this... *rummages*
<sphalerite>
cement: IMHO, nix-env -i just shouldn't be used without -r (install the given packages into an empty profile, i.e. remove everything else) or --set (set the profile to a specific path rather than building a profile from multiple paths)
<pyvpx>
cement: and not that much in the way of "here is how to get from A to B" in documentation. I mean, the documentation is thorough but sometimes I need to apply it quickly rather than soak in the full picture & gain *understanding*
<sphalerite>
cement: I totally agree that nix's attempt at imperative package management is really not good. But imperative package management isn't what nix is for anyway ;)
<cement>
been using nixos on my dev computers for years, and I couldn't sit an exam or even do much beyond use "nix-env -iA <attrpath>" to set up part of my environment
<cement>
'course, 90% of that is overeliance on clever, as he was very much a close friend for most of those years
<srhb>
Is nix (much) worse at imperative package management than other solutions though?
<srhb>
(Honest question, been a while since I touched any of the others)
<sphalerite>
srhb: yes, because of the whole "everything has two names" business
<srhb>
Ah, right, that is a pain indeed.
<sphalerite>
and let's be honest, nix-env is awful at upgrading things.
<cement>
is the "correct" approach much better?
rauno has quit [Ping timeout: 240 seconds]
<sphalerite>
cement: yes!
<srhb>
Yeah
<srhb>
A lot...
Guest30516 has quit [Ping timeout: 252 seconds]
<cement>
eg. it was always a huge chore to update the haskell environment, and I certainly don't use nix-env for that crapshoot
sigmundv has joined #nixos
<srhb>
nix-shells are life.
<srhb>
is life?
* goibhniu
would argue that nix is the best imperative package manager available
<srhb>
English is weird.
<sphalerite>
nix-shell is great, declarative environments installed using nix-env -ir or nix-env --set are great, nixos config is great
<sphalerite>
srhb: I'd say are there
<sphalerite>
goibhniu: oh?
<goibhniu>
user profiles are awesome too though
<goibhniu>
the attr path vs. name thing is a small price to pay IMO
<srhb>
Names are overrated anyway!
<srhb>
Let's get rid of them!
<sphalerite>
goibhniu: but there's no workable equivalent of apt-get [dist-]upgrade for instance
<cement>
yeah... even with the nix-shell *and* the specifically pinned nixpkgs approach to the haskell env, it was a huge PITA to keep up-to-date at my last position
<goibhniu>
oh, but problems with installing Qt programs into a user profile are terrible
<goibhniu>
sphalerite: is that different from using nix-env -u?
<srhb>
cement: I somehow doubt it'd be easier without Nix though?
<cement>
oh heavens no
<srhb>
Like, fundamentally I can barely think of a better approach to this...
<sphalerite>
goibhniu: `nix-env -f '<nixpkgs>' -iA mumble ; nix-env -u` will upgrade your mumble to mumble_git. Because of the name/attrpath thing.
<srhb>
cement: Ah okay. I misunderstood ^^
<goibhniu>
sphalerite, ahhh ... I see
<cement>
yeah, it's *currently* the easiest approach, but it's kind of... unautomatable
<cement>
unless something's changed since April
nD5Xjz has quit [Ping timeout: 252 seconds]
<sphalerite>
cement: what's unautomatable about it?
<mpu>
is nix-env -u working on names?
<sphalerite>
mpu: yep
<mpu>
uuuh
<cement>
choosing the pinned nixpkgs and there's usually many many ghc errors that need correcting
<cement>
with just a simple change to the git revision
<mpu>
sphalerite, how are nixos users updating their system, then?
<srhb>
cement: Right, that also seems like a fundamental issue
<sphalerite>
mpu: using nixos-rebuild switch --upgrade
<cement>
it's not inherently nix's fault, though
<srhb>
cement: At least it's easy to set up a system where you can override things as easily as foo = callHackage "package" "version" {} these days
<sphalerite>
mpu: and for user profiles, declarative envrionments.
<srhb>
cement: That helps a lot.
<srhb>
cement: Main issue being that tons of stuff is just plain incompatible in the latest-whatever version.
Guest30516 has joined #nixos
<NickHu_>
Is anyone with commit access free to go over some of my prs that have gotten a bit stale?
<mpu>
sphalerite, what's a declarative environment?
Guest30516 has quit [Changing host]
Guest30516 has joined #nixos
Guest30516 is now known as Myrl-saki
<mpu>
So users give attr paths in their configuration and all goes well because those do not change that often in nixpkgs?
<sphalerite>
mpu: an expression that contains everything you want in your user profile, and you install using nix-env -ir or nix-env --set
<sphalerite>
mpu: oh yeah and there's also home-manager which provides per-user nixos-like configuration
<cement>
hm. I should offload my "nix-env" installs into a .nix file that's included in configuration.nix
<srhb>
mpu: For big projects, you often end up specifying the exact revision of nixpkgs to use
<srhb>
mpu: So nothing changes version by accident
<srhb>
mpu: And this way every developer sees the exact same version of the dev/build/ci environment
<srhb>
mpu: No more "works for me" :)
<cement>
in theory
<NickHu_>
mpu: It's like docker but less garbage
<srhb>
In theory.
<mpu>
nix-env -ir only gives you a single package, though, doesn't it?
<srhb>
But also in practice a very, very long way.
<cement>
yeah, it was most of the way there
<cement>
the weird bits were hardware quirks because of course hardware effects how ghc works, doesn't it?
<srhb>
It happens..
<mpu>
srhb, that's why I'm interested in nix :)
<srhb>
mpu: :)
<srhb>
cement: re. offloading nix-env: I really recommend home-manager
<srhb>
cement: It's like NixOS for your user and homedir.
<srhb>
You can even include that in your nixos configuration, though I have not tried that yet personally.
<cement>
oh I'm on nixos already, I've just been lazy about doing the "right thing"
<srhb>
(Which means I have two separate rebuilds, one for the system and one for the user)
<srhb>
cement: Right, but NixOS doesn't manage your homedir :)
<srhb>
They go very well together.
<cement>
and I suppose I could set up the now sudo-less nix in a new system and have all my shit ready to go with that, right?
<srhb>
cement: With home-manager you get do do things like programs.ssh.matchBlocks."somehow".identityFile = ...
<srhb>
s/somehow/somehost
<cement>
terrifying.
<srhb>
(Just don't accidentally import it into the nix store and you're fine :P)
<cement>
wait wouldn't that make my machines all identify as the same machine?
<srhb>
cement: Just like your nixos configuration you can import specific machine configs and merge together in a sane manner
<srhb>
cement: Most of my config in both nixos and home-manager is host-agnostic, but some of it isn't.
<cement>
right. that's how clever set me up
<cement>
configuration.nix and hardware-configuration.nix are where my stuff all lives
<srhb>
My NixOS configuration is... Extensive.
<srhb>
And spread over quite a lot of files.
<cement>
mine is the absolute minimum
<srhb>
And configuration.nix is essentially imports = [ allthethings hostspecific ];
<cement>
besides my vim config living there, but that's justified.
jperras has joined #nixos
<{^_^}>
[nixpkgs] @andir pushed to master « vmTools: update debian repositories to stable Release.xz urls »: https://git.io/fA6EW
<cement>
waitasecond I could move my vim config (or emacs) config around onto any machine that I touched using that, couldn't I
<srhb>
Yeah.
<cement>
without root access?
<srhb>
As long as you have nix available.
<cement>
so yes
<cement>
dayum.
<srhb>
I don't think you can sanely do it with proot nix, but I'm not sure
<srhb>
Because you'd need to use nix run for everything (or build everything from scratch because of the altered store path)
<srhb>
Could we patch the loader to allow having a variable prefix in front of every library path? :-P
<cement>
even then, that'd be fantastic for the kinds of machine-agnostic things I expect to need to do, and dragging around a completely custom editor like most people do a vimrc sounds like heaven
<srhb>
cement: I bet you could even do some cool things with sshfs, forwarding the nix things you need.
<ldlework>
I got global theme unification working!
<srhb>
ldlework: :o
<ldlework>
I define a theme in Nix, and I use it with substituteAll in all my config files
<ldlework>
so I have the same theme being used across all my tools
<Taneb>
ldlework: sounds neat, but theme in what sense?
<teto>
btw I also got astroid and alot muas configuration generated by home-manager so you can configure your mail accounts once and then HM configures msmtp/offlineimap/mbsync/alot/astroid configs
<teto>
s/configures/generates
Guanin has joined #nixos
<ldlework>
Taneb: I specify 16 colors in Nix, and that gets used in my window manager, terminal emulator, emacs, rofi and qutebrowser themes
<srhb>
Myrl-saki: I think i use one of them, but I forget which
<Myrl-saki>
THe recent convo made me think of auto-generating suckless configs.
<Myrl-saki>
s/auto-generating/nixifying/
<srhb>
Myrl-saki: I've often wanted an easy inline "patch generator"
<srhb>
substitute is a bit meh at scale
<Myrl-saki>
srhb: I'm thinking of targeting just per-version.
<ldlework>
I used to use dmenu
<ldlework>
Switched to Rofi
<Myrl-saki>
Still use dmenu until now. :D
<Myrl-saki>
srhb: Also, "path generator"?
<srhb>
Myrl-saki: patch. Isn't that how st stuff is mostly configured?
<Myrl-saki>
whoops, patch* right.
<srhb>
And right, dmenu is the one I use.
<Myrl-saki>
But what do you mean by that/
<srhb>
Myrl-saki: I mean I want an easy and expressive way in Nix to specify "generate a patch for the patches list that changes these lines (contextually, not by number) in this way"
__lawlesseel__ has quit [Remote host closed the connection]
__lawlesseel__ has joined #nixos
lawlesseel has joined #nixos
kisik21 has joined #nixos
Dedalo has joined #nixos
<{^_^}>
[nixpkgs] @mcmtroffaes opened pull request #46600 → wolfssl: enable all features → https://git.io/fA62A
<WilliamHamilton[>
can you help me debug the error "relocation error: /usr/lib/libc.so.6: symbol _dl_exception_create, version GLIBC_PRIVATE not defined in file ld-linux-x86-64.so.2 with link time reference" when using steam-run?
<sphalerite>
Myrl-saki: maybe passing -dir ?
exarkun_ has quit [Ping timeout: 252 seconds]
exarkun_ has joined #nixos
<Myrl-saki>
sphalerite: Turns out the problem was simpler. I had the Steam directory as root:root.
<rawtaz>
hm. when using runCommand with the following two statements, why would you wrap the src variable in {} but not the out variable? mkdir -pv $out/bin; gcc ${src} -o $out/bin/hello-world
Guanin__ has joined #nixos
<andi->
rawtaz: ${src} is expanded by nix, $out is shell variable
carlosdagos has quit [Quit: Connection closed for inactivity]
<andi->
${ is a magic prefix that allows inline nix-expressions until the final }
<rawtaz>
oh, ok. how come nix sets $out as a shell variable instead of a regular nix variable? is it just a matter of it doing that by default, and me having defined the src variable myself makes it only available "inline"?
Guanin_ has quit [Ping timeout: 252 seconds]
<Myrl-saki>
Huh, good question.
kreetx has joined #nixos
<Myrl-saki>
I'm guessing it's because Nix fundamentally requires everything that is referenced to exist.
<jasongrossman>
rawtaz: Thanks. Downloading that video.
<Myrl-saki>
So you can't have the build script with ${out}, because it hasn't existed when you're making it.
<Myrl-saki>
Just a guess.
<exarkun1>
Can I make nix-build re-build something that already exists in the store?
<kreetx>
hi! how does one add static files to a docker generated from nix?
<Myrl-saki>
rawtaz:
<kreetx>
could it be nix.sandboxPaths? ;)
<srhb>
kreetx: You should probably expand on the purpose of those files/how the image is going to use them. It might be as simple as a string reference to them
<betaboon>
does anyone use the GithubPulls hydra plugin ?
<srhb>
kreetx: There's a few different answers that depend on your usage
<srhb>
betaboon: Yup.
<kreetx>
srhb: a web server is going to serve them from disk
__lawlesseel__ has quit [Remote host closed the connection]
simukis has joined #nixos
<srhb>
kreetx: So say that you had the directory as a nix package and your web server took the path to serve as an argument
<betaboon>
srhb: does it automatically create a job for each newly created PR or do i have to add each PR manually?
Wharncliffe has joined #nixos
<srhb>
kreetx: In that case your Cmd would simply be "${webserver}/bin/serve --static-dir ${static-content}"
<srhb>
kreetx: And you're done.
xok has joined #nixos
<srhb>
betaboon: Hydra gets a json blob that contains every PR in the repo
<teto>
exarkun1: you can add --check
<srhb>
betaboon: It's up to you to make a function that produces a jobset with the jobs you want
<kreetx>
srhb: I don't pass them in from the command line. But would just mentioning the path make it to be copied in?
<srhb>
betaboon: Hydra will keep polling for the json, and you do with it what you like :)
<srhb>
kreetx: Essentially yep :)
<srhb>
kreetx: The usual rules that you expect from any other mkDerivation apply.
<srhb>
If you use a store path, you depend on it.
<andi->
rawtaz: https://nixos.org/nix/manual/#ssec-derivation read that chapter, it is an environment var set by nix itself. It determines the name & hash of the derivation you are going to build and that also includes the expansion of ${src} since when ${src} changes the $out (hash & name) also changes.
<ekleog>
exarkun1: I seemed to remember --check, but can't find it in the manual
<kreetx>
but if I don't say it on the command line, is there some other way -- an attribute I could set? like include-dirs = [[./src, ./dest]] or the like?
<Myrl-saki>
Seems like `out` is a Nix thing, and not a Nixpkgs thing.
<Myrl-saki>
Am I wrong?
<sphalerite>
Myrl-saki: you're right
orivej has quit [Ping timeout: 250 seconds]
<sphalerite>
Myrl-saki: it's the name of the single output a derivation has unless otherwise specified
<Myrl-saki>
Right. Thanks.
<sphalerite>
rawtaz: also it's an environment variable, not just any shell variable
<rawtaz>
sphalerite: not sure i understand the difference. it's like you had done export out=foo , no?
<sphalerite>
rawtaz: yes, but every process has environment variables, even if it's not a shell
<sphalerite>
rawtaz: shell variables aren't necessarily exported to become environment variables
<sphalerite>
rawtaz: and stdenv makes extensive use of shell variables too
<sphalerite>
rawtaz: and the reason that out is an env var rather than a nix variable is because it's used in stuff that determines its value. So if you made it a nix variable you'd have a circular reference
<srhb>
betaboon: Ok, back.
<sphalerite>
because out depends on the hash of the drv, and the hash of the drv depends on the build script, and you can't determine the hash of the build script if you need the value of out to do so…
<srhb>
betaboon: You can download the PR json from github yourself, it's translated 1-1 to nixin that example
<Myrl-saki>
Yay, nixos-18.09 has finally moved! \o/
<sphalerite>
rawtaz: nix 2.0 has the placeholder builtin, which works around this by having a fixed string for the output's name which is substituted at build time
<srhb>
Myrl-saki: Twice, in fact.
<Myrl-saki>
srhb: Oh. ; ~ ;
Neo-- has quit [Ping timeout: 252 seconds]
<rawtaz>
sphalerite: okay, it all makes some sense
<Myrl-saki>
Finally I can remove the Nix 2.1 hacks in my Nix files! \o/
<betaboon>
srhb: are you using GithubStatus-plugin aswell? does it play nicely in combination with GithubPulls ?
<srhb>
betaboon: I am, yes.
<srhb>
betaboon: I don't think they interact in any way (so I guess you can say they play nicely by not playing with each other)
<Taneb>
What's the release schedule for 18.09?
<srhb>
betaboon: It just pushes a status to whatever rev the given input is on on github
<betaboon>
srhb: It's too sad that most of the hydra-stuff seems to be very (if at all) sparesly documented
<srhb>
Taneb: "When it's done" :-)
<srhb>
betaboon: Yep. Please feel free to contribute, now that you're setting it up is the excellent time to take notes and do exactly that :)
<Taneb>
srhb: haha, fair
kreetx has quit [Ping timeout: 252 seconds]
<betaboon>
srhb: I'll try XD
<Taneb>
It's going to be the day after I get us at work moved onto 18.03, I can feel it
<srhb>
betaboon: Nice! :) I'll be happy to proofread.
<srhb>
Taneb: Count on it! ;)
<srhb>
Taneb: fwiw it usually takes about a month, but we're in pretty good shape this time.
<betaboon>
srhb: might take a while tho. trying to setup hydra as a ninja-side-project (i feel the need to set it up for our development, but ofc feature-work is "more important" atm ;) )
<srhb>
betaboon: Ah, the usual story. :)
<betaboon>
srhb: not even shocked anymore xD
<srhb>
Even "thought process notes" can be turned into documentation with low effort... :)
<srhb>
The hard thing is to remember to write anything down :-P
<betaboon>
i guess i should at some point revive my blog xD
Kelppo has joined #nixos
patrl has joined #nixos
spear2 has joined #nixos
<{^_^}>
[nixpkgs] @Mic92 pushed commit from @jluttine to release-18.09 « syncthing: 0.14.48 -> 0.14.50 »: https://git.io/fA6K0
lopsided98 has quit [Ping timeout: 240 seconds]
<WilliamHamilton[>
hi, could someone explain what the error `relocation error: /usr/lib/libc.so.6: symbol _dl_exception_create, version GLIBC_PRIVATE not defined in file ld-linux-x86-64.so.2 with link time reference` means and how I'd proceed to debug it?
<WilliamHamilton[>
I'm on the latest nixos unstable channel
<WilliamHamilton[>
and it happens when I use steam-run, independently of the argument
<exarkun1>
anyone have any idea why those libraries wouldn't be found?
<fgaz>
Does nix-copy-closure handle key exchange yet?
revtintin has quit [Quit: WeeChat 1.9.1]
orivej has quit [Ping timeout: 245 seconds]
xok has joined #nixos
sbdchd has joined #nixos
nD5Xjz has quit [Ping timeout: 264 seconds]
Wharncliffe has quit [Quit: Lost terminal]
sbdchd has quit [Ping timeout: 244 seconds]
Dedalo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
nD5Xjz has joined #nixos
johanot has quit [Remote host closed the connection]
civodul has quit [Quit: ERC (IRC client for Emacs 26.1)]
<Myrl-saki>
Lol, what does Discord do to autostart, because there's apparently a setting on Discord for it but doesn't work (and I don't want it to work either.)
<sphalerite>
Myrl-saki: probably sticking itself in ~/.config/autostart
<{^_^}>
[nixpkgs] @xeji pushed commit from @iimog to master « seaview: init at 4.7 (#46595) »: https://git.io/fA6SJ
<jasongrossman>
Minimal window managers all have their own idiosyncratic ways of autostarting things. Desktop managers do too, which is nice in principle but I've been having trouble getting them to work, maybe because they run things too early.
<{^_^}>
[nixpkgs] @xeji pushed commit from @Ma27 to master « tamarin-prover: fix ghc 8.4 build (#46597) »: https://git.io/fA6ST
<{^_^}>
[nixpkgs] @xeji pushed commit from @Ma27 to release-18.09 « tamarin-prover: fix ghc 8.4 build (#46597) »: https://git.io/fA6S8
<sphalerite>
jasongrossman: AFAIK putting desktop files in ~/.config/autostart is the XDG standard for autostarting things
tzemanovic has quit [Ping timeout: 245 seconds]
<jasongrossman>
sphalerite: Thanks. That makes sense. But I suspect that only the big DEs respect it.
tzemanovic has joined #nixos
<sphalerite>
jasongrossman: yep. According to the minimals, it's not the WM's responsibility, and you should use something like https://github.com/jceb/dex
<{^_^}>
[nix] @edolstra merged pull request #2349 → dirOf: allow use on non-absolute paths → https://git.io/fNd98
Neo-- has quit [Ping timeout: 252 seconds]
lsyoyom has quit [Ping timeout: 245 seconds]
<tobiasBora>
Hey!
<tobiasBora>
I would like to use OVFM with qemu to emulate bios
<tobiasBora>
UEFI*
<tobiasBora>
so I installed the nixos package of OVFM.
<tobiasBora>
However, when I run "qemu-system-x86_64 -bios /nix/store/wj31x7c0c70bkz9w0vai7l24wwysn810-OVMF-2017-12-05/FV/MEMFD.fd -cdrom xubuntu-16.04.1-desktop-amd64.iso", it fails
<tobiasBora>
(with an error like "qemu-system-x86_64: Trying to execute code outside RAM or ROM at 0x00000000000a0000"
<tobiasBora>
(1) You told QEMU to execute a kernel for the wrong machine type, and it crashed on startup (eg trying to run a raspberry pi kernel on a versatilepb QEMU machine)
<tobiasBora>
...)
<tobiasBora>
So I guess I provided the wrong bios
<tobiasBora>
so here is my question: what file in the OVFM folder should I use as bios to emulate UEFI?
<witchof0x20>
My libvirtd setup uses I use {pkgs.OVMF}/FV/OVMF.fd
tertl3 has quit [Quit: Connection closed for inactivity]
<tobiasBora>
witchof0x20: I don't have this file...
<{^_^}>
[nixpkgs] @yegortimoshenko opened pull request #46604 → [WIP] Wrap Nix to add Git as runtime dependency, resolves #46603 → https://git.io/fA6dM
jperras has quit [Ping timeout: 272 seconds]
<Henson>
when I try using haskell.lib.buildStackProject, which ultimately references this file, it always fails for me. But if I put "true" at the end of the configurePhase list of command, it works.
<Henson>
command -> commands
<Myrl-saki>
sphalerite: I meant command-not-found.
TonyTheLion has quit [Quit: leaving]
<Henson>
is there a way I can get nix-build to use disk-backed temporary storage for a build instead of RAM-backed? I sometimes run out of memory when doing builds because of this.
<sphalerite>
Myrl-saki: yeah command-not-found is only for commands ;)
<sphalerite>
Henson: it uses TMPDIR
hyper_ch2 has quit [Quit: Page closed]
<Henson>
sphalerite: the environment variable TMPDIR?
<sphalerite>
Henson: so either don't mount tmpfs on /tmp, or give the daemon or your build command (if you're in a single-user setup) a differnet TMPDIR
<{^_^}>
[nixpkgs] @Mic92 pushed commit from @matthewbauer to release-18.09 « aliases: add nixos-rebuild »: https://git.io/fA6N9
xenog has joined #nixos
<Henson>
sphalerite: ok, here's my problem with running out of memory. You're right about build files being put into /tmp. But there's also the variable $NIX_BUILD_TOP which on my system is being set to /run/user/1000. Is this variable supposed to be set to this location? Here the Haskell builder is download a large amount of files which is causing memory issues on my system.
<sphalerite>
Henson: oooooh so you're using nix-shell
jtojnar has quit [Read error: Connection reset by peer]
<Henson>
sphalerite: I'm trying to make a Nix derivation that builds a Haskell Stack project. Instead of mkDerivation I'm using haskell.lib.buildStackProject.
derped has quit [Remote host closed the connection]
jtojnar has joined #nixos
<sphalerite>
Henson: setting TMPDIR for your nix command should result in NIX_BUILD_TOP getting set to the given value as well
<Henson>
sphalerite: is there a maintainer for the generic-stack-builder.nix file? There seems to be a problem with the configurePhase on line 51
<Henson>
sphalerite: ahhh, ok. It's quite possible I tried a "stack build" inside a nix-shell to see if it worked. That could have put all those files in that directory.
<sphalerite>
Henson: no, that line makes sense, since nix builders have a nonexistent $HOME so you don't want stack to try and install stuff there
xok has joined #nixos
<Henson>
sphalerite: sorry, line 51 is related to the failure of the configuration phase. Take a look at what I asked to the channel about 45 minutes ago.
<sphalerite>
Henson: ooooh right. The idea is to have the proper dependencies specified in buildInputs ;)
nD5Xjz has joined #nixos
<sphalerite>
Henson: on a nix setup with sandboxing, this will fail fast because it doesn't get network access
<sphalerite>
Henson: so if anything, the problem is that it doesn't pass some sort of flag to stack that stops it from downloading anything
<betaboon>
damn I'm lost on setting up hydra. so confused :(
graphene has quit [Remote host closed the connection]
graphene has joined #nixos
<Henson>
sphalerite: so if the full set of dependencies isn't specified, the configurePhase is supposed to fail? When I modified it and put "true" at the end, stack downloaded the missing dependencies and continued on to the build phase.
<sphalerite>
Henson: yeah, nix builders aren't supposed to download anything
<Henson>
sphalerite: ohh, I didn't know that.
<LnL>
on ci builds are sandboxed and can't download stuff
<Henson>
sphalerite: so, a tool like "stack2nix" is rather necessary for building Haskell packages with Nix. There are hundreds of dependencies.
<sphalerite>
Henson: yes
<{^_^}>
[nixpkgs] @rembo10 opened pull request #46607 → Sickbeard/Sickgear/Sickrage: Init and module → https://git.io/fA6je
wpcarro has quit [Ping timeout: 246 seconds]
<Henson>
sphalerite: Great. Thank you for your help.
baimafeima has quit [Remote host closed the connection]
semilattice has quit [Ping timeout: 240 seconds]
jperras has quit [Ping timeout: 246 seconds]
Ariakenom has quit [Ping timeout: 245 seconds]
civodul has quit [Quit: ERC (IRC client for Emacs 26.1)]
<infinisil>
Henson: stack has nix support built-in
<infinisil>
No need to enter a nix-shell before you can call stack commands
<infinisil>
It automatically does that for you
<exarkun1>
is there a statically linked libc in nix somewhere?
<Henson>
infinisil: I'm trying to make a nix derivation of my stack project so I can build it using nix-build. I don't want to use "stack build" to build my project using Nix underneath, but the other way around.
<infinisil>
,locate libc.a
<{^_^}>
Found in packages: musl, dev86, klibc, uclibc, arduino, avrlibc, androidndk, and 5 more
<infinisil>
exarkun1: It's also in glibc.static
vaibhavsagar has quit [Remote host closed the connection]
vaibhavsagar has joined #nixos
<infinisil>
Henson: If you're developing, you can use the stack commands, it will enter the nix-shell. If you want to build it with nix-build, buildStackProject or stack2nix is the way to go
<{^_^}>
[nixops] @yorickvP opened pull request #1003 → Take NIX_SSHOPTS into account → https://git.io/fAiU3
<infinisil>
I'd recommend stack2nix
<infinisil>
Or did I misunderstand something
<exarkun1>
infinisil: thanks
<Henson>
infinisil: yeah, I'm trying to use buildStackProject. The problem is all of your Haskell build dependencies have to be specified in buildInputs. stack2nix won't compile using "nix-env -i" for some reason, and takes a LONG time to compile from the github source, but I figured out another way to determine the dependencies. Just use "stack ls dependencies"!
<infinisil>
Hmm.. I don't remember having to specify all haskell deps
<wpcarro>
Can anyone who uses Nix to manage their Emacs packages explain how to a) prevent Emacs from installing or updating packages (especially if using use-package) b) how Emacs can find the packages that Nix installs in the nix-store
* Henson
suspects he's doing something wrong
jperras has joined #nixos
<infinisil>
Henson: You're cabal file has all the deps specified?
<infinisil>
Your*
_0bitcount has joined #nixos
<hodapp>
wpcarro: I have never run into issues with this myself and I use Emacs with various packages... I can paste my configuration
<Henson>
infinisil: ahh yes. I forgot they're all specified in there.
<Henson>
infinisil: well, all the top-level dependencies, anyway
<wpcarro>
hodapp: I think I'm just a little confused about what happens after they're pulled from the channel. They go in the nix-store... but then how are they exposed to Emacs?
<infinisil>
Henson: Not sure what you mean by top-level deps
xok has quit [Ping timeout: 272 seconds]
<hodapp>
wpcarro: it creates an emacs 'executable' which is just a wrapper script to the real Emacs, and which sets the load path before calling the real binary
erasmas has joined #nixos
<Henson>
infinisil: well, there are about 60 top-level dependencies, which themselves depend on lower level dependencies, making 212 dependencies reported by "stack ls dependencies"
<hodapp>
and points that load path to relevant things in the nix store
<infinisil>
Henson: Ah, those are usually called immediate dependencies, while the other ones are transitive ones (or the dependency closure)
<Henson>
infinisil: ah, ok. So the immediate dependencies in the cabal file need to be specified in buildInputs.
<infinisil>
Huh, no, you just put them in the cabal file
Ariakenom has joined #nixos
<infinisil>
Haskell always uses cabal files to determine dependencies, whether you use stack, nix, cabal, snack or hpack
<wpcarro>
hodapp: wow... that helps a lot
<wpcarro>
hodapp: is there documentation where I can read more about this process? Or did you just read the source code?
<Henson>
infinisil: ok, well the problem I had with haskell.lib.buildStackProject is that it would exit during the buildPhase without any useful information. It turned out the problem seemed to be with the configurePhase. If all the dependencies weren't in buildInputs, stack would try downloading them. sphalerite tells me that's not allowed, so configurePhase is intended to fail if all the...
<infinisil>
Henson: Oh yeah, you need to turn off the sandbox
<Henson>
infinisil: dependencies aren't found. Specifying all of the dependencies in buildInputs seems to make things work for me
<Henson>
infinisil: what the heck is that?
<hodapp>
wpcarro: in my case I just typed 'which emacs' and looked at the file with 'less' >_>
<infinisil>
The sandbox prevents downloads for stuff you don't have a hash for, and stack needs that to work, buildStackProject just calls stack to build its stuff
<infinisil>
--option build-use-sandbox false
<Henson>
infinisil: is that an option to nix-build?
<infinisil>
Yeah
<Henson>
infinisil: can I somehow specify that in a derivation?
<wpcarro>
hodapp: thanks so much. Huge help
<sphalerite>
infinisil: Henson already doesn't have sandboxing, they're workign with single-user nix
<infinisil>
Not sure why that's not mentioned anywhere
<hodapp>
wpcarro: there are various examples in Nixpkgs of similar cases that are handled by producing a wrapper script in order to point a wrapped binary to specific dependencies. Look around for 'makeWrapper'
<infinisil>
Henson: (you can't)
<sphalerite>
infinisil: I figured the sensible thing to do would be to fix the dependency specification, not to ignore purity
<infinisil>
sphalerite: single user nix doesn't have sandbox?
<{^_^}>
[nixops] @yorickvP closed pull request #1003 → Take NIX_SSHOPTS into account → https://git.io/fAiU3
<Henson>
sphalerite: how can I tell if I'm using single-user nix or not?
<sphalerite>
Henson: if you're running nix-daemon, it's multi-user
<Henson>
sphalerite: it's single-user
<sphalerite>
Henson: if /nix is owned by your user, it's single-user
<Henson>
sphalerite: yep
<sphalerite>
yeah in that case you can't even activate the sandbox :p
<infinisil>
Does the option to turn off sandboxing not make the build work?
<infinisil>
Because that's the only thing I can see preventing downloads
<infinisil>
I guess I never realized this that you can use buildStackProject with nix deps
<infinisil>
It's nowhere mentioned in nixpkgs, neither is the sandbox thing
sbdchd_ has joined #nixos
<wpcarro>
hodapp: will do! Thanks
<infinisil>
Oh I guess it's mentioned in generic-stack-builder.nix
<hodapp>
wpcarro: good luck
<{^_^}>
[nixos-homepage] @aszlig opened pull request #240 → Add Hetzner Online GmbH as sponsor → https://git.io/fAiIr
<Henson>
infinisil: it looks like stack wants to build a whole bunch of these dependencies from source. If they're specified as a buildDependency, shouldn't they be downloaded from the nix cache and not need to be built?
<infinisil>
Well I always used it without specifying any deps in the nix expression, then this download and build behaviour is expected
<infinisil>
Because the build needs to stay somewhat pure, stack can't reuse any things you have compiled in your user env
<infinisil>
But if specifying the deps works for you then go for it :)
<infinisil>
Maybe you could even use cabal2nix to find the deps automatically
<Henson>
infinisil: so do you have to download and build all the dependencies every time you build your derivation?
<Henson>
infinisil: because if stack downloads and compiles a dependency, shouldn't stack's root directory be in a temporary location that gets removed once building your derivation is complete?
<infinisil>
Yup, that's the reason I'm not using it anymore
graphene has quit [Remote host closed the connection]
<infinisil>
Henson: Oh, and: If you get the build inputs from Nix, then the whole stack thing is kinda pointless
graphene has joined #nixos
<infinisil>
Because it will just use the versions nix provides, which don't have the guarantees of the stackage package set
Ariakenom has quit [Ping timeout: 245 seconds]
<infinisil>
To get these guarantees you need to either do it with the turn-off-the-sandbox way, or stack2nix
Ariakenom_ has joined #nixos
<{^_^}>
[nixops] @yorickvP opened pull request #1004 → remove failing test (after 2e7a78bb) → https://git.io/fAits
<Henson>
infinisil: does stack2nix do it properly?
<infinisil>
Yeah, try it out, works fairly well
<yorick>
stack2nix does it outside of nix
<Henson>
infinisil: ok. It seems to want to compile from source all of its dependencies, so it's going to take a while
<infinisil>
Henson: stack2nix is in nixpkgs
<yorick>
yeah, but it's output generally isn't
Neo-- has joined #nixos
mayhewluke has quit [Ping timeout: 272 seconds]
Lears has quit [Ping timeout: 245 seconds]
amfl has quit [Ping timeout: 252 seconds]
flokli has joined #nixos
<Henson>
infinisil: yes, and for some reason it wants to compile itself from source, and it fails to compile because of a missing dependency in Nix.Parser :-P
<lesh>
hey, nixos newbie here, but experienced with linux generally.. I'm trying to deploy to hetzner bare metal via nixops, and getting a strange error, "partitioning disks..." and fails when it tries to import NixKickstart, with "ImportError: No module named selinux" any idea where to start looking? tnx
<betaboon>
why isnt the hydra documentation at https://nixos.org/hydra/manual/ not the most recent version of the master branch (which has its last change two years ago) oO
<exarkun1>
How do I get a static boost? I thought `callPackage boost { enableStatic = true; }` but I don't know how to actually refer to the nixpkgs boost path there.
<exarkun1>
symphorien: the boost expression has a bunch of logic that's conditional on enableStatic. does that really work?
<hodapp>
does it really work how?
<hodapp>
it definitely builds a static version (I'm using it to build Appleseed)
jedahan has quit [Ping timeout: 272 seconds]
<symphorien>
If enableStatic is an argument at the beginning of the file you mentionned, then yes
<exarkun1>
okay. I don't understand `override`.
Guest42674 has quit [Client Quit]
edef has joined #nixos
edef is now known as Guest40137
<symphorien>
override will change the value of the arguments at the top of the file where boost is defined
Guest40137 has quit [Client Quit]
edef_ has joined #nixos
edef_ is now known as edef
<symphorien>
(I mean the file you callPackage)
<exarkun1>
As a kind of hand-wavey explanation, sure, I get that. Doesn't really help my understanding of how nix really works though (not a useful model, doesn't help me predict much).
<{^_^}>
[nixpkgs] @Mic92 pushed commit from @xeji to release-18.09 « pythonPackages.zodb: fix tests »: https://git.io/fAiYy
phreedom_ has joined #nixos
Mateon1 has quit [Ping timeout: 240 seconds]
Mateon2 has joined #nixos
<symphorien>
I think when you callPackage a function f, it evaluates it with the provided arguments a or default values but stores f and a aside; it also defines an attibute override which when called on b will return (f (a//b))
<sphalerite>
I'm rather confused, `nix build -f '<nixpkgs/nixos/release.nix>' iso_minimal.x86_64-linux` tells me that /nix/store/default.nix doesn't exist
<sphalerite>
Anyone know why?
<exarkun1>
symphorien: I think callPackage takes a path, not a function
<{^_^}>
[nixpkgs] @costrouc opened pull request #46610 → scalapack: init at 2.0.2 → https://git.io/fAiOt
Mateon2 is now known as Mateon1
<sphalerite>
exarkun1: it takes a function, and if it's given a path it will try importing that path to get at the function
phreedom has quit [Ping timeout: 256 seconds]
<exarkun1>
sphalerite: so it takes a function or a path
<sphalerite>
yes
<sphalerite>
and the path is expected to contain a nix expression which evaluates to a function
<hexagoxel>
raagh "nix" is such search-engine-hostile naming /rant
<sphalerite>
might well not be helpful though :)
jedahan has joined #nixos
<{^_^}>
[nixpkgs] @benley opened pull request #46611 → NetworkManager: fix VPN service source locations → https://git.io/fAiOH
<{^_^}>
[nixpkgs] @e-user opened pull request #46612 → nix-selinux-policy: init at 1.0 → https://git.io/fAi3I
<greymalkin>
Is there a default haskell.packages.[??] to use for building? I keep running into errors when I try to upgrade my shell.nix from ghc802 to ghc(anything else) on the project I'm working on now.
exarkun_ has quit [Ping timeout: 246 seconds]
<greymalkin>
And the errors are not in my project, but in trying to build other hackage (or stackage?) packages on which my project is built.
xenog has quit [Ping timeout: 252 seconds]
<{^_^}>
[nixpkgs] @jtojnar opened pull request #46613 → xpra: port to gtk3 → https://git.io/fAiso
kreetx has quit [Quit: leaving]
mayhewluke has quit [Ping timeout: 246 seconds]
exarkun_ has joined #nixos
mayhewluke has joined #nixos
<WilliamHamilton[>
having solved my previous problem with `steam-run` I have another question: when doing `steam-run ./executable-file` I get a `No such file or directory` though the file is there. I think this is in general a problem solvable with patchelf, but I remember not having to use these tricks when using steam-run. Does anyone know a quicker solution or a debug method?
sbdchd_ has quit [Remote host closed the connection]
<goibhniu>
Hi WilliamHamilton[, what was the cause of the other issue?
<WilliamHamilton[>
goibhniu: it seems that in the end was the conflict between the packages declared in the global nixos configuration, and the packages in my nix-env: although I thought they were compatible (they were on the same nix-channel, and updated), there must have been some incompatibility
<WilliamHamilton[>
so I moved all to my configuration.nix, and cleared my local environment, and now I'll use the first exclusively
<{^_^}>
#46509 (by kalbasit, 2 days ago, open): bazel-watcher: init at 4d5928e
lebel has joined #nixos
lebel has left #nixos [#nixos]
sbdchd_ has quit [Ping timeout: 264 seconds]
xenog has joined #nixos
kenshinC1 has joined #nixos
Neo-- has quit [Remote host closed the connection]
nuncanada has joined #nixos
slack1256 has joined #nixos
joedevivo has joined #nixos
<{^_^}>
[nixpkgs] @jtojnar pushed 138 commits to gnome-3.30: https://git.io/fAine
sbdchd has joined #nixos
johnw has joined #nixos
johnw is now known as Guest1556
vmandela has joined #nixos
b1000101 has joined #nixos
<{^_^}>
[nixpkgs] @jtojnar pushed 68 commits to gnome-3.30: https://git.io/fAin4
Guest1556 has quit [Changing host]
Guest1556 has joined #nixos
Guest1556 is now known as johnw
<philipp[m]>
What's the procdure to enable dhcpv6 on an interface in nixos, but set a static ipv4?
<b1000101>
Hi - a noob question. I did install a package, first in user environment nix-env -iA nixos.<packagename>, then uninstalled it, included in configuration.nix as a service and then removed it and did nixos-rebuild switch. Now, I did run the garbage collector but I can still see some paths with the package /nix/store/96nc3khb2w4c2hkm1mykiz3z89sxpmjz-nixos-18.03.133188.8b92a4e6004/nixos/pkgs/servers/<packagename>. How to get rid of it co
waleee has quit [Quit: WeeChat 2.2]
<elvishjerricco>
b1000101: `nix-env` and `nixos-rebuild` both support rollbacks, so you have to delete the old generations of your profiles for each of them. You can delete *all* old generations of *all* profiles with `sudo nix-collect-garbage -d`
<b1000101>
Oh, and I have removed all the previous generations
<elvishjerricco>
oh
<elvishjerricco>
heh
<b1000101>
elvishjerricco yeap, I did that. When I try to nix-store --delete /nix/store/96nc3khb2w4c2hkm1mykiz3z89sxpmjz-nixos-18.03.133188.8b92a4e6004 it says it's still alive
<goibhniu>
b1000101: are these paths still in use? ... you can check with lsof
<elvishjerricco>
b1000101: Oh, actually I think that path you're querying is just a nixpkgs version, isn't it?
<HensonLunch>
infinisil: is it possible to get nix-build to reuse the stack directory? Downloading and compiling everything every time you want to build your stack package seems insane. The alternative is to use stack to use nix to build your package, and then create a derivation that just copies the stack-build binaries into a nix derivation.
<elvishjerricco>
The channels can also be rolled back, so they keep old versions of nixpkgs around in generations.
HensonLunch is now known as Henson
<elvishjerricco>
But nixpkgs itself isn't really the whole package; just nix expressions for it
<Henson>
stack-build -> stack-built
<infinisil>
Henson: Just use stack2nix
<elvishjerricco>
So that file will be there in your nixpkgs version no matter what
<{^_^}>
[nixpkgs] @samueldr pushed 2 commits to release-18.09: https://git.io/fAic3
orivej has joined #nixos
<elvishjerricco>
infinisil: stack2nix or stackage2nix? I always used the latter since it can convert whole stackage snapshots, not just what your project uses.
<elvishjerricco>
Makes it easier to add deps to my project later on
<Henson>
infinisil: I tried, and it create a monsterous nix file containing all haskell packages, and refuses to evaluate because a bunch of Windows and Mac OS packages are included, and various other inconsistencies.
<infinisil>
stack2nix has (almost) always worked perfectly for me :/
<elvishjerricco>
Henson: If those were the errors, it sounds like you were trying to evaluate *all* haskell packages instead of just the ones you needed
<Henson>
infinisil: maybe I was invoking it incorrectly, but for the URL path it wanted, I just specified the directory containing my stack.yml file.
<b1000101>
elvishjerricco oh, silly me...so it's actually the nixpkgs folder where info about all currently available packages is stored?
<elvishjerricco>
b1000101: Yea, looks like it
<elvishjerricco>
Henson: how were you trying to do the build after running stack2nix?
<b1000101>
elvishjerricco wow, thanks... sorry for such stupid question then, I'm using NixOs just for 3 days :) ...thanks a million
<elvishjerricco>
b1000101: Happy to help :) Takes some getting used to
<b1000101>
elvishjerricco yeap, but it's absolutely fantastic. I'm so glad I made the switch from ubuntu.
<Henson>
infinisil: so that seemed to work. It looks like it's still going to build a bunch of derivations from source. Shouldn't they all be fetched in binary form from nix-cache and not require any compilation?
<infinisil>
Nope, stack gets the exact right versions of packages, those are not usually in the cache
Guanin_ has quit [Ping timeout: 246 seconds]
<{^_^}>
[nixpkgs] @costrouc opened pull request #46615 → parmetis: init at 4.0.3 → https://git.io/fAiCZ
<Henson>
infinisil: ok
<Henson>
infinisil: I didn't know Haskell development with nix and stack would be so painful :-(
<elvishjerricco>
Henson: It's better than Stack at least, which has no concept of binary caches :P You can at least put those builds in your own cache for teammates to use.
<infinisil>
Henson: Well, you decided to want to use stack, and that's what stack needs, whether you use stack directly or via stack2nix, it will have to compile stuff
<Henson>
elvishjerricco: speaking of which, where should I look to make nix use my own private cache, in addition to nix's public cache?
semilattice has joined #nixos
<{^_^}>
[nixpkgs] @Mic92 pushed commit from @edolstra to release-18.09 « Revert "aliases: add nixos-rebuild" »: https://git.io/fAiCi
<elvishjerricco>
Henson: Probably `nix-store --serve`. This lets you specify `ssh://server-running-nix-store-serve` as an authenticated binary cache
xok has joined #nixos
<betaboon>
can anyone suggest something for CI different than hydra? I'm not happy after trying to get at-least-something work in a day without succeeding :(
grp has joined #nixos
georges-duperon has joined #nixos
<elvishjerricco>
betaboon: Yea Hydra is a massive pain. It's *good* once you get it working, but not great. I don't really have a better alternative in mind though.
<oscarvarto>
symphorien, before trying with pypi2nix, I tried this http://ix.io/1mDP
<oscarvarto>
It was failing too
ibraheemmoosa has quit [Remote host closed the connection]
jtojnar has quit [Quit: jtojnar]
<oscarvarto>
symphorien, This one fails with `Could not find a version that satisfies the requirement tornado (from cite2c==0.2.1) (from versions: )`
sbdchd has quit [Ping timeout: 272 seconds]
<symphorien>
then you need to patch the file which defines dependencies to remove this constraint
<symphorien>
I don't know the specifics but there should be examples in nixpkgs
<oscarvarto>
So, trying to manually write the derivation, when there are a lot of dependencies, also seemed innefective (and I am not experienced enough with Nix expressions)
<{^_^}>
#18678 (by chris-martin, 1 year ago, open): Documentation for mkDerivation
copumpkin has joined #nixos
<ldlework>
Is there a Nix documentation team?
<ldlework>
Or is it just like dealt with as just another part of the overall dev/maintenance
<demize>
Would be neat if there was something liket the packages or options pages for all the functions, hmm.
sigmundv has joined #nixos
<ldlework>
i wonder how i can get started helping with documentation from a planning perspective
aw has joined #nixos
spacefrogg has joined #nixos
drewr has joined #nixos
kenshinC1 has quit [Ping timeout: 244 seconds]
<exarkun1>
How do I get a .drv in /nix/store without doing a complete build?
<exarkun1>
given an expression
<hexagoxel>
i don't have an actual problem, but just out curiosity i just tried `nix-shell -p nix-info --run nix-info` and it gives "nix-shell -p nix-info --run nix-info"
xok has quit [Read error: Connection reset by peer]
<hexagoxel>
what is up with that?
<hexagoxel>
sorry, it gives "error: file 'nixpkgs' was not found in the Nix search path (add it using $NIX_PATH or -I), at (string):1:13"
<hexagoxel>
is my setup fundamentally borked?
<symphorien>
exarkun1: nix-instantiate instead of nix-build
rauno has quit [Ping timeout: 240 seconds]
<pyvpx>
oi. okay. so how do I know what nixos.python36Full or p
<pyvpx>
erm
<pyvpx>
hit enter too fast
<pyvpx>
how do I understand the difference between nixos.python36Full or nixos.python36 or nixos.python3 ?
jbgi has joined #nixos
bennofs has joined #nixos
rihards has joined #nixos
<symphorien>
python3 will be redefined as python37 at some point in the future
<exarkun1>
symphorien: thanks
<exarkun1>
any clue how I can get the segfaulting conftest or the core file from this failing configure?
<symphorien>
coredumps are managed by systemd iirc
<pyvpx>
symphorien: good to know. my question is more general, despite using specific python3 example. how can I understand differences between identical names and very similar attribute paths?
<symphorien>
pyvpx: honnestly, read the source
<symphorien>
sometimes it is easy
<symphorien>
sometimes not
fendor has quit [Ping timeout: 246 seconds]
<symphorien>
I found: python36Full = python36.override{x11Support=true;};
<pyvpx>
ok. so read the source is the way to go
<pyvpx>
didnt know if I was missing some flag combo in the manual page
<symphorien>
the manual explains that python does not contain tkinter by default
<symphorien>
so the full version should be the one with tkinter
<pyvpx>
the source? or which manual page? I was referring to man nix-env
<Henson>
infinisil: when you switched to using cabal instead of stack, do you cherry-pick the right versions, or do you just use the derivations in haskellPackages?
<infinisil>
the latter
<infinisil>
I only pin the nixpkgs version and get all deps from that
<{^_^}>
[nixpkgs] @xeji pushed commit from @costrouc to master « parmetis: init at 4.0.3 (#46615) »: https://git.io/fAizj
<Henson>
infinisil: it seems as though stack2nix didn't generate a consistent set of packages, and semigroupoids is unable to build because tagged is the wrong version :-P
rtjure has joined #nixos
<Henson>
infinisil: it also missed dependencies on a bunch of haskell packages, which I had to manually add to stack2nix's output.
<infinisil>
Does your stack project build with stack build?
<Henson>
infinisil: yes
wpcarro has quit [Ping timeout: 245 seconds]
<infinisil>
Really shouldn't be the case
<Henson>
infinisil: is there a proper way to choose an internally-consistent nixpkgs version when you want to pin nixpkgs?
dbmikus__ has joined #nixos
_ris has joined #nixos
<infinisil>
Probably want to get a version from a channel
<{^_^}>
[nixpkgs] @zimbatm pushed commit from @r-ryantm to master « google-compute-engine: 20180129 -> 20180510 (#46278) »: https://git.io/fAigh
humanoyd has joined #nixos
<{^_^}>
[nixpkgs] @zimbatm pushed commit from @r-ryantm to release-18.09 « google-compute-engine: 20180129 -> 20180510 (#46278) »: https://git.io/fAi2U
<{^_^}>
[nixpkgs] @xeji pushed to master « parmetis: set license to unfree »: https://git.io/fAi2s
<Henson>
infinisil: I've already pinned my nixpkgs to whatever nixpkgs-unstable was there at the time I pinned it. Is there a more stable channel to which I should have pinned it? I'm thinking of the difference between debian-stable where everything is well-tested and consistent with each other, and debian-unstable where things are more likely to break or have issues.
Tobba has joined #nixos
<infinisil>
Well you can of course use the stable channel, 18.03 would be the current one
sbdchd has quit [Remote host closed the connection]
<elvishjerricco>
Can we cross compile with carnix?
fragamus has joined #nixos
haslersn has joined #nixos
<grp>
when realizing a derivation, I've seen that merging the folders structure of the 'man' output into the user's profile works right, but I've been trying to put stuff into $out/lib/common-folder/package/ and packages seem to compete for ~/.nix-profile/lib/common-folder/, so at any one time I have only one sub-element in it. What am I missing? Should I wrap stuff up so that only single files are put into
<grp>
$out/lib/common-folder/ ?
<haslersn>
Hi, I just forked nixpkgs and added a package. How can I test if it works before submitting a pull request?
<symphorien>
nix-build /path/to/clone -A mypackageattr
<symphorien>
then try executing result/bin/foo
sigmundv__ has joined #nixos
<oscarvarto>
garbas: Thanks a lot! Let me check your reply. Thanks a lot! I've been stuck since yesterday
mounty1 has joined #nixos
Ericson2314 has joined #nixos
<oscarvarto>
garbas, I think I have tried to use -s also, but I may have tried with -s ipykernel instead of -s ipython
<haslersn>
Thanks
sigmundv has quit [Ping timeout: 246 seconds]
mayhewluke has quit [Ping timeout: 272 seconds]
mayhewluke has joined #nixos
page has quit [Quit: Lost terminal]
martingale has joined #nixos
Growpotkin has joined #nixos
mounty1 has quit [Ping timeout: 240 seconds]
knupfer has quit [Ping timeout: 252 seconds]
<Growpotkin>
Hey does anyone else have issues with their laptop lids opening up to a black screen?
<Growpotkin>
I tried a solutions with acpid I found but no luck
<Growpotkin>
it only happens when it is closed for a while. If I immediately open and close it's fine.
<haslersn>
should my build script for a nix package include 'cp LICENSE.txt $out' ?
<symphorien>
Depends if the license requires it. Don't put it at the root of $out in any case.
<{^_^}>
[nixpkgs] @LnL7 opened pull request #46625 → cargo-update: fix darwin build → https://git.io/fAiid
<sphalerite>
haslersn: if it's a standard licence, probably not necessary, we have the meta.license field for it
humanoyd has quit [Quit: WeeChat 2.2]
_0bitcount has quit [Remote host closed the connection]
_0bitcount has joined #nixos
<infinisil>
I wouldn't mind some written-down conventions on where stuff goes in $out
<oscarvarto>
garbas, I am getting different errors, no matter what I try... Now I am getting a Stage2: Extracting metadata from pypi.python.org ...Error: Source for path `cite2c` does not exists.
<oscarvarto>
So, apparently it succeeds with Stage 1. But then fails immediately after starting Stage 2
<rawtaz>
sphalerite: why not put stuff in root of $out (i.e., $out)?
<sphalerite>
rawtaz: nothing wrong with it, but I'd probably put it in $out/share/doc/<programname>
<sphalerite>
sort of like debian does
<rawtaz>
ah ok good, not a tech matter then :)
<rawtaz>
yeah thats true, should follow conventions. i was thinking repository mode, not right.
<{^_^}>
[nixpkgs] @LnL7 opened pull request #46626 → ceres-solver: fix darwin build → https://git.io/fAiPB
<symphorien>
rawtaz: because if you put two packages with $out/licence.txt in systemPackage the build will fail because the files collide
<{^_^}>
[nixpkgs] @xeji merged pull request #46622 → brlaser: cleanup and mark linux only → https://git.io/fAiVM
<{^_^}>
[nixpkgs] @xeji pushed commit from @LnL7 to master « brlaser: cleanup and mark linux only (#46622) »: https://git.io/fAiP0
jbgi has quit [Quit: WeeChat 2.1]
<rawtaz>
symphorien: why would they do that? i thought if im writing a derivation for my little hello world program, it will get its own directory, so any other derivation (thats not identical) should get its own directory and the files wont collide
<garbas>
oscarvarto: i'm off to bed in few minutes, can you report the problem in the issue and i will look at it in the morning
<{^_^}>
[nixpkgs] @xeji pushed commit from @LnL7 to release-18.09 « brlaser: cleanup and mark linux only (#46622) »: https://git.io/fAiP2
<symphorien>
hum right this only happens for files in a pathToLink (ie /share)
<oscarvarto>
garbas, sure. Have a good rest! Thanks for your help
<rawtaz>
right, some other type of thing than $out i take it
<{^_^}>
[nixpkgs] @LnL7 opened pull request #46628 → broken darwin packages (c) → https://git.io/fAi1a
georges-duperon has joined #nixos
xenog has quit [Remote host closed the connection]
xenog has joined #nixos
sbdchd has quit [Remote host closed the connection]
sbdchd has joined #nixos
grp has quit [Quit: box shutting down...]
sigmundv__ has quit [Remote host closed the connection]
patrl1 has joined #nixos
sigmundv has joined #nixos
<pie_>
any reason there isnt some kind of rubyPackages?
<{^_^}>
[nixpkgs] @LnL7 opened pull request #46629 → calaos_installer: fix darwin install → https://git.io/fAiME
<rawtaz>
oh, that reminds me. is there a haskellPackages somewhere in Nix(OS) that i can query with `nixos-options`?
<samueldr>
pie_: I was wondering the same the other day
<samueldr>
(but didn't ask)
npmccallum has quit [Quit: npmccallum]
<samueldr>
at a glance it looks like "anything useful" is in the main namespace (apps, tools) and gems for libraries and misc. stuff isn't made available directly
<samueldr>
(e.g. nixpkgs knows of nokogiri, in a way, but you can't nix-shell -p ...nokogiri)
<samueldr>
tilpner: if / when I do other patches or upgrades, I'll ping you
<infinisil>
tilpner: "If you want for this logger to be present on a particular chat.freenode.net channel, drop a letter to whitequark." https://irclog.whitequark.org/
<samueldr>
^ good altenative, wanted to provide the nix service independently only because this way we can diverge into myriad channels
oscarvarto has quit [Quit: Leaving]
<tilpner>
I was just proposing it for now, someone else will have to decide, and I have no idea how it would be deployed. Thanks for the offer though :)
<samueldr>
oh, and ftr, I really like what whitequark did, code is quite minimal for the whold bunch it does
<LnL>
"hundreds of users"
<LnL>
lol
mizu_no_oto has quit [Quit: Computer has gone to sleep.]
mizu_no_oto has joined #nixos
<LnL>
makes it sound like irc isn't a thing anymore
<{^_^}>
[nixpkgs] @xeji pushed commit from @LnL7 to master « calaos_installer: fix darwin install (#46629) »: https://git.io/fAiSU
<rawtaz>
hehe, i only read the first X chars of the topic, it's all that fits in my screen :)
<{^_^}>
[nixpkgs] @xeji pushed commit from @LnL7 to release-18.09 « calaos_installer: fix darwin install (#46629) »: https://git.io/fAiSt
<rawtaz>
sigh
<rawtaz>
yeah that sucks badly. really bad decision to publish logs from this irc channel
<rawtaz>
total disappointment.
Wharncliffe has joined #nixos
<tilpner>
Why do you think so?
<LnL>
eh?
<rawtaz>
it's one thing if someone wants to keep logs, but it's another thing to actively publish logs
<rawtaz>
let me put it this way - if someone is interested in what's being said in here, then feel free to join
DigitalKiwi has joined #nixos
<rawtaz>
but it's a room that one has to join to participate in - it's like a room with a door that you walk into. it's in a sense respectless to start broadcasting what is being said in that room
<LnL>
guess people can find out how many typos I make now
<LnL>
but what's the problem otherwise?
<samueldr>
counter-point: the logs are a treasure trove of solutions, them being indexed is a boon for the arcane knowledge (sadly) missing from other locations
<edef>
i do keep my own logs of here
<rawtaz>
samueldr: ive been on the irc for ages and i have yet to hear *anyone* having found the solution to a problem from published irc logs. seriously, that's REALLY rare
<{^_^}>
[nixpkgs] @xeji pushed commit from @LnL7 to master « ceres-solver: fix darwin build (#46626) »: https://git.io/fAiS8
<edef>
but i often find solutions to problems, or enough of a hint, by googling nad finding the logs from here
<edef>
*and
<samueldr>
I found solutions more than once
<{^_^}>
[nixpkgs] @xeji pushed commit from @LnL7 to release-18.09 « ceres-solver: fix darwin build (#46626) »: https://git.io/fAiS0
<andi->
rawtaz: I once did, I found multiple people with the same questions on random channels as well.. :)
<edef>
which often tells me a bunch of relevant github issues, or who to talk to to find out more
<rawtaz>
LnL: it's the publishing of an otherwised closed (but available to anyone) chat room that's disturbing. it's like i'd put a speaker on the outside of a building that you and some friends are sitting in a room in, broadcasting everything you say in that room.
<samueldr>
(and also on IRC for ages)
<edef>
rawtaz: this room isn't you and some friends
<edef>
rawtaz: it's a NixOS community venue
CodeKiwi has quit [Disconnected by services]
DigitalKiwi is now known as CodeKiwi
<sphalerite>
rawtaz: If you have a problem with using a logged channel, feel free not to participate. It's disclosed right there in the topic, and is done because it's a valuable resource
<ldlework>
rawtaz has it all wrong anyway
<ldlework>
this channel is not like a room with a door
<sphalerite>
also nice for catching up if my internet goes down :)
<rawtaz>
edef: it's still a room and not an open space in a colosseum or similar
<ldlework>
it is like a square in a public forum
<sphalerite>
rawtaz: this one *is* an open space because it's publicly logged.
<ldlework>
in a public park
<edef>
rawtaz: that's your take, tbh
<LnL>
this is a public channel on the internet
<rawtaz>
sphalerite: i am not debating whether or not it's disclosed. im voicing my opinion on the matter that it's being done.
<ldlework>
i don't know how many times i've found infinisil or clever discussing something a year ago that solves my problem
<LnL>
dunno what's closed about that
<ldlework>
or sphalerite
<ldlework>
hell
<ldlework>
i've even found my own conversations with infinisil where he already answered the question I'm looking into
<ldlework>
lmao
<rawtaz>
ldlework: the fact that you have to actively join this chat room/channel/whatever you want to call it makes it more similar to a room that you have to enter by opening a door, than an open space out in the public.
<rawtaz>
edef: yes, it's my take
<ldlework>
you have to walk to a public forum
<samueldr>
the worse: seeing past-self with the answer
mizu_no_oto has quit [Quit: Computer has gone to sleep.]
Barnabas[m] has joined #nixos
<rawtaz>
i understand how you think it's practical to publish solutions etc. i just feel it's wrong to automatically publish what people are saying, that's all. but each to their own.
<rawtaz>
since there's literally nothing i can do about it, ill just have to accept it or something like that
<ldlework>
it is *rude* to publish logs without telling anyone first
<ldlework>
but it isn't wrong
<rawtaz>
or start a competing nixos channel :>
<ldlework>
there are no guarantees for anything
<ldlework>
anywhere
<infinisil>
Please take this to #nixos-chat
<rawtaz>
on a constructive note, the channel topic could be much clearer on the fact that it does publish logs, than one url amongst a bunch of other urls, something like: "Channel logs: <url>"
<rawtaz>
infinisil: too late :P we're done
martingale has joined #nixos
<rawtaz>
oh wait, i didnt see the "Logs: " - never mind what i said
<JonReed>
I think publishing it by default is the way do go. It just wasted everybody's time when somebody asks the same question that was already asked 100 times. If it's published you can just search logs and find what you're looking for
<rawtaz>
its clear enough
<sphalerite>
this pointless discussion brought to you by: rawtaz not reading the topic
<sphalerite>
:D
<rawtaz>
JonReed: yeah and how many do you think come in here and goes to search through logs? hardly any. very few even notice that logs link :)
<ldlework>
it is painless to point people to them
<JonReed>
I would rather stumble on my own comment in the logs and become red and embarrased reading something stupid I said, than to loose the utility of having a search through logs
<rawtaz>
infinisil: sorry about that
<JonReed>
rawtaz: I do. I always in IRC logs for every channel I just before asking some question. And it's very annoying when the channel doesn't have logs.
<rawtaz>
sphalerite: ;)
<ldlework>
you can always use a pseudonymnmnymn
<sphalerite>
also useful for people who don't have reliable internet connections or access to a server with such for running a bouncer! :)
<emily>
it's freenode. many big channels are publicly logged.
<edef>
Ericson2314: is there any documentation on the state of musl things?
martingale has quit [Ping timeout: 252 seconds]
<emily>
you should check the topic when you join if you're twitchy about logs -- it's required to disclose logging on entry in some way per freenode guidelines
<sphalerite>
edef: you can try it for yourself — `nix build -f channel:nixos-unstable pkgsCross.musl64.hello`
<rawtaz>
emily: just on a general note, something being done often or much doesnt necessarily mean that its right or good. just saying, unrelated to this discussion
<edef>
sphalerite: i sort of specifically want to not use cross
<sphalerite>
edef: oh
<rawtaz>
emily: yeah, most often i notice it in the topic. not this time though :)
<sphalerite>
idk then
<edef>
sphalerite: which seems to error out with trying to run /bin/bash
<edef>
sphalerite: even though there appears to be a stdenv bootstrap for musl
<sphalerite>
edef: huh. It works for me
<edef>
sphalerite: maybe i should check what crossSystem gets set to
<edef>
sphalerite: what's the system value you're using?
<edef>
sphalerite: oh. you mean cross works
<edef>
sphalerite: yeah, i bet cross works
<sphalerite>
edef: yep
graphene has quit [Remote host closed the connection]
graphene has joined #nixos
<emily>
rawtaz: sure. just, it is what it is; big freenode channels tend to be fairly open, public spaces by culture
<haslersn>
If I install a package via 'nix-env -i pkgname -f reponame/archive/branch.tar.gz', what would be the equivalent to install it in the system packages?
magnetop` has quit [Remote host closed the connection]
jackdk has joined #nixos
sanscoeu_ has quit [Ping timeout: 272 seconds]
fragamus has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
jluttine has quit [Ping timeout: 252 seconds]
haslersn has quit [Ping timeout: 252 seconds]
oscarvarto has joined #nixos
xenog has quit [Ping timeout: 252 seconds]
vaibhavsagar has quit [Ping timeout: 244 seconds]
jluttine has joined #nixos
lassulus_ has joined #nixos
Ericson2314 has quit [Ping timeout: 272 seconds]
fragamus has joined #nixos
lassulus has quit [Ping timeout: 244 seconds]
lassulus_ is now known as lassulus
sbdchd has quit [Remote host closed the connection]
derped has joined #nixos
mayhewluke has quit [Ping timeout: 246 seconds]
mayhewluke has joined #nixos
martingale has joined #nixos
dbmikus_ has quit [Ping timeout: 246 seconds]
tzemanovic has quit [Remote host closed the connection]
martingale has quit [Ping timeout: 240 seconds]
tzemanovic has joined #nixos
jperras has joined #nixos
lord| has quit [Ping timeout: 245 seconds]
lord| has joined #nixos
<{^_^}>
[nixpkgs] @jtojnar pushed to master « gnome2.gtkglextmm: drop »: https://git.io/fAibq
roni has joined #nixos
<roni>
hi all! i just posted a rather long topic to the discourse instance, and instead of seeing the new post, i get an error message that says "Oops! That page doesn’t exist or is private.