2017-11-14
06:08
<
clever >
and did the error happen right after that?
06:07
<
clever >
Lisanna: add a "set -x" near the top and then see what happens
06:07
<
clever >
Lisanna: what was the exact command to give that error?
06:05
<
clever >
Lisanna: hmmm, can you try just doing mkdir /tmp/ and see what happens?
06:01
<
clever >
just pop nixUnstable into line 9, and: nix copy --to local?root=/mnt/ ${paths}
06:00
<
clever >
no need for chroot
06:00
<
clever >
it works similar to nix-copy-closure, but allows the destination to be a local FS
06:00
<
clever >
this lets you recursively copy things from one store to another, including all deps
06:00
<
clever >
nix copy --to local?root=/mnt
05:59
<
clever >
its from nixUnstable
05:59
<
clever >
let me find an example
05:59
<
clever >
you could use the new nix copy for that
05:58
<
clever >
for the most part, yeah
05:58
<
clever >
and there is a make-disk-image in nixos to do this
05:58
<
clever >
also, the new nix copy lets you do similar things
05:57
<
clever >
Lisanna: line 31 is using the nixos vm, not the /mnt nix
05:57
<
clever >
and nix plus utillinux plus packages will be in PATH
05:56
<
clever >
so line 7 runs the build script of 8 inside a vm, as root
05:54
<
clever >
Lisanna: ah, i'll need more info then about what your doing, the nix expression would be a good start
05:53
<
clever >
Lisanna: only things in the scope of the nixos for the vm will be "valid" in its nix store, but it will still have read access to things that are "not valid"
05:52
<
clever >
Lisanna: can you gist the nix expression?
05:16
<
clever >
dhess: currently, you just need to define a release.nix file and have it return derivations for the major services
05:15
<
clever >
dhess: thats one of the things ive been wanting to finish
05:13
<
clever >
dhess: hydra cant edit the channel, but you can point hydra to the head of the channel
05:12
<
clever >
notthemessiah: you can try just wiping only /etc and keep the config, no need to even reinstall
05:12
<
clever >
dhess: hydra can automate running tests (in a vm) on the current and future nixpkgs version, so you know if things are broken before you deploy
05:11
<
clever >
dhess: hydra can handle pre-building things before nixops needs it, so deploys are faster
05:11
<
clever >
dhess: ahh
05:09
<
clever >
hydra handles covering everything, to find things i may have missed
05:08
<
clever >
dhess: mostly, i be aware of what attributes of release or top-level my changes affect, and build those to test them
05:06
<
clever >
so you can make sure you never push stuff that will fail on hydra
05:06
<
clever >
dhess: you can use nix-build to test the release.nix file locally, so you can pre-test things the same way hydra will test them
05:04
<
clever >
you need to boot it to make the users exist
05:04
<
clever >
nixos-install --chroot doesnt setup the new users
05:02
<
clever >
notthemessiah: are you booted into the install or the livecd?
05:01
<
clever >
notthemessiah: "sudo -u USER -i"
05:00
<
clever >
notthemessiah: use sudo, not su
05:00
<
clever >
if you enable ssdm but disable xserver, things break
04:53
<
clever >
so we need to see your configuration.nix file
04:53
<
clever >
this error means the configuration.nix file isnt valid
04:53
<
clever >
2017-11-14 00:47:24 < notthemessiah> "attribute 'display-manager' missing, at /nix/store/bqf4...fsd-nixos-17.09.2055.c19...c9/nixos/nixos/modules/services/x11/display-managers/sddm.nix
04:52
<
clever >
notthemessiah: can you gist /mnt/etc/nixos/configuration.nix?
04:49
<
clever >
nixos-install automatically creates a new generation
04:47
<
clever >
thats not your generation, thats your current configuration.nix
04:45
<
clever >
notthemessiah: what error is it giving?
2017-11-13
06:02
<
clever >
Golden_Skittle: you may also want to look into "stack --nix"
06:01
<
clever >
Golden_Skittle: run nix-shell
04:16
<
clever >
i didnt give a path starting with //
04:16
<
clever >
what cannot access what?
04:14
<
clever >
Golden_Skittle: it should have a symlink like this
04:14
<
clever >
lrwxrwxrwx 1 clever users 44 Oct 11 2015 channels_root -> /nix/var/nix/profiles/per-user/root/channels
04:14
<
clever >
[clever@amd-nixos:~]$ ls -lh .nix-defexpr/
04:14
<
clever >
did you delete the old channels_root symlink?
04:12
<
clever >
and as root?
04:12
<
clever >
Golden_Skittle: what are the contents of ~/.nix-defexpr/ ?
04:09
<
clever >
thats not how defexpr works
01:44
<
clever >
romildo: it will already have been unpacked in postFetch, so you shouldnt need to do that
2017-11-12
21:37
<
clever >
betaboon: try also setting boot.isContainer = true;
21:33
<
clever >
betaboon: nixos also supports containers directly, and you dont need to define the machine at the nixops level
21:33
<
clever >
betaboon: interesting, i havent seen the container backend used like that before
21:29
<
clever >
betaboon: what error is it giving when building?
21:22
<
clever >
betaboon: nixpkgs.system in configuration modules
21:17
<
clever >
betaboon: if you dont set the system param for a build, it will default to the same system that nix-build was compiled for
11:08
<
clever >
i should have gotten to bed long ago
11:08
<
clever >
anyways, its now 7am
11:05
<
clever >
how are you refering to PhiledAlsa?
11:03
<
clever >
not haskellPackages.language-c
11:03
<
clever >
that is applying an override to pkgs.language-c
11:03
<
clever >
oh, and 31 is also of no use
11:03
<
clever >
4 is still of no use
11:02
<
clever >
ah no, 26 is seperate
11:02
<
clever >
if that indent is right...
11:02
<
clever >
toppler: and line 26 sets the nixpkgs attribute of the config, which is also never read
11:01
<
clever >
toppler: line 4 just leaves a stray attribute in the middle of the nixpkgs config, that will never be read by anything
10:55
<
clever >
and then manualy copy the 2 rescue files to /boot2
10:55
<
clever >
srhb: try symlinking /boot to /boot1/
10:55
<
clever >
srhb: ah, i dont think boot.loader.grub.extraFiles supports mirroredBoots
10:54
<
clever >
srhb: are you using grub or systemd-boot?
10:54
<
clever >
srhb: thats a path that the existing grub config sets up
10:43
<
clever >
adisbladis: placing all bluetooth dongles into a 55 galon drum of gas "solves" the problem :P
10:42
<
clever >
adisbladis: ive had a lot of trouble before with getting bluetooth to work
10:41
<
clever >
srhb: so snapshots didnt try go save everything i GC'd
10:41
<
clever >
srhb: i recently used that module to split /nix/ out of my / dataset and make a new /nix/ dataset
10:40
<
clever >
Yaniel: did you set hardware.opengl.driSupport32Bit = true; ?
10:40
<
clever >
srhb: if you add this module, you can boot into a recovery env, then make the changes with nixos "off"
10:39
<
clever >
srhb: a: it will probably overload the argv limit, b: its not atomic, it will delete a directory, then slowly re-populate it
09:36
<
clever >
without any number
09:36
<
clever >
change the openjdk to oraclejdk
09:34
<
clever >
you must use the name you used in config.nix
09:33
<
clever >
nixos.redserverv3
09:32
<
clever >
yeah, that looks right
09:28
<
clever >
infact, you merged 3 of them together now
09:28
<
clever >
playX: you still merged 2 of the lines that shouldnt have been merged
09:21
<
clever >
fix that, then re-run the previous nix-build and paste its output to a pastebin
09:21
<
clever >
line 22 and 23 should be one line, line 24
09:20
<
clever >
sounds like something didnt work right when building
09:19
<
clever >
playX: and add /bin/ at the end
09:19
<
clever >
sphalerite: yeah, i see the issue
09:18
<
clever >
playX: now run ls -lh on that path
09:18
<
clever >
sphalerite: ahh, then you want nix-push + scp, i see where your problem is
09:18
<
clever >
playX: oops, its called RedServer in that namespace
09:17
<
clever >
and nothing in nix is really meant to automate pushing, only pulling (hydra)
09:17
<
clever >
sphalerite: ah, only nix-copy-closure can upload over ssh
09:16
<
clever >
playX: you need to take out both the " at the start and the " at the end
09:15
<
clever >
playX: what is the output of "nix-build '<nixpkgs>' -A redserver"
09:13
<
clever >
playX: and nix-env -q ?
09:12
<
clever >
playX: what is the output of "ls -lh ~/.nix-profile/bin/" ?
09:08
<
clever >
playX: redserver
09:05
<
clever >
playX: what are the contents of the .nix file
09:04
<
clever >
sphalerite: cant find a concrete example skimming over the logs
09:02
<
clever >
sphalerite: 2017-09-19 22:00:01< nh2> clever: do you know if there's a nix.* option for ssh-subsituter-hosts? Can't find anything on
https://nixos.org/nixos/options.html . Or can I give ssh:// for the normal binary cache setting?
08:52
<
clever >
did you reinstall it with nix-env after changing the name in the nix file?
08:51
<
clever >
can you take a screenshot of it failing to run redserver?
08:49
<
clever >
you called the command RedServerV3
08:48
<
clever >
playX: why did you put a $ in the name?, thats even more special then .
08:46
<
clever >
you may need to also remove that . in the nix exression and re-install
08:46
<
clever >
dont start the filename with a .
08:42
<
clever >
you have to merge them correctly
08:42
<
clever >
{ allowUnfree = true; packageOverrides = pkgs: { RedServer = pkgs.callPackage ./redserver.nix {}; }; }
08:41
<
clever >
you have 2 sets in the same file
08:39
<
clever >
{ packageOverrides = pkgs: { RedServer = pkgs.callPackage ./redserver.nix {}; }; }
08:39
<
clever >
between the } and the }
08:38
<
clever >
i missed a ; in my example
08:38
<
clever >
playX_: oops, that should end with }; }
08:31
<
clever >
then you can just nix-env -iA nixos.RedServer
08:31
<
clever >
and config.nix goes in ~/.config/nixpkgs/config.nix
08:31
<
clever >
{ packageOverrides = pkgs: { RedServer = pkgs.callPackage ./redserver.nix {}; } }
08:30
<
clever >
playX_: you need to create a config.nix that contains the following
08:28
<
clever >
playX_: have you looked at the nixpkgs manual, the section on package overrides?
08:28
<
clever >
nixpkgs loads config.nix
08:27
<
clever >
playX_: after putting it into your packageOverrides, it can be installed like normal, the command you run is the name you gave it on 19/29
08:23
<
clever >
playX_: the same path needs to be on both 19 and 29
08:21
<
clever >
depends on if you want to install it with nix-env or systemPackages
08:20
<
clever >
packageOverrides are described in the nixpkgs manual
08:20
<
clever >
playX_: and in config.nix under packageOverrides, you need to do RedServer = pkgs.callPackage ./redserver.nix {};
08:19
<
clever >
playX_: lines 19 and 29 refer to different files
08:06
<
clever >
playX_: load it with callPackage in a normal packageOverride
08:02
<
clever >
so if you do ./foo.jar; it will look for foo.jar in the same directory as the nix file
08:02
<
clever >
all relative paths are relative to the file that contains them
08:01
<
clever >
playX_: change the src= line
07:55
<
clever >
playX_: yeah
07:46
<
clever >
playX_: sounds like you will need to patch that launcher the same way multimc was patched
07:43
<
clever >
case sensitive
07:42
<
clever >
playX: run MultiMC
07:42
<
clever >
playX: then multimc should just work
07:40
<
clever >
playX: the library giving the failure is also X related, so i dont see that version working as a server
07:40
<
clever >
playX: multimc needs an Xorg session to run
07:38
<
clever >
playX: MC works fine when ran under multimc, which is packaged in nixpkgs
07:00
<
clever >
lines 1-3, and 41
06:39
<
clever >
tnks: there is also a stack2nix program, which will take your stack file, and generate a new haskellPackages set around that
06:38
<
clever >
via hackage2nix
06:38
<
clever >
tnks: so it will depend on your nixpkgs revision, and what peti last commited when converting the hackage db into nixpkgs
06:38
<
clever >
tnks: when using just plain cabal2nix, it just expects the packages to already be in pkgs.haskellPackages, and uses whatever version nixpkgs contains
03:17
<
clever >
viaken: when using the acme modules in nixos, you have to restart nginx manualy after the cert is setup
2017-11-11
22:56
<
clever >
ahmad: add autoreconfHook to the buildInputs
04:17
<
clever >
shanemik_: split outputs, you need to build the .doc attribute of the derivation
03:29
<
clever >
mekeor: while .overrideAttrs changes the arguments as they are passed into stdenv.mkderivation
03:28
<
clever >
mekeor: .override is to change the arguments going into the file, on line 1-ish
03:15
<
clever >
.override cant change src, that needs .overrideAttrs
02:09
<
clever >
Unode: you may also want to set "neededForBoot=true;" on the entry in nixos, so the initrd mounts it
02:07
<
clever >
then things fail in an obvious way if you dont mount
02:07
<
clever >
i try to chmod the mount-point to 0, so nothing can access the directory under it
02:06
<
clever >
but most things dont care
02:06
<
clever >
zfs and s3fs are special, in that they demand the directory to be empty first
02:06
<
clever >
even of its not empty
02:06
<
clever >
its often caused /boot problems for new nixos users
02:05
<
clever >
you can mount any fs over an existing directory
02:05
<
clever >
Unode: thats how linux has always worked
02:02
<
clever >
Unode: oops, ^^
02:01
<
clever >
there is already an option to do just that
01:59
<
clever >
how did you configure tmp to be a tmpfs?
01:59
<
clever >
then the system fixed the problem
01:59
<
clever >
and you where storing files in the /tmp directory of /
01:59
<
clever >
Unode: it sounds like the tmpfs wsnt mounted to begin with
01:47
<
clever >
what about the timestamp of the oldest file?
01:45
<
clever >
journalctl would also help if that was the case
01:44
<
clever >
i just happened to catch dhcp refreshing /etc/resolv.conf
01:44
<
clever >
Unode: yeah, leave it running into a log file, and wait for it to happen
01:44
<
clever >
23195 23194 resolvconf -d enp3s0.ra -f
01:44
<
clever >
23194 32403 /nix/store/azq5rpd6z2m6qs80fcr56mcflggabv7y-dhcpcd-6.11.5/libexec/dhcpcd-run-hooks
01:43
<
clever >
Unode: this shows every program being ran on the system, and the parent pid of each
01:43
<
clever >
[root@amd-nixos:~]# nix-shell -p perf-tools --run execsnoop
01:42
<
clever >
Unode: execsnoop may help
01:40
<
clever >
tests go under buildInputs like the rest of the deps
01:34
<
clever >
Unode: done
01:34
<
clever >
gnome2.libart_lgpl.out 0 s /nix/store/hrjassnhnpwl59ymb4vnqb7xrm3i0bpq-libart_lgpl-2.3.21/lib/libart_lgpl_2.so
01:34
<
clever >
[clever@amd-nixos:~]$ nix-locate art_lgpl_2
01:32
<
clever >
yeah, after preunpack, unpack, and postunpack have ran, the stdenv will cd into the dir it made
01:28
<
clever >
Unode: yeah, just throw in an ls and pwd
01:27
<
clever >
sauyon1: neededForBoot = false; should do that
01:27
<
clever >
Unode: also try an echo on prePatch, postPatch, and preConfigure
01:26
<
clever >
Unode: what if you put an echo statement into it?
01:23
<
clever >
i have the type encoded into the device
01:22
<
clever >
and set the fstype to fuse
01:22
<
clever >
sauyon: i had to give an absolute path
01:22
<
clever >
sauyon: line 10 of the file i linked, # mount unsets PATH when running this
01:22
<
clever >
so you can just do postUnpack = "rm foo/bar";
01:21
<
clever >
Unode: i think it will accept any arg that stdenv.mkDerivation accepts
01:20
<
clever >
55 buildPythonPackage = makeOverridablePythonPackage (callPackage ../development/interpreters/python/build-python-package.nix {
01:20
<
clever >
{ column = 10; file = "/nix/store/q71jxrnm2a49s8hzfirm4ssri1x0lqqg-nixos-18.03pre118328.6d86fcb86d/nixos/pkgs/top-level/python-packages.nix"; line = 85; }
01:20
<
clever >
nix-repl> builtins.unsafeGetAttrPos "buildPythonPackage" pythonPackages
01:19
<
clever >
Unode: find the definition of buildPythonPackage, and see what arguments it accepts
01:18
<
clever >
so you never have to touch access keys
01:18
<
clever >
sauyon: that module does everything, even setting up the iam role and bucket with nixops
01:15
<
clever >
Unode: run "gist -p" on the file from a shell
01:14
<
clever >
i think your terminal did that when you copied
01:14
<
clever >
scroll to the right
01:14
<
clever >
its visible in raw mode
01:13
<
clever >
also the '' is missing from that patch
01:13
<
clever >
it creates a new package, that is compiled by running the command, then returns the result of building it
01:12
<
clever >
runCommand doesnt work like that
01:09
<
clever >
Unode: somewhere in the patchPhase i'm thinking
2017-11-10
23:03
<
clever >
tanonym: what does which enlightenment.efl say?
22:59
<
clever >
so realpath $(which enlightenment.efl)
22:59
<
clever >
it has to go into argv[1], not stdin
22:58
<
clever >
tanonym: just run realpath on the output of which or type
22:58
<
clever >
pie_: if you create a file like this, it will fool nix-env into thinking you have a channel called foo
22:58
<
clever >
[clever@amd-nixos:~]$ cat .nix-defexpr/test/foo/default.nix
22:58
<
clever >
import /home/clever/apps/nixpkgs
22:57
<
clever >
yeah, snapshots basicaly ruin any type of rolling garbage collection
22:54
<
clever >
thats basicaly 90% of it for history
22:54
<
clever >
so 80mb for the rest
22:54
<
clever >
and 719mb of that is just .git
22:54
<
clever >
tanonym: 799mb
22:52
<
clever >
--shallow would reduce the usage, but it has trouble pulling when shallow
22:52
<
clever >
pie_: the size of the entire history of the repo
22:44
<
clever >
"git checkout REV" with the right version (check nixos-version), then just edit it in that tree and "nixos-rebuild -I nixpkgs=/home/clever/nixpkgs test"
22:44
<
clever >
and if your cloning the repo, you dont even need an override
22:42
<
clever >
tanonym: if you had a copy of the enlightenment directory in /etc/nixos/, you could so something like this to recreate the right value
22:42
<
clever >
callPackage = newScope pkgs.enlightenment;
22:41
<
clever >
enlightenment = recurseIntoAttrs (callPackage ../desktops/enlightenment {
22:41
<
clever >
but you could manualy run the new E from that symlink, if it supports upgrading itself
22:41
<
clever >
the symlink would basicaly have zero effect
22:40
<
clever >
oh wait, hmmm, line 31
22:40
<
clever >
looks like its just enlightenment = pkgs.callPackage ./efl.nix {};
22:39
<
clever >
you will need to override the right attribute
22:39
<
clever >
and otherwise, it will have zero impact on the system
22:39
<
clever >
the nix-build command will just spit out a result symlink in the current directory
22:38
<
clever >
tanonym: just keep in mind, that wont have any effect on nixos-rebuild, but you can then put it into a packageOverride
22:37
<
clever >
tanonym: yeah, should be that simple
22:34
<
clever >
just edit the version in the name&url, and the failure will tell you the right hash
22:30
<
clever >
the new default.nix would have the new hash in it already
22:10
<
clever >
ive found that libinput cant disable the mouse while typing on this laptop
20:17
<
clever >
its a glitch in the matrix :P
20:10
<
clever >
the linux version isnt limited to the numpad
20:09
<
clever >
sphalerite: there is that old alt+numpad thing, but it might be windows only
19:15
<
clever >
adamt: shouldnt need to use a channel anymore
16:30
<
clever >
Unode: or it used a binary cache to download a pre-build 2.26
16:29
<
clever >
havent tried others
05:33
<
clever >
check env's output
05:33
<
clever >
ylwghst-nix: you need to unset one of the TMP vars
05:20
<
clever >
ylwghst-nix: export NIX_PATH=nixpkgs=/nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs:nixos-config=/etc/nixos/configuration.nix:/nix/var/nix/profiles/per-user/root/channels
05:13
<
clever >
ylwghst-nix: you can try doing "nixos-install --chroot" then "nixos-rebuild boot" inside that
04:23
<
clever >
its already in nixpkgs
04:23
<
clever >
that generates a bash script, that will run vim and tell it to use a given vimrc
04:20
<
clever >
a modified version can also be made, that would just be installable with nix-env
04:18
<
clever >
so now i can get the exact same vim config, on machines i fully control, and also on other machines where i dont want to hijack the vim
04:18
<
clever >
gfixler: and this second version is for use with nixos, it just goes into the imports list of configuration.nix
04:17
<
clever >
gfixler: in this case, i just run nix-shell on that file, and i get a fully working vim with all of the config i expect
04:17
<
clever >
gfixler: this is something i had thrown together for using my normal vim config on a shared machine
04:16
<
clever >
gfixler: one second
04:14
<
clever >
Lisanna: yep
04:09
<
clever >
then nixos-rebuild wont have to do any network IO
04:09
<
clever >
let it run until it finishes, that should build everything
04:08
<
clever >
Lisanna: lets try something simpler, nix-build '<nixpkgs/nixos>' -A system --option binary-caches ""
04:08
<
clever >
Lisanna: yeah