<darkpsi>hey guys if anyone can help me there seems to be a bug with nvme the new linux kernel (4.16.1) has the nvme drivers compiled in to the kernel and when i guix reconfigure it ither demands that i put load nvme on the initramfs or if i have done that it will say it can not find nvme.ko as it does not exist. so what would be the best way to sort this problem i could ither edit the kernel config or disable the
<darkpsi>nvme check if any one can help that would be great
<zybell_>There should be a file /sys/class/nvm... or similar that exist in *earlier* kernels only if nvme.ko is loaded. It would exist in 4.16.1 anyway. Extend the test to look for that file, and if lsmod says no module in and file exist goto no module needed.
<OriansJ>pkill9: I'm pretty sure it is in vim-full
<thomassgn>what is the difference between guix environment --root=./.dev --ad-hoc gcc and guix package -p dev -i gcc? I'm trying to get an environment where I can choose to enter and work without internet connection, separate from my system state
<thomassgn>another entry to the same question would be, what is the difference between a profile and a gc-root?
<pkill9>do you mean the difference between a profile and a guix environment?
<pkill9>a gc-root is basically just a symlink that tells the Guix garbage collector not to delete anything inside it/anything that is linked from inside it
<thomassgn>I mean , the root from guix environment looks, to me, identical to the guix package profile
<atw>thomassgn: your "guix environment" invocation includes a --root, so I think that either command will yield a profile. Either will accomplish your goal of a GC-safe set of packages available while offline. I think that "guix environment --root=..." will save you the trouble of naming the environment (contrast "guix package -p <name>"). Personally, I'm aiming for a setup where I can run "cd <project> && guix environment --root=profile
<beneroth>I guess my use case is a bit away from the usual one with guix. I'd look to have an universal package manager able to run with independent decentralized repositories, e.g. to publish/deploy my own software packages. I'm trying to find out if Guix would be the tool for this.
<beneroth>so the point is less about the securing of one central repo but how to ensure/check if a certain piece of software (possibly source code to build locally) really is from the author/distributor I trust or not
***Piece_Maker is now known as Acou_Bass
<mbakke>beneroth: I think Guix supports that case well.
<mbakke>Currently juggling multiple repositories is somewhat primitive, but there is a "channels" facility planned.
<zybell_>beneroth:That use case is what git was written for
<mbakke>Guix is inherently "trustless", everything is (and can be independently) built from a small set of "bootstrap binaries", but we're trying to get rid of those too. And you can easily fork the code and create your own distribution, with your own bootstrap binaries.
<mbakke>Many users don't use our binary substitutes at all.
<mbakke>Substitutes are also cryptographically signed and it's easy to run your own substitute server (see `guix publish`).
<beneroth>interesting. though I'm not pondering about the substitutes alone - I think it would be a good idea to be able to verify that a certain source code file is signed by its author (tampering would invalidate the signature).
<userr>The game may also be purchased through the digital distribution outlets Steam or GOG. The game's TE4 game engine source code is under a GNU GPLv3 license, the game's assets are licensed for use "with the Tales of Maj'Eyal game only."
<JorgeMorais>Hi. I use Debian buster on my workstation and Ubuntu 16.04.4 (preinstalled) on my personal laptop (I intend to later migrate it to Debian, which better respects libre software ethics). In the workstation, I have installed afew (version 1.3) and notmuch via the Debian repositories. In the laptop I have installed notmuch 0.26.1 though Guix. Now I want to install afew on the laptop, but it is missing on Ubuntu repositories, and in G
<JorgeMorais>it is version 1.2. Guix's recipe for afew seems not to apply any patch; and while I don't know Scheme or Guix's API, the recipe is quite short and apparently simple. Therefore it seems safe to "blindly" transform it into a 1.3 recipe, right? How exactly would I do that?