| 29 Mar 2023 |
Colin | In reply to @rkwq:matrix.org Not sure if it's the right place to ask this. I've never used NixOS but I'm interested in doing so for dev. Is it possible possible to install Jetbrains IDE on NixOs and use it as I would with a regular distro? I'm not directly looking into leveraging nix shell etc. From what I've been reading online it's not supported. I like the idea behind nix and the idea of reverting to a previous *working* configuration is the main reason I'm looking to switch. rkwq: you might have better luck asking in the more general-purpose #nix:nixos.org room. there are some Jetbrains packages, though i couldn't tell you anything more about them than their descriptions: https://search.nixos.org/packages?type=packages&query=jetbrains | 02:56:25 |
@rkwq:matrix.org | Thanks! | 16:33:43 |
| 30 Mar 2023 |
R̴̨͕͇͍̞̮̐̅͆̌̀̉̐͋̈́̃̀͒́̎̅̚̚̚͠͝Ĕ̵̡̛͖͖̟̙̫̱͈̘̞̭͍͍͑̌̄͑̓̋̓̀̈̏̈́͊̇͊͆̉͂̏̀̃̚͘͝͝ͅͅD̶̡̢͔̱̖̮͙͉̘̺͓͍̩̮͈͍͗̃̀̏͌͘͜ͅŚ̸̬̭̯̬͙͇͓̬̩̳̤͚͓̤̩̺͉͖̉͛̓̿̎͊̿̆́̐͂̇͌̄̇̓͘ͅͅT̴̞̫̘̝͇͔̟̪̪̦͂̔̎̀̎ͅŎ̷̡̬̹̪͈̭̣͈̭̭͉̦̖̝̘̪͖͔̥̦̘̻̳Ṋ̶̛̫͈̳̘͚̜̔̋͆̅̈́͊̑͊̉̌̈́̾͑̈́̚ͅË̸̡̨̨̛͇̜̖͔͖̻̟̗̠̙͓̘̗̥͉͇̜͑͆͊͑͑̀̓͒͜͝͝ | So I'm on nixos-unstable and I'm trying to update my system, but the package gnome-decoder is marked as broken and halts the build. A fix has been pushed to master, but hasn't hit nixos-unstable yet.
I've set environment.gnome.excludePackages = [pkgs.gnome-decoder] and have no references to the package anywhere else, but it still somehow keeps being added to my system, and I have no idea why or where. I've looked through the linked file in the NixOS package search, and it doesn't reference the package. GitHub search on the nixpkgs repo only shows commits and no code references to the package.
Here's the file on the commit fixing the package: https://github.com/NixOS/nixpkgs/blob/bcf8849a8144cd2dde13784e3de04d9b1e27cfb6/pkgs/applications/graphics/gnome-decoder/default.nix
Any idea what options enable this?
| 12:00:52 |
R̴̨͕͇͍̞̮̐̅͆̌̀̉̐͋̈́̃̀͒́̎̅̚̚̚͠͝Ĕ̵̡̛͖͖̟̙̫̱͈̘̞̭͍͍͑̌̄͑̓̋̓̀̈̏̈́͊̇͊͆̉͂̏̀̃̚͘͝͝ͅͅD̶̡̢͔̱̖̮͙͉̘̺͓͍̩̮͈͍͗̃̀̏͌͘͜ͅŚ̸̬̭̯̬͙͇͓̬̩̳̤͚͓̤̩̺͉͖̉͛̓̿̎͊̿̆́̐͂̇͌̄̇̓͘ͅͅT̴̞̫̘̝͇͔̟̪̪̦͂̔̎̀̎ͅŎ̷̡̬̹̪͈̭̣͈̭̭͉̦̖̝̘̪͖͔̥̦̘̻̳Ṋ̶̛̫͈̳̘͚̜̔̋͆̅̈́͊̑͊̉̌̈́̾͑̈́̚ͅË̸̡̨̨̛͇̜̖͔͖̻̟̗̠̙͓̘̗̥͉͇̜͑͆͊͑͑̀̓͒͜͝͝ | I'm attempting to make an overlay, but I'm a noob with all the override methods and the package doesn't call stdenv.mkDerivation, but clangStdenv.mkDerivation, so I'm not sure how to make this work. My attempts so far have yielded errors with fixed-points, missing arguments, or wiping out the other packages in nixpkgs | 12:05:01 |
R̴̨͕͇͍̞̮̐̅͆̌̀̉̐͋̈́̃̀͒́̎̅̚̚̚͠͝Ĕ̵̡̛͖͖̟̙̫̱͈̘̞̭͍͍͑̌̄͑̓̋̓̀̈̏̈́͊̇͊͆̉͂̏̀̃̚͘͝͝ͅͅD̶̡̢͔̱̖̮͙͉̘̺͓͍̩̮͈͍͗̃̀̏͌͘͜ͅŚ̸̬̭̯̬͙͇͓̬̩̳̤͚͓̤̩̺͉͖̉͛̓̿̎͊̿̆́̐͂̇͌̄̇̓͘ͅͅT̴̞̫̘̝͇͔̟̪̪̦͂̔̎̀̎ͅŎ̷̡̬̹̪͈̭̣͈̭̭͉̦̖̝̘̪͖͔̥̦̘̻̳Ṋ̶̛̫͈̳̘͚̜̔̋͆̅̈́͊̑͊̉̌̈́̾͑̈́̚ͅË̸̡̨̨̛͇̜̖͔͖̻̟̗̠̙͓̘̗̥͉͇̜͑͆͊͑͑̀̓͒͜͝͝ | Is there some sort of nix subcommand or CLI package to trace an option or package to some place in your config that causes it to be enabled? Debugging my config feels like finding a needle in a haystack, which leads me to believe I'm missing a useful part of the debug workflow. | 12:13:33 |
Jan Tojnar | In reply to @redstone-menace:matrix.org
So I'm on nixos-unstable and I'm trying to update my system, but the package gnome-decoder is marked as broken and halts the build. A fix has been pushed to master, but hasn't hit nixos-unstable yet.
I've set environment.gnome.excludePackages = [pkgs.gnome-decoder] and have no references to the package anywhere else, but it still somehow keeps being added to my system, and I have no idea why or where. I've looked through the linked file in the NixOS package search, and it doesn't reference the package. GitHub search on the nixpkgs repo only shows commits and no code references to the package.
Here's the file on the commit fixing the package: https://github.com/NixOS/nixpkgs/blob/bcf8849a8144cd2dde13784e3de04d9b1e27cfb6/pkgs/applications/graphics/gnome-decoder/default.nix
Any idea what options enable this?
GNOME decoder is not installed by GNOME NixOS module so excludePackages will not work. In fact it is not really installed by anything by default. Are you sure you are not adding it somewhere? | 16:03:35 |
Jan Tojnar | you can use --show-trace to find the call chain | 16:04:01 |
Jan Tojnar | In reply to @redstone-menace:matrix.org I'm attempting to make an overlay, but I'm a noob with all the override methods and the package doesn't call stdenv.mkDerivation, but clangStdenv.mkDerivation, so I'm not sure how to make this work. My attempts so far have yielded errors with fixed-points, missing arguments, or wiping out the other packages in nixpkgs final: prev: { gnome-decoder = prev.gnome-decoder.overrideAttrs (attrs: { preBuild = ...; }); } should work asan overlay | 16:06:25 |
| @rkwq:matrix.org left the room. | 16:37:59 |
R̴̨͕͇͍̞̮̐̅͆̌̀̉̐͋̈́̃̀͒́̎̅̚̚̚͠͝Ĕ̵̡̛͖͖̟̙̫̱͈̘̞̭͍͍͑̌̄͑̓̋̓̀̈̏̈́͊̇͊͆̉͂̏̀̃̚͘͝͝ͅͅD̶̡̢͔̱̖̮͙͉̘̺͓͍̩̮͈͍͗̃̀̏͌͘͜ͅŚ̸̬̭̯̬͙͇͓̬̩̳̤͚͓̤̩̺͉͖̉͛̓̿̎͊̿̆́̐͂̇͌̄̇̓͘ͅͅT̴̞̫̘̝͇͔̟̪̪̦͂̔̎̀̎ͅŎ̷̡̬̹̪͈̭̣͈̭̭͉̦̖̝̘̪͖͔̥̦̘̻̳Ṋ̶̛̫͈̳̘͚̜̔̋͆̅̈́͊̑͊̉̌̈́̾͑̈́̚ͅË̸̡̨̨̛͇̜̖͔͖̻̟̗̠̙͓̘̗̥͉͇̜͑͆͊͑͑̀̓͒͜͝͝ | In reply to @jtojnar:matrix.org
final: prev: { gnome-decoder = prev.gnome-decoder.overrideAttrs (attrs: { preBuild = ...; }); } should work asan overlay Thanks! This worked when I added meta.broken = false to the attrset to override with. I could've sworn I tried this exact overlay, using arg names super and self, but I realized I accidentally reversed the order of the args at the beginning. | 20:03:36 |
R̴̨͕͇͍̞̮̐̅͆̌̀̉̐͋̈́̃̀͒́̎̅̚̚̚͠͝Ĕ̵̡̛͖͖̟̙̫̱͈̘̞̭͍͍͑̌̄͑̓̋̓̀̈̏̈́͊̇͊͆̉͂̏̀̃̚͘͝͝ͅͅD̶̡̢͔̱̖̮͙͉̘̺͓͍̩̮͈͍͗̃̀̏͌͘͜ͅŚ̸̬̭̯̬͙͇͓̬̩̳̤͚͓̤̩̺͉͖̉͛̓̿̎͊̿̆́̐͂̇͌̄̇̓͘ͅͅT̴̞̫̘̝͇͔̟̪̪̦͂̔̎̀̎ͅŎ̷̡̬̹̪͈̭̣͈̭̭͉̦̖̝̘̪͖͔̥̦̘̻̳Ṋ̶̛̫͈̳̘͚̜̔̋͆̅̈́͊̑͊̉̌̈́̾͑̈́̚ͅË̸̡̨̨̛͇̜̖͔͖̻̟̗̠̙͓̘̗̥͉͇̜͑͆͊͑͑̀̓͒͜͝͝ | In reply to @jtojnar:matrix.org GNOME decoder is not installed by GNOME NixOS module so excludePackages will not work. In fact it is not really installed by anything by default. Are you sure you are not adding it somewhere? ripgrep isn't finding any usage of it in my config. I figured there was some option I was unaware of that was adding it to environment.systemPackages or home.packages. | 20:10:31 |
R̴̨͕͇͍̞̮̐̅͆̌̀̉̐͋̈́̃̀͒́̎̅̚̚̚͠͝Ĕ̵̡̛͖͖̟̙̫̱͈̘̞̭͍͍͑̌̄͑̓̋̓̀̈̏̈́͊̇͊͆̉͂̏̀̃̚͘͝͝ͅͅD̶̡̢͔̱̖̮͙͉̘̺͓͍̩̮͈͍͗̃̀̏͌͘͜ͅŚ̸̬̭̯̬͙͇͓̬̩̳̤͚͓̤̩̺͉͖̉͛̓̿̎͊̿̆́̐͂̇͌̄̇̓͘ͅͅT̴̞̫̘̝͇͔̟̪̪̦͂̔̎̀̎ͅŎ̷̡̬̹̪͈̭̣͈̭̭͉̦̖̝̘̪͖͔̥̦̘̻̳Ṋ̶̛̫͈̳̘͚̜̔̋͆̅̈́͊̑͊̉̌̈́̾͑̈́̚ͅË̸̡̨̨̛͇̜̖͔͖̻̟̗̠̙͓̘̗̥͉͇̜͑͆͊͑͑̀̓͒͜͝͝ | In reply to @jtojnar:matrix.org you can use --show-trace to find the call chain I use this, but the output I get is almost always entirely comprised of a super long call chain through some libs/builtins and an entrypoint I already knew was part of the fault, but not enough context about scoping & option values to diagnose why that entrypoint is broken.
I'm new to functional stuff in any real capacity outside of some scheme for a college course, are these long call traces thru external code useful? I usually only can really follow a frame or two of it before it becomes basically a black box.
| 20:20:13 |
Jan Tojnar | redstone-menace: they should point you to useful place | 20:33:32 |
Jan Tojnar | * redstone-menace: the traces should point you to useful place | 20:33:39 |
Jan Tojnar | but it might be hidden amid the noise | 20:33:51 |
| 1 Apr 2023 |
| kadawee joined the room. | 13:42:01 |
| 5 Apr 2023 |
| zck joined the room. | 01:12:58 |
| @rimuru:gentoo.chat changed their profile picture. | 12:27:38 |
| 6 Apr 2023 |
Jan Tojnar | bobby285271: I would not block on the tracker issue, I do not think we support 32-bit platforms | 02:21:21 |