<lfam>shoaloak: Those lines are used to import other files of code. (gnu system nss) is the module used by GuixSD for the Name Service Switch functionality. The module name (gnu system nss) corresponds to the filesystem path gnu/system/nss.scm in a copy of the Guix source code
<mbakke>shoaloak: I think it should be (use-modules (gnu) (gnu system nss)), which simply means load "gnu.scm" and load "gnu/system/nss.scm".
<mbakke>lfam: (guix utils) need to be imported in the builder. But, that will change all users of meson-build-system. So I'll revert it for now.
<swiftgeek>what i can say additionally is that some kind of kcmdline option is required for passing location of squashfs image
<swiftgeek>then it can nicely fit with everything else out there
<swiftgeek>but again since i'm not an user i can't propose anything
<swiftgeek> --root=31393730-3031-3031-3139-343131363739 --system=/gnu/store/1adnfzni8i9zbn4fjabwr82b01fpk352-system --load=/gnu/store/1adnfzni8i9zbn4fjabwr82b01fpk352-system/boot # looks as alien as it gets to me
<voronovank>hi! I'm an applicant for outreachy program and I have some problem with guix. I'm trying to add "dropbox" package. I've got package definition by "guix import pypi", but apparently it requires "pytest-runner" and when I'm trying to get its definition by "guix import pypi pytest-runner" I get this -- https://paste.debian.net/1015661/. And right now if I'm trying to "guix import pypi dropbox" I also get something similar. I'm definitely doing something
<voronovank>wrong but I can't figure out what exactly and I'll be grateful for help!
<efraim>it has to do with the certificate, there's something in the manual about X.509 certificates
<wxie>civodul: I do understand that, but is guixSD iso a problem for booting?
<rekado>grafoo: you can define a package variant. If you want to use it as a dependency throughout the package graph, you will need to rebuild dependent packages though. It’s possible with the package-input-rewriting facility.
<nee``>I removed a bunch of services from my config, ran reconfigure, readded some and made a new reconfigure. Now some of the service user-accounts have different UIDs and can no longer access their old files, so the services fail to start. I manually reset some UIDs and GIDs, but mariadb still fails to start.
<mbakke>nee``: That's terrible. Can you file a bug report?
<nee``>I haven't checked if it's completely reproducable, yet. It took me some time to realize the UIDs changed. I assume users get removed when there are no references to them?
<mbakke>nee``: Yes, "service users" get removed when they are no longer needed.
<mbakke>NixOS have dedicated user IDs for each service, maybe we'll need to employ something similar.
<thorwil>so now my build fails with: module not found "xts.ko". but i have Cryptographic API: -*- XTS support
<thorwil>i.e. it's fixed on Yes. if that isn't the option tied to xst.ko, i have a hard time finding any hint
<g_bor>I'm preparing two patches now, and I have questions about how to divide them up, and how to parse the commit message.
<thorwil>most surprising of that list of modules (or kernel features?) guix expects was hid-apple
<g_bor>One of those is a refactoring. Do we use refactoring terminology there, like extract function from module to module, and like or just like we do with any other patch: delete variable from module 1, module 2 new variable?
<g_bor>The other patch adds the same native input to over 50 packages. Should that be a series of 50 patches, with the usual commit messages broken up by package, or is there any other way to create that, and still be acceptable? Usual policy demands to patch one package at a time if I get it right...
<efraim>I did one per package for source-file-name, but it could go either way
<bavier`>g_bor: factoring terminology is fine. you'll see commit logs like "* file.scm (foo): move to ...\\n* file2.scm: ... here."
<mbakke>efraim: Can you also/instead try the updated patch sent recently?
<rekado>vvedantham: oh, you know, this could be a problem of the guix-daemon’s environment.
<vvedantham>rekado: just doing an unset without the export gives me guile: warning: failed to install locale warning: failed to install locale: Invalid argument substitute: guile: warning: failed to install locale substitute: warning: failed to install locale: Invalid argument bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8): No such file or directory
<vvedantham>rekado: I simply rebooted after the install script and tried "guix package -i hello" and that gave some results. Doing guix-daemon --build-users-group=guixbuild now says "guix-daemon: command not found"
<rekado>vvedantham: that’s okay. “guix-daemon” is not in your environment.
<nckx>‘Selects’ are distinct from ‘depends’, and are declared by the selecting symbol. I think the output above is about as close as the Kconfig system comes to listing them sanely. It's all very... suboptimal.
<nckx>Usually it's pretty easy to parse once you learn the precedence, but I can't make head nor tail of yours. :-/