<slabity>
Yea, don't use busybox in systemPackages. But you could put it in your `appimage-run.override` line.
<slabity>
busybox is a bunch of common linux utilities rewritten as a single tiny binary.
<slabity>
iqubic: If this is still the appimages problem. I'd suggest just trying to use busybox. It adds a ton of tiny binaries that are likely expected
<slabity>
gchristensen: Are you telling me I shouldn't be using nodejs-11_x to provide my tar binary?
<slabity>
Probably want gnutar out of those
<slabity>
Wrap that in parens before putting it in your systemPackages
<ldlework>
slabity: I still contend that NixOS wont win-out in this space because someone is going to come along and turn Nix into a relative assembly language.
<slabity>
Not to mention there's multiple ways of doing so depending on the situation. Do I use 'override', or 'overrideAttrs'? Maybe I need 'overrideDerivation'? No wait this is a python package I need overridePythonAttrs... Fuck it just gonna put it in an overlay
<ldlework>
slabity: ah, as in ever. yeah
<slabity>
Not overriding a derivation despite having used Nixos for a year.
<slabity>
That's impressive
<tilpner>
iqubic, slabity: Correct, appimage-run does not give access to the system environment
<slabity>
Typically an appimage should contain all the dependencies that it relies on. I don't believe it should be able to access any binaries outside of the image.
<slabity>
iqubic: Does it happen on all appimages? Or just a particular one?
<slabity>
,locate cpio
<clever>
slabity: thats an eval-time failure, rather then a build-time failure
<slabity>
worldofpeace: Unfortunately that script has a bunch of hardcoded paths. It also just tries to start a new KDE session and run 'plasmashell -p ...phone', so I'm not sure if it's useful
<worldofpeace>
slabity: I'm seeing a plasma-phone script. I'm guessing you tried just executing that as to start the session.
<worldofpeace>
slabity: Guess its the same situation that's in GNOME then (systemd managed vs xdg autostart)
<slabity>
worldofpeace: I believe those systemd services are just placeholders
<slabity>
Pretty much. Just a few changed dependencies
<slabity>
worldofpeace: It's very similar to the `plasma-desktop` package in nixpkgs
<slabity>
I guess I could start a WIP pr
<slabity>
worldofpeace: 'Working manually' as in I have a working derivation for plasma-phone-components and can run `pkill plasmashell && plasmashell -p org.kde.plasma.shell.phone`
<worldofpeace>
slabity: Have you thought about submitting a pr (you said it was working manually)?
<slabity>
That sounds about right
<worldofpeace>
slabity: I see, well your problem seems to be that all the plasma desktop stuff is in the environment (xdg autostarts) and you don't want that as to start the plasma phone shell
<slabity>
worldofpeace: Yes. I got it running on NixOS manually. Now I'm making a module for it
<worldofpeace>
slabity: Are you working on getting plasma phone things?
<slabity>
worldofpeace: Yes
<slabity>
I'm guessing it's executing something like `plasmashell -p org.kde.plasma.shell.desktop` and want to execute `plasmashell -p org.kde.plasma.shell.phone` instead
<slabity>
I guess specifically I'm looking for what starts the desktop shell and replace it with a new one
<slabity>
What executes the autostart file?
<slabity>
worldofpeace: Searching for 'plasmashell' in that script returns nothing unfortunately.
<worldofpeace>
slabity: I think it's all within the startkde script. Which in is the .bin output
<slabity>
Damn. I have no idea how all these files work together
<clever>
slabity: which may also wind up in /run/current-system/sw/etc or sw/share
<slabity>
Oh wait, it might be in `etc/xdg/autostart/*` files
<slabity>
goibhniu1: Sorry, I meant I can't find plasmashell within that script. Unfortunately nix-locate only checks file names and not contents :/
<goibhniu1>
slabity: FWIW, I do have /nix/store/raa3g87n6ar9hll50v787igaff7hgv3j-plasma-workspace-5.14.5-bin/bin/startkde
<slabity>
can't seem to find it*
<slabity>
Does anyone know where `plasmashell` is called when running a system with desktopManager.plasma5.enable? I thought it would be in the `${plasma-workspace}/bin/startkde`, but I can'
2019-03-25
<slabity>
Does it appear when you run `ip a`
<slabity>
Now just gotta get it running on my tablet :D
<betaboon>
slabity: ouh nice. you made progress :D
<slabity>
Just got plasma-mobile working in Nix!
2019-03-24
<slabity>
Has that been done before?
<slabity>
Anyone know how I can make a nixos-container with xserver services? Like have the container open a window of another desktop on my main system?
2019-03-22
<wolfman154>
slabity: a bunch of logs about gnome shell desktop
<slabity>
wolfman154: Anything when you run 'journalctl -xn'?
<wolfman154>
slabity: gdm log directory is empty
<slabity>
If not, the X.0.log should at least be there
<slabity>
wolfman154: I believe gdm logs get stored in /var/log/ if you can find it there
<wolfman154>
slabity: gnome crashes and when I reboot it stops at services sign in gdm throws me to a terminal where I get stuck, I had to switch back to an older configuration.nix
<slabity>
wolfram154: It sounds like you're crashing GNOME or the X11 service
<slabity>
wolfram154: It might not be correct to put it in systemPackages. There's a few options like `services.xserver.xkb*`
<wolfman154>
slabity: gnome breaks and gen stops working and it removes a bunch of symlinks?
<betaboon>
slabity: i dont see any msrest-depency in nixops either oO
<slabity>
I'm running nixos-unstable channel
<slabity>
betaboon: Nixops uses python2-msrest which uses aiohttp
<betaboon>
slabity: plus i can build nixops from current nixpkgs-master just fine
<betaboon>
slabity: but i cant see any dependency for aiohttp ? oO
<slabity>
betaboon: Well the derivation changed to reject python2 only few weeks ago
<betaboon>
slabity: aiohttp has required python3 since atleast early 2017.
<slabity>
aiohttp now requires python3, so nixops won't build
<slabity>
That explains why it doesn't work anymore :(
<slabity>
Nixops is written in python2?
<slabity>
nixos-unstable channel
<slabity>
error: aiohttp-3.5.4 not supported for interpreter python2.7
<slabity>
Is nixops breaking for anyone else? I'd expect at least that package to be well tested
<slabity>
Is anyone else unable to install NixOps from nixos-unstable? Getting an error: `error: aiohttp-3.5.4 not supported for interpreter python2.7`
<slabity>
linarcx: Do you have a makefile?
2019-03-21
<slabity>
I'm guessing you're not using JACK either?
<slabity>
noonien: Are you running PA?
<slabity>
noonien: I believe alsa starts up in the kernel
<illegalprime>
slabity: andi-: that worked! thanks a bunch!
<slabity>
Yea, bad things will happen if you try and just make it yourself
<slabity>
illegalprime: It's a socket owned by root
<illegalprime>
slabity: that's set correctly, who do you have it owned by? my error message is: error: cannot connect to daemon at '/nix/var/nix/daemon-socket/socket': Connection refused
<slabity>
illegalprime: srw-rw-rw-
<slabity>
Kind of a long-shot, but I don't suppose anyone knows how to get plasma mobile on NixOS?
<slabity>
Wanna see if I can get plasma mobile running on it...
<betaboon>
slabity: congrats for gettint it to run :D
<slabity>
betaboon: Yea, just jokin around
<betaboon>
slabity: hew was talking about pseudonoms problem
<slabity>
Ralith: Getting a 32-bit bootloader on a 64-bit system was kinda hard :(
<slabity>
Just got NixOS running on an old windows tablet :D
<slabity>
I guess I'll try it out and see if it works
<slabity>
Wow. That is incredibly good timing. Literally merged a minute ago
<linarcx>
slabity: Thank you. i also try: `nvim --noplugin`, but nothing changed. Maybe i have to try another terminal.
<slabity>
linarcx: Possibly. Might be a config issue, but I can't tell.
<linarcx>
slabity: xterm-256color and my terminal is kitty. Is it a bug?
<slabity>
linarcx: It's likely neovim is not interacting with your terminal properly if it won't respond to `:terminal /bin/sh`. What's your TERM variable?
<slabity>
And building it using `nix-build '<nixpkgs/nixos>' -A config.system.build.isoImage -I nixos-config=iso.nix`
<slabity>
I'm not even sure I have enough swap space
<srhb>
slabity: Which one?
<slabity>
I don't suppose anyone knows why building a NixOS ISO takes up over 26GB of memory...
<linarcx>
slabity: No, i try it but nothing changed.
<srhb>
slabity: It's actually pretty accessible.
<slabity>
It's probably far outdated by now
<slabity>
And definitely don't study the PhD paper
<slabity>
hodor123456: So what do you mean update a specific version to latest version? If you want a specific version you can do so. If you want the latest version you can do so
<hodor123456>
slabity, that's nice.
<slabity>
If it fails, then you're not left with a half-way installed system
<slabity>
Each time you update, it creates a new profile. If it successfully builds, then it atomically switches to the new one
<slabity>
Yea
<slabity>
Because your system has a profile, and your user has a profile
<hodor123456>
slabity, that is awesome.
<slabity>
hodor123456: It also allows you to do things like rollback to a 'safe' profile if a package breaks or your system becomes unstable
<slabity>
~/.nix-profile; hidden folder
<slabity>
hodor123456: Well, for example I could run 'nix-shell -p gcc5' and that shell now has a profile with gcc on it. Then I can run `nix-shell -p gcc7` in another shell and they will both work
<slabity>
But they're definitely worth a read
<slabity>
tbf the manuals are pretty... Heavy
<slabity>
hodor123456: Yea, you can't install v1 and v2 of a package in the same profile. You need to install them in separate profiles
<slabity>
linarcx: Can you try running `:terminal /bin/sh` in neovim? Does a shell appear?
<linarcx>
slabity: *neovim indeed.
<linarcx>
slabity: I put nvim in `/etc/nixos/configuration.nix` and `sudo nixos-rebuild swtich`.
<slabity>
linarcx: Is it not executing your shell?
<slabity>
Building a live-cd has used up 12GB of memory and 14GB of swap. What? How much memory do I need?
<slabity>
If you don't need to pip-provided wxPython package, I would recommend using the Nixpkgs one. It sounds like a headache to get it working
<slabity>
kandinski: I got most of the way using `-E "pkgconfig zlib libjpeg openjpeg libtiff freetype lcms2 libwebp tcl gtk3 libGLU gstreamermm which glibc libcxx libstdcxxHook"` as a flag, but the wxPython tests are looking for a hardcoded /lib/cpp path. Normally a nix expression would pass `--replace CPP=/lib/cpp CPP=${stdenv.cc}/bin/cpp` to direct it to the actual compiler, but I'm not sure how to get pypi2nix to do so.
<kandinski>
slabity: (and thanks!)
<kandinski>
slabity: it's 2am here, I'm going to bed now. Please let me know how you go if you give it a try.
<slabity>
kandinski: Which python version do you need to build this for?
<slabity>
kandinski: Can you post the requirements.txt?
<slabity>
Does `pypi2nix -r requirements.txt` not work?
<slabity>
Huh. I was gonna point you to https://nixos.wiki/wiki/Python, but it looks like the pypi2nix section is completely blank
<kandinski>
slabity: I'm trying to install the dev environment from work, which includes wxPython
<slabity>
If you're just using wxPython as a test for learning pypi2nix, that's a little more involved
<slabity>
Sorry, what I mean is do you want to just install wxPython in your user environment? If so, you can just use `nix-env -iA nixos.pythonPackages.wxPython`
<slabity>
How do you want to install it? Just in your user environment?
<slabity>
Ah. For some reason I completely missed your first msg
<slabity>
kandinski: Pre-set recipe?
<slabity>
Is there a easy way to generate a NixOS 32-bit install ISO from a 64-bit machine?
2019-03-15
<slabity>
timor: You should be able to access them with 'options.*'
<srhb>
slabity: Sorry to hear that :-P
<srhb>
slabity: Go figure.
<srhb>
slabity: .. Oh, I do. The files are literally called Fabric-....tar.gz in the old versions, but fabric-....tar.gz in the newer ones
<slabity>
That wild goose chase cost me over 2 hours. Thanks for the help :)
<srhb>
slabity: Frankly I'm not sure why the lowercase one works for any version.
<srhb>
slabity: I just noticed that the pypi url, when I tried "fabric" lowercase, redirected me to Fabric uppercase.
<slabity>
How did you know the name difference? Where did you see that?
<srhb>
slabity: Sure thing.
<srhb>
slabity: Funtimes.
<slabity>
srhb: Thanks.
<slabity>
They even broke name compatibility wtf
<slabity>
Oh yea. That seems to do it
<slabity>
It works if I set a 2.* version, but not a 1.* version for some reason
<srhb>
slabity: So do you just need to use Fabric instead of fabric? :)
<slabity>
srhb: The current version is 2.*, but I need 1.* because it breaks compatibility. I looked at the release history of the package and found the latest 1.* release was 1.14.1: https://pypi.org/project/Fabric/2.4.0/#history
<srhb>
slabity: The closest thing I can find to that is Fabric3-1.14.post1
<srhb>
slabity: Alright! Now, regarding the version.. Where did you actually find that?
<srhb>
slabity: Hard to answer if it's "special" -- what did you do? :)
<slabity>
An overriden derivation that uses `fetchPypi` is targetting the wrong URL from pythonhosted.org (resulting in 404). Do I need to do anything special when overriding a `fetchPypi` derivation?
2019-03-13
<jD91mZM2>
slabity: Ah, my bad
<slabity>
jD91mZM2: Unfortunately no. That appears to give all options instead of just the ones set in my system config
<jD91mZM2>
slabity: I don't know of any general way, but in your case you should be able to do `nix eval --raw '(builtins.concatStringsSep "\n" (builtins.attrNames (import <nixpkgs/nixos> {}).config.services))'`. Does that do what you wanted or did I misunderstand?
<slabity>
Don't suppose there's a way to get `nix repl` to pretty print?
<slabity>
clever: Thanks. That works perfectly
<clever>
slabity: nix repl '<nixpkgs/nixos>' then eval config.services
<slabity>
Not to sound like a broken record, but is it possible to use nixos-option to evaluate an entire set? Or get the variables that have been set?
<musicmatze>
slabity: Here's the relevant file I guess:
<slabity>
musicmatze: Does allowUnfree accept all licenses? I still need to include `oraclejdk.accept_license` to run oraclejdk
<slabity>
I'd like to get a list of variables that are evaluated in the system
<slabity>
Or get a list of variables that are evaluated in the system? Doing something like `nixos-option --xml services` just gives me a bunch of `<unevaluated />` tags
<slabity>
nixos-option works well. But is there any way to get it to evaluate all variables in a set?