<bandali>btw, some feedback regarding the installer: it'd be nice if the user had the ability to edit the configuration shown to them right before the install, in case they want to make any manual small tweaks before proceeding
<civodul>g_bor[m]: yes, you have to use ssh forwarding
<bandali>hey folks, anyone know if it's possible to have guix/gruix prompt for luks password only once?
<bandali>i *think* trying the installer i'd noticed it happening, but i'm not sure
<lfam>bandali: It's an old user experience bug with a Guix-specific reason. I can't remember the exact reason but if you search the archives of guix-devel, bug-guix, and help-guix you will definitely find discussion
<bandali>lfam, ha, i found something from a couple years ago, but wasn't sure if it's still relevant
<bandali>especially since i *think* i'd seen the installer wizard take care of it
<efraim>recursive importer doesn't see the packaged crates, probably because they're hidden
<Franciman>efraim, I was thinking about what you said regarding Cargo.lock
<Franciman>if a package has a Cargo.lock, isn't it enough to provide reproducibility?
<efraim>we have to provide the crates for the build, and if there are any scripts we patch them. With that we necessarily change the hash and have to recompute it. Plus there's everything else in the build environment, not just the crates
<davie`>hi! Anyone knows is there a way to quickly install package using `guix package --install-from-file=` if it has inputs that are not defined in any channel?
<davie`>I could do a local channel with `define-global` package definitions but `guix pull` takes a bit too long for debugging
<roptat>davie`, you could define these additional inputs in the file you're installing from
<roptat>or use -L to load more definitions from a directory
<TheZeus121>davie`: You can make a local channel with all that but instead of commiting and then `guix pull` use something like `guix environment -L <path to channel> --ad-hoc <package name>`
<Parra>hey guys I'm trying to run a cmake build script from Guix, but my cmake script does things like npm install during the build step, so this is problematic with guix, because npm install needs root permissions it seems... I've tried to use node-build-stystem but I don't have any example, what can I do? It's being frustrating
<TheZeus121>Parra: I'm not familiar with npm, does `npm install` installs dependencies or some part of your package during the build?
<TheZeus121>If it installs dependencies you should be able to remove `npm install` from CMake and list the dependencies in package inputs
<Parra>yes, my cmake file just does: execute_process("npm install ..")
<Parra>that was my original idea but I can't find an example of guix using a npm dependency, do you have an example?
<roptat>Parra, the actual issue with your cmake file is that npm install requires network access, which we don't have in the build environment
<Parra>not only that, also the root access to do mkdir in some temp.folders
<roptat>now, the npm package is probably going to be extremely hard to package (because usually npm packages have a huge number of dependencies, and we still have none of them)
<Parra>someone told me that there is a workaround around that too, because I want to install .NET Core runtime from curl-ing a sh script
<Parra>rotpat: it isn't because it's node-addon-api
<bandali>also if not, would y'all consider making one or the other available in the installation iso?
<bandali>it'd be convenient for retrieving my config.scm, at least
<roptat>when building a standard derivation, guix wants to maximize the chances that it's reproducible, so it builds in a container with exactly the defined inputs and no network access
<roptat>network access is only granted if you build a fixed-output derivation, in which case you have to know what will be downloaded in advance
<davie`>roptat: Thanks! Ill check out the -L option. You also mentioned that I could define additional inputs in the file. I've tried that but failed.. It seems like i can't just substitute input field with a package like (native-inputs `("some-package" ,(package (name "some-package") ...))
<roptat>bandali, oh wait I thought you were talking about the install phase of the building process, not the installer!
<Parra>python backend already works, I should try to build the nodejs frontend now
<Parra>(aka the node port which offers metacall to node world)
<Parra>vagrantc: it's not a big deal, 3.5h with car, 2h with ave
<pkill9>does anyone get message slike this when trying to play music with "lollypop": `(lollypop:4341): GStreamer-WARNING **: 14:25:54.570: Failed to load plugin '/run/current-system/profile/lib/gstreamer-1.0/libgstreplaygain.so': /gnu/store/h90vnqw0nwd0hhm1l5dgxsdrigddfmq4-glibc-2.28/lib/libm.so.6: version `GLIBC_2.29' not found (required by /run/current-system/profile/lib/gstreamer-1.0/libgstreplaygain.so)`
<PotentialUser-13>Hi, I'm following the video tutorials on the website to add new packages to guix. I have followed the instructions for Part One, but in part two, the video uses guix without ./pre-inst-env to guix import cran aspi, I cannot use these after following Part One, nor can I use git to switch over to a new branch in the repo
<PotentialUser-13>My guess is that I'm in an environment that only has the packages I specified with guix environment, but I still don't get why the video does not explain well in Part Two how to follow the steps over from Part One if we're on a guix environment
<nomr>Qt5 isn't working for me on a foreign distro, due to being unable to find libQt5Core.so.5, which is in my profile lib path which is $LIBRARY_PATH
<nomr>I tried setting LD_LIBRARY_PATH to the same value, but then everything segfaults on launch 0_0
<roptat>basically, they divide documentation into four parts: tutorials, how-tos, explanations and reference
<roptat>that's two dimensions: either theoretical or practical, and either work-oriented or study-oriented
<PotentialUser-13>They don't transition well between parts -- part one talks about setting guix environment but part two doesn't mention how this connects to part one, it only starts using guix import right away
<nomr>(ok ... it is because libQt5Core.so.5 from qtbase-5.11.3 uses ABI 3.16 and I am running linux 3.3.8. other stuff is ABI 2.6.32. hard problem to diagnose, got lucky)
<roptat>I'd like to suggest a change to the cookbook to put everything in one of the first three categories, instead of having everything ordered by topic
<roptat>so the cookbook would start with tutorials (tutorial on guix installation, tutorial on the guix system, tutorial on scheme, on packaging), then with how-tos (guides on advanced uses of the package manager, on how to configure certain things on the guix system, on how to package) and finally with more theoretical discussions and explanations about guix (what is a derivation, how do generations work, etc)