<infinisil>
boxofrox: Needs a ControlPath to work too
tmaekawa has quit [(Quit: tmaekawa)]
<boxofrox>
infinisil: you can add `-o ControlPath=path/to/control-master` to the ssh commands
NixOS_GitHub has joined #nixos
<NixOS_GitHub>
[nixpkgs] Ericson2314 opened pull request #32827: CODEOWNERS: Add me, @Ericson2314, to a few things (master...codeowners) https://git.io/vbPwT
NixOS_GitHub has left #nixos []
<infinisil>
boxofrox: umm, file doesn't exist
<infinisil>
and when i touch it, connection refused
<infinisil>
whatever
<boxofrox>
infinisil: sorry, i'm confused. did you use `path/to/control-master` or swap in the appropriate path for your system?
<boxofrox>
if you're trying to reuse an existing connection with ControlMaster, `ssh -o ControlMaster=auto` should be sufficient, and leave the control socket location to the default setting.
<boxofrox>
infinisil: i may be wrong about a default control path. `man ssh_config` doesn't specify a default value, and I wrongly recalled seeing one there.
<infinisil>
Hehe
<boxofrox>
infinisil: anyhow, using touch to create the control path file won't work because the file is supposed to be a unix socket.
<infinisil>
IT WORKED
<boxofrox>
congrats :)
<infinisil>
The linked answer is key
<infinisil>
The GatewayPorts's sshd option specifically
<boxofrox>
good to know
<infinisil>
I'm sure as hell gonna commit these changes, damn
<Lisanna>
Anyone have any handy patterns for building many versions of the same thing but linked to different versions of a library, without killing my disk space?
<Lisanna>
because the naïve way would have n full copies of the product, the only difference between them being the rpaths of some of the binaries
<infinisil>
Lisanna: optimize-store?
<infinisil>
that hardlinks all same files in the nix store
<pkill9>
how do you use nix-build? I'm reading the nix-build section of the manual. I keep getting this error: `error: cannot auto-call a function that has an argument without a default value (‘stdenv’)`
<pkill9>
i feel like it's not taking into account the nixpkgs channel
<pkill9>
so isn't 'seeing' the variables it includes, which I assume are the packages
<infinisil>
pkill9: Are you in a nixpkgs checkout? If so, then use `nix-build -A pkgname` instead of directly calling the file
<pkill9>
i don't know, so i assume not
<infinisil>
pkill9: what are you nix-building, which file?
<Lisanna>
infinisil: that would work somewhat, although that's not so great for when you have to copy packages between two different nix stores
<infinisil>
pkill9: Then modify the file, and `nix-build -A qutebrowser` in the nixpkgs directory
<pkill9>
ah i see, so you need to be in the whole package-channel tree when building for nix-build to see all the other packages?
drakonis has joined #nixos
dan_b has joined #nixos
<infinisil>
pkill9: yeah, nixpkgs gives a specific version of everything, which it needs to build stuff
sworne has joined #nixos
Sonarpulse has quit [(Ping timeout: 255 seconds)]
sbjorn has quit [(Ping timeout: 255 seconds)]
<pkill9>
just to note if you suggest cloning that repo to anyone else, add `--depth 1` to the `git clone` command so it doesn't clone the entire history of the repo also
sworne has quit [(Client Quit)]
<infinisil>
Well the history is quiet useful in a lot of usecases actually :2
<infinisil>
but yeah it's pretty big
cmiles74 has quit [(Ping timeout: 248 seconds)]
erasmas has quit [(Quit: leaving)]
<infinisil>
Alright, I'm going to bed, see ya ;)
<pkill9>
cya, thanks for the help
Mic92 has quit [(Ping timeout: 255 seconds)]
digitus has quit [(Quit: digitus)]
jb55 has joined #nixos
ssmike has joined #nixos
johnsonav has quit [(Read error: No route to host)]
jsgrant has joined #nixos
leothrix has quit [(Quit: ZNC 1.6.5 - http://znc.in)]
ssmike1 has joined #nixos
hellrazor has joined #nixos
ssmike has quit [(Ping timeout: 240 seconds)]
ssmike1 is now known as ssmike
<dhess>
is it a bad idea to run Hydra on a build machine?
<dhess>
should the Hydra master not be a part of the build pool?
<clever>
dhess: ive seen deadlock issues with hydra builds on localhost
<dhess>
clever: so your Hydra you help maintain, the Hydra master is not in the pool?
<clever>
most of them build on seperate machines, i found one yesterday that was unable to build anything, because hydra grabbed a lock on $x, then ssh;d into itself to build $x, which waited on the lock, forever
<clever>
ah, if the slave is literally just "localhost" it special-cases it to not break
<clever>
still not clear why i saw it break on that recent system
<clever>
oh, the user is set in the common options, so it was root@localhost
<clever>
which fails the check
<clever>
to git blame!
<dhess>
oh ouch
<clever>
yeah, it should have been broken for months, cant see why it worked until just recently
ryantm has quit [(Quit: Connection closed for inactivity)]
evhan has quit [(Ping timeout: 240 seconds)]
<palo>
Hey I want to work on a package using my overlay. I used it in my configuration.nix but I dont like that anymore. So I put it into ~/.config/nixpkgs/overlay.nix I put in my README on how to test if the build works. (using nix-build). But I could not figure out on testing if the app works. I expect to use nix-shell -p newpencil (for example). But I guess I did not unterstand how overlays and ~/.config/nixpkgs/o
<palo>
maybe somebody has a good hint on how to install a package from an overlay in a sandbox (like nix-shell)
tejing has joined #nixos
dieggsy has joined #nixos
thc202 has quit [(Ping timeout: 264 seconds)]
jtojnar has quit [(Quit: jtojnar)]
jtojnar has joined #nixos
jb55 has quit [(Ping timeout: 256 seconds)]
<palo>
Ah it was a typo
<palo>
it is overlays.nix not overlay.nix :D
<palo>
now everything works like expected !
<tejing>
the latest steam update broke the nixos steam package. I searched around a bit and I see people talking about fixes and backporting them into 17.09, like here: https://github.com/NixOS/nixpkgs/issues/32687
<tejing>
but doing a upgrade doesn't fix the issue, so I'm wondering how I get the patch into my system now
<tejing>
I assume it just hasn't gotten in there yet
<samueldr>
looking into it, then I'll explain tricks I use to know
<samueldr>
so your assumption is right, it hasn't gotten in there yet
ssmike has quit [(Ping timeout: 272 seconds)]
<samueldr>
oh, looking at the PR, it seems to have been reverted
<samueldr>
ah, and it has been fixed right after (looking at the commit history)
oahong has quit [(Ping timeout: 260 seconds)]
<tejing>
ok, so practical upshot: how do I get the fix on my system now?
jb55 has joined #nixos
<samueldr>
if you're using a nixpkgs checkout for your system, you could apply that commit in it
<samueldr>
otherwise, I'm sorry, I don't know yet the best way
<tejing>
hmm, well it sounds like I shouldn't have long to wait before it goes out anyway. if there isn't a simple solution to getting it now maybe waiting is the most sensible thing to do
<gchristensen>
NIX_PATH=nixpkgs=https://github.com/NixOS/nixpkgs/archive/release-17.09.tar.gz nix-shell -p steam will get you a new steam
<samueldr>
\o/ I was writing up that some invocation of nix-shell probably should work
<gchristensen>
:D
<aanderse>
damned steam... breaking on everyone
<aanderse>
ps. thanks again for the help the other night :)
erictapen has quit [(Ping timeout: 264 seconds)]
<aanderse>
gamed out for a couple hours saturday night as planned
<aanderse>
:D
<samueldr>
error: undefined variable ‘will’ at (string):1:74
<samueldr>
that's what I get for copying from IRC without reading :)
<gchristensen>
hah
<samueldr>
(I copied the whole line like an idiot)
oahong has joined #nixos
oahong has quit [(Changing host)]
oahong has joined #nixos
Guest84811 has quit [(Quit: My MacBook has gone to sleep. ZZZzzz…)]
ssmike has joined #nixos
evhan has joined #nixos
<tejing>
the nix-shell thing worked great, tyvm :-)
<gchristensen>
w00t
<pkill9>
if i install something by running `nix-build -A package-ver`, how can i run `nix-env -i package-ver`?
<dhess>
Anyone here doing NixOps deployments from a macOS box?
<gchristensen>
nix-build doesn't install, it just builds it
<pkill9>
gchristensen: how do i refer to it from nix-env without supplying the path?
<pkill9>
e.g. if i build multiple versions and just wanna switch between them
<gchristensen>
you can do nix-env -i ./result (nix-build puts a link to the output path in ./result by default) but why do you want to nix-env it at all, I wonder?
hotfuzz has joined #nixos
<pkill9>
I'm trying to understand where nix-env refers to package names/versions
<pkill9>
when you do e.g. `nix-env -i packagename`
<pkill9>
and if you do nix-build how it is referred to by nix-env
<gchristensen>
is there a goal for after you learn this?
hotfuzz_ has quit [(Ping timeout: 256 seconds)]
ssmike has quit [(Ping timeout: 255 seconds)]
* dhess
fires up Ansible and cries
<pkill9>
gchristensen: to be able to switch between versions of the same package with 'nix-env -i packagename-version`
<gchristensen>
(I promise I'm not trying to be rude, I think I have a better solution for you) and why do you want to do that?
<pkill9>
honestly, just because I read that you can have multiple versions of packages installed side-by-side, i don't really have a serious use-case :P I just feel like that implies i could switch between different versions of the same package just by passing the version you want
<gchristensen>
ah
<gchristensen>
ok! cool
<gchristensen>
in three different terminals try doing: nix-shell -p ruby_2_0 , nix-shell -p ruby_2_1 , nix-shell -p ruby_2_2
NixOS_GitHub has joined #nixos
<NixOS_GitHub>
[nixpkgs] orivej opened pull request #32830: Fix build of 3 perl packages with ld-is-cc-hook (staging...ld-is-cc) https://git.io/vbPMj
NixOS_GitHub has left #nixos []
<pkill9>
hmm in all of them, the output of `ruby --version` is "ruby 2.2.8p477 (2017-09-14 revision 59906) [x86_64-linux]"
dieggsy has quit [(Quit: ERC (IRC client for Emacs 27.0.50))]
<NixOS_GitHub>
[nixpkgs] romildo opened pull request #32839: connman: enable support for Wireless daemon for Linux (iwd) (master...connman) https://git.io/vbXGU
NixOS_GitHub has left #nixos []
Itkovian_ has joined #nixos
ixxie has joined #nixos
civodul has joined #nixos
rodgort has quit [(Quit: Leaving)]
Itkovian has quit [(Ping timeout: 260 seconds)]
dywedir has quit [(Remote host closed the connection)]
vidbina has joined #nixos
dywedir has joined #nixos
rodgort has joined #nixos
tusj has quit [(Ping timeout: 272 seconds)]
RayNbow` has joined #nixos
RayNbow`TU has quit [(Ping timeout: 248 seconds)]
otherjrolfs has joined #nixos
ilja_kuklic has quit [(Ping timeout: 263 seconds)]
otherjrolfs has quit [(Ping timeout: 260 seconds)]
rvolosatovs has joined #nixos
<rvolosatovs>
Hello. What would be the correct approach to debug issues like this: collision between `/nix/store/6cgambzmvaqxmbfp8adzngnpqd4fhf3b-gst-python-1.10.4/lib/python2.7/site-packages/gi/overrides/__init__.pyc' and `/nix/store/iscj8s9xj9l893b0ndwi67ss9169sq16-python2.7-pygobject-3.24.1/lib/python2.7/site-packages/gi/overrides/__init__.pyc' ?
<rvolosatovs>
during nixos-rebuild
b has quit [(Quit: Lost terminal)]
pie_ has quit [(Quit: Leaving)]
<rvolosatovs>
What does this error actually mean? Does in mean I have 2 packages to-be-installed in my environment, which provide gi overrides for python and the md5 hash of __init__.pyc of those differ?
iyzsong has joined #nixos
<Lisanna>
rvolosatovs: it means your environment is trying to include two packages that have files with the same path, so it doesn't know which one it should symlink to
<Lisanna>
on a non-NixOS system, you couldn't have both of those packages installed at the same time either without doing something special, since they would try to place files in the same place
otherjrolfs has joined #nixos
<Lisanna>
I'm not sure what the default behavior for the nixos-rebuild environments is regarding complaining only if the hashes mismatch
<rvolosatovs>
Okay, so how can I fix this?
<rvolosatovs>
Before I could fix issues like this with `nix-collect-garbage`
<rvolosatovs>
not sure why it worked, but it did
<rvolosatovs>
Now this approach does not work anymore
<Lisanna>
I don't think nix-collect-garbage was fixing those issues. Collisions usually are only warnings, not errors. So if you issued nixos-rebuild a second time and the only thing you did in between them was nix-collect-garbage, it won't give you those warnings again, since it doesn't need to rebuild that.
<Lisanna>
I get collision warnings all the time during my nixos rebuilds
otherjrolfs has quit [(Ping timeout: 256 seconds)]
<rvolosatovs>
In my case the system does not build because of the collision
<rvolosatovs>
building path(s) ‘/nix/store/vd05bsj1fms3pb7fh8wf0x2r2hy73y76-python-2.7.14-env’
<rvolosatovs>
collision between `/nix/store/6cgambzmvaqxmbfp8adzngnpqd4fhf3b-gst-python-1.10.4/lib/python2.7/site-packages/gi/overrides/__init__.pyc' and `/nix/store/iscj8s9xj9l893b0ndwi67ss9169sq16-python2.7-pygobject-3.24.1/lib/python2.7/site-packages/gi/overrides/__init__.pyc'
<rvolosatovs>
builder for ‘/nix/store/h65ak38nji3ir4ipswl9s77z50g5dgiv-python-2.7.14-env.drv’ failed with exit code 25
<rvolosatovs>
YY
<rvolosatovs>
any idea?
<rvolosatovs>
or is this "exit code 25" something unrelated to the collision?
yegortimoshenko has quit [(Ping timeout: 264 seconds)]
<Lisanna>
Nothing specific, no, sorry ):
<Lisanna>
other than "whatever two things are depending on those packages are not compatible with eachother and you just can't have them both installed" ):
<rvolosatovs>
Hmm.. the funny thing is, I don't modify my python environment manually and mostly don't even install packages in environment of the system. This happens after I do `services.mopidy.enable = true`
<rvolosatovs>
So I assume that should work, as that's pretty much only python package installed in the system
nuncanada has joined #nixos
jensens has joined #nixos
<Lisanna>
I'd bank on mopidy having a problem, sounds like you've had some other issues with it recently
<Lisanna>
it might be doing something that is incompatible with something else you specifically have enabled... nixos modules are not very well isolated from eachother
otherjrolfs has joined #nixos
MasseR has quit [(Quit: WeeChat 1.7.1)]
<rvolosatovs>
Yeah, I had issues with it on nixos-unstable, it didn't start, then I switched to nixos-17.09 and it doesn't even build anymore
<Lisanna>
Oh, what do you have in extensionPackages?
<rvolosatovs>
I commented that out to not cause any issues
<Lisanna>
I bet that's what's biting you
<Lisanna>
oh
sary has quit [(Ping timeout: 240 seconds)]
<Lisanna>
I've got nothin' then ):
sary has joined #nixos
<rvolosatovs>
Alright, thanks for taking your time to help!
i-am-the-slime has quit [(Ping timeout: 272 seconds)]
yegortimoshenko has joined #nixos
<joko>
Hello, has anyone used VMware Professional on NixOS?
<yegortimoshenko>
rvolosatovs: you can prioritize one package over another via stdenv.lib.hiPrio
<yegortimoshenko>
(or alternatively, demote another via stdenv.lib.lowPrio)
<yegortimoshenko>
joko: i don't think that any vmware software is packaged yet. i've tried packaging vmware player, but i quickly lost interest. it should not be too hard, though.
<NixOS_GitHub>
[nixpkgs] grahamc pushed 1 new commit to master: https://git.io/vbX8G
<NixOS_GitHub>
nixpkgs/master 035aca9 Graham Christensen: electron: Properly handle evaluating on unsupported archs
NixOS_GitHub has left #nixos []
simukis has joined #nixos
<Lisanna>
joko: I feel you. patchelf is a terrifying tool.
<yegortimoshenko>
joko: i don't think you'll need patchelf, you'll probably need buildFHSUserEnv instead
raynold has quit [(Quit: Connection closed for inactivity)]
RayNbow` has quit [(Read error: Connection reset by peer)]
<srhb>
patchelf feels a lot more lightweight than resorting to fhsenvs..
<srhb>
Then again, I may just be crazy. I like it. :-P
<yegortimoshenko>
srhb: it's just patchelf is not a very good tool for dealing with self-extracting installers
<srhb>
Oh, very true.
<srhb>
Been there. :/
NixOS_GitHub has joined #nixos
<NixOS_GitHub>
[nixpkgs] rycee pushed 2 new commits to master: https://git.io/vbX4r
<NixOS_GitHub>
nixpkgs/master 51fcd88 Robert Helgesson: perl-B-C: fix homepage
<NixOS_GitHub>
nixpkgs/master 424427f Robert Helgesson: perl-boolean: 0.45 -> 0.46
NixOS_GitHub has left #nixos []
Guest18 has joined #nixos
dan_b has quit [(Ping timeout: 240 seconds)]
<yegortimoshenko>
srhb: buildFHSUserEnv works every time, and was recently fixed (in c rewrite) to work inside nix sandbox so can be used for self-extracting installers
<srhb>
Nice!
<srhb>
I was unaware of that.
<Lisanna>
yeah, I'm going to use buildFHSUserEnv for dealing with the Intel Parallel Studio installer, which is a self-extracting installer x_x
<Lisanna>
srhb: patchelf *feels* nice, as long as you don't look too closely at the terrifying messages it outputs sometimes
<Lisanna>
like, sometimes it will make empty holes in your binary to deal with kernel bugs :)
otherjrolfs has quit [(Ping timeout: 272 seconds)]
NixOS_GitHub has joined #nixos
<NixOS_GitHub>
[nixpkgs] mbode opened pull request #32842: docker_compose: add darwin to platforms (master...docker_compose_darwin) https://git.io/vbXEC
NixOS_GitHub has left #nixos []
i-am-the-slime has quit [(Ping timeout: 268 seconds)]
<srhb>
I wonder if this is just because the queue-runner runs with -v by default
<srhb>
It's probably a verbosity flag
<srhb>
lol
<srhb>
hydra-queue-runner --help: error: unrecognised flag '--help'. Try 'hydra-queue-runner --help' for more information.
<srhb>
:D
otherjrolfs has joined #nixos
proteusguy has quit [(Ping timeout: 265 seconds)]
<joepie91>
haha
<vcunat>
:-D
<vcunat>
reminds me of $ command-not-found nix-env
<srhb>
Oh, that sounds fun too :P
freusque has quit [(Quit: WeeChat 1.9.1)]
otherjrolfs has quit [(Ping timeout: 264 seconds)]
iyzsong has quit [(Ping timeout: 272 seconds)]
drakonis has joined #nixos
i-am-the-slime has quit [(Ping timeout: 248 seconds)]
freusque has joined #nixos
proteusguy has joined #nixos
dan_b has quit [(Ping timeout: 264 seconds)]
<gerschtli>
hey, does anyone know, how to set a fixed ip for nixops virtualbox deployments?
<srhb>
The easiest way is probably to add an extra interface alongside whatever device nixops is using. You'll have to figure out the modifyvm command and feed it to deployment.virtualbox.vmFlags, and then also set up the interface in your actual configuration.
<srhb>
I do something similar for virtd.
dieggsy has joined #nixos
szicari has joined #nixos
<gerschtli>
do you know what the purpose of private_ipv4 in the nixops config is? I thought, assigning an ip there would solve my problem, but it doesn't work in that way
freusque has quit [(Ping timeout: 272 seconds)]
ertes-w is now known as supercynic
<srhb>
Nope.
civodul has quit [(Quit: ERC (IRC client for Emacs 25.3.1))]
<gerschtli>
doesn't seem to exist an option to set via vmFlags..
evhan has quit [(Ping timeout: 265 seconds)]
<srhb>
I can't see a way to do it then.
* sphalerite
joins the chorus: "Anyone know how to get steam working today?"
<gchristensen>
NIX_PATH=nixpkgs=https://github.com/NixOS/nixpkgs/archive/release-17.09.tar.gz nix-shell -p steam will get you a new steam
* __Sander__
is amazed how important steam is
<srhb>
Muh factorios.
* gchristensen
considers teaching {^_^} !steam
<sphalerite>
hmmmmnope, no change since current state of nixos-17.09
<sphalerite>
it's like Valve try to break it as quickly as possible just as soon as we've fixed it
* sphalerite
tries master
dieggsy has quit [(Remote host closed the connection)]
dieggsy has joined #nixos
<sphalerite>
Steam is the only place to get the game data for Barony's beta for now. I can build barony from source and just run it from there, but need the data first >_>
jb55 has quit [(Ping timeout: 268 seconds)]
i-am-the-slime has joined #nixos
dieggsy has quit [(Ping timeout: 265 seconds)]
NixOS_GitHub has joined #nixos
<NixOS_GitHub>
[nixpkgs] vcunat pushed 5 new commits to staging: https://git.io/vbX68
<NixOS_GitHub>
nixpkgs/staging 7535385 Spencer Baugh: curl: use the "kerberos" package rather than specifically GNU gss...
<NixOS_GitHub>
nixpkgs/staging 3c51628 Vladimír Čunát: fetchurl: switch to the usual curl...
NixOS_GitHub has left #nixos []
steshaw has quit [(Quit: Connection closed for inactivity)]
<sphalerite>
Right so steam is broken on release-17.09 but works on master
jcbrand_ has joined #nixos
<page>
sphalerite: steam should be fixed in 17.09, but not in the channel yet
NixOS_GitHub has joined #nixos
<NixOS_GitHub>
[nixpkgs] Ma27 opened pull request #32845: test-driver: support testing user units (master...test-driver/allow-user-units) https://git.io/vbXiX
NixOS_GitHub has left #nixos []
<sphalerite>
page: I tried installing it from release-17.09 but it didn't help
reinzelmann has quit [(Quit: Leaving)]
asuryawanshi has quit [(Ping timeout: 265 seconds)]
<page>
huh, issue 32687 or different?
pkill9 has joined #nixos
yegortimoshenko has quit [(Remote host closed the connection)]
yegortimoshenko has joined #nixos
<sphalerite>
yeah looks like the same
<sphalerite>
maybe I did it wrong somehow. Oh well, it works now.
<sphalerite>
On master at least
tusj has joined #nixos
coot_ has joined #nixos
pie_ has quit [(Remote host closed the connection)]
i-am-the-slime has quit [(Ping timeout: 272 seconds)]
pie_ has joined #nixos
i-am-the-slime has joined #nixos
NixOS_GitHub has joined #nixos
<NixOS_GitHub>
[nixpkgs] vbgl opened pull request #32846: coqPackages.tlc: init at 20171206 (master...coq-tlc-20171206) https://git.io/vbX13
NixOS_GitHub has left #nixos []
pkill9 has quit [(Quit: WeeChat 1.9.1)]
pkill9 has joined #nixos
asseadinho has joined #nixos
asuryawanshi has joined #nixos
jcbrand_ has left #nixos ["Disconnected: closed"]
MercurialAlchemi has quit [(Ping timeout: 264 seconds)]
pkill9 has quit [(Quit: WeeChat 2.0)]
pkill9 has joined #nixos
b has joined #nixos
civodul has joined #nixos
freusque has joined #nixos
orivej has joined #nixos
jb55 has joined #nixos
pie_ has quit [(Ping timeout: 256 seconds)]
dan_b has joined #nixos
erasmas has joined #nixos
ylwghst has joined #nixos
freusque has quit [(Quit: WeeChat 1.9.1)]
i-am-the-slime has quit [(Ping timeout: 265 seconds)]
otherjrolfs has joined #nixos
jrolfs has joined #nixos
freusque has joined #nixos
pie_ has joined #nixos
mmlb has joined #nixos
NixOS_GitHub has joined #nixos
<NixOS_GitHub>
[nixpkgs] 7c6f434c pushed 1 new commit to master: https://git.io/vbXHG
<NixOS_GitHub>
nixpkgs/master e618aad Michael Raskin: lispPackages.cl-fuse: compile the small wrapper library manually, because for some reason NIX_LDFLAGS get lost with the new binutils wrapper
NixOS_GitHub has left #nixos []
Sonarpulse has joined #nixos
otherjrolfs has quit [(Ping timeout: 265 seconds)]
jrolfs has quit [(Ping timeout: 265 seconds)]
cmiles74 has joined #nixos
dan_b has quit [(Ping timeout: 255 seconds)]
NixOS_GitHub has joined #nixos
<NixOS_GitHub>
[nixpkgs] bjornfor force-pushed apache-directory-studio from e590c69 to cb80a4c: https://git.io/vbXQb
<NixOS_GitHub>
nixpkgs/apache-directory-studio cb80a4c Bjørn Forsman: apache-directory-studio: init at 2.0.0.v20170904-M13
NixOS_GitHub has left #nixos []
mrkgnao has joined #nixos
<mrkgnao>
I have an FHSUserEnv that needs access to my Nvidia drivers. what package provides them? (is it even possible to install those packages "normally"?)
<yegortimoshenko>
mrkgnao: is libGL.so all you need?
NixOS_GitHub has joined #nixos
<NixOS_GitHub>
[nixpkgs] bjornfor deleted apache-directory-studio at cb80a4c: https://git.io/vbX7G
NixOS_GitHub has left #nixos []
<pkill9>
are you running NixOS or just the Nix package manager on a non-NixOS mrkgnao?
i-am-the-slime has joined #nixos
phdoerfler has joined #nixos
otherjrolfs has joined #nixos
jrolfs has joined #nixos
NixOS_GitHub has joined #nixos
<NixOS_GitHub>
[nixpkgs] bjornfor opened pull request #32849: apache-directory-studio: init at 2.0.0.v20170904-M13 (master...apache-directory-studio) https://git.io/vbX5E
NixOS_GitHub has left #nixos []
<the-kenny>
What's the correct way to package a compiler that translates to C and then calls gcc on that code, but always depends on (at least) a few libraries?
<the-kenny>
A simple way would be putting gcc and the libs in `propagatedBuildInputs`, but that doesn't feel right
Lisanna has quit [(Ping timeout: 260 seconds)]
<avn>
the-kenny: libs to propagated....., gcc is always in stdenv ;)
iqubic has joined #nixos
<iqubic>
Which package provides the strip command?
<the-kenny>
avn: but that wouldn't work when the compiler is installed via nix-env
<catern>
the-kenny: should be straightforward, if you want to fix the libraries it uses at build time: just have the compiler bundle the libraries, i.e., have it remember the location of the libraries
<iqubic>
Stack is complaining that it can't find the strip command.
<the-kenny>
catern: so do we have a `gccWithPackages` or similar? :)
<iqubic>
Also, what options for TeX do we have on NixOs?
<the-kenny>
avn: that was actually done using wrapProgram (by prefixing PATH, NIX_LDFLAGS and NIX_CFLAGS_COMPILE). It doesn't seem to work anymore though.
otherjrolfs has quit [(Ping timeout: 265 seconds)]
<the-kenny>
Maybe I should've said earlier that I'm playing around with nixpkgs's gnu-cobol
jrolfs has quit [(Ping timeout: 248 seconds)]
<avn>
most scary language, which I heard about ;)
<the-kenny>
I agree
<the-kenny>
so gnu-cobol translates Cobol to C, then calls gcc. The generated source at least needs gmp and db.
<samae>
Is there something intermediate between runCommand and a full blown mkDerivation? Like producing an out path from a (bash) script.
<vcunat>
samae: that's what runCommand does
<samae>
but like can I use $out in there?
<vcunat>
yes
hotfuzz_ has joined #nixos
<the-kenny>
So I guess I need to strace a bit more to check why NIX_LDFLAGS aren't honored
<vcunat>
samae: if you don't produce $out, derivation will actually fail to build
<samae>
ok \o/ seems perfect then
<vcunat>
:-)
rogue_koder has joined #nixos
<mrkgnao>
sorry I went offline
hotfuzz has quit [(Ping timeout: 248 seconds)]
NixOS_GitHub has joined #nixos
<NixOS_GitHub>
[nixpkgs] peti opened pull request #32854: Switch Haskell package set to LTS-10.x / GHC 8.2.2 (master...haskell-updates) https://git.io/vbXb7
NixOS_GitHub has left #nixos []
<mrkgnao>
yegortimoshenko: no, I need libcuda.so (and possibly other things, but the first error I hit says libcuda.so)
<mrkgnao>
pkill9: NixOS, unstable
i-am-the-slime has quit [(Ping timeout: 268 seconds)]
rihards has joined #nixos
asseadinho has quit [(Quit: Leaving.)]
jcburnham has joined #nixos
<mrkgnao>
if it helps, I'm trying to use the Haskell bindings to TensorFlow. the only Nix support is in the form of an FHS chroot, but that script is a non-GPU setup.
jrolfs has joined #nixos
<mrkgnao>
and the lack of .so files is where I'm hitting a wall. I've been able to fix other missing .so's by adding packages to the environment (e.g. cudatoolkit).
freusque has joined #nixos
<mrkgnao>
but this one has me stumped. I don't even know if drivers are normal packages.
asuryawanshi has quit [(Remote host closed the connection)]
otherjrolfs has joined #nixos
jcb_ has quit [(Quit: Page closed)]
<iqubic>
How the heck does TeX work on NixOS?
<iqubic>
Reading the manual section is not helping me.
<vcunat>
iqubic: we can try to do something about that
<vcunat>
(I wrote most of the TeX packaging and docs)
jrolfs has quit [(Ping timeout: 260 seconds)]
erictapen has quit [(Ping timeout: 240 seconds)]
asuryawanshi has joined #nixos
otherjrolfs has quit [(Ping timeout: 260 seconds)]
<hyper_ch>
vcunat: howdy
<vcunat>
hello
<Baughn>
I'm missing the /dev/dri directory. Anyone know what is supposed to provide the udev rules for that?
<Baughn>
Context: Attempting to *not* run an X window manager, still want /dev/dri for wayland.
NixOS_GitHub has joined #nixos
<NixOS_GitHub>
[nixpkgs] Ericson2314 pushed 1 new commit to staging: https://git.io/vbXAT
<NixOS_GitHub>
nixpkgs/staging 13acbea John Ericson: Merge branch 'master' into staging
NixOS_GitHub has left #nixos []
Tucky has quit [(Ping timeout: 248 seconds)]
<vcunat>
iqubic: any pointers to what isn't clear about TeX?
<iqubic>
vcunat: I haven't looked to closely at the documentation.
<Baughn>
Hum. I was rather hoping it wasn't, because it's really slow. :P
erictapen has joined #nixos
<iqubic>
Is it possible to just get all the TeX packages, and not hand pick what I want?
hellrazo1 has joined #nixos
<Baughn>
iqubic: You can use the collection- metapackages for that.
<vcunat>
iqubic: texlive.combined.scheme-full
NixOS_GitHub has joined #nixos
<NixOS_GitHub>
[nixpkgs] 7c6f434c pushed 1 new commit to master: https://git.io/vbXxG
<NixOS_GitHub>
nixpkgs/master 1d7f90c Michael Raskin: quicklisp-to-nix: update after fixes to our ASDF handling suggested by upstream
NixOS_GitHub has left #nixos []
<Baughn>
Or listen to vcunat. He probably knows better.
<iqubic>
vcunat: What's the difference between scheme-basic and scheme-full?
<vcunat>
that should contain all, except sources and docs of non-important stuff
<vcunat>
iqubic: some gigabyte, perhaps
requisitebits has joined #nixos
<vcunat>
Upstream TeX Live defines some schemes and collections
<vcunat>
collections should be an exact partitioning of all packages
<vcunat>
schemes should be some fully functional and usable units
freusque has quit [(Quit: WeeChat 1.9.1)]
<iqubic>
Is there a difference in the packages I get when using basic vs using full?
rardiol1 has joined #nixos
jcburnham has quit [(Quit: Leaving)]
<vcunat>
yes, basic contains relatively few packages
<vcunat>
iqubic: a few dozen megabytes IIRC
<vcunat>
it can do basic LaTeX, but you may need to explicitly add some other particular packages that you use
<vcunat>
scheme-small is a bit bigger and you may often fit into it
<iqubic>
I'm just going to get full.
<iqubic>
I have space.
balsoft has joined #nixos
<vcunat>
the individual package files are shared in nix store (and not affected by any rebuilds), so you may experiment easily
<balsoft>
Hey everyone! I've got a question: is there any way to change gdm theme? I thought it would be possible with patches passed with overrideAttrs, but services.xserver.displayManager.gdm module doesn't have the package attribute (it just uses pkgs.gnome3.gdm by default). Is there any workaround?
<iqubic>
vcunat: Does texlive give me pdflatex? Or is it some other version of Latex?
jcb__ has joined #nixos
otherjrolfs has joined #nixos
<vcunat>
iqubic: it has all kinds, including pdflatex
<iqubic>
Alright then.
<iqubic>
Does it include bibtex?
coot_ has quit [(Quit: coot_)]
<symphorien>
iqubic: yes
<iqubic>
Good. Now I need to figure out how to integrate this into Emacs. But that's a task for later.
roberth has quit [(Ping timeout: 240 seconds)]
<rardiol1>
If I run nixos and hydra says I have a derivation failing on darwin, is there some way to test a fix without pushing the potential fix to nixpkgs and waiting for hydra to try again?
otherjrolfs has quit [(Ping timeout: 256 seconds)]
<rvolosatovs>
Talking about latex, I had encountered some pretty weird issue recently in university. Out of ~200 students the pdf I submit is the only one, which can not be viewed "online", so the instructors are forced to download the pdf. I worked around this issue by using Ubuntu docker image to compile my latex source, but I would like to know what's causing this.
balsoft has left #nixos []
danl1240 has joined #nixos
<jtojnar>
Baughn: wrt Wayland, do you have `hardware.opengl.enable` set to true?
<rvolosatovs>
latexmk on Ubuntu image refuses to re-compile sources compiled on NixOS(unless I remove the outputs), stating that everything is up-to-date
<rvolosatovs>
not sure what kind of checks it performs
<woffs>
rvolosatovs: maybe post-processing your pdf with ps2pdf (from ghostscript) helps
<woffs>
rvolosatovs: and "online" means using pdf.js in the browser?
<woffs>
rvolosatovs: and "can not" means what?
erictapen has joined #nixos
goibhniu has quit [(Ping timeout: 255 seconds)]
<Baughn>
jtojnar: Nope. I'll try that.
drakonis has joined #nixos
<Baughn>
I've been trying to provide feedback to the Wayland bug, but it's tough going. :p
<rvolosatovs>
Alright, so the university uses some kind of platform, which allows to (pre-)view i.e. pdf's in the browser, add annotations etc., AFAIK it uses google docs API for that somehow, but I'm not sure about that. I believe https://github.com/instructure/canvas-lms this is the source of the platform.
civodul has quit [(Quit: ERC (IRC client for Emacs 25.3.1))]
nschoe has quit [(Quit: Program. Terminated.)]
<rvolosatovs>
usually the instructors see a fancy window popping up once they click on a submitted pdf, but only in my case the only thing they see is a new download starting
jensens has quit [(Ping timeout: 240 seconds)]
<rvolosatovs>
exactly the same command (`latexmk -pdf *.tex`) generates "previewable" pdf on Ubuntu in docker
<Baughn>
It might actually be your browser, or however you upload the PDF. Have you tried uploading the Ubuntu-generated PDF from NixOS?
<rvolosatovs>
I'm uploading from NixOS always
__Sander__ has quit [(Quit: Konversation terminated!)]
<Baughn>
You say "docker", so I'm guessing probably yes... right. Hmm, tried diffing them? It should be something in the header,I guess.
<Baughn>
PDF isn't exactly diffable, though. The problem might already exist in the PS... If you're lucky. *sigh*
<rvolosatovs>
Will try now. I thought `pdfs` are "undiffable" as they're binary, right?
<Baughn>
They're undiffable unless you use a specialized dissector.
<rardiol1>
wikipedia says " PDF file is a 7-bit ASCII file, except for certain elements that may have binary content."
sigmundv__ has quit [(Ping timeout: 248 seconds)]
<Baughn>
What *should* be going on is the server is serving your PDF with the wrong mime-type, but I have no idea why.
vidbina has joined #nixos
<rvolosatovs>
Hmm, yeah that makes sense
asuryawanshi has quit [(Remote host closed the connection)]
<Baughn>
rardiol1: Yeah, but it's still pretty opaque and there aren't many linebreaks.
<kolinsol>
thanks for being so nice but i don't think i need gui. i'll be using linux only on my home server primarily or exclusively
vidbina has quit [(Ping timeout: 260 seconds)]
<rvolosatovs>
kolinsol: are you comfortable with shell?
<kolinsol>
yes kind of
<kolinsol>
i am not really good at shell scripting but yes i feel okay doing stuff in shell
<rvolosatovs>
For learning about Linux, installing Arch and playing with it could be a very nice experience then, I think. Not as good of a choice for a server tho, I think.
<gchristensen>
kolinsol: so you have more than "never used a linux based system" worth of experience?
<rvolosatovs>
BSD's are pretty well documented afaik, but that's not Linux. Pretty close though.
<Baughn>
jtojnar: ...no, worse. It exists, but it isn't documented. It's appareny true by default though.
<Baughn>
... ...how can it not be documented? That's auto-generated.
<kolinsol>
i mean i have never oned a linux machine. i have a macbook. i guess it's somewhat similar to linux rigth?
otherjrolfs has joined #nixos
<Baughn>
Noooot really.
<Baughn>
A lot of linux software will also work on darwin, but that's not to say the overall user experience is similar.
<gchristensen>
kolinsol: you should try it!
<Baughn>
Please don't throw the newbie off a cliff to see if he'll fly...
<gchristensen>
kolinsol: it is hard to judge how easy / difficult it'll be for you, but it'll be easy to start over if you don't like it
sary has quit [(Ping timeout: 265 seconds)]
<gchristensen>
kolinsol doesn't seem like that much of a newbie, I guess
<rvolosatovs>
Install FreeBSD on your server -> try Arch -> ... -> NixOS
<kolinsol>
yes exactly thats why i want to do try it on a separate machine
dpren has joined #nixos
<gchristensen>
just a newbie to nixos and linux, but with experience on the shell they might have a just fine time getting going
<Baughn>
nixos is simpler in some ways, harder in others. Mostly, it's hard because nixos really *isn't linux*, and linux experience doesn't help that much.
<gchristensen>
I guess then I feel good suggesting kolinsol try it
<kolinsol>
so some of you metioned Arch is not the best choice for the server. Is nixOS good for that purpose?
dpren has quit [(Client Quit)]
<gchristensen>
nixos is a great server os
<hyper_ch>
it's also a gread Desktop os
<Baughn>
Depending on your comfort level and ability to learn, anywhere from "Yes yes yes!" to "You'll fail halfway". :P
<Baughn>
What makes NixOS great is that there's a higher *peak*.
dpren has joined #nixos
<hyper_ch>
the nice thing about nixos is is, once you have set it up for your server, redeploying your server or another one is easy :)
otherjrolfs has quit [(Ping timeout: 260 seconds)]
<kolinsol>
what do you mean by "peak"?
<gchristensen>
kolinsol: try nixos, we're here to help, is what I'd say
vidbina has joined #nixos
<Baughn>
The learning curve tops out higher up.
sbjorn has joined #nixos
<Baughn>
And yeah, we're here to help.
<kolinsol>
oh sure
<Baughn>
NixOS also makes mistakes really cheap. Fixing them is generally easy.
<kolinsol>
thanks you are really extremely helpful
<Baughn>
(With a few exceptions, and worst-case you can reinstall it in about five minutes.)
<jcb__>
one thing that I've found really interesting about NixOS is that I can actually experiment with things
<hyper_ch>
it's not easy to screw up a working installation :)
<Baughn>
Well, you can screw up the bootloader if you're playing with it.
endformationage has joined #nixos
NixOS_GitHub has joined #nixos
<NixOS_GitHub>
[nixpkgs] bjornfor pushed 1 new commit to master: https://git.io/vb1Up
<NixOS_GitHub>
nixpkgs/master 65fb15a Kevin Hanselman: nixos/smartd: allow extra cli options for daemon...
NixOS_GitHub has left #nixos []
NixOS_GitHub has joined #nixos
<NixOS_GitHub>
[nixpkgs] bjornfor closed pull request #32327: nixos/smartd: allow extra cli options for daemon (master...smartd_expose_cli_options) https://git.io/vbGqM
NixOS_GitHub has left #nixos []
<kolinsol>
and the github integration (in the channel i mean) is really nice
<Baughn>
kolinsol: In NixOS, there's no real distinction between a fresh reinstall and a minor configuration change.
<jcb__>
you can play with the system in a way you can't with e.g. Arch
<kolinsol>
yes thats why they call it a purely functional os right?
<Baughn>
Yes, though I'm not sure I like that description.
<gchristensen>
yep
<Baughn>
It works if you're a Haskell programmer. :P
<kolinsol>
i am :)
otherjrolfs has joined #nixos
<gchristensen>
welcome home, you've found your linux!
<hyper_ch>
Baughn: I said "not easy" and not "not possible"
<Baughn>
Just make sure not to put `extensions.language = [ "UndecidableConfigurations"];` in configuration.nix
<hyper_ch>
nixos also has great zfs support
<kolinsol>
im no sure what zfs is actually but ill look at it
verite has joined #nixos
<Baughn>
ZFS is the only filesystem without fatal flaws. :V
<hyper_ch>
it's btrfs done right :)
<gchristensen>
I'd say skip ZFS and follow what the install guide does
<Baughn>
Btrfs is ZFS done wrong, you mean. :P
<Baughn>
For playing with NixOS, sure, it doesn't matter. For a long-term install, I'd always go with ZFS.
<hyper_ch>
Baughn: since he doesn't know zfs, I thought I had to use something maybe familiar to him as starting point :)
<Baughn>
Sure. Limit the novelty.
<Baughn>
NixOS on its own is probably 'nuff.
<rardiol1>
considering you can't change the filesystem by editing configuration.nix, better to start with the better one, no?
<mog>
ext for life
<hyper_ch>
rardiol1: why? re-deploying nixos is simple
<Baughn>
For a long-term system, yes.
<mog>
its a filesystem not rocket science
<disasm>
kolinsol: if your looking for a server OS on a cloud offering (like d.o, aws, etc...) nixops is a great tool for deploying the instance and managing it.
<Baughn>
hyper_ch: Reinstalling NixOS is easy, keeping your data may be harder.
<gchristensen>
rardiol1: better is relative
otherjrolfs has quit [(Ping timeout: 248 seconds)]
<hyper_ch>
Baughn: that's why you always have backups in a t least 2 different places
<duncan^>
mog: If by ext, you're referring to ReiserFS, then sure!
ixxie has joined #nixos
<Baughn>
That's truly a killer FS.
<duncan^>
ew
<mog>
ext4 i guess currently is what i mean
pkill9 has quit [(Ping timeout: 240 seconds)]
<hyper_ch>
I heard Reiser provides good entertainment :)
<mog>
stability of data is only concern so i go stock in that regard
<Baughn>
mog: ext4 doesn't provide checksums, ZFS does.
<rardiol1>
Baughn, hyper_ch: well, i use nixos on my desktop, and have my data(/home) as a btrfs subvolume, so reinstalling mine might be slightly nontrivial (I think?)
<Baughn>
rardiol1: You've got backups, right? Restore from backup~
<hyper_ch>
real men have decentralised backups
<mog>
redundant decentralised encrypted backups
<Baughn>
*Real* men offer their /home via torrent and let the world back it up.
<hyper_ch>
:)
<mog>
you first
<mog>
^_^
szicari has quit [(Ping timeout: 240 seconds)]
ThatDocsLady has quit [(Ping timeout: 272 seconds)]
mrkgnao has quit [(Ping timeout: 248 seconds)]
<hyper_ch>
doesn't everyone use encryption by default? oO
<samueldr>
my ~ is on the blockchain
* samueldr
ducks
<kolinsol>
nice
<gchristensen>
that must be very frustrating, having it take days to fsync samueldr
<rardiol1>
Torrent is too 00's, I gonna put my ~ on ipfs
<hyper_ch>
samueldr slows the blockchain down.. it's all his fault
<dhess>
clever: however last time I tried, it didn't work, kept complaining "I'm not an x86_64-linux". This was maybe 4 or 5 months ago. Just wondering if anyone here is doing it reguarly with success
NixOS_GitHub has joined #nixos
<NixOS_GitHub>
[nixpkgs] nh2 opened pull request #32858: nginx service: Make http2 an option. (master...nginx-add-http2-option) https://git.io/vb1Y4
NixOS_GitHub has left #nixos []
szicari has joined #nixos
<clever>
dhess: how did you configure your linux build slave?
<dhess>
I believe it was the kernel that prompted this. It's not even clear what the problem was as I believe that "I'm not a ___" is the standard NixOps response when a remote build breaks for practically any reason.
<clever>
dhess: thats a standard nix error
<dhess>
yeah
<clever>
happens any time you dont have a build slave for a given arch
<dhess>
so it wasn't very easy to figure out what was going wrong.
<dhess>
clever: I've seen that when I didn't have a remote build slave in .ssh/known_hosts as well
<clever>
yeah, the user that nix-daemon runs as has to trust the host
<dhess>
of course. All I'm saying is, it's not a very useful error message because it gets used for so many things :)
<clever>
yeah
<clever>
theres not much debug for build slaves
<dhess>
Anyway I'm not really complaining, just wondering out loud whether the NixOps from macOS situation has improved before I spend a bunch of time trying to make it work again.
<gchristensen>
dhess: if you have a linux build host then sure
<clever>
if you have an error from a recent setup, i can help you debug it
erictapen has quit [(Ping timeout: 240 seconds)]
<dhess>
gchristensen: I do, but see above, could never make it work and couldn't figure out why due to nix-remote-build's lack of debug-ability.
<gchristensen>
ah
<dhess>
clever: Thanks. I'm pretty sure you were one of the people helping me back when, too, but we coudln't get anywhere
hellrazo1 has quit [(Ping timeout: 256 seconds)]
<dhess>
anyway maybe I'll try again later today. People who were running nix-darwin seemed to have better success
ma27 has quit [(Ping timeout: 272 seconds)]
hellrazo1 has joined #nixos
<Baughn>
I think the amdgpu driver just plain might not support my gpu. Unfortunately, every single line of output (from X, kernel, etc.) suggests otherwise. (Except the part where the KMS device is missing.)
<Baughn>
The amdgpu-pro driver works, for X, but then the GBM extension is missing so Wayland won't boot.
<Baughn>
Why is this so hard? *sigh*
ma27 has joined #nixos
pie_ has quit [(Ping timeout: 248 seconds)]
<cmiles74>
I'm working on a Nix package that installs a daemon and some systemd units. I know how to get everything staged in the $out directory for a user account and environment, but is there any docs on how I can do that for the system environment?
<cmiles74>
I have some stuff to go in /etc, /var/lib, etc.
[0x4A6F] has joined #nixos
<symphorien>
If I understand what you want to achieve correctly, you can't do that with a nix package. You have to use a nixos module.
<cmiles74>
vcunat: vcunat: Is it the case with NixOS modules that the module will pull in a nix package to get the files it needs to install it's stuff? I'm looking at the docker module and it looks like it pulls in the docker package.
jb55 has quit [(Quit: WeeChat 1.9)]
pie_ has joined #nixos
jb55 has joined #nixos
<dhess>
cmiles74: you can get whatever you need from the NixOS module definition with something like, "${pkgs.the-package-you-want}/etc/foo.conf" etc.
NixOS_GitHub has joined #nixos
<NixOS_GitHub>
[nixpkgs] yegortimoshenko closed pull request #23382: xfce: delay package selection for pulseaudio volume to nixos modules (master...pr-2) https://git.io/vyshu
NixOS_GitHub has left #nixos []
<dhess>
that will ensure the package is installed on the target and you can then copy or symlink that file wherever the package expects to find it.
NixOS_GitHub has joined #nixos
<NixOS_GitHub>
[nixpkgs] yegortimoshenko pushed 1 new commit to master: https://git.io/vb1sZ
<NixOS_GitHub>
nixpkgs/master 62a974b Wei Tang: xfce: delay package selection for pulseaudio volume to nixos modules (#23382)...
NixOS_GitHub has left #nixos []
<vcunat>
well, yes
<vcunat>
some modules also extend systemPackages
<vcunat>
(e.g. to make related CLI tools available)
<dhess>
Where is the list of all nix.buildMachines.supportedFeatures values documented?
<ariutta>
Why does nix-build on macOS try to copy something to "/var/empty/local/bin/"? Is that the default system-wide bin directory for NixOS?
<gchristensen>
dhess: lol. documented. *cries*
<dhess>
gchristensen: :(
<gchristensen>
they don't have a specific list
<dhess>
gchristensen: Looks like `git grep requiredSystemFeatures` from the top of the nixpkgs repo is currently the best we've got
<gchristensen>
yes I think so
<gchristensen>
we could document it and then make it a checked meta field to force future docs too ...
<vcunat>
well, the grep seems to work OK for now
<ariutta>
Is there a flag or something I can set to change the location from "/var/empty/local/bin/" to something else? It doesn't seem any of the nix-build flags are for that.
ilyaigpetrov has quit [(Quit: Connection closed for inactivity)]
<dhess>
ariutta: which package is this? I've never seen that happen on macOS, myself.
<Baughn>
jtojnar: It's not the problem anyway. The driver doesn't seem to be working.
fendor has joined #nixos
<dhess>
ariutta: ahh. Well it probably has something to do with the fact that /var/empty is $HOME for user 'nobody' on macOS
<ariutta>
dhess: if you clone my fork and run "nix-build -A keepassxc" on macOS, it give this error: CMake Error at src/cli/cmake_install.cmake:39 (file): file INSTALL cannot copy file "/tmp/nix-build-keepassxc-2.2.4.drv-0/source/build/src/cli/keepassxc-cli" to "/var/empty/local/bin/keepassxc-cli".
<ariutta>
dhess: should I run nix-build for a specific user? Sorry, I'm pretty new to nix.
spietz has joined #nixos
<dhess>
ariutta: My guess is that cmake is trying to install itself in the build user's $HOME
<dhess>
install keepass I mean
ilja_kuklic has joined #nixos
<dhess>
like, perhaps PREFIX is set to $HOME by default or something like that.
<dhess>
ariutta: so you will want to make sure that PREFIX is set to $out, though I'm not sure why that wouldn't also happen when it's built on Linux
<dhess>
or whatever the equivalent is for PREFIX in cmake's build system.
ixxie has quit [(Quit: Lost terminal)]
<ariutta>
dhess: does "-DCMAKE_PREFIX_PATH" sound reasonable?
<dhess>
ariutta: sure.. ?
<ariutta>
dhess: "-DCMAKE_PREFIX_PATH=$out"
<dhess>
ariutta: is there a reference to CMAKE_PREFIX_PATH in CMakeLists.txt ?
<dhess>
ariutta: you might have to escape that $out path, like "-DCMAKE_PREFIX_PATH=\${out}". I'm not exactly sure when that's needed and when it's not.
<dhess>
but there is also CLI_INSTALL_DIR and BIN_INSTALL_DIR
drakonis has quit [(Ping timeout: 240 seconds)]
<dhess>
ariutta: you're going to have to spelunk for all of the "if(APPLE)" bits and look for paths to override
<ariutta>
dhess: thanks, that's something to get me started here
<dhess>
and maybe even patch up the file a bit, looks like some bits are hardcoded? e.g. find_program(MACDEPLOYQT_EXE macdeployqt HINTS /usr/local/opt/qt5/bin ENV PATH)
<dhess>
anyway that explains why it doesn't happen on Linux and only on macOS. I'm pretty sure this is your problem, you just need to find all of the guilty parties.
zzamboni has joined #nixos
verite has quit [(Ping timeout: 248 seconds)]
otherjrolfs has joined #nixos
jrolfs has joined #nixos
<dhess>
gchristensen: clever: what kind of load does Hydra put on the master machine? I know that's a loaded question (ha) but is there some kind of general rule?
<gchristensen>
eval load + xz + network xfer
<dhess>
this is a Hydra for personal use BTW, not a team
<dhess>
gchristensen: is that a command for one of your bots, or a cryptic answer to my question? ;)
<gchristensen>
a cryptic answer :)
<dhess>
oh hehe ok
asuryawanshi has quit [(Remote host closed the connection)]
asuryawanshi has joined #nixos
nevermind has joined #nixos
nevermind is now known as Guest25439
jb55 has quit [(Ping timeout: 256 seconds)]
jcbrand_ has joined #nixos
NixOS_GitHub has joined #nixos
<NixOS_GitHub>
[nixpkgs] dywedir opened pull request #32859: rust-bindgen: 0.31.1 -> 0.32.1 (master...rust-bindgen) https://git.io/vb1Cb
NixOS_GitHub has left #nixos []
jcbrand_ has left #nixos []
athan has quit [(Remote host closed the connection)]
athan has joined #nixos
ilja_kuklic has quit [(Remote host closed the connection)]
<dpren>
but I might have accidently run that in another tab
<gchristensen>
if you do that PATH line ^ will you be able to use the nix commands?
<dpren>
yes
<gchristensen>
ok
<gchristensen>
dpren: there is a way to debug zsh startup ...
<gchristensen>
ah, `zsh -x 2>&1 | tee
<samueldr>
hmmm, fun, our (hacky) provision scripts fail using nix, but not when doing the same thing manually
<gchristensen>
`zsh -x 2>&1 | tee startup.log` when it shows the prompt, exit the zsh process and comb through startup.log looking for PATH
ariutta has quit [(Ping timeout: 260 seconds)]
<samueldr>
looking into stuff, but the error I'm having is → error: syntax error, unexpected $undefined, expecting IND_STR or DOLLAR_CURLY or IND_STRING_CLOSE, at /nix/store/zmdmfykvrqiph09lw6lcnkrvm35pr1r8-nixpkgs-18.03pre122585.b212125b541/nixpkgs/pkgs/tools/graphics/gnuplot/default.nix:42:44
<samueldr>
ah, fine enough, it's the "bootstrap" nix that maybe is too old
<samueldr>
1.11.4
<samueldr>
(when doing it manually it used the previously nix-installed nix which is newer)
<dpren>
gchristensen: okay, should I pastebin the lines containing PATH?
<gchristensen>
dpren: well, I'm hoping you can use the output to debug why it is happening :$
NixOS_GitHub has joined #nixos
<NixOS_GitHub>
[nixpkgs] ck3d opened pull request #32865: welle-io: init at 1.0-rc1 (master...welle-io) https://git.io/vb1ah
<Dezgeg>
at least I have been fixing eval errors on old nix since I still need the ones pre-seccomp
<Ankhers>
gleber_: Do you think it would be beneficial to have versions for Erlang R20.0, R20.1, R20.2, etc?
<gleber_>
Ankhers: I do not think so
<Ankhers>
gleber_: Why not?
simukis has quit [(Ping timeout: 255 seconds)]
<gleber_>
Ankhers: Changes in between are usually minor, hence should be API-compatible hence no real differences. Maintaining multiple versions is a burden on nixpkgs maintainers.
<gleber_>
Ankhers: Do you have specific needs?
<Ankhers>
gleber_: not me specifically. I just maintain multiple versions for Elixir (e.g., 1.4, 1.5, etc). I was just wondering if we should start doing the same for Erlang.
<yegortimoshenko>
there is no point
<yegortimoshenko>
also, even major Erlang releases are highly reverse compatible
hiratara has quit [(Ping timeout: 265 seconds)]
<gleber_>
Ankhers: We already have multiple Rnn, which should cover all cases IMO
<yegortimoshenko>
i personally don't know of a single breaking change
<gleber_>
Ankhers: Given that Elixir is younger it might make more sense to maintain multiple versions, since things change more often
hiroshi has quit [(Ping timeout: 256 seconds)]
hiratara has joined #nixos
jacob_ has quit [(Quit: Lost terminal)]
otherjrolfs has joined #nixos
<Ankhers>
Ok, I can live with that.
jrolfs has joined #nixos
hiroshi has joined #nixos
NixOS_GitHub has joined #nixos
<NixOS_GitHub>
[nixpkgs] Mic92 pushed 2 new commits to master: https://git.io/vb1ok
<NixOS_GitHub>
nixpkgs/master 682022a José Romildo Malaquias: materia-theme: 20171112 -> 20171213
<gchristensen>
can you find any files laying around that you can delete? :$
<gchristensen>
something not in the nix store
<gchristensen>
then we'll be able to run nix-collect-garbage
<Rovanion>
Separate home partition, so perhaps in /tmp.
<Rovanion>
Found something to remove in tmp.
<BlessJah>
maybe hardlinking could save some space without need to commit anything?
nevermin_ has joined #nixos
cmiles74 has quit [(Ping timeout: 248 seconds)]
<ottidmes>
I am trying to install my NixOS config on a new server, but I get the following error: file ‘nixcfg/shared/config/default.nix’ was not found in the Nix search path ... at /mnt/wheel/proj/nixcfg/server/config/default.nix
<Ankhers>
gleber_: Do you have a bit of time to discuss the hex2nix, rebar32nix, etc projects?
<ottidmes>
With my NIX_PATH being: nixos-config=/wheel/proj/nixcfg/server/config/default.nix:nixcfg=/wheel/proj/nixcfg:nixpkgs=/wheel/fork/nixpkgs:nixpkgs-unstable=/wheel/fork/nixpkgs-unstable:/wheel/fork/nixpkgs
<gleber_>
Ankhers: yes, I have around 20-30 minutes before I go to sleep
<ottidmes>
So it seems as if my NIX_PATH env var is being ignored for nixos-install
aarvar has joined #nixos
<Ankhers>
gleber_: I think we should skip the hex2nix project. If I'm not mistaken, rebar3 provides a lock file for your dependencies.
<gleber_>
Ankhers: It might be useful to have it, but rebar2nix is definitely higher priority
<Ankhers>
I think the mix2nix and rebar2nix projects are still helpful. THey can read the lock file and grab the deps from hex as needed. With the specific versions that are already in your project.
<Ankhers>
And obviously the common lib that I am, ever so slowly, working on.
<gleber_>
Ankhers: agree. Although ideally these are should be plugins for mix and rebar3
<gleber_>
Ankhers: I got side-tracked a lot too :(
<gleber_>
Ankhers: On the positive side I get to use a bit of Nix at work
<Ankhers>
gleber_: I'm jealous
<gleber_>
Ankhers: Just a bit and not without political issues...
<Ankhers>
gleber_: Can I ask what political issues you are running into? I want to introduce it at work. I just want to know the kinds of things I will run into.
berce has joined #nixos
sigmundv has joined #nixos
<yegortimoshenko>
Ankhers: status quo, probably
<yegortimoshenko>
or, just use whatever everyone is using
<gleber_>
Ankhers: Status quo + a team of Ansible experts who do not seem to want to learn new things
<Ankhers>
That is fair.
<yegortimoshenko>
it's ridiculous how much traction there is into accepting new technology
<gchristensen>
Ankhers: my most successful "introductions" were "this is just for me" and then smug satisfaction when my tools don't break
<samueldr>
:D
<gchristensen>
and then people start taking a gander
<gleber_>
gchristensen: +1
seanparsons has quit [(Ping timeout: 256 seconds)]
<samueldr>
mine was by saving the day, using a pinned older revision of a known good working server when something broke in a dependency later on
<Ankhers>
I'm not sure if it is a pro or a con, but I am the lead developer at work. I'm not sure if that will make it easier or not to introduce.
* gchristensen
shrug maybe! :)
<samueldr>
then, right after that, it was approved that the toolchain for the new version of our app be built using nix
<gleber_>
We use Nix for a stable development environment, but Nix is not used for deployments for anything important
<gchristensen>
yeah, keep nix out of the critical path for a while
<samueldr>
Ankhers: nix-shell in itself is probably something you can make your team accept
<gchristensen>
until it is more annoying to not
<samueldr>
rails and webpack (for dev) are made available through nix-shell, otherwise it would be a headache to have all that installed properly statefully through the different configurations on our dev team's workstations
<gleber_>
gchristensen: I'll be hiring people to my team soon, need a way to find people who are willing to push for wider Nix adoption, while still delivering value using current messy tooling.
NixOS_GitHub has joined #nixos
<NixOS_GitHub>
[nix] dtzWill opened pull request #1748: release.nix: use 'nixpkgs' argument, even if nixpkgs in NIX_PATH (master...fix/use-nixpkgs-argument) https://git.io/vb1Pq
NixOS_GitHub has left #nixos []
<gchristensen>
gleber_: I'd be surprised if you didn't find some interested members of the nix community
civodul has quit [(Read error: Connection reset by peer)]
seanparsons has joined #nixos
<samueldr>
1.8.7 ?!?
<Ankhers>
I just need to find someone I can hire that likes nix and Elixir.
<samueldr>
I find myself lucky I was able to sneak in 2.3 by using nix :)
<gchristensen>
samueldr: thank goodness for nix
<samueldr>
amen
aarvar has quit [(Quit: Leaving.)]
<gleber_>
We tried using Nix to build stuff in a large monorepo, but it was not fast enough in practice. Had to move to Buck. I'd be curious if Nix could be practically made into a Buck/Blaze-like build system
<BlessJah>
gleber_: was it rebuilding whole monorepo every time anything as changed?
<BlessJah>
s/as/has
<samueldr>
how I approached the problem with my team initially was: it's like a (php) composer, but for the whole system
<gleber_>
BlessJah: it was before my times, I think it were two issues: big rebuilds due to non-significant changes and slow re-evaluation of all of .nix tree
sigmundv__ has joined #nixos
aarvar has joined #nixos
jrolfs has quit [(Ping timeout: 260 seconds)]
sigmundv has quit [(Ping timeout: 240 seconds)]
<gleber_>
BlessJah: And, of course, people not willing to learn new things...
<BlessJah>
you could try trick nix into evaluating parts of monorepo based on tree hashes, instead of commit hashes
otherjrolfs has quit [(Ping timeout: 272 seconds)]
<gleber_>
It was doing tree hashes. I think the problem was no caching based on a hash of an output. I.e. an intensional model would have fixed part of the problem
<dhess>
Hi hydra people. When I run hydra-create-user on a new Hydra instance, I get this error: Class::XSAccessor exists but failed to load with error: Can't locate Class/XSAccessor.pm: ./Class/XSAccessor.pm: Permission denied at /nix/store/svvaf98l33bn7prcc6y3z1pa9sr1i3ki-hydra-perl-deps/lib/perl5/site_perl/5.24.3/Module/Runtime.pm line 317.
<dhess>
the user does get created/updated, as far as I can tell
<dhess>
I mean, I can log in and all that
<manveru>
gleber_: well, given that nixpkgs works, i'm not sure size is the issue :)
hiratara has joined #nixos
balaji has joined #nixos
<manveru>
but i had the same issue with people unwilling to even learn nix basics...
<ottidmes>
How can I determine what nixos-install uses as Nix search path? The file not found can be found when I run nix-instantiate --eval, I also tried passing $NIX_PATH as the -I argument, but that did not work either
<manveru>
because learning 5 different package managers and docker is easier :P
grw has quit [(Quit: WeeChat 1.7.1)]
ma27 has quit [(Ping timeout: 272 seconds)]
<gleber_>
manveru: :D
thblt has quit [(Ping timeout: 248 seconds)]
aarvar has quit [(Quit: Leaving.)]
aarvar has joined #nixos
fenedor has joined #nixos
otherjrolfs has joined #nixos
jrolfs has joined #nixos
dan_b has joined #nixos
NixOS_GitHub has joined #nixos
<NixOS_GitHub>
[nixpkgs] yegortimoshenko created yegortimoshenko-patch-1 (+1 new commit): https://git.io/vb11i
<NixOS_GitHub>
nixpkgs/yegortimoshenko-patch-1 014dcb0 Yegor Timoshenko: time.timeZone: default to GMT
NixOS_GitHub has left #nixos []
NixOS_GitHub has joined #nixos
<NixOS_GitHub>
[nixpkgs] yegortimoshenko opened pull request #32868: time.timeZone: default to GMT (master...yegortimoshenko-patch-1) https://git.io/vb11X
NixOS_GitHub has left #nixos []
fenedor has quit [(Remote host closed the connection)]
fendor has quit [(Ping timeout: 272 seconds)]
aarvar has quit [(Quit: Leaving.)]
jrolfs has quit [(Ping timeout: 256 seconds)]
otherjrolfs has quit [(Ping timeout: 272 seconds)]
otherjrolfs has quit [(Ping timeout: 268 seconds)]
<samueldr>
yet, somehow, the latest build's `nix-channel` fails to run on debian, in the *same conditions*, with "Problem with the SSL CA cert (path? access rights?) (77)"
pkill9 has quit [(Quit: WeeChat 1.9.1)]
<samueldr>
(nix-channel --update)
<samueldr>
as of right now, it's repeatable in a dirty environment, but I can install one, nix-channel --update using that binary, it fails, intall the other, nix-channel --update and it works, repeatably
pkill9 has joined #nixos
jensens has quit [(Ping timeout: 248 seconds)]
zzamboni has quit [(Quit: Leaving.)]
ariutta has quit [(Ping timeout: 260 seconds)]
<rnhmjoj[m]>
do you know what can cause `Error in tempdir() using /run/user/1000/nix-shell.XXXXXX`?
cybrian has quit [(Ping timeout: 256 seconds)]
<samueldr>
rnhmjoj[m]: did your X crash recently?
<samueldr>
and had to re-login?
pkill9 has quit [(Client Quit)]
<rnhmjoj[m]>
samueldr: no, why?
pkill9 has joined #nixos
<samueldr>
(had something similar recently wherein X crashing and re-logging-in made some things usint /run/user/1000 wonky)
<rnhmjoj[m]>
this is an error from Nix that i think has something to do with a missing environment variable
spietz has quit [(Ping timeout: 255 seconds)]
<rnhmjoj[m]>
it only appears when i'm logged through mosh
berce has quit [(Quit: leaving)]
<samueldr>
through mosh only or through mosh on a machine where you have another session active?
<samueldr>
is there anything mounted `mount | grep run/user`
<rnhmjoj[m]>
samueldr: well, no. it says 0 sessions. with ssh it lists one.
<samueldr>
I'm still verifying, but that may be a symptom
<samueldr>
something is not opening the session "properly"
<samueldr>
but another part is still assuming it has (for the tempdir)
<samueldr>
I'm all assuming though
<samueldr>
rnhmjoj[m]: enabled mosh through `programs.mosh.enable`?
<rnhmjoj[m]>
yes
jb55 has quit [(Ping timeout: 240 seconds)]
<samueldr>
(installing, looking at something which may explain the issue)
<rnhmjoj[m]>
I just found issue #29234, seems to be the same problem
<samueldr>
possibly caused by mosh too
<samueldr>
hmmm, how does mosh logs a user in?
<samueldr>
almost looks like it doesn't go through pam
<rnhmjoj[m]>
if it's systemd closing the session i'll try setting KillUserProcesses=no
<samueldr>
I see, mosh seems to auth through ssh
<samueldr>
well, that's not an easy fix, I guess if KillUserProcesses=no works, that's the easiest way
<rnhmjoj[m]>
what I don't understand is why I didn't see this issue before. something must have changed recently because i have been using mosh for more that a year.
vidbina has quit [(Ping timeout: 240 seconds)]
<dhess>
gchristensen: maybe a dumb question but is it safe to point Hydra's store_uri to file:///nix/store ?
<rnhmjoj[m]>
samueldr: NixOS actually has already KillUserProcesses=no set.
<samueldr>
(I'd assumed you looked at that configuration and it would set lingering for you)
ariutta has joined #nixos
<samueldr>
it must be two different concepts
alp has joined #nixos
<samueldr>
one doesn't reap left-over processes, and the other allows the session to continue living on
jrolfs has joined #nixos
otherjrolfs has joined #nixos
<samueldr>
what would be the nix-build incantation to build the nix .deb, and how would I go understanding how the incantation is made?
jrolfs has quit [(Ping timeout: 240 seconds)]
<samueldr>
I know it somehow will use `debian-build.nix`, looking at the name of the build steps, but nothing seems to "use" debian-build in nixpkgs
otherjrolfs has quit [(Ping timeout: 240 seconds)]
<samueldr>
oh, look at that, reproduce locally on hydra