<nckx>…what even is a .guixrc? Everything that rekado_ says is true. Anyway, here's the relevant snippet from my configuration: <http://paste.debian.net/1100175/>. If you use %base-services or equivalent (which is likely), I suspect you'll have to use modify-services too, dunno.
<montxero>nckx: I am using guix in a forigen distro, (essentially as a package manager). The purpose of the guixrc is to have a place where I can manage things like path modifications when certain packages are installed
<nckx>montxero: On a foreign distro you'll have to edit your foreign guix-daemon service (probably /etc/systemd/system/guix-something). You can just add --substitute-urls='…' there. I can assure you: that works.
<nckx>Hm. I don't know how fussy guix-daemon is about ‘=’ vs. ’ ’.
<montxero>nckx: For me, it just freezes up `# guix-daemon --build-users-group=build --substitute-urls=the-urls` just sits freezes up
<gnu_srs1>quiliro: I know a lot about Hurd, what did make you believe the opposite?
<rekado>montxero: there are three problems: mirror.hydra.gnu.org no longer exists; berlin.guixsd.org and ci.guix.info are now just ci.guix.gnu.org (which is the default); you wrote “https//:” instead of “https://”.
<rekado>montxero: I’d also recommend against setting all these environment variables.
<gnu_srs1>civodul: I've read the whole manual already. Time to read it again. I have not reached the threshold where things are easy yet.
<rekado>gnu_srs1: downloading/building packages happens later. Do you have a copy of the Guix source tree yet?
<rekado>If you want to change the Hurd port you’ll need it.
<numerobis>Hi #guix! I get an error when installing hypre-openmpi, see http://paste.debian.net/1100233/ . I have three questions related to this: 1) Is there a way to fix this bug? 2) Is there a website where a list of packages that do not currently build is maintained? 3) For a given package, how do I check whether substitutes are available? (I think someone here told me how to do this before, but I forgot, sorry)
<gnu_srs1>I have it on a Debian GNU/Hurd image, but here I'd need it within the Guix image on Linux gnu 5.2.9-gnu #1 SMP 1 x86_64 GNU/Linux
<roptat>numerobis, for 3, you can try to use guix weather
<rekado>numerobis: 1) yes! xy.sty is provided by the texlive-xypic package, which would need to be part of the build environment; 2) ci.guix.gnu.org lists all builds
<rekado>sirmacik1: is “guile” installed into your personal profile?
<rekado>sirmacik1: Guix sets up environment variables automatically when a package that “manages” the environment variable is installed into a profile. In the case of GUILE_LOAD_PATH that’s the “guile” package.
<sneek>apteryx, leungbk says: the update to python-jedi 0.15.1 is not compatible with Guix's current of python-language-server, which expects python-jedi < 0.15. Please review my patch for python-language-server. Thanks.
<civodul>i may have a fix for icecat's tz issue, in icu4c
<civodul>funny thing: we use zimbra at work and in icecat it thinks i live in UTC
<civodul>so if i don't pay attention, i go two meetings two hours ahead of time
<apteryx>civodul: this is because of tracking protection is enabled
<apteryx>if you disable this, you'll see the actual time
<apteryx>I had the same problem (we use zimbra at work too!)
<apteryx>(in retrospect I think this was in Mattermost, not Zimbra -- I don't remember if it applied to Zimbra also)
<apteryx>rekado:pathpy is another thing, so it's confusing
<apteryx>and guix import pypi pathpy import that wrong thing; path.py imports the correct package.
<rekado>apteryx: it should be called python-path-py
<bgardner>Good morning guix, I'm trying to set up an apache instance with a virtualhost definition. I'm following the docs but getting errors. I think the issue is that for httpd-virtualhost entries it says "These should be added to the extra-config for the httpd-service." but I may be doing the "adding" wrong. Can anyone point me to a sample configuration block?
<apteryx>rekado: our packaging guideline only mentions to transform underscore to hyphens, not dots... can't we use python-path.py, given that Scheme doesn't restrict us to do so?
<apteryx>but I don't feel strongly; I just think that's it neat if we can stick to upstream names when it's feasible.
<roptat>we already have lots of go-github.com-* packages :)
<rekado>lots of matplotlib tests fail because of insignificant differences in the generated PNGs :-/
<civodul>apteryx: oh really? how did you disable that?
<apteryx>(answer: yeah, pretty much broken everywhere :-)
<apteryx>the interesting twist is I can't find any reference to importlib_metadata in python-pytest-shutil sources, yet it fails looking for it (probably through a propagated dep -- something else must be broken).
<civodul>efraim: 127 is usually (but not necessarily) "file not found"
<civodul>vagrantc: note that download.savannah.gnu.org redirects to a nearby mirror, so it's not deterministic
<vagrantc>well, only because you pointed to an example i could maybe steal :)
<apteryx>OK, found the culprit: grep -rin importlib_metadata /gnu/store/j67rzvp32lc7j6sdivm62i20ch48ysvi-profile/lib/python3.7/site-packages/* --> /gnu/store/j67rzvp32lc7j6sdivm62i20ch48ysvi-profile/lib/python3.7/site-packages/path.py-11.5.0-py3.7.egg-info/requires.txt:1:importlib_metadata>=0.5
<quiliro>every time i reconfigure since about a week, I have this message at the end:
<quiliro>guix system: bootloader successfully installed on '/dev/sda'
<nckx>It's not that clean in practice; many packages (CUPS is a good example of both) either store ‘state’ (like timestamps!) that should be in /var in /etc, and/or treat settings in /etc as mutable through their UI, neither of which jive well with Guix's model.
<nckx>It's simple if you ignore the complications 😛
<quiliro>I have a problem with my locales since a week ago when I did guix pull and guix upgrade...I have done them a moment ago. The problem persists.
<efraim>ng0: using 'crate build --verbose' i was able to copy and hand-craft a rust package to use a previous package's .rlib and run the tests, but I don't think it's sustainable unless I can figure out how to point it to a list of directories.
<kmicu>Formbi: roptat (guix-home-manager’s creator) had some ideas for escape hatches. In my mind partial reproducibility is like being partially pregnant.
<Formbi>why should someone make a shitload of symlinks to configs of unmanaged programs?
<kmicu>To have a rock-solid eternal, immutable, reproducible environment.
<Formbi>you can have a full reproducibility in one place and not in the other
<Formbi>and you can have things like Emacs config on git
<kmicu>Not really, my Emacs touches to many places.
<kmicu>home-manager is opt-in so there’s no issue I think.
<g_bor[m]><Formbi "why should someone make a shitlo"> Formbi: guix home manager is implemented along the lines of that philosopy. It is not the only way to do this, it is one way. I believe the semantics you are after could also be implemented by some other software. Wdyt?
<Formbi>but when you opt in, you have to make a lot of exceptions?
<Formbi>couldn't there be just a switch to enable the opposite way?
<kmicu>Yes. It’s the same way as opting in into Guix.
<rekahsoft>NixOs has `nixos-generate-config`, however I have not seen a similar facility for guix. Furthermore, how do folks keep abstract away hardware details/configuration with guix so that a config can be easily applied across machines?
<rekahsoft>Also thanks to Formbi for pointing out Guix Home Manager (GHM as he abbreviated it). Looks pretty fresh still. Would love to see something like this get into guix/guixsd.
*kmicu was referring to btrfs. guix-home-manager is immutable and invincible already.
<rekahsoft>oops. My mistake kmicu. btrfs is great, however my preferred setup is LUKS + LVM where within LVM I have a root and swap partition. The root partition is btrfs and split in subvolumes. I can't yet do this with Guix, but am still working on switching over my main system.
<erudition>I as someone using apt all the time I often have to wait for all the "triggers" to run, after the package had been already installed, before I can get control back and run another command. Is there a similar thing when installing guix packages? Because I kinda assumed that's what you were talking about
<rekado>whenever a package is installed (or removed) Guix builds a new profile generation.
<rekado>when all packages have been built and the union directory has been assembled the profile hooks are executed.
<erudition>Of course, if the very next command I run is "man <thing I just installed>" then the page might be missing, but otherwise I feel like it could be non-blocking
<rekado>and they add stuff to the profile generation.
<erudition>rekado: hmm, yeah I guess that model kinda means everything must be totally blocking