2019-03-17
03:32
<
clever >
yep, my laptop is missing EGL.so
03:32
<
clever >
00:02.0 VGA compatible controller: Intel Corporation Device 591b (rev 04)
03:30
<
clever >
the contents will depend on which gpu drivers you have
03:28
<
clever >
mine happens to come from libGL
03:28
<
clever >
lrwxrwxrwx 1 root root 69 Dec 31 1969 /run/opengl-driver/lib/libEGL.so -> /nix/store/2yni0rxjcdsl56by9y7m73q2kp9krzv1-libGL-1.0.0/lib/libEGL.so
03:28
<
clever >
dramforever: are other files present in that dir?
03:28
<
clever >
dramforever: nixos puts that into LD_LIBRARY_PATH automatically
03:28
<
clever >
/run/opengl-driver/lib/libEGL.so
2019-03-16
23:27
<
clever >
andrewrk: can you pastebin your configuration.nix file?
23:27
<
clever >
which simulates the old textmode console, at a higher resolution, but its not full-on graphics
23:26
<
clever >
ah, thats more to do with the framebuffer and fbcon stuff
23:25
<
clever >
andrewrk: that disables powersaving on the monitor
23:24
<
clever >
andrewrk: ah, no text-login at all?
23:24
<
clever >
andrewrk: you want auto-login?
23:06
<
clever >
oops, and its a desktopManager, not a window manager
23:06
<
clever >
justanotheruser: or select another WM at the login screen
23:06
<
clever >
justanotheruser: xterm is enabled by default, you need to windowManager.xterm.enable = false;
22:16
<
clever >
[clever@amd-nixos:~/iohk/daedalus-1195]$ nix-store -r -vvvv /nix/store/mzs612q5h655vxwzclqpah0p2r1pkz9l-daedalus.drv
22:15
<
clever >
by evaling the nix on its own, i can then build it with -vvv, and get less spam in the debug
22:15
<
clever >
[clever@amd-nixos:~/iohk/daedalus-1195]$ nix-instantiate release.nix -A staging.daedalus -I cardano-sl=/home/clever/iohk/cardano-bittrex/ -Q
22:15
<
clever >
samueldr: ^^
22:15
<
clever >
delroth: very first thing i asked
22:14
<
clever >
yeah, i think line 26 does that
22:13
<
clever >
yet i'm not doing that, and it works for me ....
22:13
<
clever >
delroth: this source implies that it will only use the ssh-key if you use ssh://nixbld@my.build.host
22:12
<
clever >
delroth: you should see this msg, if you build with -vvvv
22:12
<
clever >
debug("considering building on remote machine '%s'", m.storeUri);
22:12
<
clever >
delroth: here is where it parses /etc/nix/machines
22:11
<
clever >
delroth: everything looks perfect so far
22:09
<
clever >
the nix.conf parsing area, where that default value came from
22:08
<
clever >
checking some source...
22:08
<
clever >
yep, identical to what i have
22:07
<
clever >
delroth: what about `nix show-config | grep builders` ?
22:07
<
clever >
yeah, that looks like it should just work
22:06
<
clever >
delroth: can you pastebin the contents of /etc/nix/machines ?
22:05
<
clever >
delroth: what nix-build command are you using to initiate the build?
22:04
<
clever >
HatesLongFiles: i dont think systemd-boot allows custom boot entries, you would need to switch to grub
22:04
<
clever >
delroth: have you tried restarting the nix-daemon.service in systemd?
22:03
<
clever >
HatesLongFiles: what are you trying to add the entry to?
22:02
<
clever >
HatesLongFiles: thats how you add entries to the grub config
21:08
<
clever >
Avaq: they should also be in the nix or nixpkgs docs
21:06
<
clever >
Avaq: run `nix repl` and then hit tab a couple times
20:24
<
clever >
linarcx: in general, i prefer `type` over `which`, since `type` can detect functions and aliases
20:22
<
clever >
Avaq: you can also put the string into a file, and then just replace -E expr, with the filename
20:21
<
clever >
$ nix-instantiate --eval -E '{ yes = "it is"; }.yes'
20:20
<
clever >
Avaq: `nix eval` or `nix-instantiate --eval`, and `nix repl`
18:21
<
clever >
samueldr: already packaged
18:19
<
clever >
therealwaphire[m: you would either need to put the driver onto a fat32 fs, or modify the firmware
06:19
<
clever >
nimblepoultry: dont quote the path
05:09
<
clever >
it uses the version of the python you start with
05:04
<
clever >
buildInputs = with pkgs; [ zlib (python.withPackages (p: with p; [ scipi numpy ... ])) ];
05:03
<
clever >
justanotheruser: and the withPackages call itself, must be in the buildInputs LIST
05:03
<
clever >
justanotheruser: only python packages can be inside the withPackages call
05:01
<
clever >
justanotheruser: and with the changes?
04:59
<
clever >
justanotheruser: can you pastebin the code your using?
01:03
<
clever >
haslersn[m]: nix-build can only look in channels if the channels happen to be in NIX_PATH
00:56
<
clever >
haslersn[m]: that would be an empty nix-env profile
2019-03-15
22:56
<
clever >
but you may need to logout and login for some env vars to update
22:56
<
clever >
Fare: when you nixos-rebuild, it updates /etc/static
19:04
<
clever >
noonien: nix repl '<nixos/nixos>'
17:44
<
clever >
elvishjerricco: this also works
17:44
<
clever >
1zmk00s48s627lxz1qd280dv4p8vihgjp926qynsa7vd4wf00kj8
17:44
<
clever >
echo -n nix-output:bogus | nix-hash --type sha256 --base32 --flat /dev/stdin
17:44
<
clever >
hadnt seen `nix to-base32` before
17:42
<
clever >
let me play with it a bit more...
17:42
<
clever >
hmmm, --flat isnt actually needed
17:42
<
clever >
1zmk00s48s627lxz1qd280dv4p8vihgjp926qynsa7vd4wf00kj8
17:42
<
clever >
[clever@system76:~/nixpkgs]$ nix-hash --type sha256 --to-base32 --flat 484e001c276d1fa5adc746a42b1f8c1b5db21b40a2e1f03b3dc268443400b3fe
17:42
<
clever >
[clever@system76:~/nixpkgs]$ echo -n nix-output:bogus | sha256sum
17:42
<
clever >
484e001c276d1fa5adc746a42b1f8c1b5db21b40a2e1f03b3dc268443400b3fe -
17:42
<
clever >
elvishjerricco: --flat
17:32
<
clever >
dont think so
17:31
<
clever >
elvishjerricco: there is more magic elsewhere, that will search for that magic string, and sub in the real $out
17:14
<
clever >
simukis: builtins.placeholder
17:08
<
clever >
then it just magically fixes everything, any time c2hs is in the buildInputs
17:08
<
clever >
hakujin: but once its working, you can properly add it to the c2hs package
17:08
<
clever >
hakujin: for testing, you can make a new derivation with only the setup hook
17:07
<
clever >
hakujin: this one is much simpler, and adds every buildInput to the pkgconfig search path
17:06
<
clever >
hakujin: this one for example, will add every buildInput to the cmake search path, i think
17:06
<
clever >
basically, if any derivation has a $out/nix-support/setup-hook file, the stdenv will soure it, before processing buildInputs
17:05
<
clever >
but a setup hook may be simpler/nicer
17:04
<
clever >
make a c2hs wrapper or setup-hook, to fix things
17:03
<
clever >
but c2hs likely hasnt
17:02
<
clever >
and gcc has been modified to obey that
17:02
<
clever >
hakujin: oh right, nix uses NIX_CFLAGS_COMPILE to make buildInputs work
17:00
<
clever >
hakujin: can you pastebin the version with buildInputs?
16:43
<
clever >
hakujin: all attributes of the derivation are also env vars
16:24
<
clever >
ddellacosta: you can put that entire -E string into a shell.nix
16:22
<
clever >
ddellacosta: this would provide cabal-install as well
16:22
<
clever >
nix-shell -E 'with import <nixpkgs>{}; (haskellPackages.callCabal2nix "foo" ./. {}).env.overrideAttrs (drv: { buildInputs = drv.buildInputs ++ [ haskellPackages.cabal-install ]; })'
16:20
<
clever >
ddellacosta: Setup.hs (by default) just calls the main function in cabal, so once compiled, its identical to the cabal binary
16:19
<
clever >
infinisil: and thats not in the .env by default
16:19
<
clever >
ddellacosta: nix currently doesnt provide a cabal binary, only a Cabal library, so you want to compile Setup.hs in that shell
16:17
<
clever >
ddellacosta: if you have a foo.cabal, then this is all you need
16:17
<
clever >
nix-shell -E 'with import <nixpkgs>{}; (haskellPackages.callCabal2nix "foo" ./. {}).env'
16:17
<
clever >
behind the scenes, the .env on every haskell package, is calling shellFor
16:16
<
clever >
> haskellPackages.shellFor
14:55
<
clever >
if that is written within a nixos module, it can refer to the nixos args
14:55
<
clever >
nixpkgs.overlays = [ (super: self: { foo = unstable.foo; }) ];
14:54
<
clever >
or, define the overlay itself within nixos modules
14:54
<
clever >
noonien: and then you have a pkgs.unstable
14:54
<
clever >
noonien: you would need to instead make an overlay for nixpkgs, that sets unstable=
02:20
<
clever >
ive not really bothered changing that
02:20
<
clever >
thomashoneyman: yeah, somewhere in the window manager, you would select the default font for the ui, i think
01:46
<
clever >
then your shell.nix can be much simpler
01:45
<
clever >
hakujin: i would modify default.nix to return a set, with both the haskell and libical
01:36
<
clever >
hakujin: .env is limited to haskell based packages
01:35
<
clever >
.env has some bugs like that
01:35
<
clever >
hakujin: so the .env needs its own override, with .env.overrideAttrs (drv: { ... })
01:34
<
clever >
hakujin: the .env doesnt have any of the buildInputs you overrode
01:21
<
clever >
hakujin: can you pastebin the nix files and the error msg?
2019-03-14
23:47
<
clever >
188 export PATH="$HOME/bin:$PATH"
23:47
<
clever >
187 # ~/bin if it exists overrides other bin directories.
23:47
<
clever >
nixos/modules/config/shells-environment.nix: # ~/bin if it exists overrides other bin directories.
23:46
<
clever >
infinisil: right at the very start
23:46
<
clever >
$ echo $PATH
23:46
<
clever >
/home/clever/bin:/run/wrappers/bin:/home/clever/.nix-profile/bin:/nix/var/nix/profiles/default/bin:/run/current-system/sw/bin:/etc/profiles/per-user/clever/bin
23:19
<
clever >
growpotkin: nixos puts ~/bin/ on PATH automatically
22:38
<
clever >
or is the bootstrap curl even lacking ssl?
22:38
<
clever >
doesnt fetchurl also just disable ssl cert checking, and trust all certs blindly?
22:31
<
clever >
then `import <nixos-unstabke>` will give you the new feature
22:31
<
clever >
you need `sudo nix-channel --update` to update the other channels
22:31
<
clever >
and nixos-rebuild --upgrade, only updates the nixos channel
22:30
<
clever >
boogiewoogie: so by default, it will be using 18.09, which doesnt have that change
22:29
<
clever >
boogiewoogie: sudo nix-channel --list
22:15
<
clever >
infinisil: dang!
22:10
<
clever >
scientist: its a nixos option, that goes into configuration.nix
22:09
<
clever >
i use that all the time, so you can easily mutate a set of packages i'm creating
22:07
<
clever >
but not for overrideScope'
22:07
<
clever >
i believe mine is correct, for overrideScope
22:06
<
clever >
noonien: notice that super and self are swapped
22:06
<
clever >
noonien: yeah, its been renamed since i last looked at it, and i keep forgetting
22:03
<
clever >
noonien: so you want gnome3 = super.gnome3.overrideScope (gsuper: gself: { vte-ng = gsuper.vte-ng ...; });
22:03
<
clever >
noonien: gnome3.overrideScope exists
22:03
<
clever >
noonien: checking...
22:02
<
clever >
scientist: i dont think i could use a machine where modifiers are sticky, i'm just too used to them being non-sticky, and i dont have to hold them much
21:54
<
clever >
scientist: and behind the scenes, the xkbOptions flag lands in xorg.conf, under this field
21:54
<
clever >
/nix/store/0632bl75ydymsx5ivx8k204b9aagw40w-etc-unnamed-12.1: Option "XkbOptions" "caps:shiftlock"
21:53
<
clever >
scientist: that file i just pasted, does the remapping, similiar to your pastebin
21:53
<
clever >
share/X11/xkb/symbols/ctrl:xkb_symbols "swapcaps" {
21:52
<
clever >
scientist: it should be as simple as xkbOptions = "ctrl:swapcaps";
21:52
<
clever >
scientist: an xkbOptions exists to swap ctrl and capslock
21:52
<
clever >
share/X11/xkb/rules/base.lst: ctrl:swapcaps Swap Ctrl and Caps Lock
21:46
<
clever >
scientist: i dont see sticky anywhere in that derivation
21:44
<
clever >
/nix/store/9x7cilwdr3x0xjm624xkcnzjwbfnlhjz-xkeyboard-config-2.24/share/X11/xkb/rules/evdev.xml: <name>caps:shiftlock</name>
21:44
<
clever >
scientist: there it is, you can read your xkeyboard-config files, to file all xkb options
21:44
<
clever >
/nix/store/9x7cilwdr3x0xjm624xkcnzjwbfnlhjz-xkeyboard-config-2.24/share/X11/xkb/rules/base: caps:shiftlock = +capslock(shiftlock)
21:44
<
clever >
[root@amd-nixos:~]$ grep -r --color shiftlock $(nix-store -qR /run/current-system | grep xkeyboard)
21:43
<
clever >
which file did i find that in...
21:42
<
clever >
scientist: on my end, i set this, after poking around with some things: xkbOptions = "caps:shiftlock";
18:11
<
clever >
noonien: can you add the nix file that is actually installing termite, to the gist
18:11
<
clever >
ehhh, its in the binary cache, so it doesnt really matter
18:09
<
clever >
noonien: what configure flags do you see?
18:09
<
clever >
noonien: then nix-store -l /nix/store/avsg46y3lpw0xcr8wlsj3chlhqv920lk-vte-ng-0.50.2.a
18:08
<
clever >
noonien: what storepath does this give?
18:08
<
clever >
noonien: nix-store -qR $(realpath $(which termiate)) | grep vte-ng
18:05
<
clever >
NickSeagull: with what error?
18:00
<
clever >
noonien: can you put all involved files into a gist?
17:59
<
clever >
> vte-ng.meta.position
17:58
<
clever >
noonien: that should be working
17:57
<
clever >
and how is termite then being installed?
17:54
<
clever >
noonien: in a nixos config file, you must set overlays like: nixpkgs.overlays = [ (import ./overlays/qemu) ];
17:53
<
clever >
they just do nothing when in imports
17:52
<
clever >
noonien: overlays cant be loaded with the imports list
17:51
<
clever >
just the file that is importing the above one
17:50
<
clever >
noonien: and then pastebin the configuration.nix as well
17:49
<
clever >
noonien: first, remove the rec from your attrset, that tends to just cause more problems in overlays
17:47
<
clever >
can you pastebin your changes?
17:46
<
clever >
thats the whole point of overlays, to automatically feed it to everything
17:46
<
clever >
noonien: and if you did an overlay against vte-ng, you dont have to touch termite-unwrapped either
17:45
<
clever >
noonien: an overlay will mutate pkgs.termite-unwrapped, so you dont have to override termite itself
17:44
<
clever >
noonien: so you want an override against termite-unwrapped
17:44
<
clever >
19672 termite = callPackage ../applications/misc/termite/wrapper.nix { termite = termite-unwrapped; };
17:44
<
clever >
19670 termite-unwrapped = callPackage ../applications/misc/termite { };
17:43
<
clever >
overrideAttrs wont help in this case
17:43
<
clever >
its default.nix, that accepts vte-ng
17:43
<
clever >
wrapper.nix doesnt accept vte-ng
17:43
<
clever >
1 { makeWrapper, wrapGAppsHook, symlinkJoin, configFile ? null, termite }:
17:42
<
clever >
noonien: and if you read termite/wrapper.nix, what arguments does it accept?
17:38
<
clever >
noonien: .override
15:24
<
clever >
romildo: in the case of fetchzip, you can also nix-prefetch-url --unpack
14:29
<
clever >
glasserc: yep
00:59
<
clever >
sm: rather then having to type out the full package name, then 4-5 characters of the hash
00:59
<
clever >
sm: you can uniquely identify almost any storepath with just the first 4-5 characters of the hash
00:56
<
clever >
infinisil: for random nixos services, i dont bother
00:56
<
clever >
infinisil: though i only do that for users i have a shell as, and that own a lot of files
00:54
<
clever >
infinisil: also, it makes things simpler when your doing recovery, and mounting disks in the "wrong" system
00:54
<
clever >
infinisil: i'm used to the days when that didnt exist :P
00:49
<
clever >
infinisil: i staticly assign uids, so they have the same uid on every box, and then nfs is simpler to manage
00:38
<
clever >
sm: hydra uploads the logs to cache.nixos.org
00:27
<
clever >
DigitalKiwi: if you try to nix-build the same thing in 2 windows, one will build, and the other will wait on a lock
00:22
<
clever >
DigitalKiwi: are you building similar things in multiple windows?
2019-03-13
23:42
<
clever >
i could easily upload every file i have read access to
23:42
<
clever >
infinisil: IFD + /etc/shadow in an expression?
23:30
<
clever >
noonien: looks like #nixos-dev is already looking into your qemu problems
22:58
<
clever >
ajs124: there are some performance issues in the eval of nixos
22:53
<
clever >
noonien: and then this, to see all snapshots on that
22:53
<
clever >
[root@amd-nixos:~]$ zfs list -t snapshot -r -o name,used,refer,written amd/dedup ; df -h /home/clever/
22:52
<
clever >
noonien: i mainly use the above cmd, to find the biggest USEDSNAP
22:52
<
clever >
noonien: it might be snapshots that affect one
22:51
<
clever >
noonien: i think they are blurred into eachother
22:51
<
clever >
noonien: i'm not sure which one is dedup and which is from gzip
22:48
<
clever >
noonien: one entry for every single block, even if its got no dups
22:47
<
clever >
but maintaining and searching that hashtable, is ram-expensive
22:47
<
clever >
noonien: and if 2 blocks have the same hash, it reuses the block on-disk
22:47
<
clever >
noonien: it just blindly hashes every block, and then updates a hashmap from hash->block
22:46
<
clever >
avn: 2.47x ratio
22:46
<
clever >
amd/dedup 32.1G 27.1G 50.2G 45.5G 382M 5.03G 27.1G 2.47x 2.35x gzip-9
22:46
<
clever >
NAME USED REFER LUSED LREFER WRITTEN USEDSNAP USEDDS REFRATIO RATIO COMPRESS
22:46
<
clever >
[root@amd-nixos:~]$ zfs list -t filesystem -o name,used,referenced,logicalused,logicalreferenced,written,usedbysnapshots,usedbydataset,refcompressratio,compressratio,compression
22:44
<
clever >
avn: i only have dedup enabled for a dataset where i store duplicate copies of blockchains
22:39
<
clever >
noonien: same
22:39
<
clever >
newhoggy:
you need a newer nixpkgs i believe
22:38
<
clever >
sm: it likely depends on ghc itself, which is massive
22:37
<
clever >
noonien: 32gig of ram on my laptop&desktop
22:35
<
clever >
noonien: ah, zfs usage doesnt show up in a lot of utils, but it will shrink on its own when needed, as long as you dont try to get too much at once
22:34
<
clever >
noonien: i also have zfs on this end, and none of your issues
22:27
<
clever >
ajs124: often times, the first eval is fairly slow, as it builds up all of the .drv files
22:21
<
clever >
ajs124: what does `strace -p 25975` show?
22:18
<
clever >
ajs124: can you pastebin the output of `ps -eH x` ?
22:18
<
clever >
ajs124: import from derivation
22:17
<
clever >
ajs124: IFD results in hydra having to build a lot of things just to eval, and it cant give status when doing so
22:17
<
clever >
ajs124: are you doing any IFD?
22:15
<
clever >
ajs124: are the hydra-eval-jobs processes using a lot of cpu?
22:15
<
clever >
noonien: yeah, all args to the bash script get forwarded to qemu
22:15
<
clever >
noonien: kvm, but i believe you already have it
22:14
<
clever >
noonien: that is a very weird issue, but i cant see anything obvious
22:14
<
clever >
noonien: yep
22:12
<
clever >
ajs124: what does the journal for hydra-evaluator say?
22:12
<
clever >
ajs124: is there a hydra-eval-jobs process running for it?
22:11
<
clever >
though is o+r, so it shouldnt matter
22:10
<
clever >
noonien: cat /proc/<pid>/status on the host, with qemu's pid, then look at the uid: and gid:, what does it say?
22:09
<
clever >
noonien: so qemu on the host is failing to open the init file, and forwarding the error down to the guest
22:06
<
clever >
noonien: find the pid of qemu, and try doing `strace -p <pid> -ff -e open,openat` from a second terminal, then try to cat init from inside it
22:06
<
clever >
noonien: looks fairly normal
22:03
<
clever >
noonien: what about the host /proc/mounts ?
22:02
<
clever >
noonien: boots normally here
22:00
<
clever >
thats more how i'm trying to reproduce your issue, your already on that rev, so it wont make much of a difference
21:58
<
clever >
this should build a vm, with a totally empty config file, from the same rev
21:58
<
clever >
[clever@amd-nixos:~/apps/nixpkgs]$ nix-build nixos -A vm --arg configuration '{}'
21:58
<
clever >
[clever@amd-nixos:~/apps/nixpkgs]$ git checkout 37694c8cc0e
21:56
<
clever >
noonien: what nixpkgs rev are you on?
21:55
<
clever >
noonien: how is /nix/store setup on the host?
21:54
<
clever >
/etc/passwd is missing, so it cant translate 0 -> root
21:54
<
clever >
noonien: thats uid 0 group 0, size 5127 bytes
21:53
<
clever >
noonien: and what about the contents of /proc/mounts ?
21:52
<
clever >
noonien: you want /mnt-root/nix/store/
21:50
<
clever >
noonien: boot.debug1mounts is what you want
21:50
<
clever >
noonien: oh, debug1devices is too early
21:50
<
clever >
noonien: then you can get an interactive shell in stage1, and ls the file again from inside the guest
21:49
<
clever >
noonien: same here, you want -append "boot.debug1devices console=ttyS0" -nographic
21:47
<
clever >
noonien: try -append boot.debug1devices -nographic
21:46
<
clever >
noonien: looks like something is breaking with the 9plan stuff to mount /nix/store into the guest
21:45
<
clever >
noonien: switch_root: can't execute '/nix/store/yp1zk95186rqcvnnp3xl6lgbnvg00bnd-nixos-system-nomad-18.09.2327.37694c8cc0e/init': Operation not permitted
21:42
<
clever >
noonien: there should be more error above that, try running it with -nographics i think it was
21:38
<
clever >
noonien: can you screenshot or pastebin the kernel panic?
21:38
<
clever >
global access, thats not it
21:38
<
clever >
noonien: what does `ls -lh /dev/kvm` report?
21:26
<
clever >
noonien: yeah, that will also build a vm, but it may also need a -I nixos-config= if you want to change the cfg it uses
21:19
<
clever >
noonien: nixos-rebuild build-vm -I nixos-config=foo.nix
20:53
<
clever >
azazel: ahh, i was trying to remember what that domain was
20:48
<
clever >
alj[m]: all of this gets built when you nixos-rebuild the laptop
20:48
<
clever >
alj[m]: the tftp is just so the firmware can download ipxe when booting
20:47
<
clever >
alj[m]: and then it uses nix to build the pxe images that it hosts on nginx!
20:47
<
clever >
alj[m]: and the dhcp server includes pxe support, which fetches files from the tftp and nginx the module also configures
20:47
<
clever >
alj[m]: it sets up NAT, so the ethernet can leech off your wifi
20:46
<
clever >
alj[m]: that module sets up dhcp and dns, so the ethernet port can get an ip
20:46
<
clever >
alj[m]: yep
20:45
<
clever >
noonien: non-graphical, and that would greatly increase the memory usage of it
20:44
<
clever >
pie___: thats what callPackage is for
20:41
<
clever >
pie___: add --show-trace to nix repl, with the same args i gave before
20:41
<
clever >
noonien: plug any machine into the ethernet port, and infect away!
20:41
<
clever >
noonien: 3 will take the same basic nix expressions, and then mutate your laptop to behave more like a router, with full pxe booting configured